Simple Windows (WinRM) Remote Script Execution TestIssue Windows Discovery requires clients to properly configure Windows Remote Script execution in their environment. This can have a variety of compounding factors, such as different domains, trying to execute against domain controllers, etc. This is a nice, simple command that you can run from the MID server host to the desired Discovery target to validate end-to-end that WinRM is properly configured from host to target. ResolutionRun the following commands from a PowerShell command prompt on the MID server host: # Enter the intended Discovery credential when prompted by this line: $cred = Get-Credential # Enter the hostname of the desired target between the single quotes: $computer = 'enter_host_name_here' $s = New-PSSession -ComputerName $computer -Credential $cred Invoke-Command -Session $s -ScriptBlock { hostname } If WinRM is configured correctly then we should return the hostname of the target server. This tests the following components: DNS resolution (since we resolve direct IP to DNS in PowerShell for Discovery)Credential (proper access and authentication)Remote PSSessionRemote script executionNetwork/Firewall connectivity from MID to targetRelated LinksThere are a variety of KBs for troubleshooting WinRM and PowerShell discovery issues, utilize those as well as research Microsoft Docs/articles on the internet for any errors encountered. Some articles for WinRM configuration: https://docs.microsoft.com/en-us/windows/desktop/winrm/installation-and-configuration-for-windows-remote-management https://docs.microsoft.com/en-us/powershell/scripting/learn/remoting/running-remote-commands?view=powershell-6 https://support.microsoft.com/en-us/help/2019527/how-to-configure-winrm-for-https https://www.visualstudiogeeks.com/devops/how-to-configure-winrm-for-https-manually https://www.techdiction.com/2016/02/11/configuring-winrm-over-https-to-enable-powershell-remoting/