Discovering servers in different domain
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-11-2014 10:38 AM
Is there a clean way of discovering servers in a different domain? From what I've read, best practice is to install a MID server in that domain but i was wondering if there was a "good" way as a temp solution.
- Labels:
-
Discovery
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-11-2014 11:15 AM
Simply enable powershell and the related paramters on the MID servers. That will let the MID server scan using different credentials from different domains.
MID Server Configuration - ServiceNow Wiki
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-11-2014 11:40 AM
Greg,
The MID server should be able to go across domains as long as you log onto the Windows server where the MID server Windows Service is, then go to the properties for that Windows Service, go to the Log On tab, and set the credentials to use a Windows account for that domain (provide domain\user and the password). So, you might need at least 1 MID server per domain, so that you can use one domain's credentials for one MID server and another domain's credentials for another MID server (they can both be on the same Windows machine).
Then, for the Discovery schedules, make sure to use different schedules for different domains. For example - for a domain called "yourcompany-test", create a schedule and include all of the IP addresses / ranges for that domain in it (144.144.144.155/28, or individual IPs). For that schedule, make sure to specify the MID Server (or MID Server in the Behavior that's specified for the schedule) that has the proper credentials for that domain (if you set up the Windows service for MID Server #1 to Log On as a "yourcompany-test\user", then you should add the IP ranges for the machines/gear that reside on the yourcompany-test domain to that schedule and ensure MID Server #1 is the one used by that schedule).
Then, for the "yourcompany-stage" domain, create a separate schedule, and include all of the IP addresses / ranges for that domain in it. Then, schedule them at different times and try running Discovery.
Please respond on here if you face any issues - happy to work through this with you (I'm a Discovery and CMDB owner at my organization).
Thank you,
Dmitri

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-19-2015 04:03 AM
A better way is to have AD architecture by your side. There may be domains with two-way trusts. In that case, optimization can be done!