- This topic has 1 reply, 2 voices, and was last updated 5 years, 10 months ago by .
-
Posts
-
I’m having issues connecting BatchPatch to Server 2016 servers in my domain.
Error 1601: Failed to retrieve WMI info. Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
I don’t think it’s actually a permissions issue. I am able to connect and run commands on Server 2012 R2 servers on the same subnet, same domain, same account, same permissions. I have also tried creating a local admin account with the same results. I’ve also confirmed RPC, WMI are running, etc.
This appears to be something specific to Server 2016 in my environment. Any suggestions?
It’s pretty much gotta somehow be related to permissions/authentication. Microsoft is not ambiguous about access denied errors, and we have not ever heard of an access denied error that didn’t have something to do with the machine denying access due to something relating to permissions. That said, I can also tell you that a normal installation of 2016 behaves just the same as a normal installation of 2012 in terms of having no issues using BP and WMI. We have many customers using 2016 without issues, and we have no issues with 2016 and BP internally here. All that said, I would suggest you start with the link below. Please go through it carefully and make any necessary changes. Additionally please note that testing with a local account does not create an apples/apples situation because local account authentication requires additional registry modification on the target, as described toward the bottom of the link.
batchpatch-authentication-in-domain-and-workgroup-non-domain-environments
If you continue to have trouble after that I would refer you to Microsoft’s WMI troubleshooting page.
More here:
https://batchpatch.com/troubleshooting-common-errors-in-batchpatch
- You must be logged in to reply to this topic.