[Discovery] Windows servers may fail to discover with error "gwmi : Could not get objects from namespace root\default. Not foundAt **PATH**"Description<!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms Sometimes the windows servers may fail to discover with below error message: "" gwmi : Could not get objects from namespace root\default. Not foundAt <<MID_Server_Agent_Folder_Path>>\agent\scripts\PowerShell\WMIFetch.psm1:363char:20+ $reg = gwmi -list -computer $computer -credential $cred-namespace r ...+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo : ObjectNotFound: (:) [Get-WmiObject], ManagementException+ FullyQualifiedErrorId : INVALID_NAMESPACE_IDENTIFIER,Microsoft.PowerShell.Commands.GetWmiObjectCommandYou cannot call a method on a null-valued expression. "" Release All. Cause The issue is because the namespace "root\default" is not available on the target devices when we run PS commands. You can get this exact namespace on the related input ECC queue. Resolution Request the customer to log in to the target device with the credentials same as in credentials tables and then run the below sample PS script in PS editor. "" Get-WmiObject -Namespace "root/default" -List "" Make sure the intended namespace is returned. If not work with their admin team why the namespaces are not returned.One of the other issues might be related to PowerShell version 2.0. So, please try to use a higher version of less than 6.