SCCM server discovery issueIssue <!-- div.margin{ padding: 10px 40px 40px 30px; } table.tocTable{ border: 1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); padding-top: .6em; padding-bottom: .6em; padding-left: .9em; padding-right: .6em; } table.noteTable{ border:1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); width: 100%; border-spacing:2; } table.internaltable { white-space:nowrap; text-align:left; border-width: 1px; border-collapse: collapse; font-size:14px; width: 85%; } table.internaltable th { border-width: 1px; padding: 5px; border-style: solid; border-color: rgb(245, 245, 245); background-color: rgb(245, 245, 245); } table.internaltable td { border-width: 1px; padding: 5px; border-style: solid; border-color: #E0E0E0; color: #000000; } .title { color: #D1232B; font-weight:normal; font-size:28px; } h1{ color: #D1232B; font-weight:normal; font-size:21px; margin-bottom:-5px } h2{ color: #646464; font-weight:bold; font-size:18px; } h3{ color: #000000; font-weight:BOLD; font-size:16px; text-decoration:underline; } h4{ color: #646464; font-weight:BOLD; font-size:15px; text-decoration:; } h5{ color: #000000; font-weight:BOLD; font-size:13px; text-decoration:; } h6{ color: #000000; font-weight:BOLD; font-size:14px; text-decoration:; } ul{ list-style: disc outside none; margin-left: 0; } li { padding-left: 1em; } --> Description Open the SCCM Server record from list https://<INSTANCE>.service-now.com/sn_client_sf_dist_cmdb_ci_sccm_server_list.do?sysparm_query= 2. Click "Discover Now" button (as shown below in the screenshot) 3. Workflow context return error as below: The term 'Get-CMUserCollection' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.HRESULT: [-2146233087] Solution 1. Get-Command : module ConfigurationManager -- Name “Get-CMDeviceCollection”, “Get-CMUserCollection” from their powershell console within the SCCM server to proof issue is resided in the cmdlet. Error return as below: @@@ The term 'Get-CMUserCollection' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. @@@ 2. Customer needs to update cmdlet library. 3. If issue persist, powershell admin need to repair the library from console. Root Cause: The root cause of the issue is the cmdlet unavailableRun following command Applicable Versions London