Microsoft SCCM Integration
Microsoft System Center Configuration Manager (SCCM) can now be integrated with an Agiloft knowledgebase, making it possible to monitor and manage the assets in an ITIL-based system. For more information about SCCM, see https://www.microsoft.com/en-us/cloud-platform/system-center-configuration-manager. In Agiloft it is now possible to set up a one-directional sync using time-based rules that can pull the information from SCCM into Agiloft and automatically map the relationships between SCCM child and parent assets.
The SCCM integration is managed in Agiloft's ITIL platform, and all monitored assets are identified as Configuration Items, with their CI Types and Subtypes, and relationship diagrams set up between child and parent assets, making it easy to identify all software and hardware components of a parent device.
The deployment must use an ITIL KB, and it will be beneficial to familiarize yourself with the configuration of the ITIL system. For more information, see ITIL Documentation. At present, it will not work in the standard system.
Deploy the SCCM Integration
- In the knowledgebase, navigate to Setup > Integrations and select SCCM Integration > Deploy.
- A dialog will open, asking you to confirm the deployment and noting that it will take some time to complete due to the large number of new fields and rules being added. Click OK to confirm.
- See below for more details on some of the elements that will be added during this step.
- After the deployment, the user will be directed automatically to the SCCM Sync wizard.
Configure the SCCM Sync Wizard
- In the SCCM Sync wizard, the SCCM sync type will already be chosen. Add a name and if necessary configure the remote proxy in case the instance of SCCM is outside your knowledgebase firewalls. Click Next.
- Add the Database Host Name, Database Port, Database Name, username and password.
- Click Next to proceed. The system will check the database connection and if valid, will open the Mapping tab.
- In the Mapping tab, scroll to the Configuration Item table and click Map. The Field Mapping screen will open with all the initial field mappings preconfigured.
- Check that the field mappings are correct, and add any if needed for your implementation.
- After ensuring that the field mappings are correct, click Finish, then Next.
- In the Relation Mapping tab, ensure that the Configuration Item linked field set for Parent and child ID is added and click Next.
- Select how you wish to run the sync - Manual will enable you to run it as an action from the Configuration Items table view.
- Click Finish. At this point the sync will be configured and need to run.
Run the Sync
There are several possible ways to run the SCCM synchronization, but it is most likely that you will want to set up a time-based rule to run at scheduled intervals. To create a time-based rule to synchronize SCCM:
- In the Configuration Items table setup, create a new Rule. For more information, see Rules.
- In the Rule Type tab, select "At selected time intervals".
- In the Condition tab, select "Run once per scheduled time interval".
- In the Schedule tab, set an appropriate interval for your needs.
- In the Action tab, click the Create Sync Action button.
- Add a name and description for the sync.
- In the External System ID field, do a lookup to find and import the SCCM sync ID.
- Save the rule.
Removing Assets from SCCM Sync
The rule "TB: Set Missing CI to Removed and deactivate CI Relationships - change filter as needed" identifies assets that have not been updated by the sync in two weeks, and changes their status to Removed. By default this rule finds assets that have not been updated for two weeks and that have a Status of Active, and changes the Status to Removed and deactivates its CI Relationships. The asset will remain in the knowledgebase with the last updated date in the "Last SCCM Sync" field. This should be reviewed for your requirements and then enabled.
Structure of an SCCM Integrated Knowledgebase
At this point your knowledgebase will be synchronized with the assets from SCCM, and you can check to ensure that all assets are correctly represented and have established the necessary CI Relationships between the parent and child items.
CI Relationships and Relationship Diagrams in SCCM
CI Relationships and relationship diagrams are added during the creation rule "CI Create Actions", with the action "Convert to CI Parent-Child Relationship". This establishes the link between the parent asset and its children. For example, a laptop will have a set of internal components and software, and will use networked equipment such as IP phones and printers. The CI Relationship table enforces this link, and the relationship diagram field type illustrates it and allows you to navigate between items in one system. For more information, see: Relationship Diagram Fields. An asset with CI Subtype of System will most likely be a parent, such as a computer containing child components and software.
Elements Added in SCCM Deployment
The deployment will add a new entity set consisting of SCCM fields primarily to the Configuration Items table, a set of rules and actions to create the related records and CI Relationships, followed by a set of new CI Subtypes.
The following CI Subtypes are added by default from the entity set, but if further subtypes are pulled in during sync, they will also be mapped in the CI Subtypes table:
- Software License
- USB Controller
- System Device
- Sound Device
- Software Installed
- Server Feature
- SCSI Controller
- Printer Device
- Printer Configuration
- PCMCIA Controller
- Network Client
- Network Adapter Configuration
- Logical Disk
- IDE Controller
- Encryptable Disk
- Device Info
- Device Driver
- Config Manager Client
- 1394 Controller
- Pointing Device
The new subtypes are created using a conversion action "Create new CI Subtype from SCCM" as part of the initial creation rule.
CI Name is an important identifying field for SCCM assets. This is added during the creation rule, using the following if-then clause:
This clause constructs the CI name in the following way:
- If SCCM provides a CI Name, it will be used by default. For example,
Qualcomm Atheros AR8171/8175 PCI-E Gigabit Ethernet Controller (NDIS 6.30).
- If SCCM does not provide a CI name but does contain a Manufacturer, the CI Name is defined as Manufacturer name + the CI Subtype + the Asset ID. For example,
Kingston RAM - 16777222-2-10.
- If SCCM does not provide a CI Name or Manufacturer, the CI Name is defined as the CI Subtype + the Asset ID. For example,
Monitor - 16777222-2-6.