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.
Why to add * to trusted hosts when servers are in domain and RM commands are executed when running manually ? - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Why to add * to trusted hosts when servers are in domain and RM commands are executed when running manually ?
KB0856433

Why to add * to trusted hosts when servers are in domain and RM commands are executed when running manually ?


1902 Views Last updated : Jul 24, 2025 public Copy Permalink
KB Summary by Now Assist

Issue

  • Why to add * to trusted hosts when servers are in domain and RM commands are executed when running manually ?

Release

  • All

Resolution

Adding * to the trusted hosts list is a requirement for ServiceNow due to the following:

  1. WinRM Discovery as Discovery, is using all the same APIs and needs the same access as if you were doing remote management of 'another server' from the 'MID Server'.

    2. Microsoft's rules are that the 'another server' has to be listed as trusted in the 'MID server'.

    3. Until Discovery has found the new server, it's not in the CMDB, and ServiceNow doesn't know that it exists, and so nor can the MID Server.

    4. If you don't know it exists yet, you can't list it as trusted, so you have to trust all.


In theory, you could list each server individually, but you would need:

  1. A comprehensive list of all Windows servers and laptops. It may be possible to extract that from Active Directory, or SCCM/SCOM.

  2. Each time a new device is added to the network, it will need adding to the list on every MID Server. That might be daily. That needs doing before the device can be fully discovered for the first time.

  3. Each MID Server will need the list adding. As more MID Servers are added, they will also need adding and the list maintaining.


Since that will become a big job, it would need automating to be feasible.

Related Links

  • Please refer the article KB0687786 for information on adding "*" to the trusted hosts.

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.