Configuration Item Life Cycle - Virtual Servers

Single-character identifier indicating the environment in which the server will be operating. See the Environment Classification Codes table below for a list of valid codes for this segment.

Service identifier provided by the client using the server. This is usually something meaningful to the client to help identify the purpose of the server.

Sequential two-digit number beginning with "00" to prevent duplication of names.

Phase 1: Server Requested & Approved
During this phase, a need for the server is determined and a decision is made to deploy a VM rather than a physical server. The specifications for the VM are determined, and a new VM is requested from the appropriate OIT team. This phase ends when all internal documentation is complete and a request for the new VM has been submitted and the new VM is ready to be configured.

If ServiceNow will be used to track incidents, changes, or task assignments during the initial steps then a CI will be required. Otherwise, a CI is not required until the VM is ready to be configured.

Phase 2: VM Configured & Tested
The server must be compared to the original specifications to confirm that it matches the original requirements. Any required configuration is done during this phase. This includes operating system software, application software and services, databases, network connections, user definition and security rules, and arrangements made for backups and disaster recovery. When all configuration steps are complete, a final system test is performed on the server in place to ensure it meets all client requirements. This phase ends when the server is ready to be used for its intended purpose.

A Configuration Item Management Form is submitted by a member of the team supporting the VM and the new CI will be added to the CMDB by the CMDB Administration Team. The Status field should be set to Installed. Although the Status and State fields can be adjusted to indicate the actual current state of the server, the Status field is usually set to Installed throughout the configuration and testing phase.

Phase 3: VM in Service & Maintained
This phase represents the useful production life of the VM. Throughout this phase, the server will undergo periodic maintenance, upgrades, failures, and fixes. At some point, its usefulness will come to an end and plans need to be made to take it out of service. This phase ends when the VM is deactivated and is no longer being used, even for archive purposes, and is ready to be deinstalled.

Ongoing adjustments to the Status, State, and other fields in the CI record are made as needed by a member of the team supporting the VM.

Phase 5: VM Retired
When the server is no longer needed, either because it is being replaced by something newer or it no longer serves any useful function, it is retired.

The Status and State are updated by a member of the team supporting the VM to reflect the fact that it is no longer operational and has been retired. At the same time, the name of the VM in the CI is modified to include a prefix of RETIRED to make it obvious in listings and searches that it is no longer in use. Under no circumstances should a CI ever be deleted from the CMDB. Deleting a CI record will make it impossible to trace the history of the software and any activity documented by incidents and change requests.