Running executable under 'System' account
Does anyone know of a way to run an executable in wise script and ensure it is run from the ‘System’ account when run? We need to deploy a package and have it run with the SYSTEM rights.
We cannot find a method to do this through SCCM 2007 either.
If anyone could help out it would be greatly appreciated.
Thanks,
Anthony
Run as system
Maybe there is an easier way, but what I've always done is used Sysinternals psexec. Run the following on the machine and it will run as the local system account:
Psexec.exe -i -s <executable>
AT Scheduler
The "AT" scheduler runs in system context, so you could try installing your executable on the machine and then setting up a task in the AT scheduler to run it a few minutes later.
SysInternal's psexec is also a very useful tool for this sort of install.
However, can we be nosy and ask what you are trying to achieve? Perhaps there is an alternative solution that we can suggest which would make this process easier to implement.
One final thing - the increasing security of operating systems such as Vista and Win 7 makes it more difficult to run stuff in the system context. So let us know which operating systems you are currently targetting.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
We are trying to install a
We are trying to install a plugin for Office Communicator Web, but it requires that UAC be turned off and it is, but when we try to execute this package it gives us an error message saying to either turn off UAC or run under the system account.
We have tried selecting 'Run with Administrative Rights' within the SCCM 2007 hoping it would override and use the SYSTEM account to install but without success, so i was trying to see what other alternative methods are available to achieve this task.
The "AT" scheduler workaround is not an option for us.
I will surely give the Psexec.exe utlity a try and see if that will work.
We are using Windows Vista Enterprise.
Thanks for all your help and suggestions.
Anthony
UAC needs a reboot?
Doesn't UAC need a reboot after being turned off?
Have you tried capturing what changes a successful install of the Office Communicator Web plugin makes to the local system?
I suspect there is a component that needs to install to the user profile, which SCCM cannot target.
If it happens to be an ActiveX control - have you checked if the antivirus is blocking the install?
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Our UAC is turned off on our
Our UAC is turned off on our image so that is not the cause. I have tried the PSEXEC program without success as it executed but we got the same result error message. The name of the program is "CWAPlugin.exe" it is an addon for Office Comunicator.
Which version of Office?
Have you checked that the CWA plugin is correct for your version of Office and also is compatible with Vista?
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Just checked turning off
Just checked turning off Mcafee services and got the same results.
Would you like to reply?
Login or Register to post your comment.