The deployment process

The deployment process has numerous steps, including hardware discovery, hard disk partitioning, and installing operating systems and other software modules.

A typical deployment proceeds as follow:

1. Start the target remotely, possibly using Wake on LAN or vPro. The target starts up on the network. It receives IP information from the DHCP server, and a bootstrap program from the OS deployment server that directs the next steps.
2. The target performs hardware discovery through DMI and PCI system calls.
3. The target queries the ODBC/JDBC database for all relevant information regarding the operating system and the software modules to be installed, and dynamically generates a deployment plan.
4. If specified in the database, it prompts the user (or the administrator on the web interface) for additional deployment information.
5. Depending on the planned deployment steps, the bootstrap can start WinPE 3.0 for Windows or Linux deployment engine for Linux in a ramsdisk to perform some of the configuration and installation tasks.
6. If specific hardware configuration software needs to be run early (such as RAID controller configuration), it is started. After a subsequent reboot, the target resumes the process.
7. The target partitions its hard disk according to the information retrieved from the database. A small bootstrap is also written to the hard disk, to be able to take over any subsequent reboot on the hard disk.
8. The target initiates a multicast transfer for all files needed during the deployment.
9. The content of the hard disk partitions is built by merging the base operating system image and all incremental images and other software updates. The data is then written onto the disk with optimal efficiency.
10. An answer file is dynamically generated, providing all necessary information for an unattended customization of the operating system. Unattended setup command lines for software modules are prepared.
11. The target computer boots on the hard disk, and completes operating system installation, then issues unattended setup command lines for the selected software modules. The target reboots and Tivoli® Provisioning Manager for OS Deployment takes control again.
12. If other software modules have been configured to be installed after one (or more) reboot, they are installed and the operating system is started again.
13. If the computer is still connected to the network, it automatically updates the deployment status in the database.
14. When everything is done, the deployment process terminates by either turning off the target, starting up into the operating system, restarting the target, or displaying a green banner page.