Upgrade the SCCM integration version
If you are using an earlier version of an System Center Configuration Manager(SCCM) plugin, you can switch over to a later version to take advantage of new features.
Before you begin
About this task
The ServiceNow SCCM integrations are self-contained and
can exist independently. They each use their own import set tables, data sources and
transform maps. However, all SCCM integrations will transform data into the same
tables within the ServiceNow CMDB. To avoid the data being overwritten by another
source:
- Use one SCCM integration and disable all other SCCM scheduled imports.
- Perform a full import to clear the cmdb_software_instance table, the cmdb_sam_sw_install table, and other tables of old SCCM data.
Note:
It is possible to configure each plugin to integrate with SCCM 2007 or
2012 because the mechanism of the integration is actually the same, which is to
leverage Java Database Connectivity (JDBC) imports. However, a data source must
be modified if it is used for an SCCM version for which it was not written. Use
the plugin version that corresponds to the SCCM version for which the data
source is intended.
To change the SCCM integration:
- Disable the current integration by deactivating the SCCM import schedule.
- Activate the new SCCM plugin.
- Reimport all the software records when you are switching to an integration that supports incremental imports of removed software.
To disable the SCCM import schedule: