- This topic has 6 replies, 3 voices, and was last updated 4 years, 3 months ago by .
-
Posts
-
Hello,
I have this error… I read some solutions on batchpatch tutorials… in those PC’s when I put the IP instead by PC name, it works!
how can i do??
thx!
If the IP works but name does not work, it could be an issue with your DNS.
However, you need to look at the *reason* that is printed at the end of the error message to evaluate why the error occurred in the first place. When error 1601 appears it says *what* happened: “Failed to retrieve WMI info”, and then immediately after that it says *why* it happened. For example, here are just two of the possible ways it might appear:
Error 1601: Failed to retrieve WMI info: Access is denied (Exception from HRESULT: 0x80070005)OR like this:
Error 1601: Failed to retrieve WMI info. The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)See section on “RPC server is unavailable” here: Troubleshooting Common Errors in BatchPatch
I have a similar issue : after upgrading the pc to Windows 10 2004 BP is not able to see the pc anymore. I have 50 new laptops, all have the same issue : when they are connected to the internal network, BP works fine. When they are connected via Direct Access, BP is not able to see them anymore. There are no changes to any GPO’s so I expect it to be a new feature in the 2004-release. Any ideas ?
If they are fine when connected to the LAN and are only not working when using DirectAccess, then it seems pretty clear that the issue is with your DirectAccess configuration. I don’t have experience with DirectAccess, so I’m not able to provide much guidance, but based on some very quick and minimal research it appears you have to configure “Manage Out” capability for DirectAccess in order to be able to remotely manage clients from within the LAN. I wouldn’t be surprised if you also have to configure firewall rules specifically for when using DirectAccess.
- You must be logged in to reply to this topic.