WEBVTT

1
00:00:00.000 --> 00:00:02.310
In this lesson, we are going to learn

2
00:00:02.310 --> 00:00:05.070
about change and configuration management.

3
00:00:05.070 --> 00:00:07.020
Change and configuration management

4
00:00:07.020 --> 00:00:09.090
involves structured processes

5
00:00:09.090 --> 00:00:11.250
to manage system modifications,

6
00:00:11.250 --> 00:00:14.580
ensuring they're carried out, efficiently, approved,

7
00:00:14.580 --> 00:00:16.470
and tracked accurately

8
00:00:16.470 --> 00:00:17.460
Critical aspects

9
00:00:17.460 --> 00:00:20.220
of the change and configuration management process,

10
00:00:20.220 --> 00:00:23.520
our inventory, the asset management lifecycle,

11
00:00:23.520 --> 00:00:28.110
and the use of a Configuration Management Database, or CMDB.

12
00:00:28.110 --> 00:00:30.060
Let's dive deeper into each

13
00:00:30.060 --> 00:00:32.970
of the change and configuration management elements.

14
00:00:32.970 --> 00:00:35.490
First, we have inventory.

15
00:00:35.490 --> 00:00:39.030
Inventory is crucial to change and configuration management

16
00:00:39.030 --> 00:00:42.270
because it provides a complete and accurate record

17
00:00:42.270 --> 00:00:45.720
of all hardware, software, and other assets

18
00:00:45.720 --> 00:00:47.640
within an organization.

19
00:00:47.640 --> 00:00:50.400
Knowing exactly what assets are in use,

20
00:00:50.400 --> 00:00:53.520
where they are located, and their current configuration

21
00:00:53.520 --> 00:00:56.370
allows IT teams to assess the impact

22
00:00:56.370 --> 00:00:58.080
of any proposed changes.

23
00:00:58.080 --> 00:01:00.690
Knowing the impact will help prevent disruptions

24
00:01:00.690 --> 00:01:04.020
or unexpected failures during updates or maintenance.

25
00:01:04.020 --> 00:01:06.600
For example, if an organization is planning

26
00:01:06.600 --> 00:01:08.460
to roll out a system upgrade,

27
00:01:08.460 --> 00:01:10.410
having a precise inventory

28
00:01:10.410 --> 00:01:13.590
ensures that no critical systems are overlooked

29
00:01:13.590 --> 00:01:16.290
and that upgrades are applied uniformly.

30
00:01:16.290 --> 00:01:18.900
And inventory also helps with troubleshooting

31
00:01:18.900 --> 00:01:20.940
as teams can quickly identify

32
00:01:20.940 --> 00:01:24.330
and isolate issues related to specific assets.

33
00:01:24.330 --> 00:01:27.390
An example of a tool used to manage inventory

34
00:01:27.390 --> 00:01:30.690
is the Microsoft System Center Configuration Manager

35
00:01:30.690 --> 00:01:32.640
or SCCM.

36
00:01:32.640 --> 00:01:35.670
The Microsoft Systems Center Configuration Manager

37
00:01:35.670 --> 00:01:38.400
allows IT teams to track and manage

38
00:01:38.400 --> 00:01:40.800
both hardware and software assets

39
00:01:40.800 --> 00:01:44.220
by collecting detailed information about hardware, such as

40
00:01:44.220 --> 00:01:48.510
device specifications, configurations, and locations,

41
00:01:48.510 --> 00:01:52.020
and monitor what software applications are installed,

42
00:01:52.020 --> 00:01:55.440
including their versions and licensing details.

43
00:01:55.440 --> 00:01:56.430
Additionally,

44
00:01:56.430 --> 00:01:59.700
the Microsoft System Center Configuration Manager

45
00:01:59.700 --> 00:02:03.270
allows IT teams to push updates, patches,

46
00:02:03.270 --> 00:02:05.610
and new software across devices,

47
00:02:05.610 --> 00:02:09.420
ensuring that systems are consistently up to date.

48
00:02:09.420 --> 00:02:12.900
Second, we have the Asset Management Lifecycle.

49
00:02:12.900 --> 00:02:15.450
The Asset Management Lifecycle is crucial

50
00:02:15.450 --> 00:02:17.400
to change and configuration management

51
00:02:17.400 --> 00:02:21.420
because it ensures that all assets are tracked, maintained,

52
00:02:21.420 --> 00:02:24.450
and updated in an organized and controlled manner

53
00:02:24.450 --> 00:02:26.070
throughout their lifespan.

54
00:02:26.070 --> 00:02:28.740
The five steps of the lifecycle are,

55
00:02:28.740 --> 00:02:31.110
planning and procurement, deployment,

56
00:02:31.110 --> 00:02:34.200
utilization and maintenance, asset tracking,

57
00:02:34.200 --> 00:02:36.750
and decommissioning and disposal.

58
00:02:36.750 --> 00:02:39.180
These five steps allow organizations

59
00:02:39.180 --> 00:02:42.540
to manage assets methodically, ensuring that changes

60
00:02:42.540 --> 00:02:44.910
or updates are applied efficiently

61
00:02:44.910 --> 00:02:47.460
and without disrupting operations.

62
00:02:47.460 --> 00:02:50.370
For example, in the planning and procurement phase,

63
00:02:50.370 --> 00:02:52.380
organizations acquire assets

64
00:02:52.380 --> 00:02:53.940
that align with their needs,

65
00:02:53.940 --> 00:02:56.910
laying the groundwork for effective configuration.

66
00:02:56.910 --> 00:02:58.110
In the deployment phase,

67
00:02:58.110 --> 00:03:00.630
assets are integrated into the environment,

