[Discovery] Windows discovery pattern might not mark as Virtual an AWS ServerIssue For specific AWS EC2 Windows Servers, you might see that the Windows OS Pattern will return empty results when trying get the AWS information related to EC2 in step "Get EC2 server Details". The step will not be marked as failed, and the pattern logic will continue. The side effect of not having the EC2 metadata from AWS will be that the Windows Server will not be marked as Virtual. The errors in horizontal pattern log might be like: or inline Command result: 'powershell' is not recognized as an internal or external command, operable program or batch file.CauseThe step "Get EC2 server Details" is executed on the remote Windows Server using PowerShell remote execution of an WMI invoke-WebRequest-Uri cmdlet. If the PowerShell executable location is not in the environment variable PATH of that specific EC2 Windows Server, the command will return empty results and the AWS specific internal temporary variables for the pattern will not be initialized. The metadata AWS EC2 is needed for correctly discover the server and its type as "Virtual". Additionally, all the steps dependent of PowerShell will return empty results and therefore the host will not be included in the AWS Virtual server CIs. In order to confirm this behavior, the MID Server performing the discovery will need to have the increased log verbosity as per the article KB0970268 Steps to reproduce are: Increase the MID Server log level by setting MID Server Parameter:mid.log.level=debug Restart the MID Server (not necessary for this parameter change, but does help with reading the logs if you have a clean startup first)Collect the MID Server logs from <agent_home>\logs\agent0.log.0Identify the messages related to "'powershell' is not recognized as an internal or external command, operable program or batch file."ResolutionGet in contact with your infrastructure team and make sure that the PowerShell binary path is included in the global system variable PATH as depicted in the printscreen from below. After including the PowerShell directory and correct the variable PATH, perform a quick check as: open a CMD prompt with administrative privilegesexecute "set | find "Path="execute "PowerShell -$PSVersionTable" If there are no errors or warnings on executing the commands from above then the step for "Get EC2 server Details" will be able to execute the query to AWS EC2 metadata and complete the rest of the discovery steps.