Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
SCCM server discovery issue - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • SCCM server discovery issue
KB0728408

SCCM server discovery issue


1447 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Description


  1. 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

 


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.