After updating Windows 10 , Batchpatch reported to me the PC access was denied.

BatchPatch Forums Home Forums BatchPatch Support Forum After updating Windows 10 , Batchpatch reported to me the PC access was denied.

  • This topic has 6 replies, 2 voices, and was last updated 3 years ago by Matrixgp.
Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #13150
    Matrixgp
    Participant

    After updating Windows 10-20H2 , Batchpatch reported to me the PC access was denied.
    Before the update, it was on PC version 1809 and I could control the PC via BatchPatch (I had the firewall turned off, the RPC service is running), but as I ran the update on 20H2, I lost control of this PC, while the firewall is completely turned off (local , private and domain) RPC service is running. I still have Administrator rights, but whenever I want to send anything via BatchPatch, or send any query, it will write “Access would be denied”

    #13151
    doug
    Moderator

    “Access denied” indicates that there is a permissions or authentication problem of some kind. We have not ever seen nor heard of any issues that are specifically tied to upgrading to 20H2, so I would suggest you simply re-go-over the permissions/requirements, and make sure everything is in place for that particular computer.

    https://batchpatch.com/batchpatch-authentication-in-domain-and-workgroup-non-domain-environments

    https://batchpatch.com/getting-started-with-batchpatch

    https://batchpatch.com/troubleshooting-common-errors-in-batchpatch

    https://msdn.microsoft.com/en-us/library/aa394603%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396

    -Doug

    #13152
    Matrixgp
    Participant

    Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
    It doesn’t show me this error. Everything is set as it should. Everything worked before the client was updated.
    Obr.1

    #13153
    Matrixgp
    Participant

    PC-B3-11 has 1809 version and is OK, it can be seen in the picture, now I will upgrade to version 20H2
    Obr1

    #13154
    Matrixgp
    Participant

    Now the upgrade 20H2 is installed and it is not possible to connect to the client, while the firewall is turned off, I checked everything, according to the attached links. So I don’t know where to look anymore.
    Obr2

    #13155
    doug
    Moderator

    I understand what you’re saying. It’s not clear to me why you would see a change after upgrading, as we have not observed that before, and Windows shouldn’t be making modifications that would lock you out. However, with Windows anything is possible. Even including a bug in the particular build of 20H2 that you have installed. Regardless, BatchPatch didn’t change during the upgrade, the target computer changed. And ‘Access Denied’ is always a permissions/authentication issue of some kind. Specifically, the error you are encountering is occurring when BatchPatch attempts to make a WMI connection to the target computer. I would suggest that you try the following things:

    1. Log on to the target computer directly/manually with the same logon account that you are using to attempting to connect from BatchPatch. Just make sure that you’re able to log on successfully with the same username/password.

    2. Since you are using a local account (not a domain account), check the registry values described in the section titled ‘Using Alternate Credentials with a Local Account’ at https://batchpatch.com/batchpatch-authentication-in-domain-and-workgroup-non-domain-environments Make sure the necessary registry values were not removed/modified during the upgrade process

    3. Test out option 1 and option 2 instead of just option 3 at the following link to see if you experience different results: https://batchpatch.com/batchpatch-authentication-in-domain-and-workgroup-non-domain-environments Make sure the necessary registry values were not removed/modified during the upgrade process

    4. This link has some further WMI troubleshooting steps to try that are equally relevant for BatchPatch because in both cases it’s just a WMI connection that is being attempted, so it doesn’t matter if that WMI connection is being attempted from BatchPatch or from a different app, it’s still a WMI query being made in all cases: https://community.spiceworks.com/support/inventory/troubleshooting/advanced-wmi-issues

    5. If you have any type of anti-virus or HIPS or similar security app running on the target, check that too as a possible culprit. However, generally ‘Access Denied’ is virtually always something specific to Windows permissions/authentication

    6. See if you have the latest build of 20H2 or if there is an update available. You can manually/directly check for updates at the Windows Update control panel of the target computer

    #13156
    Matrixgp
    Participant

    Thanks, I’ll try to talk about it, it’s weird that it happened to me on these specific computers. I have 250 PCs under management and on some, where Windows 10 – 20H2 is already running, BatchPatch works, so I’m confused here.

Viewing 7 posts - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.