You can do this just by launching 'regedit /s regfile.reg'
The issue arises when this reg file contains information for the current user section of the registry as local system can't do that. In those cases you need to launch it as the logged on user either within the proprties of your distribution job or using something like 'runas'.
anyone know how to invoke RUNAS for a particular action using provisioning tasks?
I had a previous post about using "elevated priveledges" here:
folks educated me in that provisioning uses the local system account, something I didn't know for sure. They went on to say that this account has full admin rights to the local machine only. In this case I'm currious why an account with "full" admin rights can't modify the CU side of the registry? Whatever.
I guess I'd really like to know how to invoke the RUNAS option via provisioning so that an author of a provisioning task can inject elevated credentials where needed to work around the local system account limitations. It seems pretty simple to me that it would be possible; after all landesk does allow an author to enter user credentials for mapping drives/connecting to a resource. Why not expand this into other provisioning actions?
any thoughts as to how to go about this?
an ER on the subject:
If it's for the current user, then you can always run the regedit command by launching it via startasuser.exe.
ldclient\startasuser.exe ///timeout=300 ///silent regedit.exe /s file.reg