General
- Ensure that Remote Powershell is enabled on the given servers. To enable, open the Powershell console as an Administrator, and execute the following command: Enable-PSRemoting -Force
- Ensure Remote Powershell network ports are open on the given servers (as well as open on any firewalls between the OC Scanner and the scanned / target machines): TCP 5985, 5986
- To test Remote Powershell connectivity, execute the following Powershell command on the OC Scanner server: Test-WSMan -ComputerName SERVER_to_scan
- Ensure the account running the scan, has the right to access Remote Powershell on the given server.
- If the Remote Powershell has been enabled, and the appropriate firewall configuration is in place, but the Remote Powershell connection issues are still present, then it could be that the Remote Powershell has not been correctly configured on the given servers. Typically this can happen when configuring Remote Powershell through Group Policy, and if a mistake is made in the IPV4 Filter GPO option. If IPV4 Filter is left blank, or incorrectly configured, then Remote Powershell cannot bind to the correct networking interface, and no Remote Powershell port is being opened. This can be checked by enumerating the WinRM listener configuration using the following command (executed under an Administrator account, using either cmd.exe or Powershell): winrm enumerate winrm/config/listener
If the result is as follows, then it indicates a configuration issue, as explained above:
##
Listener [Source=”GPO”]
Address = *
Transport = HTTP
Port = 5985
Hostname
Enabled = true
URLPrefix = wsman
CertificateThumbprint
ListeningOn = null
##
The solution to the above issue is to reconfigure the GPO to have * in the IPV4 Filter GPO Option, and then to save the GPO changes, and update the policy on the servers either manually via gpupdate /force command, or wait for it to update automatically.
Desktop Applications
This issue is present if Remote Powershell is not enabled, or is not working correctly on the given server. Please check the Remote Powershell diagnostics above.