The purpose of this document is to provide steps for testing the local SYSTEM account permissions in the event a custom action or patch has not been deployed to ensure this account has the appropriate permissions.
The custom action and/or patches being deployed through Shavlik Protect do not appear to kick off or install.
1. In order to test the SYSTEM account, you will first need to download PsExec from Microsoft using the following link : http://live.sysinternals.com/psexec.exe. Please save this .exe to the root of the C: drive on the target machine.
Note: PsExec is a Microsoft tool that will allow you to test the SYSTEM account while logged on using your current credentials.
2. On the target machine, open a command prompt and navigate to the directory housing psexec.exe, which should be the root of C: based upon Step 1.
3. Within the command prompt type in the command psexec.exe -i -s cmd.exe and hit 'Enter'. This will launch a separate command prompt using the SYSTEM account.
4. Within the new command prompt window, navigate to the C:\Windows\ProPatches\Patches or the C:\Windows\ProPatches\Install directory and attempt to launch the patch file or custom action using the SYSTEM command prompt.
Note: Patches can be tested from the C:\Windows\ProPatches\Patches directory while custom actions will be tested from the C:\Windows\ProPatches\Install directory.
5. If any errors or inconsistencies are seen when launching the patch or custom action we would suggest checking to ensure the SYSTEM account privileges have not been altered. In the event the issue persists we suggest reaching our Microsoft as they would be the best resource to correct issues regarding the SYSTEM account.
Additional Information regarding PsExec can be found here: PsExec
Shavlik Protect 9.x