How to troubleshoot WMI and PowerShell issues on a remote machine for Windows Discovery - Support and Troubleshooting

How to troubleshoot WMI and PowerShell issues on a remote machine for Windows Discovery Issue .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } }  Troubleshoot WMI and PowerShell issues on a remote machine that may cause Windows Discovery to fail. This article provides steps to verify firewall settings, credentials, WMI configuration, remote PowerShell, and WMI permissions on the target machine.

Release .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } All supported releases

Resolution .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Discovery may fail to discover a remote machine due to a configuration issue on the target machine. Follow these steps to troubleshoot.

Note : Some of these steps take an aggressive approach but in most cases resolve the issue. Test these steps in a non-production environment first.

Step 1: Check for issues caused by Windows Firewall or RPC/DCOM Try disabling Windows Firewall to isolate the issue. If disabling the firewall resolves the issue, follow the steps in Opening ports in Windows Firewall for remote server access to configure the firewall correctly. Step 2: Verify that the MID Server credential can log in to the remote machine From a computer other than the MID Server, try to connect to the remote machine using the user account configured in the credential.

Step 3: Verify that WMI is correctly configured on the remote machine Verify that the WinRM service is running. Open a command prompt as an administrator and run the following command: winrm quickconfig Open a PowerShell session as an administrator and run the following command: Enable-PSRemoting -Force Step 4: Enable and configure remote PowerShell on the remote machine Right-click the PowerShell icon and select Run as administrator . Check the current script execution policy by running the following command: Get-ExecutionPolicy PowerShell returns a value of Restricted. Change the script execution policy by running the following command: Set-ExecutionPolicy unrestricted Verify that the policy has changed by running Get-ExecutionPolicy again. PowerShell should return a value of Unrestricted. You should now be able to run PowerShell scripts. Step 5: Grant WMI access for the MID Server user on the remote machine Go to Server Manager (mmc.exe) > Configuration > WMI Control > Properties . Go to Root > Security > Add . Enter the MID Server account and enable account and remote call permissions. Step 6: Check for Windows Server 2003 If the remote machine runs Windows Server 2003, the MID Server account may need to be in the local Administrators group of the remote machine.

Step 7: Check domain trust in multi-domain environments In a multi-domain environment, a domain trust may be required for a credential to successfully use WMI to discover devices that belong to a different domain.

Step 8: Verify WMI connectivity Use the PowerShell cmdlets Get-WmiObject or Get-CimInstance to verify WMI connectivity:

Get-WmiObject -Class Win32_OperatingSystem -ComputerName

Get-CimInstance -ClassName Win32_OperatingSystem -ComputerName