Hi @Ashish2007 ,
If you want to learn ITOM, You can refer the ITOM Batch 3 from TechTrek with AJ youtube channel which helps to understand each and everything for ITOM.
Here is the Link :- https://www.youtube.com/watch?v=-5QkJ4B300c&list=PLXRgDc4BgFSwbng6_F85D9VSCBPnSdNiU
Also as per my understanding , below which can help you understand more ITOM.
1. Pre-Implementation Planning – ITOM Readiness
Understand ITOM Product Scope
Before beginning, be crystal clear on which ITOM modules you’re implementing:
* Discovery
* Event Management
* Service Mapping
* Cloud Management
* CMDB Health
Each module has specific configuration, licensing, and MID Server dependencies.
2. Best Practices Before First ITOM Project
a. Prepare CMDB & CSDM Foundation
* Ensure CMDB model is aligned to the CSDM framework (Common Service Data Model).
* Clean your foundation data (like Locations, Departments, Business Units).
* Define CI Class Mapping and ownership model (Group & Individual).
b. Setup Environments Properly
* Prepare separate dev, test, and prod instances.
* Install ITOM plugins ahead of time.
* Understand data segregation and plan for data loads and volume.
3. MID Server Setup – Best Practices
a. Dedicated MID Server for each environment
* Install at least one MID Server per network segment you plan to discover.
* Separate Discovery MID and Orchestration MID if possible.
* Keep MID Server versions in sync with your instance version.
b. MID Server Prerequisites
* Ensure Windows/Linux host has appropriate firewall rules, Java installed, and network reachability.
* Test MID connectivity using MID Server > Validate option.
4. Managing Update Sets for MID Server Configurations
Important Note: The MID Server itself is not moved via Update Sets, but some configurations related to Credentials, Patterns, and Discovery Schedules can be.
What goes in Update Sets:
| Configuration Item |
Can be moved via Update Set? |
| MID Server (actual) |
No – it's tied to local machine |
| MID Server Capabilities |
Yes |
| Discovery Schedules |
Yes |
| Credentials (shared) |
Yes (but security sensitive – use carefully) |
| IP Ranges, Classifications |
Yes |
| Patterns, Probes, Sensors |
Yes |
| Event Rules / Alert Rules |
Yes |
Credential Warning: While credentials can be exported, it’s recommended to manually recreate them in PROD due to security risks.
Best Practices:
* Use named update sets per feature/module, e.g., ITOM_Discovery_Config_US.
* Group related changes logically: Credentials, Schedules, MID Capabilities.
* Always test updates in DEV or UAT before promoting to PROD.
* Use Application Picker (Global or Custom Scoped) consistently.
* Export MID Server name & properties in documentation — not in update sets.
| Area |
Best Practice |
| CMDB Readiness |
Implement CMDB health dashboards & CI class mapping |
| MID Server |
MID Server validated, Capabilities assigned |
| Credentials |
All credential types created and tested |
| Network Access |
Ports opened between MID and target devices |
| Discovery Schedule |
Defined by IP ranges and schedules |
| Event Rules |
Predefined for known events and alert routing |
| ServiceNow Roles |
Discovery_Admin, evt_mgmt_admin, etc. properly assigned |
| Update Set Flow |
DEV → TEST → PROD process documented and followed |
| Rollback Plans |
Manual CI backups or scripts exported |
Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
Thank You
AJ - TechTrek with AJ - ITOM Trainer
LinkedIn:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj
Topmate:- https://topmate.io/aj_techtrekwithaj (Connect for 1-1 Session)
ServiceNow Community MVP 2025
