Version history for the Now Platform capabilities Service Graph Connector for Microsoft SCCM on the ServiceNow Store.

Important: For details on system requirements and family compatibility, view the application listing on the ServiceNow Store website.

Version history

Version 3.6.0 - November 2024
New: Onboarded connector to SGC Central.
Version 3.4.2 - March 2024
  • Fixed:
    • The Last Scanned field is now populated in the Software Installation [cmdb_sam_sw_install] table for the SG-SCCM Software AI data source
    • Menus intended for admin users in the application navigator will no longer appear for non-admin users
    • Fixed encoded URLs during the creation of data sources
    • Updated the SQL query for the v_GS_CCM_RECENTLY_USED_APPSSCCM table to improve the performance
    • The serial numbers in the Serial Number [cmdb_serial_number] table now use the Cleanse Serial Number RTE transform operation
Version 3.4.0 - September 2023
  • New:
    • Support for the common connection framework
    • Implemented the cleanse serial number operation for serial numbers
  • Fixed: Tuned the SQL query in the SG-SCCM Software data source for the last used software
Version 3.3.0 - March 2023
  • Fixed:
    • Removed dots from field names so they are equivalent to the path. Dots in the field names prevented them from appearing on the user interface.
    • Fixed issue updating SG-SCCM SAMP SW USAGE record for certain products.
    • Fixed issue aggregating usage time when multiple records exist with the same combination of filename and related fields.
    • Removed hard-coded value to provide flexibility to run software usage for a given month.
Version 3.2.1 - May 2022
  • Change:
    • Use Raw value of Publisher, Display Name, and Version for Software Source Native key instead of cleansed value
    • Move the left navigation items of SCCM to the Integration Commons Service Graph Connectors navigation menu
Version 3.0.6 - January 2022
  • Fixed: When a user runs the "Test Load 20 Records" and a MID server is used, the last run date time is set. Steps added to the Guided Setup that users need to clear the last run date time to force a full import on the first run.
  • Note: Upgrade of existing 2.x version to 3.x will work as is but changes to credential and connections will require going through guided setup again.
Version 3.0.4 - December 2021
  • New: Support for connecting with multiple SCCM instance using new/updated guided setup process
  • Note: Upgrade of existing 2.x version to 3.x will work as-is, but changes to credential and connections will require going through guided setup again.
Version 2.5.0 - September 2021
New: Added support for Computer Identity: Asset Tag, Assigned On, DNS Domain and Organizational Unit (OU)
Version 2.4.2 - August 2021
Changed: Software titles incorrectly removed from CMDB when title contained escaped characters (e.g. "&amp").
Version 2.4.1 - July 2021
Changed: Implemented a new data source to populate cmdb_ci_computer.last_discovered with LastHWScan from SCCM to reflect the last time SCCM scanned the computer.
Version 2.3.1 - May 2021
  • New:
    • Remove licensing restrictions.
    • Support Subscription Software rules for "last used" usage model.
    • Populate source_recency_timestamps from source data.
  • Fixed: Updated handling of removed software to take into account multiple computer identity records for a single computer CI in the CMDB.
Version 2.1.6 - March 2021
Fixed: Software installation records were incorrect under certain circumstances.
Version 2.1.1 - September 2020
  • The Microsoft SCCM integration is a one direction import of SCCM data into the ServiceNow Configuration Management Database (CMDB).
  • Scheduled imports bring relevant SCCM data into the ServiceNow instance from an SQL Server database and map the data to the appropriate tables in the CMDB. You can configure either a full or incremental data import. The import is achieved using a JDBC connection via the MID Server. The integration keeps the ServiceNow CMDB synchronized with the SCCM SQL Server database, so that only relevant data is imported from the SCCM database to the CMDB. The SCCM database is considered an authoritative source and is not written to.