Access Denied

[DFSS]

Good Morning,

I am using BatchPatch on windows 11 PC, in a domain environment.

The remote PC ins windows 11 24H2, when I try an get MAC address or any other info from the remote PC I get access denied.

The user I am using is a member of the local administrators group on the remote PC, the firewall ports used by BP are open on the remote PC.

I can access info and batchpatch is working for other PCs in the same domain and same sub-net which are WIN11 23H2.

Only seems to be a issue with the 24H2 PC

Any suggestions please to resolve this.

[doug]

Is the user account a local account or a domain account? I’m guessing it’s a local account, in which case the resolution is you need to create a registry value on the target computer. That’s described here:

batchpatch-authentication-in-domain-and-workgroup-non-domain-environments

Alternatively, if you use a domain account you do not need the registry value but will need to ensure that the account credentials are correct.

[DFSS]

Yes it is a domain account, the domain account is in the local administrators group of the 24H2 PC, the credentials are correct because it works on the other 23H2 PCs

[doug]

Which Win 11 version is on the source computer?

[DFSS]

23H2

[doug]

Well… I’m not aware of any specific WMI authentication incompatibility issues for authentication between 23H2 and 24H2. However, we did see that occur some years ago with a particular version of Win 10, and it required both OSes to get upgraded to same version in order to resolve. In that case it was a bug in the OS, and Microsoft fixed it. Then we also saw something similar but not exactly the same a couple of years ago, which was a known behavior, and that’s desscribed in more detail here. I provide this for reference, not because I think it’s what’s going on in your case now:

access-is-denied-in-batchpatch-after-installing-the-june-2022-cumulative-windows-update

In your case I’d first try running BP as the actual user (right-click > run-as, or log on to the BP computer as that user), and then see if you can get it to work WITHOUT specifying alternate logon credentials (it won’t be necessary to specify alternate credentials because the app will already be running in the context of that user). If that doesn’t work, and there really isn’t any difference aside from OS version, then it seems to point to the next step maybe upgrading the BP machine to 24H2. However, realistically that shouldn’t be necessary, as I’m almost certain that we have patched from one to the other and vice versa with no issues, and we surely would have heard from other people encountering that if it were a widespread problem, so it’s pretty questionable what exactly is going on in your situation. Therefore I’d also point you to review the WMI troubleshooting links that are posted on this page:

troubleshooting-common-errors-in-batchpatch

[Author]

Posts