Skip to main content
Configuration Items in Service Desk

Configuration Items in Service Desk

$249.00
Your guarantee:
30-day money-back guarantee — no questions asked
Who trusts this:
Trusted by professionals in 160+ countries
When you get access:
Course access is prepared after purchase and delivered via email
How you learn:
Self-paced • Lifetime updates
Toolkit Included:
Includes a practical, ready-to-use toolkit containing implementation templates, worksheets, checklists, and decision-support materials used to accelerate real-world application and reduce setup time.
Adding to cart… The item has been added

This curriculum spans the full operational lifecycle of configuration items in a service desk environment, equivalent in scope to a multi-workshop program for designing, populating, governing, and integrating a CMDB across IT operations, change management, and security functions.

Module 1: Defining and Scoping Configuration Items (CIs)

  • Selecting which IT assets qualify as CIs based on business criticality, lifecycle management needs, and support dependencies.
  • Establishing ownership boundaries for CI data between IT operations, asset management, and application support teams.
  • Determining the granularity of CI records—whether to model individual servers or logical clusters—based on operational impact and monitoring requirements.
  • Aligning CI classification with existing ITIL frameworks while adapting categories to reflect organizational infrastructure patterns.
  • Resolving conflicts between automated discovery tools and manual documentation by defining authoritative data sources for CI attributes.
  • Documenting exceptions where shadow IT assets are temporarily excluded from the CMDB due to compliance or security constraints.

Module 2: Data Modeling and CI Hierarchy Design

  • Structuring parent-child relationships between CIs such as data center > rack > server > virtual machine > application instance.
  • Choosing between flat and hierarchical models based on change impact analysis requirements and tool performance limitations.
  • Defining custom attributes for specialized CIs like network firewalls or SaaS applications to support incident and change workflows.
  • Implementing inheritance rules for attributes like support group or SLA across related CIs in a dependency chain.
  • Managing polymorphic relationships where a single CI (e.g., load balancer) serves multiple environments (production, staging).
  • Validating model changes in a non-production CMDB instance before promoting to production to prevent workflow disruptions.

Module 3: CI Discovery and Data Population

  • Configuring agent-based vs. agentless discovery methods based on OS support, security policies, and network segmentation.
  • Handling discovery failures in air-gapped environments by implementing manual import processes with audit trails.
  • Mapping raw discovery output (e.g., SNMP data) to standardized CI fields using transformation rules and normalization scripts.
  • Resolving duplicate CI records caused by IP reassignments or hostname changes through reconciliation key policies.
  • Setting discovery frequency intervals based on CI volatility—daily for cloud instances, monthly for static network gear.
  • Integrating third-party inventory systems (e.g., MDM, cloud consoles) into the CI population workflow using API-based sync jobs.

Module 4: CI Lifecycle and State Management

  • Defining lifecycle states (planned, live, decommissioned) and enforcing state transitions through change control processes.
  • Triggering automated notifications when a CI enters end-of-support or end-of-life status based on vendor data feeds.
  • Coordinating CI retirement with asset disposal workflows to ensure financial, security, and compliance alignment.
  • Handling rollback scenarios where a reverted change requires restoring a CI to a prior configuration state.
  • Managing temporary CI states during migrations, such as "migrating" or "in validation," to prevent erroneous incident routing.
  • Archiving inactive CIs instead of deletion to preserve historical incident and change records for audit purposes.

Module 5: CI Relationships and Dependency Mapping

  • Validating application-to-infrastructure dependencies by correlating CI relationships with actual traffic flow data from APM tools.
  • Identifying indirect dependencies (e.g., shared authentication service) that are not reflected in direct CI links.
  • Managing bidirectional relationships where changes to a database affect an app, and app usage patterns affect database performance.
  • Using dependency maps to scope impact assessments during change advisory board (CAB) reviews.
  • Handling circular dependencies in CI graphs that can cause infinite loops in impact analysis algorithms.
  • Updating relationship metadata (e.g., dependency strength, criticality) based on post-incident review findings.

Module 6: Integration with Incident, Change, and Problem Management

  • Enabling automatic CI population in incident tickets based on reported hostname, IP, or service identifier.
  • Requiring change requests to reference affected CIs and validate relationships before approval workflows proceed.
  • Using CI change history to identify recurring failure patterns during problem management root cause analysis.
  • Blocking high-risk changes on CIs marked as critical or under warranty review without additional approvals.
  • Correlating CI update timestamps with incident spikes to detect change-induced outages.
  • Configuring notifications to CI owners when related incidents exceed predefined volume thresholds.

Module 7: CMDB Governance and Data Integrity

  • Establishing data stewardship roles with clear accountability for CI accuracy in each business unit or domain.
  • Implementing automated data quality checks—such as mandatory fields, format validation, and stale record detection.
  • Conducting quarterly CI audits by comparing CMDB records against discovery logs and asset registers.
  • Defining reconciliation policies for conflicts between authoritative sources (e.g., procurement system vs. discovery tool).
  • Managing access controls to prevent unauthorized modifications to CI records, especially in shared service environments.
  • Documenting and publishing CMDB SLAs—such as data freshness and completeness targets—for stakeholder transparency.

Module 8: Reporting, Metrics, and Continuous Improvement

  • Generating compliance reports for software licensing using CI data on installed applications and host entitlements.
  • Measuring CMDB accuracy by sampling incident records and verifying referenced CIs exist and are correctly classified.
  • Tracking CI reconciliation success rates across discovery tools to identify integration gaps or configuration drift.
  • Using CI volatility metrics to prioritize stabilization efforts in high-change environments.
  • Reporting on unmanaged CIs to identify shadow IT growth and inform security remediation initiatives.
  • Reviewing CI-related process bottlenecks—such as delayed discovery syncs—and adjusting tooling or staffing accordingly.
!