Adding a WinRM/WMI node to the SolarWinds Platform fails

If you find that adding a Windows node to the SolarWinds Platform fails, perform the troubleshooting steps below to address the issue.

WinRM/WMI not fully configured on the node and SolarWinds server.

If you are configuring WinRM, do the following on the target node:

1. Open PowerShell and run "Get-Service WinRM" to determine the status of the service. This should return a status of Running:

2. Run "WinRM enumerate winrm/config/listener" to confirm the service is listening:

3. Add the user to the Remote Management Users Group
   1. In PowerShell, run Add-LocalGroupMember -Group "Remote Management Users" -Member "DOMAIN\Username"
4. Configure firewall exceptions. If your polling engine is under a strict outbound policy that blocks outgoing traffic to the TCP ports 5985 (HTTP) and 5986 (HTTPS), you also need to configure the firewall to allow outbound connections for these ports on the polling engine. 
   1. For HTTP, run netsh advfirewall firewall set rule group="Windows Remote Management" new enable=yes
   2. For HTTPS, run New-NetFirewallRule -Name "WinRM over HTTPS" -DisplayName "WinRM over HTTPS" -Enabled True -Profile Any -Action Allow -Protocol TCP -LocalPort 5986

If you are configuring WMI over DCOM, do the following on the target node:

1. Run "Get-WMIObject -Namespace root\cimv2 -Class Win32_operatingsystem" to confirm WMI is running.

   

   1. If the command fails, run "Get-Service Winmgmt" to check the service status.
   2. If WMI is stopped, run "Start-Service Winmgmt".
2. Enable firewall rules with the following commands in PowerShell:
   1. Enable-NetFirewallRule -Name "WMI-RPCSS-In-TCP"
   2. Enable-NetFirewallRule -Name "WMI-WINMGMT-In-TCP"
   3. Enable-NetFirewallRule -Group "Windows Management Instrumentation (WMI)" 
   4. Enable-NetFirewallRule -Name "RPC-EPMAP" #TCP 135
      1. If these commands fail, enable Windows Management Instrumentation (WMI-In) in the Windows Firewall Window, and Remote Event Monitor (RPC-EPMAP).

3. Set DCOM Permissions for Remote WMI.
   1. Do this for the account you're using in the SolarWinds Platform to monitor the node.
   2. Run dcomcnfg
   3. Go to the COM Security tab.
   4. Under Access Permissions, click Edit Limits.
   5. Add your user or group and allow Remote Access.
   6. Open Launch and Activation Permissions and allow Remote Launch and Remote Activation for the user or group.
4. Set Namespace Security in WMI
   1. Run wmimgmt.msc
   2. Right-click WMI Control (Local) > Properties.
   3. Go to the Security tab.
   4. Expand Root and select CIMV2.
   5. Click Security, add your user, and allow Remote Enable, Execute Methods, and Provider Write.

If you are configuring WinRM, do the following on the SolarWinds server:

1. Add the Target node to the WinRM trusted hosts list using the following command in PowerShell:
   1. Set-Item WSMan:\localhost\Client\TrustedHosts -Value "<targetservername>" -Force
2. Test WinRM communication to the target node using PowerShell:
   1. Test-WSMan <NodeNameorIPAddress>

2. 2. If this fails, run the following via PowerShell to test the WinRM port 5985
   3. Test-NetConnection <NodeNameorIPAddress> -Port 5985
3. Configure firewall exceptions. If your polling engine is under a strict outbound policy that blocks outgoing traffic to the TCP ports 5985 (HTTP) and 5986 (HTTPS), you also need to configure the firewall to allow outbound connections for these ports on the polling engine. 
   1. For HTTP, run netsh advfirewall firewall set rule group="Windows Remote Management" new enable=yes
   2. For HTTPS, run New-NetFirewallRule -Name "WinRM over HTTPS" -DisplayName "WinRM over HTTPS" -Enabled True -Profile Any -Action Allow -Protocol TCP -LocalPort 5986

If you are configuring WMI over DCOM, do the following on the SolarWinds server:

1. Test WMI Remotely via PowerShell with the following command:
   1. Get-WmiObject -ComputerName <ServerName> -Namespace root\cimv2 -Class Win32_OperatingSystem -Credential (Get-Credential)