Loading

Microsoft SMS/SCCM Integration 2.0

From ServiceNow Wiki
Home > Integrate > Vendor Specific Integrations > CMDB > Microsoft SMS/SCCM Integration 2.0
Jump to: navigation, search

Contents


1 Overview

The Microsoft SMS/SCCM integration is a one direction import of SMS/SCCM data into ServiceNow's Configuration Management Database (CMDB). The integration keeps the ServiceNow CMDB up to date with SMS / SCCM SQLServer database. Relevant data is imported from the SMS / SCCM database to the CMDB. The SMS / SCCM database is considered an authoritative source and is not written to. The import is achieved using a JDBC connection via the MID Server. This functionality requires the Integration - Microsoft SMS / SCCM 2.0 plugin.

2 Activating the Plugin

The Integration - Microsoft SMS / SCCM 2.0 plugin can be activated by an administrator and also activates the Integration - JDBC plugin.

3 What Version Should I Use?

ServiceNow offers three versions of the Microsoft SCCM integration:

All versions import identical data, but do it in a different way and with different results in some areas.

3.1 Version 2.0

Microsoft SMS/SCCM integration version 2.0 maps directly to each Microsoft SCCM table and imports each data object separately. Version 2.0 uses the SCCM resource ID to identify CIs in the CMDB. If you are populating the CMDB via the Microsoft SMS/SCCM integration version 2.0 only, the platform creates and updates CIs accurately. However, if you are using both ServiceNow Discovery and Microsoft SMS/SCCM to populate the CMDB, the platform creates duplicate CIs. Discovery cannot identify CIs in the CMDB by the SCCM resource ID and creates a new CI rather than updating CIs created by Microsoft SMS/SCCM.

3.1.1 Related Lists

The Microsoft SMS/SCCM integration version 2.0 can add related devices (such as network interface cards and disks) to computer CI records, but cannot delete these devices from the record if the devices are removed from the computer.

3.1.2 Software Packages

The Microsoft SMS/SCCM integration version 2.0 also adds records to the Software Instance [cmdb_software_instance] table for software packages installed on a computer CI, but cannot delete the instance record (or the relationship) from the CMDB if the software package is uninstalled from the CI. The resulting relationship looks like this:

Version 2.0 Software Updates‎

3.2 Version 3.0

Version 3.0 uses a flat transition table to gather specific data from all the SCCM tables (except the Software table). ServiceNow maps to this flat table and to the SCCM Software table and imports the data into the CMDB.

Note
Note: ServiceNow Microsoft SCCM Integration version 3.0 supports Microsoft SCCM 2007 R2.


3.2.1 Identifiers

The Microsoft SCCM integration uses CI identification to update CIs created from data imported from SCCM with a resource ID. A Discovery Identifier called SCCM ID & Class Name returns the resource ID of a computer from SCCM and stores it in a table called Source [sys_object_source]. When resource IDs are first imported, either from SCCM or Discovery, ServiceNow populates the Source table with IDs for each CI it identifies. In subsequent imports, if an incoming ID matches that of an existing CI, ServiceNow updates the information for that CI in the CMDB. If the incoming resource ID does not match that of an existing CI, ServiceNow creates a new CI and populates it with the resource ID.

3.2.2 Scripts

Data population scripts added with the Integration - Microsoft SCCM plugin populate the related data in the CMDB for each target CI discovered by the SCCM ID & Class Name identifier.

3.2.3 Software

The Microsoft SCCM Integration version 3.0 reconciles the software package count in the records for a CI and removes a software instance from the Software Instance [cmdb_software_instance] table if the software package is uninstalled from the CI.

Note
Note: The table data imported from SCCM in Microsoft SCCM Integration version 3.0 must contain complete data for the CI. ServiceNow assumes that the import represents all relationships that exist and adjusts the CMDB accordingly. Partial data received from SCCM tables can cause the deletion of active relationships.


Version 3.0 Software Updates‎

3.3 Version 2012

Version 2012 is designed to work with SCCM 2012 release 1. It comes with default table views and related column names from SCCM 2012. Version 2012 can work with SCCM 2007, but it will require configurations on the table name and column names for certain data source imports.

