Chapter 4. Redeployment scenarios 93
Draft Document for Review November 15, 2007 3:27 pm 4372ch04.fm
3. If configured to do so, Tivoli Provisioning Manager for OS Deployment
authenticates the user of the computer against the server database, to restrict
the use or the maintenance of the computer to authorized persons.
4. If configured to do so, Tivoli Provisioning Manager for OS Deployment offers
the choice of several configurations available on the computer (multiboot),
and of several levels of cleaning.
5. Using the reference image saved during deployment, Tivoli Provisioning
Manager for OS Deployment resynchronizes the hard-disk content to its
reference state. This usually takes a few seconds in the normal case, and can
take up to a few minutes if everything has been destroyed on hard disk by the
previous user.
The local redeployment is very versatile. The redeployment can be fully
automated and mandatory, or it can be based on a menu with for example a
five-seconds timeout, after which the existing system will start up without any
redeployments. Redeployments can also be protected by a user-authentication
mechanism, thereby limiting the access to authorized persons.