- This topic has 6 replies, 2 voices, and was last updated 5 years, 4 months ago by .
-
Posts
-
I’m trying to patch our BP server itself and continually get “Error 1611: 5 Failure”
Could not find file ‘\**********C$Program FilesBatchPatchBatchPatchTempResult.log’.
The 5 indicates some level of access_denied / permissions issue. First make sure you have launched BP elevated as admin. You can only use it to patch the local host if it’s running elevated. Next make sure that you don’t have some type of antivirus or host intrusion prevention or other security related app on the system that could be blocking access or preventing psexec from working properly. You might also try ‘Tools > Remote Execution > Use PsExec -r switch to specify remote service name’ and then enter something like BatchPatchExeSvc there.
The licensing wouldn’t have anything to do with it. Under typical circumstances what you are doing should work fine. It seems like there is some type of weird permissions blockage somehow in your environment. It’s also possible that SEP is treating things differently when the source is also the target.
What happens if you try BP from a different source computer but with this same computer as the target?
Might also be interesting to try running as a different local admin user on the same computer instead of a domain admin that is a member of the local admins group. You could try defining a local admin user on the BP computer, then log on to the computer as that user and see what happens when trying to patch the local host.
The default method used for reboots in a “download and install” operation (WMI) cannot reboot the local system. Windows won’t allow it. The ‘Privilege not held’ message is expected. You c instead use the ‘Reboot (shutdown.exe /r /f /t 0)’ method. This is available under the reboot menu item in BP or can be called from a job queue or task scheduler. However, realistically it’s not a great idea to use BP to reboot the local host because then it’s going to kill the BP instance, and any actions that are running in BP against other target computers will be orphaned or killed.
You can specify alternate credentials for any row under ‘Actions > Specify alternate logon credentials’
- You must be logged in to reply to this topic.