Service Now & Microsoft SCCM Integration

This blog illustrates my experiences, challenges with Microsoft SCCM Integration.

 - First and far most important to know what kind of SCCM software being used at your customer location, Based on that version, Activate the corresponding plug-in in your Service Now Instance.

- I strongly prefer to have two Mid Servers configured for PROD Environment. Setup Mid Server and make sure Mid Server(s) up and running without any errors. Make sure verify the Log files of the Mid Server once started up and running. Goto Services on where Mid servers are installed, Verify the status of the Mid Server as shown below

- Get one dedicated User who has the access to SCCM
- Right click on Mid Server -> Properties
- Log On Section, Configure the dedicated user who has the access to SCCM and enter the Password and User Name. Make sure if you have two mid servers , need to repeat this step for each MID Server

- After successful plugin activation, You should able to see 'Integration - Microsoft SCCM..' on your applications list navigator as shown below
- Click on 'Setup'

- Enter all the required info in 'Integration Setup' form, Select the Mid Server and make sure MID Server is up and running. Save the form
- Next step is to configure all the required Data Sources for your SCCM Integration.
- Click on 'Data Sources' in 'Integration - Microsoft SCCM..' application
- Out of box, SCCM stores Servers and Workstations in different databases. Out of box we get all the data sources, so Create extra data source for each already existing data source and Suffix with ' - Server' and provide the correct Database Server Name and Database Name for all the 'Server' related data sources.

- Update all out of box Data sources with correct 'Database Server Name' and 'Database Name'
   Select 'Use Integrated Authencation' check box, so that it will use Mid Server to communicate with SCCM Database. Make sure to fill all the below highlighted required information for each data source

- After entering all the required information for each Data Source, verify 'Load All Records'  and execute 'Run Transform'
- I have very bad experience with 'Test Load 20 Records' , this won't work as expected all times, so don't relay on this functionality always.
- After first load of data, Select 'Use Last Run Datetime' check box on each data source, so that it won't load everytime same data into CMDB, only delta data for subsequent runs

- After configuring all the data sources, and verifying all the data sources working fine and loading data into CMDB, Next step is to configure 'Scheduled Import

- Click on 'Scheduled Import' in 'Integration - Microsoft SCCM..' application
- Choose the 'SCCM 2012 v2 Computer Identity' as your parent data source, and select appropriate value for 'Run' field
- Choose all the subsequent data sources which need to be run after Parent data source under 'Run the following imports when complete' section and give correct 'order' for each data source.

With this your SCCM configuration and schedule completed successfully and all good to go.