A major difference between version 3.0 and SCCM 2012 is that a flat table is no longer needed for the import. Instead, data is imported from the Computer Identity data source table within SCCM. The table can be easily extended and configured to include additional information.

SCCM 2012 also provides three transform maps for a software import. Only one transform map can be enabled at a time.

  1. SCCM 2012 Software - Full Import
  2. Incremental Import
  3. Incremental Import (SAM enabled)

The first transform map performs a full import of the software data. This transform map automatically populates into the cmdb_ci_spkg and cmdb_software_instance tables or the cmdb_sam_sw_install table depending on if the Software Asset Management plugin is enabled. If the plugin is not enabled, the former tables are populated; if the plugin is enabled, the latter table is populated.

The second and third transform maps perform an incremental import and should be enabled or disabled depending on whether the Software Asset Management plugin was enabled. If the plugin is not enabled, use "Incremental import"; otherwise, use "Incremental import (SAM enabled)". By default, the incremental import transform map is enabled.

Note
Note: ServiceNow Microsoft SCCM Integration version 2012 supports Microsoft SCCM 2012. This integration is available starting with the Dublin release.


3.3.1 Identifiers

The Microsoft SCCM integration uses CI identification to update CIs created from data imported from SCCM with a resource ID. A Discovery Identifier called SCCM ID & Class Name returns the resource ID of a computer from SCCM and stores it in a table called Source [sys_object_source]. When resource IDs are first imported, either from SCCM or Discovery, ServiceNow populates the Source table with IDs for each CI it identifies. In subsequent imports, if an incoming ID matches that of an existing CI, ServiceNow updates the information for that CI in the CMDB. If the incoming resource ID does not match that of an existing CI, ServiceNow creates a new CI and populates it with the resource ID.

3.3.2 Scripts

Data population scripts added with the Integration - Microsoft SCCM plugin populate the related data in the CMDB for each target CI discovered by the SCCM ID & Class Name identifier.

3.3.3 Software

The Microsoft SCCM Integration version 2012 reconciles the software package count in the records for a CI and removes a software instance from the Software Instance [cmdb_software_instance] table if the software package is uninstalled from the CI.

Note
Note: The table data imported from SCCM in Microsoft SCCM Integration version 2012 must contain complete data for the CI. ServiceNow assumes that the import represents all relationships that exist and adjusts the CMDB accordingly. Partial data received from SCCM tables can cause the deletion of active relationships.


For a full import, the resulting relationship looks like this:

Version 2012 Software Full Import‎

For an incremental import, the resulting relationship looks like this:

Version 2012 Software Incremental Import

4 Information Imported

The following information is imported from SMS/SCCM:

  • PC Hardware (Model, Manufacturer, memory, clock speed, number of CPUs, etc.)
  • Software packages installed (Office, Photoshop, iTunes, etc.)
  • Operating System Information (Name, Service Pack)
  • User and Domain information
  • Disk information (physical, network, and logical)
  • Network (IP Address, Netmask)

5 Modules Provided

The following are the configuration and operational modules for this integration.

  • Setup
    • Configure the data sources from one form
    • Specify Database server settings and MID server
    • Test configuration
  • Scheduled Import
    • Schedule the execution of the import or import immediately
  • Data Sources
    • A list of the pre-configured data sources defining the external CMDB database
  • Progress
    • A historical list of progress on scheduled imports
  • Transform History
    • A historical list of transformations performed during scheduled imports

6 Import Set Data

The SMS / SCCM import set data section shows a list of import set tables used in containing data retrieved from using JDBC to query the SMS / SCCM database. The module names (hence the import set tables they point to) match SMS's table names and structure that it is loading from.

  • Scheduled Cleanup
    • Configure a schedule to cleanup/delete import set data that have already been transformed
  • System
  • Computer System
  • Processor
  • Operating System
  • PC Bios
  • Disk
  • Network
  • Software

When viewing each of these table lists, at the end of the list you have links to other operational functions of the import set.

Iset list actions.jpg

7 Web Services

This section lists the modules that define the web service import set tables - the schema for the import set tables that are receiving the JDBC import. From each web service, you can add/remove fields as well as access the transform maps to make modifications.

Sms computer ws.jpg

Sms computer ws2.jpg

Was this article helpful?
Yes, I found what I needed
No, I need more assistance
Views
Personal tools