In this lesson, we are going to learn
about change and configuration management.
Change and configuration management
involves structured processes
to manage system modifications,
ensuring they're carried out, efficiently, approved,
and tracked accurately
Critical aspects
of the change and configuration management process,
our inventory, the asset management lifecycle,
and the use of a Configuration Management Database, or CMDB.
Let's dive deeper into each
of the change and configuration management elements.
First, we have inventory.
Inventory is crucial to change and configuration management
because it provides a complete and accurate record
of all hardware, software, and other assets
within an organization.
Knowing exactly what assets are in use,
where they are located, and their current configuration
allows IT teams to assess the impact
of any proposed changes.
Knowing the impact will help prevent disruptions
or unexpected failures during updates or maintenance.
For example, if an organization is planning
to roll out a system upgrade,
having a precise inventory
ensures that no critical systems are overlooked
and that upgrades are applied uniformly.
And inventory also helps with troubleshooting
as teams can quickly identify
and isolate issues related to specific assets.
An example of a tool used to manage inventory
is the Microsoft System Center Configuration Manager
or SCCM.
The Microsoft Systems Center Configuration Manager
allows IT teams to track and manage
both hardware and software assets
by collecting detailed information about hardware, such as
device specifications, configurations, and locations,
and monitor what software applications are installed,
including their versions and licensing details.
Additionally,
the Microsoft System Center Configuration Manager
allows IT teams to push updates, patches,
and new software across devices,
ensuring that systems are consistently up to date.
Second, we have the Asset Management Lifecycle.
The Asset Management Lifecycle is crucial
to change and configuration management
because it ensures that all assets are tracked, maintained,
and updated in an organized and controlled manner
throughout their lifespan.
The five steps of the lifecycle are,
planning and procurement, deployment,
utilization and maintenance, asset tracking,
and decommissioning and disposal.
These five steps allow organizations
to manage assets methodically, ensuring that changes
or updates are applied efficiently
and without disrupting operations.
For example, in the planning and procurement phase,
organizations acquire assets
that align with their needs,
laying the groundwork for effective configuration.
In the deployment phase,
assets are integrated into the environment,
ensuring they work well with existing systems.
During the utilization and maintenance phase,
regular updates and patches
keep assets functional and secure.
The asset tracking phase
ensures that changes are documented and properly managed.
And finally, the decommissioning and disposal phase
enables the smooth retirement of outdated assets.
The ServiceNow IT Asset Management Tool
is an example of a tool used to manage asset lifecycle.
Third, we have a Configuration Management Database,
or CMDB.
A Configuration Management Database
is a centralized database that keeps track
of all Configuration Items or CIs, within an organization.
A Configuration Item is any asset, component or service
that needs to be managed to deliver IT services.
Configuration Items include servers, desktops,
mobile phones, software databases,
and facility infrastructure.
The Configuration Management Database
maintains detailed information
about how each configuration item is set up,
connected or used at a specific point in time.
Crucially, the configuration management database also tracks
the relationships between different configuration items
and how they connect to specific services.
Understanding configuration item relationships
allows IT teams to predict
how changes to one configuration item
may impact other configuration items
and the services they support.
Anytime a configuration items configuration changes,
whether it's a software update, hardware replacement,
or network modification,
the configuration management database
must be updated to reflect the new status.
This ensures network stability
and enables efficient IT service management
by helping IT teams understand the interdependencies
and manage potential risk.
An example of a configuration database management tool
is the ServiceNow Configuration Management Database.
ServiceNow's Configuration Management Database
allows organizations to track and manage
all their configuration items
and the relationships in one centralized location.
So remember, change and configuration management
is essential in managing system modifications,
ensuring that changes are approved and tracked accurately.
Key elements in this process include,
inventory, the asset management lifecycle,
and the configuration management database.
First, an accurate inventory provides a complete record
of all hardware and software assets,
allowing IT teams to assess the impact of changes
and avoid missing critical systems during updates.
Next, the asset management lifecycle ensures
that assets are tracked from acquisition through disposal,
helping organizations focus their efforts on active assets
and retire outdated assets efficiently.
And finally, the Configuration Management Database
tracks Configuration Items
and the relationships to other Configuration Items.
This ensures an understanding of how changes to one system
may impact other systems
preventing potential enterprise disruption.