Using ImageUltra Builder - IBM Redbooks

More documents

Recommendations

Info

Function Figure 1-2 ImageUltra Builder Image Differences The following is a list of functions available for each image type: ► Portability – A hardware-specific image is only for use on identical computers systems. Hardware variations are limited to plug-in devices and peripherals for which device drivers were provided on the source computer. No variation in software content can be handled by the deployment process. If additional device drivers or application programs are required by the target computer, they must be installed manually or through some other software-deployment mechanism. – Although portable-sysprep images can be used with IBM and non-IBM computers and provide increased portability by enabling additional device drivers and applications to be installed, there are still hardware limitations. As a general rule, a portable-sysprep image is for use on identical or similar computers, and in many cases, the portable-sysprep image is “manufacturer-unique”. There are various factors in determining what constitutes a similar computer. If you are deploying a portable-sysprep image to a target computer that has the identical system board (motherboard) as the source computer, the image will install and work successfully. If you are deploying a portable-sysprep image to a target computer that has a different system board, but the same core chip set as the source computer, there is a high probability that the image will install and work successfully. If you are deploying a portable-sysprep image to a target computer that has a different system board and a different core chip set from the source computer, there is a low probability that the image will install and work successfully. – The ultra-portable image is the most portable of the three types of supported images. Because an ultra-portable image is deployed in an uninstalled state and uses the full Windows setup for hardware detection during installation, the image is virtually hardware-independent. 12 ThinkVantage Technologies: Using ImageUltra Builder Ultra Portable Portable Sysprep System Specific Portability High Medium-High None Effort to maintain image None Medium High Need for image updates Low Medium High Installation time Image Type Integrated with HIIT modules and ImageUltra Builder modules 50 min + (Windows unattended install) 20 min + (Sysprep) 15 min + (Sysprep) Yes Yes No Supported operating systems Win2000, WinXP Win2000, WinXP Any operating system Supported hardware IBM Only IBM and non-IBM IBM and non-IBM
The high portability of the ultra-portable image is limited to IBM personal computers only. The same base module and most application modules can be used across the IBM personal computer product line of HIIT-enabled computers, regardless of hardware variations. ► Image maintenance The ultra-portable and portable images require less maintenance since they use the modular approach to image creation. The hardware specific image requires a high amount of maintenance due to having all applications, drivers, patches etc. contained within one monolithic image. Each time a change is required, the entire image must be modified. ► Installation time The installation time varies between the three image methods. The hardware-specific image is the quickest due to having all the software components included within the image itself. The portable-sysprep image has the operating system cloned but the applications and drivers to be installed can be different depending on the hardware model and user application requirements. The ultra-portable has the slowest deployment time due to using an unattended installation instead of cloning technology. ► Hardware Independent Imaging Technology (HIIT) Integration The ultra-portable and portable-sysprep image can automatically detect the model type of most IBM computers and install the drivers required for each system. The hardware-specific image does not provide this feature. ► Supported operating systems The ultra-portable and portable-sysprep images will only be supported with Windows 2000 images and Windows XP images. The hardware specific image can be used with any operating system due to no modules or add on drivers being supported. ► Supported hardware The ultra-portable image is only supported for use on IBM PCs and ThinkPads. The operating system modules were created for IBM systems only. Using the ultra-portable image on a non-IBM may violate software license agreements. The portable-sysprep and hardware-specific can be used on IBM and non IBM systems. 1.5.5 Module categories In this section are the descriptions of the modules used within the ImageUltra Builder tool. ► Operating system modules: There are three types of operating system modules: – Base operating system modules: These modules contain all of the components that are part of the base operating system. Base operating system modules include modules created from hardware-specific images and portable-sysprep images, as well as base operating-system modules imported from the service partition or Hidden Protected Area of a source IBM computer. Base operating-system modules are typically created by and installed through an imaging tool, such as Symantec Ghost or Symantec DeployCenter. An example of this would be an operating system module for Window 2000 or Windows XP. See 1.15, “Creating a base operating system hardware specific module” on page 48. – Operating system add-on modules: These modules include items such as operating-system hot fixes, service packs, patches, and updates that install through a standard setup process, similar to applications. See 1.13, “Creating an operating system add-on module” on page 39. – Partitioning modules: You use these modules to add one or more partitions beyond the C partition, or delete one or more pre-existing partitions. You can have multiple Chapter 1. ImageUltra Builder 13
Page 1: Front cover ThinkVantage Technologi
Page 4 and 5: Note: Before using this information
Page 6 and 7: 1.16.1 Installing the IBM Customiza
Page 8 and 9: Trademarks The following terms are
Page 10 and 11: He has co-authored three ThinkVanta
Page 12 and 13: 1.1 Image management today An image
Page 14 and 15: Operating system, application, and
Page 16 and 17: 1.3.2 Image ► Determine if a driv
Page 18 and 19: ► Determine the location of image
Page 20 and 21: 1.5.2 Image types ► IBM Customiza
Page 24 and 25: partitioning modules in a base map
Page 26 and 27: 1.5.6 Module Window Tabs When creat
Page 28 and 29: ► Create a utility/filter module
Page 30 and 31: 3. Click Next. You will see a windo
Page 32 and 33: Figure 1-9 New Repository folder 5.
Page 34 and 35: 6. Select all of the modules to be
Page 36 and 37: Figure 1-16 Overwrite confirmation
Page 38 and 39: How to generate a SETUP.ISS file 1.
Page 40 and 41: 8. Click Finish to complete the New
Page 42 and 43: When the building process is finish
Page 44 and 45: 9. Click Finish to complete the New
Page 46 and 47: 14.Go to the Source tab. Figure 1-3
Page 48 and 49: 3. Click the Options tab and check
Page 50 and 51: Figure 1-35 IUB repository, operati
Page 52 and 53: 7. Click Next. You will see a windo
Page 54 and 55: 13.Select the OS/Languages tab. You
Page 56 and 57: 19.Go to the Options tab. You will
Page 58 and 59: ► DrivePrep - Delete No Partition
Page 60 and 61: 10.Click Next. You will see a windo
Page 62 and 63: 5. Select the languages and operati
Page 64 and 65: Figure 1-57 Hardware Specific OS mo
Page 66 and 67: 3. Leave the MS-DOS diskette in the
Page 68 and 69: 1. Open ImageUltra Builder. 2. Sele
Page 70 and 71: 1.16.4 Setting the module attribute
Page 72 and 73:
8. Click Browse add select the exec
Page 74 and 75:
- Under the General tab in the Name
Page 76 and 77:
Figure 1-68 Identify File Destinati
Page 78 and 79:
3. Click Next to proceed to the Cre
Page 80 and 81:
9. Click Next. You will see a windo
Page 82 and 83:
12.Next, we will insert a menu item
Page 84 and 85:
20.Repeat Step 18 to insert another
Page 86 and 87:
Figure 1-87 Map settings window Gen
Page 88 and 89:
Figure 1-89 Before/ After menu opti
Page 90 and 91:
- Prompt the user when the image is
Page 92 and 93:
It is not always necessary to inclu
Page 94 and 95:
2. Click the Deploy button or click
Page 96 and 97:
Figure 1-96 Deploy CD Map Locations
Page 98 and 99:
1.20.4 Deployment methods In this s
Page 100 and 101:
Network deployment This method uses
Page 102 and 103:
Modules Maps Repository Figure 1-99
Page 104 and 105:
Image Explorer Simplify management
Page 106 and 107:
1.22.3 Confirm that you have instal
Page 108 and 109:
7. Add the file name Detect Network
Page 110 and 111:
38.Locate the C:\TEMP. 39.And selec
Page 112 and 113:
Figure 1-109 Boot Disk Builder - Mi
Page 114 and 115:
14.Add the network adapter descript
Page 116 and 117:
5. Select Boot Disk and click Next
Page 118 and 119:
1.22.7 Capturing the donor image On
Page 120 and 121:
1.23 Image deployment In this secti
Page 122 and 123:
6. Fill in your ImageCenter command
Page 124 and 125:
12.Select the option to create a Vi
Page 126 and 127:
4. Fill in all of the required fiel
Page 128 and 129:
3. Click Next. 4. Select the option
Page 130 and 131:
c:\program files\PowerQuest\DeployC
Page 132 and 133:
4. Launch the SMAsetup_.EXE program
Page 134 and 135:
Figure 1-135 Building a utility for
Page 136 and 137:
5. Create a module that puts the SD
Page 138 and 139:
Rem Connect Network Drive net use z
Page 140 and 141:
The hardware in this organization c
Page 142 and 143:
Business Units Six: ► Sales ► I
Page 144 and 145:
Table 1-3 Phase 1 The first step in
Page 146 and 147:
Acme Holdings Inc. has decided that
Page 148 and 149:
Figure 1-143 OS map module Applicat
Page 150 and 151:
Figure 1-146 Repository - UK Englis
Page 152 and 153:
Business Units Six: ► Sales ► I
Page 154 and 155:
144 ThinkVantage Technologies: Usin
Page 156 and 157:
SCSI Small Computer Systems Interfa
Page 158 and 159:
How to get IBM Redbooks Help from I
Page 160 and 161:
IBM service partition 126 IBM Think
Page 162:
V VBE See Virtual Boot Environment
show all

Using ImageUltra Builder - IBM Redbooks

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?