Windows discovery stucks at classification stage with error in ECC Queue record: Failed to launch process powershell. - Support and Troubleshooting

Windows discovery stucks at classification stage with error in ECC Queue record: Failed to launch process powershell. Issue For some Windows devices we are getting error which during the classification phase, which is aborting the discovery and no CI is getting create/updated.

Error Details :--

Failed to launch process powershell -ExecutionPolicy ByPass -NonInteractive -WindowStyle Hidden -command "& {mode con lines=1 cols=32766; Set-Variable -Name 'SNC_isWmi' -Value $true -Scope Global; function printValues{Process{foreach-object{if($_.Properties){$a=$_.Properties}else{$a=$_.PsObject.Properties}foreach($p in $a){$o=$p.Name+' : ';if ($p.Value -is [Array]){$o+=[string]::Join(',', $p.Value);}else{$o+=$p.Value;}$o;if($p.Value -is [System.Management.ManagementBaseObject] -or $p.Value -is [System.Management.ManagementBaseObject[]]){'_EXTENDED_START:';$p.Value|printValues;'_EXTENDED_END!';}}}}}gwmi -namespace root/MSCluster MSCluster_Cluster -EA SilentlyContinue|select __CLASS,Name|printValues|format-list;gwmi -namespace root/MSCluster MSCluster_ClusterToResource -EA SilentlyContinue|select __CLASS,GroupComponent,PartComponent|printValues|format-list;gwmi -namespace root/MSCluster MSCluster_ClusterToNode -EA SilentlyContinue|select __CLASS,Antecedent,Dependent|printValues|format-list;gwmi -namespace root/virtualization/v2 Msvm_ComputerSystem -EA SilentlyContinue|select __CLASS,Name|printValues|format-list;gwmi -namespace root/virtualization Msvm_ComputerSystem -EA SilentlyContinue|select __CLASS,Name|printValues|format-list;gwmi -namespace root/MSCluster MSCluster_Resource -EA SilentlyContinue|select __CLASS,PrivateProperties,Name,Type|printValues|format-list;gwmi -namespace root\cimv2 Win32_ComputerSystem -EA SilentlyContinue|select __CLASS,Domain,Name|printValues|format-list;gwmi -namespace root\cimv2 Win32_OperatingSystem -EA SilentlyContinue|select __CLASS,Caption,Version|printValues|format-list;gwmi -namespace root/MSCluster MSCluster_Node -EA SilentlyContinue|select __CLASS,Name|printValues|format-list;'---SNC-SEPERATOR---REGISTRY-SECTION---';Get-ItemProperty -Path 'HKLM:/SYSTEM/CurrentControlSet/Services/Tcpip/Parameters' -EA SilentlyContinue|select PSPath,Domain,Hostname|format-list;}" with error System.Management.ManagementBaseObject

Release All Versions.

Resolution The issue is because that the execution of the PowerShell commands got failed on the target. Please refer to the KB: KB0821217 for details.

This can be because of multiple reasons and the customer's ServerOps team should resolve.

However, the below commands are the way to check if the communication is good between the MID server and the target with appropriate privileges for the user which is used for discovery.

$userName = ' ' $userPassword = ' '

$computer = ' ' # Convert to SecureString $secStringPassword = ConvertTo-SecureString $userPassword -AsPlainText -Force $credObject = New-Object System.Management.Automation.PSCredential ($userName, $secStringPassword)

#execute ipconfig on target and write output to admin$ $fullCommand2 = "cmd /c chcp 65001 & powershell -command ipconfig > `"\\127.0.0.1\admin$\temp\ps_test_4.txt`" 2>`"\\127.0.0.1\admin$\temp\ps_test_err_4.txt`"" $processInfo = invoke-wmimethod win32_process -name create -computer $computer -credential $credObject -argumentlist $fullCommand2 Write-Host $processInfo.ProcessId

Please note that the last line should give the ProcessID of the windows object that got created.