68
00:03:00.630 --> 00:03:03.840
ensuring they work well with existing systems.

69
00:03:03.840 --> 00:03:06.210
During the utilization and maintenance phase,

70
00:03:06.210 --> 00:03:08.310
regular updates and patches

71
00:03:08.310 --> 00:03:11.220
keep assets functional and secure.

72
00:03:11.220 --> 00:03:12.720
The asset tracking phase

73
00:03:12.720 --> 00:03:16.470
ensures that changes are documented and properly managed.

74
00:03:16.470 --> 00:03:19.860
And finally, the decommissioning and disposal phase

75
00:03:19.860 --> 00:03:23.430
enables the smooth retirement of outdated assets.

76
00:03:23.430 --> 00:03:26.250
The ServiceNow IT Asset Management Tool

77
00:03:26.250 --> 00:03:30.660
is an example of a tool used to manage asset lifecycle.

78
00:03:30.660 --> 00:03:34.320
Third, we have a Configuration Management Database,

79
00:03:34.320 --> 00:03:36.060
or CMDB.

80
00:03:36.060 --> 00:03:38.250
A Configuration Management Database

81
00:03:38.250 --> 00:03:40.560
is a centralized database that keeps track

82
00:03:40.560 --> 00:03:45.270
of all Configuration Items or CIs, within an organization.

83
00:03:45.270 --> 00:03:49.380
A Configuration Item is any asset, component or service

84
00:03:49.380 --> 00:03:52.770
that needs to be managed to deliver IT services.

85
00:03:52.770 --> 00:03:56.280
Configuration Items include servers, desktops,

86
00:03:56.280 --> 00:03:58.800
mobile phones, software databases,

87
00:03:58.800 --> 00:04:01.050
and facility infrastructure.

88
00:04:01.050 --> 00:04:03.090
The Configuration Management Database

89
00:04:03.090 --> 00:04:05.040
maintains detailed information

90
00:04:05.040 --> 00:04:08.040
about how each configuration item is set up,

91
00:04:08.040 --> 00:04:12.000
connected or used at a specific point in time.

92
00:04:12.000 --> 00:04:15.870
Crucially, the configuration management database also tracks

93
00:04:15.870 --> 00:04:19.500
the relationships between different configuration items

94
00:04:19.500 --> 00:04:22.410
and how they connect to specific services.

95
00:04:22.410 --> 00:04:25.410
Understanding configuration item relationships

96
00:04:25.410 --> 00:04:27.390
allows IT teams to predict

97
00:04:27.390 --> 00:04:30.120
how changes to one configuration item

98
00:04:30.120 --> 00:04:32.670
may impact other configuration items

99
00:04:32.670 --> 00:04:34.770
and the services they support.

100
00:04:34.770 --> 00:04:38.430
Anytime a configuration items configuration changes,

101
00:04:38.430 --> 00:04:41.670
whether it's a software update, hardware replacement,

102
00:04:41.670 --> 00:04:43.560
or network modification,

103
00:04:43.560 --> 00:04:45.840
the configuration management database

104
00:04:45.840 --> 00:04:49.170
must be updated to reflect the new status.

105
00:04:49.170 --> 00:04:51.420
This ensures network stability

106
00:04:51.420 --> 00:04:54.630
and enables efficient IT service management

107
00:04:54.630 --> 00:04:58.770
by helping IT teams understand the interdependencies

108
00:04:58.770 --> 00:05:00.690
and manage potential risk.

109
00:05:00.690 --> 00:05:04.230
An example of a configuration database management tool

110
00:05:04.230 --> 00:05:08.070
is the ServiceNow Configuration Management Database.

111
00:05:08.070 --> 00:05:10.980
ServiceNow's Configuration Management Database

112
00:05:10.980 --> 00:05:13.620
allows organizations to track and manage

113
00:05:13.620 --> 00:05:15.630
all their configuration items

114
00:05:15.630 --> 00:05:19.860
and the relationships in one centralized location.

115
00:05:19.860 --> 00:05:23.160
So remember, change and configuration management

116
00:05:23.160 --> 00:05:25.920
is essential in managing system modifications,

117
00:05:25.920 --> 00:05:29.490
ensuring that changes are approved and tracked accurately.

118
00:05:29.490 --> 00:05:31.920
Key elements in this process include,

119
00:05:31.920 --> 00:05:35.130
inventory, the asset management lifecycle,

120
00:05:35.130 --> 00:05:37.980
and the configuration management database.

121
00:05:37.980 --> 00:05:41.580
First, an accurate inventory provides a complete record

122
00:05:41.580 --> 00:05:44.010
of all hardware and software assets,

123
00:05:44.010 --> 00:05:47.700
allowing IT teams to assess the impact of changes

124
00:05:47.700 --> 00:05:51.330
and avoid missing critical systems during updates.

125
00:05:51.330 --> 00:05:54.450
Next, the asset management lifecycle ensures

126
00:05:54.450 --> 00:05:58.470
that assets are tracked from acquisition through disposal,

127
00:05:58.470 --> 00:06:02.070
helping organizations focus their efforts on active assets

128
00:06:02.070 --> 00:06:05.010
and retire outdated assets efficiently.

129
00:06:05.010 --> 00:06:08.340
And finally, the Configuration Management Database

130
00:06:08.340 --> 00:06:10.200
tracks Configuration Items

131
00:06:10.200 --> 00:06:13.620
and the relationships to other Configuration Items.

132
00:06:13.620 --> 00:06:17.850
This ensures an understanding of how changes to one system

133
00:06:17.850 --> 00:06:19.860
may impact other systems

134
00:06:19.860 --> 00:06:23.013
preventing potential enterprise disruption.