- This topic has 6 replies, 2 voices, and was last updated 9 years, 2 months ago by .
-
Posts
-
Hi Matt – BatchPatch always executes remote commands in the SYSTEM account, which has the highest possible privileges. You should not need to add anything extra. However, if you want, PsExec also supports the -h parameter, which is supposed to elevate when possible. In BatchPatch Remote Commands 1 and 2 support PsExec switches, so you could include -h before any subsequent command. However, like I said, this really should not be necessary. I suspect it would not do anything anyway since the SYSTEM account already has complete system access with no UAC prompts.
-Doug
I’m not sure if you’re saying that it’s not working, or if it’s not working what the error is or isn’t…
However, my recommendation would be to just use the Deployment feature to deploy the .bat. ‘Actions > Deploy’ instead of ‘Actions > Remote Command.’ Then you don’t need to figure anything out. Just select your .bat, add the “install” parameter, and then let BatchPatch handle copying it to the targets and executing it with the proper syntax.
-Doug
Put the .bat plus all other files in a folder. Make sure the .bat file is using relative file references, not absolute paths, so that when the .bat is executed, it finds the other files in the same dir that it is executed from. Then in the Deployment window choose the option to “Copy entire directory contents.” There is an tutorial of this type of script deployment with multiple referenced files here: Install Multiple .MSU Files with a script
-Doug
- You must be logged in to reply to this topic.