WEBVTT

1.1
00:00:00.000 --> 00:00:05.600
<v Speaker 1>A configuration management database, or CMDB, is the master inventory of systems and services.

1.2
00:00:05.600 --> 00:00:12.800
<v Speaker 2>It lists configuration items and how they depend on each other so support teams have the full picture.

2.1
00:00:12.800 --> 00:00:17.600
<v Speaker 1>Start by identifying key CIs such as servers, applications and network devices.

2.2
00:00:17.600 --> 00:00:22.800
<v Speaker 2>Pull in attributes from source systems and link them together to show relationships.

2.3
00:00:22.800 --> 00:00:27.600
<v Speaker 1>For example, the "web01" server might depend on the "db01" database service.

3.1
00:00:27.600 --> 00:00:37.999
<v Speaker 1>Building the CMDB focuses attention on a concrete part of the work. Identify key configuration items, Populate attributes from trusted sources, and Map relationships between CIs.

3.2
00:00:37.999 --> 00:00:51.199
<v Speaker 2>In practice, ask who owns the work, what evidence proves it happened, and what handoff comes next. Use the supporting details as a checklist: Populate attributes from trusted sources; Map relationships between CIs.

4.1
00:00:51.199 --> 00:00:55.199
<v Speaker 1>Change requests should list the configuration items they will modify.

4.2
00:00:55.199 --> 00:01:01.199
<v Speaker 2>After approval, update those CI records and compare discovery results to catch any unplanned drift.

5.1
00:01:01.199 --> 00:01:04.399
<v Speaker 1>Keeping the CMDB accurate is a continual task.

5.2
00:01:04.399 --> 00:01:10.399
<v Speaker 2>Automate discovery and update records after every approved change, then audit regularly to find gaps.

5.3
00:01:10.399 --> 00:01:15.999
<v Speaker 1>Compare the observed state from discovery tools against the approved configuration to detect drift.

6.1
00:01:15.999 --> 00:01:20.799
<v Speaker 1>Sometimes discovery shows a system in a state the CMDB never approved.

6.2
00:01:20.799 --> 00:01:27.199
<v Speaker 2>This can come from emergency fixes, admins bypassing change control,  or forgetting to remove retired equipment.

6.3
00:01:27.199 --> 00:01:33.999
<v Speaker 1>When observed and authorised states diverge, troubleshooting and audits slow down because teams can't trust the data.

7.1
00:01:33.999 --> 00:01:37.599
<v Speaker 1>A well-maintained CMDB accelerates incident troubleshooting and change planning.

7.2
00:01:37.599 --> 00:01:42.799
<v Speaker 2>It reduces surprises from hidden dependencies and becomes your single source of truth.