IBM REDP-4372-00 manual Adding support for different hardware types

Draft Document for Review November 15, 2007 3:27 pm 4372ch03.fm

If we edit the profile details, we can add system category information, which then allows us to associate this profile with specific software packages. After we finish with the profile details, we can modify the details of the disk partitions in the image. In the profile configuration summary we see that we can make custom additions to the sysprep.inf file. Remember that this file is used when the image is deployed to a new target. Such modifications are useful to allow us to run custom actions when the deployment is completed. They might include the following:

￿A script to update an associated Change Record

￿A script to send an e-mail notification to an Administrator

The sysprep process is documented at the following web site:

http://www.microsoft.com/technet/prodtechnol/winxppro/deploy/duplicatio

n.mspx

Details of the contents of the sysprep.inf file are documented at the following Web site:

http://technet2.microsoft.com/WindowsVista/en/library/71b576bd-cca6-466f-a1db-16500be3098f1033.mspx?mfr=true

If you want to do something simple like run a script after installation completes, then see Example 3-1, which gives you the critical but incomplete items from the sysprep.inf file that you will need. In this example, we run the c:\run_this_command.cmd file the first time that the target machine boots after installation.

Example 3-1 running a script after deployment is completed

[Unattended]

[GuiUnattended]

AutoLogonCount=1

AutoLogon=Yes

[GuiRunOnce]

Command0=C:\run_this_command.cmd

3.2 Adding support for different hardware types

The cloning profile that we created in the previous section is currently perfect for exactly one type of hardware, namely the one we used to create the master image.

Chapter 3. Mass-Distributions 69