IBM Software Group © 2008 IBM Corporation IBM Tivoli Provisioning Manager 7.1 OS Management with TPM for OS Deployment

IBM Software Group | Tivoli software © 2008 IBM Corporation IBM Tivoli Provisioning Manager 7.1 Features  Integration with TPM for OS Deployment 7.1 full product  OS deployment server installed out-of-the-box  Capture cloned images from TPM managed computers  Create unattended setup images from CD media  Support for Hardware Configuration images  Deploy images to TPM managed computers  Discovery of existing OS deployment servers and images  Discovery of bare-metal computers  Install additional OS deployment servers in your TPM environment  Expose TPM for OSD features directly from TPM –Manage OS deployment server properties –Manage image properties –Manage and create software modules –Manage target computer properties

IBM Software Group | Tivoli software © 2008 IBM Corporation IBM Tivoli Provisioning Manager 7.1 Architecture Overview TPM Computer TPM TPM for OSD (Parent) TPM for OSD (Child) TPM Computer TPM for OSD (Child) TPM for OSD Shared DB

IBM Software Group | Tivoli software © 2008 IBM Corporation IBM Tivoli Provisioning Manager 7.1 Architecture Overview  Two level hierarchy with one parent OS deployment server and all others are child servers  All OS deployment servers share a common database  All images, software modules and other TPM for OSD objects are replicated automatically between OS deployment servers  Parent OS deployment server is installed out-of-the-box by the TPM installer  A child OS deployment server can be promoted to become the parent

IBM Software Group | Tivoli software © 2008 IBM Corporation IBM Tivoli Provisioning Manager 7.1 TPM 7.1 OS Management Applications  Boot Servers  Boot Server Installation  Images  Image Capture  Image Deployment  Unattended Setup Image  Hardware Configuration Image  Software Modules

IBM Software Group | Tivoli software © 2008 IBM Corporation IBM Tivoli Provisioning Manager 7.1 Boot Servers Application  Lists the boot servers managed by TPM  Manage variables and credentials of the boot server  TPM for OSD boot servers have a configuration tab that allows the user to view and edit configuration information such as log level, port numbers, …  TPM for OSD boot servers have an action to promote a child boot server to a parent. This will swap the roles of the child boot server and the parent boot server.

IBM Software Group | Tivoli software © 2008 IBM Corporation IBM Tivoli Provisioning Manager 7.1 Boot Server Installation Application  The boot server installation application is used to install additional boot servers that is managed by TPM  Installs the TPM for OSD 7.1 full product on the target system  The boot server is configured as a child boot server and uses the shared database

IBM Software Group | Tivoli software © 2008 IBM Corporation IBM Tivoli Provisioning Manager 7.1 Images Application  The images application shows the images in TPM  TPM for OSD image properties can be viewed and edited in the properties tab. Some examples of these properties are: –Partition layout and files –Product key –Time zone –Language –Administrative password –Custom sysprep.inf file

IBM Software Group | Tivoli software © 2008 IBM Corporation IBM Tivoli Provisioning Manager 7.1 Image Capture Application  The image capture application is used to capture a cloned image from a computer managed by TPM  Capturing an image from Windows computers no longer requires to run the Windows configuration discovery before the image capture  Support to capture snapshot images that does not use sysprep  Capture of golden-master image from Windows computers automatically run sysprep to prepare the image before it does the image capture  No target OS deployment server need to be selected to perform the image capture. The image capture activity is submitted parent OS deployment server and the OS deployment server that responds to the network boot request from the target computer is the one servicing the image capture.

IBM Software Group | Tivoli software © 2008 IBM Corporation IBM Tivoli Provisioning Manager 7.1 Unattended Image Setup Application  The unattended setup image is used to create images from CD media or file  For most operating systems, you can create an unattended setup image from the operating system CD  For Solaris flash archive files, you can create an image directly from the.flar file  Unlike the image capture from a computer, feature is not implemented using workflow. UI wizard guides user through image creation.

IBM Software Group | Tivoli software © 2008 IBM Corporation IBM Tivoli Provisioning Manager 7.1 Hardware Configuration Application  The hardware configuration image application is used to create hardware configuration images  Hardware configuration images can be used to: –Configure RAID adapters –Perform BIOS updates or configuration –Perform firmware updates –Perform a custom hardware configuration  Typical use of a hardware configuration image to setup a RAID array prior to image deployment so that it can be used during the OS image deployment.  Feature is not implemented using workflow. UI wizard guides user through image creation.

IBM Software Group | Tivoli software © 2008 IBM Corporation IBM Tivoli Provisioning Manager 7.1 Image Deployment Application  The image deployment application is used to deploy images to computers managed by TPM  Both OS images and Hardware Configuration images can be deployed  Option to install TCA during OS image deployment  If the target computer is already running an operating system, TPM can restart the computer to start the image deployment. Otherwise, the user will need to network boot the computer to start the image deployment activity.  Requirement checking for hard-disk size and cpu type are no longer performed by TPM. The OS deployment server has better knowledge of the target computer hardware and image requirements.  Runs CIT agentless discovery after image deployment to ensure up- to-date inventory information in TPM

IBM Software Group | Tivoli software © 2008 IBM Corporation IBM Tivoli Provisioning Manager 7.1 Software Modules Application  The software modules application shows software modules that are known to the OS deployment servers  Software modules can be: –Device drivers –Applications such as msi installers –Applications that consist of files and commands to be run –Custom commands to be run  Software modules can be configured to be deployed at specific times during image deployment. For example, a software module can be configured to be deployed after a reboot if necessary.  Binding rules can be created to bind a software module to specific images, OS types, target computers, or many other parameters  An example of a typical use of a software module: –If a computer to be deployed needs a specific device driver to access the disk, a software module can be created for that device driver. –The software module can then be bound to specific parameters such as the PCI adapter that matches the device and the OS supported by the device driver. –When an OS is deployed to the target computer, the software module with the device driver will automatically be installed if it matches the binding criteria.

IBM Software Group | Tivoli software © 2008 IBM Corporation IBM Tivoli Provisioning Manager 7.1 Discovery of bare-metal computers  All computers that register with TPM for OSD are pushed to TPM instead of being polled by providing the list of serial numbers of the computers to discover –Computer powered-on and network boots –Computer is registered by the OS deployment server that responds to the network boot request –The OS deployment server uses web services to push the computer information to TPM –Computer created in TPM with networking, CPU, disk and memory information

IBM Software Group | Tivoli software © 2008 IBM Corporation IBM Tivoli Provisioning Manager 7.1 OS Support for target computers Primary platforms  Windows Server x86-32 / x86-64  Windows Server x86-32 / x86-64  Windows XP SP2 - x86-32 / x86-64  Windows Vista - x86-32 / x86-64  RHEL 5 - x86-32 / x86-64  RHEL 5 – pSeries  RHEL 5 - cell blades  SLES 10 - x86-32 / x86-64  SLES 10 – pSeries  SLES 10 – zSeries  AIX 5L pSeries  AIX pSeries  VMWare ESX x86-64  VMWare ESX x86-64 Secondary platforms  RHEL 4 - x86-32 / x86-64  Red Hat Desktop 4 - x86-32 / x86-64  Red Hat Desktop 5 - x86-32 / x86-64  SUSE (SLES) 9 - x86-32 / x86-64  Solaris 9 – SPARC  Solaris 10 – SPARC  Windows 2000 SP4 - x86-32