Microsoft System Center Configuration Manager (SCCM) can now be integrated with an 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 it is now possible to set up a one-directional sync using time-based rules that can pull the information from SCCM into and automatically map the relationships between SCCM child and parent assets.
The SCCM integration is managed in'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 a KB based on the ITIL template. For more information and to familiarize yourself with the ITIL template design, see ITIL Documentation. SCCM does not currently work with KBs based on the Standard template.
At this point, the sync is configured. You just need to run it.
There are several possible ways to run the SCCM synchronization, but in most cases, the system is set up with a time-based rule that runs the SCCM sync at scheduled intervals.
To create a time-based rule to synchronize SCCM:
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 remains in the knowledgebase with the last updated date in the "Last SCCM Sync" field. This should be reviewed for your requirements and then enabled.
At this point, your knowledgebase should 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 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 has a set of internal components and software, and uses 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 is usually a parent, such as a computer containing child components and software.
The deployment adds 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:
|
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:
Qualcomm Atheros AR8171/8175 PCI-E Gigabit Ethernet Controller (NDIS 6.30)
.Kingston RAM - 16777222-2-10.
Monitor - 16777222-2-6
.Related articles |