Using ImageUltra Builder - IBM Redbooks

More documents

Recommendations

Info

Table 1-3 Phase 1 The first step in this process is to create one hardware specific OS module in ImageUltra Builder for each of the existing legacy images. The following process will show the steps required to bring these legacy images into the new ImageUltra process without modifying the existing images. The next section will discuss the creation of portable-syspreped images which Acme Holdings Inc. will be using for the newer four models listed above running Windows 2000 1.25.3 Business case section 2 of 3: Using portable-sysprep images In the previous section, we demonstrated how Acme Holdings Inc. began to introduce ImageUltra Builder into their environment. Acme Holdings Inc. did this by building hardware specific modules to bring all their legacy images into ImageUltra Builder. After creating the 134 ThinkVantage Technologies: Using ImageUltra Builder Existing State Phase I legacy systems Method Legacy Ghost images Hardware Specific using ImageUltra Builder Operating Systems Three: ► Windows 95c ► Windows 98 ► Windows NT 4 Hardware platforms Four: ► Compaq EN desktop ► Toshiba Tecra 8100 ► HP VL 8i ► IBM PC 300 PL Three: ► Windows 95c ► Windows 98 ► Windows NT 4 Four: ► Compaq EN desktop ► Toshiba Tecra 8100 ► HP VL 8i ► IBM PC 300 PL Technology Legacy monolithic ghost images Hardware Specific OS modules incorporating the existing legacy images Business Units Six: ► Sales ► IT ► Manufacturing ► Field ► Engineering ► Finance Languages Three: ► English - US ► English - UK ► Spanish Unique system combinations supported 144: One for each combination of hardware platform, business unit, and language. Images to create 144 144 Six: ► Sales ► IT ► Manufacturing ► Field ► Engineering ► Finance Three: ► English - US ► English - UK ► Spanish 144: One for each combination of hardware platform, business unit, and language.
144 hardware specific OS modules, we are left with 72 existing images that support the remaining four hardware platforms running Windows 2000 in three different languages. Now that Acme Holdings Inc. has become familiar with building OS modules for their legacy images, they could repeat this same process to build 72 additional new Window 2000 hardware specific modules. This would defeat the purpose of using ImageUltra Builder. By using ImageUltra Builder, we can reduce the number of unique images from 72 down to six OS modules. This great reduction is made possible by breaking the system build down into a modular process. A legacy image has one image file containing the OS, drivers, and applications. The result is when a small change needs to me made the entire image must be recreated. Additionally, by using the ImageUltra modular process, the OS module can take advantage of the OS’s built-in features that enable a single OS module to be used on more than one hardware platform. To use this portable OS module, we will need a sysprep Windows 2000 image that has had the hardware specific drivers removed. To create a sysprepped image, refer to 1.16, “Create a base operating system Portable Sysprep Image” on page 54. With the sysprep image, we only need to consider the HAL compatibility of the hardware platforms. For more information concerning HAL compatibility, refer to Microsoft’s Web site for details on HAL cross-platform compatibility. We have determined that at Acme Holdings Inc. they will require two images to support two unique HALs. The HAL of the HP VL 420 desktop and the IBM M40 NetVista desktops were determined to be compatible and the HAL of the Toshiba Tecra 9000 and the IBM T23 ThinkPad were determined to be compatible. We now have a decision to make concerning languages. Since Windows 2000 supports multiple languages, we can build one multi-language portable-sysprep image for each of the two unique HALs. The other option is to keep the portable-sysprep images language-specific. If the first option is taken, the result will be two images to support four hardware platforms using three languages. If the second choice is used, the result will be six images to support four hardware platforms using three languages. Table 1-4 on page 135 shows some of the advantages, disadvantages and features of both options. This information will be needed to make an informed decision as to whether or not (and where) to use a multi-language sysprepped OS image. Table 1-4 Multi-language OS image Type Of OS image Multi-Language Single Language Size Larger Smaller Complexity of development Complex Simple Developer Must be multi-lingual Only needs to know one language changes needed that affect only one language distributed development and division of workload Must rebuild entire image Only need to change impacted language image 1 developer per image 2 developers maximum at Acme Holdings Inc. 1 developer per image; 6 developers maximum at Acme Holdings Inc. Distribution time Slower due to larger image size Faster due to smaller image size Total number of OS modules 2 6 Chapter 1. ImageUltra Builder 135
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 22 and 23:
Function Figure 1-2 ImageUltra Buil
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:
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:
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 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

Create successful ePaper yourself

Delete template?

Save as template?