1.2.0

Figure 1-1. Stages in the Lifecycle of a Virtual Machine under LCM
request
virtual machine
approve
create
virtual machine
set up
approval
required
placement exception
or conflict -
manual placement
no approval -
placement
exception
or conflict
no approval -
automatic
placement
user decided to
decommission
manually
archive or
delete
configuration
dependent
no approval
use
virtual machine
approve
life extension
or VM
customization
end of life
archive
decommission
delete
best practice path
other possible path
other possible path with approval deactivated
The way that LCM handles requests to create virtual machines depends on how the LCM Administrator has
configured the approval process. If approval is required, an email notification is sent to the LCM Approver.
If approval is not required, and there is no conflict with the request, the virtual machine is created. If there is
a conflict, an LCM IT Staff user receives an email notification that a virtual machine is waiting to be created.
After a virtual machine is created, it can be used until the decommissioning date. Five days before the
decommissioning date, an email notice is sent to the user who requested the virtual machine if email
notifications are enabled. The requester can do one of the following:
n
Request to extend the life of the machine.
If the extension is not approved, the virtual machine is decommissioned and is archived or deleted.
The LCM Administrator determines whether decommissioned virtual machines are archived.
n
Manually decommission the virtual machine.
The LCM Administrator can choose to delete the virtual machine request. The LCM Administrator is the only
role that can remove information about a virtual machine. When a request is deleted, no information about
the virtual machine appears in reports, but the virtual machine is not deleted. If a virtual machine request is
accidentally deleted, the LCM Administrator can recover the associated virtual machine.
Lifecycle Manager Installation and Configuration Guide
12 VMware, Inc.