Integrate SCCM with ServiceNow
Integration: Microsoft System Center Configuration Manager (SCCM) with ServiceNow.
Purpose: To pull the Configuration Management data from SCCM to ServiceNow.
Outcome: With this SCCM Integration, customers can put all the relevant CI data and update or create them in the respective CMDB_CI tables.
1) Install “Service Graph Connector for Microsoft SCCM” Plugin
App id: sn_sccm_integrate
2) Create a user in ServiceNow for midserver.
Ex: UserName: SCCM.User
Password: ...........
Required Role: Mid_Server
Make “Web services access only” flag True
3)Open SCCM Server.
Need Admin privileges in SCCM to run MidServer.
4)Installation of MidServer
- Open ServiceNow in VM.
- Download midserver from SN.
- Move the downloaded file to C-Drive under a new folder and unzip the file.
- Open the config file and make the necessary configurations
Downloaded file->Agent->config
Created UserID and Password, Instance URL, MidServer name.
- Right click start then Run as Administrator.
Note: To run Midserver must have admin privileges.
5) Validation Midserver in ServiceNow
- Type Mid server under that open Server
- Validate MidServer
- Status should be up and Validated should Yes
6) Create a SQL Server account
SQL Server account on the SQL Server Database that the Microsoft Configuration Manager Site is configured to connect to and assign it the SQL Server 'db_datareader' role.
7) Open SCCM Configuration from navigator.
😎 Open the Setup and follow the guided setup
- Configure Data source access
- Configure Scheduled data import access
- Configure connection:
In order to complete this step, you will need the following information.
- Database username and password (Use Created SQL Server account)
- Database host name (ex: VMXETSCCM18)
- Database name (ex: DB_01)
Note:
- Use created SQL Server account as username and password.
- SCCM Integration, by default, uses SQL based authentication (Standard Security) to connect to the SQL server and the company may have elected to use Windows NT based authentication (Integrated Security) for their SQL server.
In order to successfully test and use the connection, the user must enable Integrated Authentication for each SCCM Data Source.
Reference: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0546840
Integrated Authentication configuration:
- Verify MID Server credentials:
- Open Services in the Windows Management Console.
- Open the ServiceNow MID Server service.
- Verify the Log On account/password are a Windows user with access to the SQL SCCM tables.
- If updated, restart MID Server (To restart you should have access, need to check with windows team).
- Select Integrated Authentication in JDBC Connection with specific Midserver.
- Test the connection.
9) Validate Data Sources
Note: Make sure Integrated Authentication is true if you are using integrated Auth.
Open Data Source from list view and click the 'Test Load 20 Records' related link.
If the completion code is Success, mark this step as complete. If the completion code is Error, there is an error in the SCCM JDBC Connection that you must fix.
Reset 'Last run datetime' in test load data source
10) Scheduled Import sets
- Execute the parent job “SG-SCCM Computer Identity”
- After Parent jobs executes automatically child jobs will run.
- After Successfully execution of jobs data is directly imported into CMDB tables by following IRE.
Make sure below things are configured perfectly
- Provide import_scheduler role to Run as user.
- Check Instance name is given properly in all Scheduled jobs.
- If we use integrated authentication, make sure all the Data Sources are enabled with Integrated authentication.
- To make any changes in attributes/tables mapping go to the Robust transform maps under each data source.
- Recommended way is to install IntegrationHubETL plugin and make mapping configurations.
Mid servers for three environments in ServiceNow
- As part of the best practice don’t use one Host machine to install three MidServers.
- Use separate VM ware for production midserver.
- Use another VM ware for Dev and Test MidServers.
- Follow the same procedure above to install midservers.
- Hosting two midservers in one VM.
- Install two Midserver Zip files in separate folders in C-drive.
- Open the wrapper-override.conf file in the MID Server installation folder. ({midinstallationfolder}/agent/conf)
- Change the wrapper.name and wrapper.displayname parameters to the service name to a different one that the dev mid (perhaps add _test to the end)
- Recommended to use different midserver usernames for Dev and Test.
Regards,
Pradeep
