Product documentation Docs
    • English
    • Deutsch
    • 日本語
    • 한국어
    • Français
  • More Sites
    • Now Community
    • Developer Site
    • Knowledge Base
    • Product Information
    • ServiceNow.com
    • Training
    • Customer Success Center
    • ServiceNow Support Videos
  • Log in

Product documentation

  • Home
How search works:
  • Punctuation and capital letters are ignored
  • Special characters like underscores (_) are removed
  • Known synonyms are applied
  • The most relevant topics (based on weighting and matching to search terms) are listed first in search results
Topics are ranked in search results by how closely they match your search terms
  • A match on the entire phrase you typed
  • A match on part of the phrase you typed
  • A match on ALL of the terms in the phrase you typed
  • A match on ANY of the terms in the phrase you typed

Note: Matches in titles are always highly ranked.

  • Release version
    Table of Contents
    • Now Platform capabilities
Table of Contents
Choose your release version
    Home Orlando Now Platform Capabilities Now Platform capabilities Configuration Management Database Integrating third-party data into the CMDB Service Graph connector for Microsoft SCCM (2.1.1)

    Service Graph connector for Microsoft SCCM (2.1.1)

    • Save as PDF Selected topic Topic & subtopics All topics in contents
    • Unsubscribe Log in to subscribe to topics and get notified when content changes.
    • Share this page

    Service Graph connector for Microsoft SCCM (2.1.1)

    Use the Service Graph connector for Microsoft System Center Configuration Manager (SCCM) to pull data from SCCM into your ServiceNow instance.

    The Service Graph connector for Microsoft SCCM imports SCCM data into the ServiceNow® Configuration Management Database (CMDB) application. The integration does not write to the SCCM database. The integration pulls data from computers, processors, operating systems, disks, networks, and software.

    Request apps on the Store

    Visit the ServiceNow Store website to view all the available apps and for information about submitting requests to the store. For cumulative release note information for all released apps, see the ServiceNow Store version history release notes.

    Supported versions

    Supported versions: Microsoft SCCM 1902, 1906, 2002, 2006, and 2010

    Supported ServiceNow versions:
    • Starting with Orlando Patch 7.
    • Starting with Paris Patch 1.

    Use Cases

    The following are examples on how you can use the Service Graph connector for different ServiceNow applications:
    • IT Operations Management (ITOM) Visibility
      • Ability to get visibility into your infrastructure.
      • Detailed hardware and software inventory tracking. The track can be done with or without Software Asset Management (SAM).
      • Ability to detect delta changes for efficient incremental imports from SCCM to NOW.
    • IT Service Management (ITSM)
      • Incidents, problems, and changes on discovered configuration items (CI).
      • Automatic device ownership assignment.
    • Software Asset Management (SAM) and IT Asset Management (ITAM)
      • Tight integration with Software Asset Management Professional and client software distribution workflows.
      • Inventory Software package and installation tracking.
      • Software Usage tracking.
      • License reclamation by detecting removed software.
      • Support for software editions, normalizing publisher information, and normalizing product Information.
      • Support for SCCM Asset Intelligence.

    Guided Setup

    The guided setup for the Service Graph connector for Microsoft SCCM provides an organized sequence of tasks to configure the integration on your instance. To access the guided setup, see Configure Service Graph connector for Microsoft SCCM.

    CMDB Integrations Dashboard

    The Integration Commons for CMDB store app provides a dashboard with a central view of the status, processing results, and processing errors of all installed integrations. You can see metrics for all integration runs. You can filter the view to a specific CMDB integration, a specific time duration, or a specific integration run. For more details about monitoring Microsoft SCCM integrations in the CMDB Integrations Dashboard, see CMDB Integrations Dashboard.

    Data mapping

    Data from the SCCM data sources is mapped and transformed into the ServiceNow CMDB Configuration Item (CI) class definitions using the Robust Transform Engine (RTE). Data is inserted into the ServiceNow CMDB using the Identification and Reconciliation Engine (IRE). The SCCM data sources include the following:
    • SG-SCCM Computer Identity
    • SG-SCCM Disk
    • SG-SCCM Network
    • SG-SCCM Operating System
    • SG-SCCM Processor
    • SG-SCCM Removed Software, ensure the Use last run datetime option is cleared for every run.
    • SG-SCCM Removed Software AI, ensure the Use last run datetime option is cleared for every run.
    • SG-SCCM Software
    • SG-SCCM Software AI
    Note: When you run SG-SCCM Removed Software and SG-SCCM Removed Software AI, the data for SG-SCCM Software and SG-SCCM Software AI is updated.
    When you complete the guided setup, you can configure the integration to periodically pull data from SCCM. The data is loaded into staging tables and then inserted into the following target tables:
    • CI Relationship [cmdb_rel_ci]
    • Computer [cmdb_ci_computer] (required)
    • Disk [cmdb_ci_disk]
    • Network Adapter [cmdb_ci_network_adapter]
    • Serial Number [cmdb_serial_number]
    • Software [cmdb_ci_spkg]
    • Software Installation [cmdb_sam_sw_install]
    • Software Instance [cmdb_software_instance]
    • Software Usage [samp_sw_usage]
    Note: By default, network adapters that are missing an IP address or MAC address are not imported. To include these network adapters in the import, do the following:
    1. Navigate to Service Graph Connector for Microsoft SCCM > Data Sources.
    2. Select SG-SCCM Network.
    3. Remove the where clause from the SQL statement field.
    Related concepts
    • IntegrationHub ETL (1.5.1)
    • Integration Commons for CMDB (2.5.0)
    • Service Graph connector for ExtraHop (2.0.3)
    • Service Graph connector for Microsoft Intune (1.1.1)
    • Service Graph connector for Jamf (2.4.0)
    • Service Graph connector for SolarWinds (2.2.1)
    • Service Graph connector for VMware Workspace ONE UEM (1.0.4)

    Configure Service Graph connector for Microsoft SCCM

    Set up and validate data source connection credentials to import Microsoft SCCM data into your CMDB.

    Before you begin

    Attention: If you are currently using the SCCM plugin, please refer to the following topic, Update from Microsoft SCCM 2016 plugin to the Service Graph connector for Microsoft SCCM.

    To use this Service Graph connector, you need a subscription to a Subscription Unit that is based in the IT Operations Management (ITOM) Visibility application or in the ITOM Discovery application. As defined in the section titled "Managed IT Resource Types" in ServiceNow Subscription Unit Overview, for managed IT resources that are created or modified in the CMDB by this Service Graph connector, but that are not yet managed by ITOM Visibility or ITOM Discovery, these resources will increase Subscription Unit consumption from that application. Review your current Subscription Unit consumption within ITOM Visibility or ITOM Discovery to ensure available capacity.

    Confirm you are in the SCCM application scope instead of a global scope so you are able to save your information.

    Dependencies and requirements:
    • The Integration Commons for CMDB store app, which is automatically installed.
    • The CMDB CI Class Models store app store app, which is automatically installed.
    • ITOM Discovery License plugin (com.snc.itom.discovery.license). You must activate this plugin.
    • Integration - JDBC (com.snc.integration.jdbc)
    • ITOM Licensing plugin (com.snc.itom.license). For more information, see Request Discovery.
    • Compatible with SCCM 2019.
    • Windows MID Server required for access to SCCM environment.
    Roles required:
    • To configure the ServiceNow platform: admin
    • To access SCCM data: User with appropriate access to SCCM database. You must have sufficient credentials to query the SQL Server that contains the SCCM database. Create a SQL Server account in order to connect to the SCCM database on the MID Server to use the data sources.

      Connect to your SCCM SQL Server and configure the following:

      1. Create a new login user name and password for SQL authentication.
      2. Choose the SCCM database that ServiceNow data sources will connect to.
      3. Assign the 'db_datareader' role membership to the new user.

    Procedure

    1. Navigate to Service Graph Connector for Microsoft SCCM > Setup.
    2. On the Getting Started page, select Get Started.
    3. On the Service Graph Connector for Microsoft SCCM page, in the Configure the connection section, select the task Configure SCCM JDBC Connection.
    4. To enter your configuration details to your Microsoft SCCM data sources, complete the following steps:
      1. On the next page, in the Configure SCCM JDBC Connection task section, click Configure.
      2. On the form, fill in the fields.
        Table 1. Microsoft SCCM data source configuration form
        Field Description
        Database name Name of the database.
        User name User name for connecting to the database.
        Password Password for connecting to the database.
        Server Server name or IP address for the database server.
        Use MID Server MID Server that has access to SCCM environment to access the JDBC server, if you require an integrated authentication, then check the 'User Integrated Authentication' check box.
        Instance name Name of the database instance, leave the field empty if you're using a default name.
        Database port Port of the database server, enter 1433 as a default port.
        Connection timeout Number of seconds before the MID server connection cache pool closes the connection and removes it. Zero means no timeout.
        Query timeout Number of seconds the JDBC driver waits for a query to complete. Zero means no timeout. If the timeout runs out, the integration considers the JDBC result inaccessible and places it in an error state.
      3. Click Save.
      4. In the Configure SCCM JBDC Configuration task section, click Mark as Complete.
    5. In the Validate data sources task section, click Configure and complete the following steps:
      1. Review the fields on the Data Source form, which are automatically set.

        There is no need to update any values on this page. The data source is pre-configured to use the SCCM JDBC Connection that you set up in the previous step.

        Table 2. Data Source form
        Field Description
        Name Unique name of this data source.
        Import set table label Label of the table that will be created for this data source.
        Import set table name Name of the table that will be created for this data source.
        Type Data storage type of the data to be imported.
        Use MID Server MID server to use to access the JDBC server.
        Format Format of the data file.
        Instance name Named instance for SQLServer.
        Database name Name of the database.
        Database port Port of the database.
        Application Application containing this record.
        Use integrated authentication Windows JDBC integrated authentication.
        User name User name for connecting to the JDBC server.
        Password Password for the JDBC server.
        Server Server name for the JDBC connection.
        Query Query type. Query all data from a table or run a specific SQL statement.
        Query timeout Number of seconds the JDBC driver will wait for a query to complete. Zero means no timeout. If timeout is exceeded, the integration considers the JDBC result inaccessible and places it in an error state.
        Connection timeout Number of seconds before the MID server connection cache pool closes the connection and removes it. Zero means no timeout.
        SQL statement SQL statement to extract the desired data from the database.
        Use last run datetime Controls the amount of data that is retrieved from a database during an import run. If unselected, then all rows in the table specified are imported, every time. You might want to use this setting if this is a one-time import, or if all the data in the target table is new. If selected, two additional fields appear, enabling you to select a datetime value to limit imported data to delta values only.
      2. Click the Test Load 20 Records related link to validate your data sources.
        Note: If the completion code is Success, mark this step as complete. If the completion code is Error, there is an error in the SCCM JDBC Connection that you must fix.
      3. In the Help sidebar, click Back to Guided Setup.
      4. In the Validate data sources task section, click Mark as Complete.
    6. In the Reset 'Last run datetime' in test load source task section, click Configure and complete the following steps:
      1. Select the Last run datetime field and delete the value.
      2. Click Update to save the change and return to the Configure the connection page.
    7. On the left side bar, click the Set up scheduled import jobs button.
    8. On the Service Graph Connector for Microsoft SCCM page, in the Set up scheduled import jobs section, select the task Configure scheduled jobs.
      1. In the Configure scheduled jobs task section, click Configure.
      2. On the form, fill in the fields.
        Table 3. Scheduled Data Import form
        Field Description
        Name Name of the scheduled job.
        Data source Data source record that defines the data to import.
        Run as Option to run the scheduled job with the credentials of the specified user.
        Active Option to activate the scheduled job. Select this option.
        Concurrent Import Function that loads the data from multiple import sets. The function then processes and transforms the data concurrently.
        Partition Method Partition method for the concurrent import set.
        Partition Size Import set size for early scheduling.
        Execute pre-import script Option to specify a script to run before the import is performed.
        Execute post-import script Option to specify a script to run after the import is performed.
        Application Application that contains this scheduled job.
        Run Frequency of running the import.
        Conditional Conditions under which this job is executed.
      3. Click Execute Now.
      4. In the Configure scheduled jobs task section, click Mark as Complete.

    Update from Microsoft SCCM 2016 plugin to the Service Graph connector for Microsoft SCCM

    Run a script and pull records to update from the Microsoft SCCM 2016 plugin to the Service Graph connector for Microsoft SCCM.

    Before you begin

    If you are upgrading to the Service Graph connector for Microsoft SCCM, the following steps are mandatory and must be executed in any instance with an existing install of the Microsoft SCCM 2016 plugin (or earlier version of the plugin).

    Note: The Service Graph connector for Microsoft SCCM is an independent implementation that does not reuse any components from the Microsoft SCCM 2016 plugin.

    About this task

    The Service Graph connector for Microsoft SCCM is a successor to the Microsoft SCCM 2016 plugin. If you already have the Microsoft SCCM 2016 plugin (or earlier version) installed in your instance, you must follow these steps to enable the successful transition from using the SCCM plugin to using the Service Graph connector.

    When the Service Graph connector for Microsoft SCCM is installed in an instance, you must no longer run any components from the Microsoft SCCM 2016 plugin, including Data Sources and Scheduled Data Imports. The SCCM 2016 plugin Scheduled Data Imports must be disabled. The Service Graph connector for Microsoft SCCM installs a new set of SG-SCCM Data Sources and Scheduled Data Imports.

    When you execute the Service Graph connector components, your existing CMDB data created by the SCCM 2016 plugin becomes managed and maintained by Service Graph connector for Microsoft SCCM.

    Attention: This upgrade process should be performed and validated in a non-production or test instance that is based on a recent clone of the customer production instance. Failure to first validate upgrade in a non-production instance may result in unexpected outcomes and possible data loss or corruption.

    Any customizations to the SCCM 2016 plugin will not automatically migrate and would have to be reimplemented in the Service Graph connector for Microsoft SCCM, such as through the use of IntegrationHub-ETL.

    Procedure

    1. Deactivate the scheduled imports from the older SCCM plugin. For more information on how to deactivate scheduled imports, see Upgrade the SCCM integration version.
    2. To run the fix scripts, complete the following steps:
      1. Type in Fix Scripts.
      2. In the application scope, run the fix script with the name: SCCM Add Dependent Relationships.
        Note: If there are no Disk or Network Adapter records in the CMDB instance, click Proceed or have it run in the background.
      3. Select Active to activate the script then Update.
      4. When the script is finished, confirm that there are relationship records for Disk and Network Adapter CIs created in the CI Relationship [cmdb_rel_ci] table.
    3. Execute a full pull of the computer records using the Service Graph connector for Microsoft SCCM before running software data or any other data source. To pull the records, complete the following steps:
      1. Navigate to Service Graph Connector Microsoft SCCM > Data Sources.
      2. In the Data Sources list, select the SG-SCCM Computer Identity data source.
      3. Confirm the Last run datetime field is empty. If not, edit the data source and clear the field then select Update.
      4. Navigate to Service Graph Connector Microsoft SCCM > Import Schedules.
      5. In the Scheduled Data Imports list, select the SG-SCCM Computer Identity scheduled data import and select Execute Now.
      6. After completing the steps, verify all the computer records with a non-empty Correlation ID have a Discovery Source value. If some computer records are left with no discovery source but have a non-empty Correlation ID, these records are from the legacy SCCM plugin. These records must be updated with SG-SCCM as the discovery source.

    Tags:

    Feedback
    On this page

    Previous topic

    Next topic

    • Contact Us
    • Careers
    • Terms of Use
    • Privacy Statement
    • Sitemap
    • © ServiceNow. All rights reserved.

    Release version
    Choose your release version

      Service Graph connector for Microsoft SCCM (2.1.1)

      • Save as PDF Selected topic Topic & subtopics All topics in contents
      • Unsubscribe Log in to subscribe to topics and get notified when content changes.
      • Share this page

      Service Graph connector for Microsoft SCCM (2.1.1)

      Use the Service Graph connector for Microsoft System Center Configuration Manager (SCCM) to pull data from SCCM into your ServiceNow instance.

      The Service Graph connector for Microsoft SCCM imports SCCM data into the ServiceNow® Configuration Management Database (CMDB) application. The integration does not write to the SCCM database. The integration pulls data from computers, processors, operating systems, disks, networks, and software.

      Request apps on the Store

      Visit the ServiceNow Store website to view all the available apps and for information about submitting requests to the store. For cumulative release note information for all released apps, see the ServiceNow Store version history release notes.

      Supported versions

      Supported versions: Microsoft SCCM 1902, 1906, 2002, 2006, and 2010

      Supported ServiceNow versions:
      • Starting with Orlando Patch 7.
      • Starting with Paris Patch 1.

      Use Cases

      The following are examples on how you can use the Service Graph connector for different ServiceNow applications:
      • IT Operations Management (ITOM) Visibility
        • Ability to get visibility into your infrastructure.
        • Detailed hardware and software inventory tracking. The track can be done with or without Software Asset Management (SAM).
        • Ability to detect delta changes for efficient incremental imports from SCCM to NOW.
      • IT Service Management (ITSM)
        • Incidents, problems, and changes on discovered configuration items (CI).
        • Automatic device ownership assignment.
      • Software Asset Management (SAM) and IT Asset Management (ITAM)
        • Tight integration with Software Asset Management Professional and client software distribution workflows.
        • Inventory Software package and installation tracking.
        • Software Usage tracking.
        • License reclamation by detecting removed software.
        • Support for software editions, normalizing publisher information, and normalizing product Information.
        • Support for SCCM Asset Intelligence.

      Guided Setup

      The guided setup for the Service Graph connector for Microsoft SCCM provides an organized sequence of tasks to configure the integration on your instance. To access the guided setup, see Configure Service Graph connector for Microsoft SCCM.

      CMDB Integrations Dashboard

      The Integration Commons for CMDB store app provides a dashboard with a central view of the status, processing results, and processing errors of all installed integrations. You can see metrics for all integration runs. You can filter the view to a specific CMDB integration, a specific time duration, or a specific integration run. For more details about monitoring Microsoft SCCM integrations in the CMDB Integrations Dashboard, see CMDB Integrations Dashboard.

      Data mapping

      Data from the SCCM data sources is mapped and transformed into the ServiceNow CMDB Configuration Item (CI) class definitions using the Robust Transform Engine (RTE). Data is inserted into the ServiceNow CMDB using the Identification and Reconciliation Engine (IRE). The SCCM data sources include the following:
      • SG-SCCM Computer Identity
      • SG-SCCM Disk
      • SG-SCCM Network
      • SG-SCCM Operating System
      • SG-SCCM Processor
      • SG-SCCM Removed Software, ensure the Use last run datetime option is cleared for every run.
      • SG-SCCM Removed Software AI, ensure the Use last run datetime option is cleared for every run.
      • SG-SCCM Software
      • SG-SCCM Software AI
      Note: When you run SG-SCCM Removed Software and SG-SCCM Removed Software AI, the data for SG-SCCM Software and SG-SCCM Software AI is updated.
      When you complete the guided setup, you can configure the integration to periodically pull data from SCCM. The data is loaded into staging tables and then inserted into the following target tables:
      • CI Relationship [cmdb_rel_ci]
      • Computer [cmdb_ci_computer] (required)
      • Disk [cmdb_ci_disk]
      • Network Adapter [cmdb_ci_network_adapter]
      • Serial Number [cmdb_serial_number]
      • Software [cmdb_ci_spkg]
      • Software Installation [cmdb_sam_sw_install]
      • Software Instance [cmdb_software_instance]
      • Software Usage [samp_sw_usage]
      Note: By default, network adapters that are missing an IP address or MAC address are not imported. To include these network adapters in the import, do the following:
      1. Navigate to Service Graph Connector for Microsoft SCCM > Data Sources.
      2. Select SG-SCCM Network.
      3. Remove the where clause from the SQL statement field.
      Related concepts
      • IntegrationHub ETL (1.5.1)
      • Integration Commons for CMDB (2.5.0)
      • Service Graph connector for ExtraHop (2.0.3)
      • Service Graph connector for Microsoft Intune (1.1.1)
      • Service Graph connector for Jamf (2.4.0)
      • Service Graph connector for SolarWinds (2.2.1)
      • Service Graph connector for VMware Workspace ONE UEM (1.0.4)

      Configure Service Graph connector for Microsoft SCCM

      Set up and validate data source connection credentials to import Microsoft SCCM data into your CMDB.

      Before you begin

      Attention: If you are currently using the SCCM plugin, please refer to the following topic, Update from Microsoft SCCM 2016 plugin to the Service Graph connector for Microsoft SCCM.

      To use this Service Graph connector, you need a subscription to a Subscription Unit that is based in the IT Operations Management (ITOM) Visibility application or in the ITOM Discovery application. As defined in the section titled "Managed IT Resource Types" in ServiceNow Subscription Unit Overview, for managed IT resources that are created or modified in the CMDB by this Service Graph connector, but that are not yet managed by ITOM Visibility or ITOM Discovery, these resources will increase Subscription Unit consumption from that application. Review your current Subscription Unit consumption within ITOM Visibility or ITOM Discovery to ensure available capacity.

      Confirm you are in the SCCM application scope instead of a global scope so you are able to save your information.

      Dependencies and requirements:
      • The Integration Commons for CMDB store app, which is automatically installed.
      • The CMDB CI Class Models store app store app, which is automatically installed.
      • ITOM Discovery License plugin (com.snc.itom.discovery.license). You must activate this plugin.
      • Integration - JDBC (com.snc.integration.jdbc)
      • ITOM Licensing plugin (com.snc.itom.license). For more information, see Request Discovery.
      • Compatible with SCCM 2019.
      • Windows MID Server required for access to SCCM environment.
      Roles required:
      • To configure the ServiceNow platform: admin
      • To access SCCM data: User with appropriate access to SCCM database. You must have sufficient credentials to query the SQL Server that contains the SCCM database. Create a SQL Server account in order to connect to the SCCM database on the MID Server to use the data sources.

        Connect to your SCCM SQL Server and configure the following:

        1. Create a new login user name and password for SQL authentication.
        2. Choose the SCCM database that ServiceNow data sources will connect to.
        3. Assign the 'db_datareader' role membership to the new user.

      Procedure

      1. Navigate to Service Graph Connector for Microsoft SCCM > Setup.
      2. On the Getting Started page, select Get Started.
      3. On the Service Graph Connector for Microsoft SCCM page, in the Configure the connection section, select the task Configure SCCM JDBC Connection.
      4. To enter your configuration details to your Microsoft SCCM data sources, complete the following steps:
        1. On the next page, in the Configure SCCM JDBC Connection task section, click Configure.
        2. On the form, fill in the fields.
          Table 1. Microsoft SCCM data source configuration form
          Field Description
          Database name Name of the database.
          User name User name for connecting to the database.
          Password Password for connecting to the database.
          Server Server name or IP address for the database server.
          Use MID Server MID Server that has access to SCCM environment to access the JDBC server, if you require an integrated authentication, then check the 'User Integrated Authentication' check box.
          Instance name Name of the database instance, leave the field empty if you're using a default name.
          Database port Port of the database server, enter 1433 as a default port.
          Connection timeout Number of seconds before the MID server connection cache pool closes the connection and removes it. Zero means no timeout.
          Query timeout Number of seconds the JDBC driver waits for a query to complete. Zero means no timeout. If the timeout runs out, the integration considers the JDBC result inaccessible and places it in an error state.
        3. Click Save.
        4. In the Configure SCCM JBDC Configuration task section, click Mark as Complete.
      5. In the Validate data sources task section, click Configure and complete the following steps:
        1. Review the fields on the Data Source form, which are automatically set.

          There is no need to update any values on this page. The data source is pre-configured to use the SCCM JDBC Connection that you set up in the previous step.

          Table 2. Data Source form
          Field Description
          Name Unique name of this data source.
          Import set table label Label of the table that will be created for this data source.
          Import set table name Name of the table that will be created for this data source.
          Type Data storage type of the data to be imported.
          Use MID Server MID server to use to access the JDBC server.
          Format Format of the data file.
          Instance name Named instance for SQLServer.
          Database name Name of the database.
          Database port Port of the database.
          Application Application containing this record.
          Use integrated authentication Windows JDBC integrated authentication.
          User name User name for connecting to the JDBC server.
          Password Password for the JDBC server.
          Server Server name for the JDBC connection.
          Query Query type. Query all data from a table or run a specific SQL statement.
          Query timeout Number of seconds the JDBC driver will wait for a query to complete. Zero means no timeout. If timeout is exceeded, the integration considers the JDBC result inaccessible and places it in an error state.
          Connection timeout Number of seconds before the MID server connection cache pool closes the connection and removes it. Zero means no timeout.
          SQL statement SQL statement to extract the desired data from the database.
          Use last run datetime Controls the amount of data that is retrieved from a database during an import run. If unselected, then all rows in the table specified are imported, every time. You might want to use this setting if this is a one-time import, or if all the data in the target table is new. If selected, two additional fields appear, enabling you to select a datetime value to limit imported data to delta values only.
        2. Click the Test Load 20 Records related link to validate your data sources.
          Note: If the completion code is Success, mark this step as complete. If the completion code is Error, there is an error in the SCCM JDBC Connection that you must fix.
        3. In the Help sidebar, click Back to Guided Setup.
        4. In the Validate data sources task section, click Mark as Complete.
      6. In the Reset 'Last run datetime' in test load source task section, click Configure and complete the following steps:
        1. Select the Last run datetime field and delete the value.
        2. Click Update to save the change and return to the Configure the connection page.
      7. On the left side bar, click the Set up scheduled import jobs button.
      8. On the Service Graph Connector for Microsoft SCCM page, in the Set up scheduled import jobs section, select the task Configure scheduled jobs.
        1. In the Configure scheduled jobs task section, click Configure.
        2. On the form, fill in the fields.
          Table 3. Scheduled Data Import form
          Field Description
          Name Name of the scheduled job.
          Data source Data source record that defines the data to import.
          Run as Option to run the scheduled job with the credentials of the specified user.
          Active Option to activate the scheduled job. Select this option.
          Concurrent Import Function that loads the data from multiple import sets. The function then processes and transforms the data concurrently.
          Partition Method Partition method for the concurrent import set.
          Partition Size Import set size for early scheduling.
          Execute pre-import script Option to specify a script to run before the import is performed.
          Execute post-import script Option to specify a script to run after the import is performed.
          Application Application that contains this scheduled job.
          Run Frequency of running the import.
          Conditional Conditions under which this job is executed.
        3. Click Execute Now.
        4. In the Configure scheduled jobs task section, click Mark as Complete.

      Update from Microsoft SCCM 2016 plugin to the Service Graph connector for Microsoft SCCM

      Run a script and pull records to update from the Microsoft SCCM 2016 plugin to the Service Graph connector for Microsoft SCCM.

      Before you begin

      If you are upgrading to the Service Graph connector for Microsoft SCCM, the following steps are mandatory and must be executed in any instance with an existing install of the Microsoft SCCM 2016 plugin (or earlier version of the plugin).

      Note: The Service Graph connector for Microsoft SCCM is an independent implementation that does not reuse any components from the Microsoft SCCM 2016 plugin.

      About this task

      The Service Graph connector for Microsoft SCCM is a successor to the Microsoft SCCM 2016 plugin. If you already have the Microsoft SCCM 2016 plugin (or earlier version) installed in your instance, you must follow these steps to enable the successful transition from using the SCCM plugin to using the Service Graph connector.

      When the Service Graph connector for Microsoft SCCM is installed in an instance, you must no longer run any components from the Microsoft SCCM 2016 plugin, including Data Sources and Scheduled Data Imports. The SCCM 2016 plugin Scheduled Data Imports must be disabled. The Service Graph connector for Microsoft SCCM installs a new set of SG-SCCM Data Sources and Scheduled Data Imports.

      When you execute the Service Graph connector components, your existing CMDB data created by the SCCM 2016 plugin becomes managed and maintained by Service Graph connector for Microsoft SCCM.

      Attention: This upgrade process should be performed and validated in a non-production or test instance that is based on a recent clone of the customer production instance. Failure to first validate upgrade in a non-production instance may result in unexpected outcomes and possible data loss or corruption.

      Any customizations to the SCCM 2016 plugin will not automatically migrate and would have to be reimplemented in the Service Graph connector for Microsoft SCCM, such as through the use of IntegrationHub-ETL.

      Procedure

      1. Deactivate the scheduled imports from the older SCCM plugin. For more information on how to deactivate scheduled imports, see Upgrade the SCCM integration version.
      2. To run the fix scripts, complete the following steps:
        1. Type in Fix Scripts.
        2. In the application scope, run the fix script with the name: SCCM Add Dependent Relationships.
          Note: If there are no Disk or Network Adapter records in the CMDB instance, click Proceed or have it run in the background.
        3. Select Active to activate the script then Update.
        4. When the script is finished, confirm that there are relationship records for Disk and Network Adapter CIs created in the CI Relationship [cmdb_rel_ci] table.
      3. Execute a full pull of the computer records using the Service Graph connector for Microsoft SCCM before running software data or any other data source. To pull the records, complete the following steps:
        1. Navigate to Service Graph Connector Microsoft SCCM > Data Sources.
        2. In the Data Sources list, select the SG-SCCM Computer Identity data source.
        3. Confirm the Last run datetime field is empty. If not, edit the data source and clear the field then select Update.
        4. Navigate to Service Graph Connector Microsoft SCCM > Import Schedules.
        5. In the Scheduled Data Imports list, select the SG-SCCM Computer Identity scheduled data import and select Execute Now.
        6. After completing the steps, verify all the computer records with a non-empty Correlation ID have a Discovery Source value. If some computer records are left with no discovery source but have a non-empty Correlation ID, these records are from the legacy SCCM plugin. These records must be updated with SG-SCCM as the discovery source.

      Tags:

      Feedback

          Share this page

          Got it! Feel free to add a comment
          To share your product suggestions, visit the Idea Portal.
          Please let us know how to improve this content

          Check any that apply

          To share your product suggestions, visit the Idea Portal.
          Confirm

          We were unable to find "Coaching" in Jakarta. Would you like to search instead?

          No Yes
          • Contact Us
          • Careers
          • Terms of Use
          • Privacy Statement
          • Sitemap
          • © ServiceNow. All rights reserved.

          Subscribe Subscribed Unsubscribe Last updated: Tags: January February March April May June July August September October November December No Results Found Versions Search preferences successfully updated My release version successfully updated My release version successfully deleted An error has occurred. Please try again later. You have been unsubscribed from all topics. You are now subscribed to and will receive notifications if any changes are made to this page. You have been unsubscribed from this content Thank you for your feedback. Form temporarily unavailable. Please try again or contact  docfeedback@servicenow.com  to submit your comments. The topic you requested does not exist in the release. You were redirected to a related topic instead. The available release versions for this topic are listed There is no specific version for this documentation. Explore products Click to go to the page. Release notes and upgrades Click to open the dropdown menu. Delete Remove No selected version Reset This field is required You are already subscribed to this topic Attach screenshot The file you uploaded exceeds the allowed file size of 20MB. Please try again with a smaller file. Please complete the reCAPTCHA step to attach a screenshot
          Log in to personalize your search results and subscribe to topics
          No, thanks Login