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. 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, the data sources will need to be modified if a plugin is to be used for an SCCM version they’re not written for. Starting with Fuji, it is recommended to use the plugin version that corresponds to the SCCM version it is designed to integrate with. 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: Procedure Navigate to Integration - Microsoft SCCM 20xx > Scheduled Import. Clear the Active check box. Figure 1. Scheduled Import form Click Save or Update. To activate the new SCCM plugin, navigate to System Definition > Plugins. Search on the name *SCCM to see all the available SCCM integrations plugins. Activate the plugin.