Hi @csatish ,
1. Verify basic RPC connectivity
From the MID Server, confirm that RPC connectivity to the target server is working. WMI relies on RPC, so this must succeed.
Test-NetConnection <TARGET_IP> -Port 135
If this test fails, WMI will not work. Review network paths and firewall rules between the MID Server and the target system before continuing.
2. Test WMI from the MID Server
Log in to the MID Server, open PowerShell, and run the following command. When prompted, enter the same Windows credential used in ServiceNow Discovery.
$cred = Get-Credential gwmi Win32_OperatingSystem -ComputerName <TARGET_IP> -Credential $cred
Expected result: Operating system details are returned.
If this command fails, Discovery will fail in the same way.
3. Resolve failures when gwmi does not work
If the WMI command fails, follow these checks in order.
First, verify that the Windows Management Instrumentation service is running on the target server. If the service is stopped or unhealthy, WMI queries cannot succeed.
Get-Service Winmgmt
Restart the service if needed and retry the WMI command from the MID Server.
Next, validate credential permissions. The account used must have sufficient rights to access WMI remotely, typically local administrator access or explicit WMI permissions. Ensure you are testing with the same credential configured in Discovery.
If permissions are correct, review host-based firewall rules on the target server. Even if port 135 is reachable, blocked RPC communication can still cause WMI failures.
If this answers your question, please mark it as helpful and accept the solution for better community visibility.
Thanks,
Vishnu
