Validating Windows Credentials from the MID Server Using WMI<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Description This article explains how to validate Windows credential access outside of ServiceNow when Discovery fails due to credential or permission issues. Running a direct WMI query from the MID Server host helps determine whether the issue is environmental or ServiceNow-related. Issue Discovery fails against a specific Windows target even though it previously worked. In some cases, Discovery may succeed against one IP address while failing against another using the same credentials. Credential tests within ServiceNow may also fail for the affected target. Cause If basic WMI connectivity from the MID Server host to the target system fails, Discovery and orchestration activities will not succeed. This typically indicates that credentials are invalid, permissions have changed, firewall rules were updated, or WMI access is blocked on the target host. Resolution Before continuing troubleshooting within ServiceNow, validate Windows credential access directly from the MID Server host to the affected target using a PowerShell WMI query. Procedure Log in to the server where the MID Server is installed. Open a PowerShell command prompt. Run the following command: gwmi win32_operatingsystem -computer 192.168.200.14 -credential LOCALDOMAIN\mid Replace LOCALDOMAIN\mid with the Windows credential being tested. Replace 192.168.200.14 with the target IP address that is failing Discovery. Expected Result If the command is successful, output similar to the following will be returned: SystemDirectory C:\Windows\system32 Organization BuildNumber 6001 RegisteredUser Windows User SerialNumber 12345 OEM 1234567 12345 Version 6.0.6001 This confirms that the credential has sufficient permissions and that basic WMI connectivity from the MID Server to the target is working. Failure Result If the command fails, the credential is either incorrect or lacks the required permissions on the target system. In this case, the Windows administration team should investigate credential validity, permissions, firewall rules, and WMI configuration. Discovery and orchestration will not function until this basic connectivity issue is resolved. Additional Information This validation step should always be completed before escalating Discovery issues as product defects, as it confirms whether the failure exists outside of ServiceNow. Reference Windows Credential Test Using WMI https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0657528