WMI issues on Discovery of workstations

cyked
Mega Guru

I read trough this thread. WMI issues on Discovery of workstations

finding something of a similar issue with windows discovery, although its a way more widespread issue for workstations I have seem similar results on win servers.

We have a huge volume of machines failing classification because of the WMI failure, with this error.

Authentication failure with the local MID server service credential.

</error>

<error>

Failed to access target system. Please check credentials and firewall settings on the target system to ensure accessibility: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

Anyone seeing something similar in the past few months?   with maybe the culprit being patching or something group policy related?   I've looked through my machine and used it for some testing, the windows firewall OFF.   So that shouldn't be the issue.

Another bit to note.   I was doing to some heavy repeated discovery on 2 laptops this morning ironing out some proposed changes for model management using field normalization.   I ran discovery on these two laptops over and over again. At least 5 times, without issue.   For some reason it stopped working.   I have machines that were discovered as recently as this morning, and now running a quick discovery FAILS.

1 ACCEPTED SOLUTION

Ended up being GP issues.   The EUC teams have been doing some cleanup of local admin policies and domain admins went wonky (domain admins was not being included in local admins - our discovery account for windows is part of domain admins).   They fixed the issue and permissions began propagating correctly and everything is looking good.   Just in time for SCCM integration!


View solution in original post

4 REPLIES 4

doug_schulze
ServiceNow Employee
ServiceNow Employee

Drew,



Can you run WMIC command from the midserver to the hosts to validate if the credentials still work?




wmic /node:"10.0.0.1" /user:"domain\user" /password:"password" path win32_operatingsystem


Ended up being GP issues.   The EUC teams have been doing some cleanup of local admin policies and domain admins went wonky (domain admins was not being included in local admins - our discovery account for windows is part of domain admins).   They fixed the issue and permissions began propagating correctly and everything is looking good.   Just in time for SCCM integration!


Doug- I'm getting this error but I am successfully able to run the WMIC command from the MID to the target.  Any other tips?

Try deleting your credential in servicenow then re-adding (if you haven't done that already)