IBM Thinkvantage Technologies, Volume 1 Creating and Deploying Client Systems

ibm.com/redbooks

Using ThinkVantage Technologies: Volume 1Creating and Deploying Client Systems

Haakon FosshaugEleanor Howard

David KohlerIve MattheessensGuy Varendonck

John ZywickiByron Braswell

Simplification of the PC life cycle process with ThinkVantage Technologies

Simple deployment in complex corporate environments

Use of ThinkVantage Technologies to lower costs

Front cover

http://www.redbooks.ibm.com/


Using ThinkVantage Technologies: Volume 1 Creating and Deploying Client Systems

September 2004

International Technical Support Organization

SG24-7045-01

© Copyright International Business Machines Corporation 2004. All rights reserved.Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADPSchedule Contract with IBM Corp.

Second Edition (September 2004)

This edition applies to Version 2.01 of IBM ImageUltra Builder, V 4.1.3 of System Migration Assistant, Secure Data Disposal (SCRUB3), V 3.30 of IBM Access Connections, and V 1.22 of IBM Active Protection System

Note: Before using this information and the product it supports, read the information in “Notices” on page ix.

Contents

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixTrademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiThe team that wrote this redbook. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiBecome a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xivComments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviiSeptember 2004, Second Edition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviiFebruary 2005, Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 ThinkVantage Technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2 ThinkVantage Technologies process improvements. . . . . . . . . . . . . . . . . . 61.3 Implementing a ThinkVantage Technologies solution. . . . . . . . . . . . . . . . . 7

Chapter 2. ImageUltra Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.1 Image management today. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.1.1 Current tools and procedures used to build and deploy images . . . . 122.1.2 Image complexity leads to image management problems . . . . . . . . 13

2.2 Image management using ImageUltra Builder . . . . . . . . . . . . . . . . . . . . . 132.3 Image creation preparation process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.3.1 Hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.3.2 Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.3.3 Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.3.4 Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2.4 Installing ImageUltra Builder V2.01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.4.1 Minimum Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.4.2 Installation procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.5 ImageUltra Builder components and basic operations . . . . . . . . . . . . . . . 202.5.1 ImageUltra Builder terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.5.2 Image types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.5.3 The use and importance of Microsoft Sysprep . . . . . . . . . . . . . . . . . 232.5.4 Which image type is best for you? . . . . . . . . . . . . . . . . . . . . . . . . . . 242.5.5 Module categories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272.5.6 Module Window Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

2.6 ImageUltra Builder process to create a Smart Image . . . . . . . . . . . . . . . . 322.7 Create a repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

© Copyright IBM Corp. 2004. All rights reserved. iii

2.8 Import IBM Preload modules into your repository . . . . . . . . . . . . . . . . . . . 392.8.1 Importing modules from an IBM recovery CD set . . . . . . . . . . . . . . . 39

2.9 Create custom modules - preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452.9.1 Windows Installer - msiexec.exe file . . . . . . . . . . . . . . . . . . . . . . . . . 462.9.2 InstallShield. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

2.10 Creating an application module from source files . . . . . . . . . . . . . . . . . . 482.11 Creating a device driver module from source files . . . . . . . . . . . . . . . . . 54

2.11.1 Install SoundMAX audio driver from a setup.exe file . . . . . . . . . . . 542.11.2 Install SoundMAX audio driver from an INF file . . . . . . . . . . . . . . . 61

2.12 Create a filter/utility module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642.12.1 Example of a filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

2.13 Creating an operating system add-on module . . . . . . . . . . . . . . . . . . . . 662.14 Creating a partitioning module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772.15 Creating a base operating system hardware specific module. . . . . . . . . 78

2.15.1 Create and prepare the image file. . . . . . . . . . . . . . . . . . . . . . . . . . 782.15.2 Add the donor image to the ImageUltra Builder repository . . . . . . . 782.15.3 Setting the module attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812.15.4 Build the module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

2.16 Create a base operating system Portable Sysprep Image . . . . . . . . . . . 872.16.1 Installing the IBM Customization Program . . . . . . . . . . . . . . . . . . . 872.16.2 Create the portable-sysprep image on a source computer . . . . . . . 882.16.3 Add the donor image to the ImageUltra Builder Repository . . . . . . 912.16.4 Setting the module attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 942.16.5 Build the module from the image files . . . . . . . . . . . . . . . . . . . . . . . 97

2.17 Customize an Ultra-Portable operating system module . . . . . . . . . . . . . 992.18 Create your base map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

2.18.1 Base map settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1142.19 Create a driver map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

2.19.1 Driver Map settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1242.20 Deploying images using ImageUltra Builder . . . . . . . . . . . . . . . . . . . . . 126

2.20.1 Creating an ImageUltra Builder boot diskette . . . . . . . . . . . . . . . . 1262.20.2 Creating a bootable Network Deployment CD from a diskette . . . 1302.20.3 Creating a custom network boot diskette . . . . . . . . . . . . . . . . . . . 1302.20.4 Deployment methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

2.21 Using ImageUltra Builder and Symantec DeployCenter together . . . . . 1392.21.1 Overview of Symantec DeployCenter . . . . . . . . . . . . . . . . . . . . . . 139

2.22 Image development. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1412.22.1 Create your donor image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1412.22.2 Use PXE and Virtual Boot Environment to capture donor image . 1422.22.3 Confirm that you have installed the PXE service correctly . . . . . . 1422.22.4 Confirm you have the correct Network drivers installed in boot disk

builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1432.22.5 Add the CAPTURE IMAGE.VFD to the Configuration Utility. . . . . 160

iv Using ThinkVantage Technologies: Volume 1 Creating and Deploying Client Systems

2.22.6 Add CAPTURE IMAGE selection to the PXE Client menu . . . . . . 1612.22.7 Capturing the donor image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1612.22.8 Add the donor image to the ImageUltra Builder repository . . . . . . 1622.22.9 Create a ImageUltra Builder Smart Image using the donor image as a

base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1622.22.10 Re-clone an ImageUltra Builder after the Smart Image has been

deployed into the Service Partition . . . . . . . . . . . . . . . . . . . . . . . . . 1622.23 Image deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

2.23.1 Unicast a cloned ImageUltra Smart Image . . . . . . . . . . . . . . . . . . 1642.23.2 Multicast a cloned IUB Smart Image. . . . . . . . . . . . . . . . . . . . . . . 170

2.24 Software integration considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . 1782.24.1 Integration with IBM Software Delivery Center (SDC) . . . . . . . . . 1782.24.2 Integration with System Migration Assistant (SMA) . . . . . . . . . . . 1792.24.3 IBM Rescue and Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1802.24.4 ImageUltra Builder with Symantec Ghost . . . . . . . . . . . . . . . . . . . 180

2.25 Business case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1812.25.1 Example organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1812.25.2 Business case section 1 of 3: Using hardware specific images . . 1832.25.3 Business case section 2 of 3: Using portable-sysprep images . . . 1882.25.4 Business case section 3 of 3: Using ultra-portable . . . . . . . . . . . . 196

Chapter 3. IBM System Migration Assistant . . . . . . . . . . . . . . . . . . . . . . . 2013.1 System migration and its effects on the organization . . . . . . . . . . . . . . . 203

3.1.1 When is system migration required?. . . . . . . . . . . . . . . . . . . . . . . . 2033.1.2 Who transfers the data and personalization of the machine? . . . . . 203

3.2 Installation considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2053.2.1 Supported operating systems and system requirements . . . . . . . . 2053.2.2 System Migration Assistant components . . . . . . . . . . . . . . . . . . . . 2063.2.3 Basic operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

3.3 System Migration Assistant installation . . . . . . . . . . . . . . . . . . . . . . . . . . 2083.3.1 Uninstalling System Migration Assistant . . . . . . . . . . . . . . . . . . . . . 2093.3.2 Silent installation creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

3.4 Using System Migration Assistant. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2113.4.1 Capturing settings and files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2133.4.2 Applying settings and files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

3.5 Using SMA in batch mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2393.5.1 System Migration Assistant capture phase in batch mode . . . . . . . 2413.5.2 System Migration Assistant apply phase in batch mode. . . . . . . . . 248

3.6 Creating a command file template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2493.7 Peer to Peer mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

Chapter 4. Secure Data Disposal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2594.1 Secure Data Disposal: the tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

Contents v

4.1.1 Using SCRUB3.EXE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2604.1.2 Performance considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2634.1.3 Practical application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2644.1.4 Running Secure Data Disposal through RDM. . . . . . . . . . . . . . . . . 264

Chapter 5. IBM Access Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2675.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2685.2 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

5.2.1 Hardware and security cross-reference . . . . . . . . . . . . . . . . . . . . . 2705.3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

5.3.1 Extraction of source files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2735.3.2 Automated Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2745.3.3 Manual installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

5.4 Creating IBM Access Connections profiles . . . . . . . . . . . . . . . . . . . . . . . 2755.4.1 Creation of a location profile using detailed setup . . . . . . . . . . . . . 2755.4.2 Quick setup for location profile creation . . . . . . . . . . . . . . . . . . . . . 292

5.5 Customization and advanced features . . . . . . . . . . . . . . . . . . . . . . . . . . 2985.5.1 IBM Access Connections Connection Status window. . . . . . . . . . . 2995.5.2 Location switching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3015.5.3 Global Settings... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3045.5.4 Managing Location Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3065.5.5 Wireless network considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . 3095.5.6 Access Connections Help and tray icons . . . . . . . . . . . . . . . . . . . . 3145.5.7 Fn+F5 key display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

5.6 Enabler for Administrator Profile Deployment Feature . . . . . . . . . . . . . . 3205.7 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3325.8 Reference material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332

Chapter 6. Active Protection System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3356.1 Active Protection System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3366.2 Supported ThinkPad models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3366.3 Active Protection System sensor status . . . . . . . . . . . . . . . . . . . . . . . . . 3376.4 User interface and task tray applet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3386.5 Description of Active Protection System properties . . . . . . . . . . . . . . . . 339

6.5.1 APS properties Configuration tab . . . . . . . . . . . . . . . . . . . . . . . . . . 3406.5.2 APS properties Real-time Status tab . . . . . . . . . . . . . . . . . . . . . . . 3426.5.3 APS properties About tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343

6.6 APS Real-time Status in action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3436.6.1 No shock detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3446.6.2 Repetitive shock detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3456.6.3 Repetitive shock detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3466.6.4 Free fall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

6.7 IBM Active Protection System design . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

vi Using ThinkVantage Technologies: Volume 1 Creating and Deploying Client Systems

6.7.1 Head unloading for increased hard disk drive shock tolerance. . . . 3486.7.2 Use of prediction algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349

6.8 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3496.8.1 Summary of features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350

Chapter 7. Implementing ThinkVantage Technologies . . . . . . . . . . . . . . 3517.1 Implementation planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3527.2 ThinkVantage Technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3557.3 Migration/rollout scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358

7.3.1 PC migration or upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3587.3.2 PC rollout scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3607.3.3 Help desk scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362

7.4 IBM Director and System Information Center scenario . . . . . . . . . . . . . . 363

Abbreviations and acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367Online resources and education. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367How to get IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371

Contents vii

viii Using ThinkVantage Technologies: Volume 1 Creating and Deploying Client Systems

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing, IBM Corporation, North Castle Drive Armonk, NY 10504-1785 U.S.A.

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces.

© Copyright IBM Corp. 2004. All rights reserved. ix

TrademarksThe following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both:

ibm.com®ImageUltra™IBM®Lotus Notes®Lotus Organizer®Lotus®NetVista™

Notes®PC 300®Redbooks™Redbooks (logo) ™Rescue and Recovery™SmartSuite®ThinkCentre™

ThinkPad®ThinkVantage™Tivoli®UltraPort™Update Connector™

The following terms are trademarks of other companies:

Intel, and Intel Inside (logos) are trademarks of Intel Corporation in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Other company, product, and service names may be trademarks or service marks of others.

x Using ThinkVantage Technologies: Volume 1 Creating and Deploying Client Systems

Preface

ThinkVantage™ Technologies bring your IBM® PCs one step closer to being self-configured, self-optimizing, self-protecting, or self-healing, to help save you time and money throughout the life of your systems. In short, ThinkVantage Technologies let you focus your attention on your business, rather than on your computer.

ThinkVantage Technologies are software tools designed to help customers drive down IT support costs (in particular, the cost of a PC in managing and supporting systems after its initial purchase), increase security and decrease the complexity of today’s IT infrastructure.

This IBM Redbook will help you install, tailor and configure the IBM ThinkVantage Technologies on IBM and OEM desktops.

This is Volume 1 of a two-volume set of ThinkVantage Technologies Redbooks™. It describes how to create and deploy client systems. The second volume is Using ThinkVantage Technologies Volume 2: Maintaining and Recovering Client Systems, SG24-6060-03.

The team that wrote this redbookThis redbook was produced by a team of specialists from around the world working at the International Technical Support Organization, Raleigh Center.

© Copyright IBM Corp. 2004. All rights reserved. xi

The team: Byron, John, Guy, Ive, David, Haakon, Eleanor

Byron Braswell is a Networking Professional at the International Technical Support Organization, Raleigh Center. He received a bachelor’s degree in Physics and a master’s degree in Computer Sciences from Texas A&M University. He writes extensively in the areas of networking and host integration software. Before joining the ITSO four years ago, Byron worked in IBM Learning Services Development in networking education development.

Haakon Fosshaug is a Technical Advocate and a Technical Support Manager in IBM PCD Norway. He is a Bachelor of Engineering in Computer Science. He works with both presales and post-sales advanced technical questions regarding ThinkVantage and IBM PC products. He has been working in IBM for five years during which he has been extensively involved with helping customers use and implement the ThinkVantage Technologies. His specialties include all the ThinkVantage tools, especially computer security, networking and image creation/distribution. He also has in-depth skills about technical support and counseling on future PC platforms for customers.

Eleanor Howard is a Large Enterprise Field Technical Support Specialist and has worked for IBM France for over six years. She covers France, Belgium and Luxembourg. Her areas of expertise include providing pre-sales support for ThinkCentre™, the IBM Desktop range, and IBM ThinkVantage tools, in particular ImageUltra™ Builder. She also works hand in hand with IBM Global Services to develop implementation services for customers around ThinkVantage tools.

xii Using ThinkVantage Technologies: Volume 1 Creating and Deploying Client Systems

David Kohler is a Systems Management Integration Professional Advanced in Pennsylvania. He has 16 years of experience in the IT industry and has worked for IBM for two and half years. He develops global technology solutions and manages projects for IBM Global Services customers. He is involved with project management support, technology research and evaluation to ensure that IBM customers are utilizing products that best fit their unique needs. He has the following certifications: Microsoft® Certified Professional, COMPTIA A+, COMPTIA Network+ and Learning Tree International Certified Windows® 2000 Professional. He is currently a senior at Thomas Edison State College of New Jersey, pursuing a bachelor’s degree in Computer Information Services.

Ive Mattheessens is a Software Engineer with the EMEA IBM Imaging Technology Center in Greenock, UK. He has worked on the ImageUltra solution development for several large international customers in the EMEA region. He specializes in system and application deployment technologies and has several years of experience with ImageUltra, Software Delivery Assistant and Rescue and Recovery™. Before joining the IBM Image Technology Center, he worked in IBM Technical Support. He has been employed with IBM for nine years.

Guy Varendonck is an accredited IT Specialist in the EMEA Techline in Greenock, UK. In his Pre-sales Technical Support role he has been extensively involved in supporting IBM Sales and IBM Business Partners on ThinkVantage Technologies. Before joining the EMEA Techline he worked in IBM Technical Support, Fulfillment and was Team Lead in ibm.com®. He has been employed with IBM for nine years.

John Zywicki is a Systems Management Professional with IBM Global Services US. He has 13 years of experience in all aspects of PC management, deployment and project leadership for large enterprise accounts. He is a technical project management lead for hardware and software standardization methods, global deployments and systems management solutions. His specialties include process development, technical guidance, and solutions development. He has co-authored three ThinkVantage Technology Redbooks. He is also responsible for providing pre-sales and post-sales support and training to IBM internal teams and customers.

Goran Wibran is a Segment Manager for IBM TCO and ThinkVantage technologies, based in Research Triangle Park, NC, USA. His mission is to help IBM PCD create solutions for cost- and resource-effective IT management, IT process automation and IT system integration. He is one of IBM's leading experts on deploying and managing PC-based products. In his leadership role, he works with the IBM Development teams to create the next generation PC and Server management solutions. He simultaneously continues his work as a consultant, helping IBM customers to develop and implement automated IT processes around the world.

Preface xiii

Thanks to the following people for their contributions to this project:

Margaret TicknorTamikia BarrowInternational Technical Support Organization, Raleigh Center

Steven BalogFrank BenzaquenJeff EstroffEgbert GraciasJoshua J. JankowskyJosh NovakCaroline PatzerRatan RayPritam PablaMichaelle WalcuttDavid WallGoran WibranJeffrey WittAdam WongIBM RTP, North Carolina

Become a published authorJoin us for a two- to six-week residency program! Help write an IBM Redbook dealing with specific products or solutions, while getting hands-on experience with leading-edge technologies. You'll team with IBM technical professionals, Business Partners and/or customers.

Your efforts will help increase product acceptance and customer satisfaction. As a bonus, you'll develop a network of contacts in IBM development labs, and increase your productivity and marketability.

Find out more about the residency program, browse the residency index, and apply online at:

ibm.com/redbooks/residencies.html

Comments welcomeYour comments are important to us!

We want our Redbooks to be as helpful as possible. Send us your comments about this or other Redbooks in one of the following ways:

xiv Using ThinkVantage Technologies: Volume 1 Creating and Deploying Client Systems

http://www.redbooks.ibm.com/residencies.html

http://www.redbooks.ibm.com/residencies.html

� Use the online Contact us review redbook form found at:

ibm.com/redbooks

� Send your comments in an Internet note to:

[email protected]

� Mail your comments to:

IBM Corporation, International Technical Support OrganizationDept. HZ8 Building 662P.O. Box 12195Research Triangle Park, NC 27709-2195

Preface xv



http://www.redbooks.ibm.com/contacts.html

xvi Using ThinkVantage Technologies: Volume 1 Creating and Deploying Client Systems

Summary of changes

This section describes the technical changes made in this edition of the book and in previous editions. This edition may also include minor corrections and editorial changes that are not identified.

Summary of Changesfor SG24-7045-01for Using ThinkVantage Technologies: Volume 1 Creating and Deploying Client Systemsas created or updated on February 18, 2005.

September 2004, Second EditionThis revision reflects the addition, deletion, or modification of new and changed information described below.

New information� Chapter 6. Active Protection System is new.

Changed information� Chapter 2. ImageUltra Builder is completely re-written.� Chapter 3. System Migration Assistant is updated.� Chapter 5. IBM Access Connections is completely re-written.

February 2005, Update

Removed information� The chapter on Software Delivery Assistant has been removed. See the

Redpaper on Software Delivery Assistant V1.31, ThinkVantage Technologies: Using Software Delivery Assistant V1.31, REDP-3974.

In addition, see the chapter on IBM Software Delivery Center in Using ThinkVantage Technologies Volume 2: Maintaining and Recovering Client Systems, SG24-6060-03, or the Redpaper on Software Delivery Center ThinkVantage Technologies: Using IBM Software Delivery Center, REDP-3976.

© Copyright IBM Corp. 2004. All rights reserved. xvii

xviii Using ThinkVantage Technologies: Volume 1 Creating and Deploying Client Systems

Chapter 1. Introduction

Over the last decade, controlling complexity has been the goal of every IT manager. With the introduction of the Internet, new devices and processes have made delivery of service more complex and it has become critical for IT managers to contain costs. Understanding the total cost of ownership has made it necessary to seek methods to reduce costs while improving service.

Despite reductions in PC hardware costs, many have seen costs rise due to increased product complexity, proliferation-related management and support issues. Today, the initial cost of buying a PC is the “tip of the iceberg”. This emphasis on cost reductions requires ways to improve the overall PC management process.

What has IBM done to alleviate the stress of these costs? The company has focused research and development efforts around the challenges of reducing total cost of ownership. Through the evaluation of each phase of the PC life cycle, IBM has developed a number of technologies in hardware and software to reduce IT management costs. Known as ThinkVantage Technologies, they manage the PC life cycle from pre-deploy planning through end-of-life disposition.

Figure 1-1 on page 2 shows an overview of the functions performed by various ThinkVantage Technologies during the hardware/software life cycle of a typical client PC.

1

© Copyright IBM Corp. 2004. All rights reserved. 1

Figure 1-1 High level ThinkVantage Technologies functions

1.1 ThinkVantage TechnologiesTo address key concerns regarding the reduction of costs and to improve return on investment (ROI), the ThinkVantage Tools can be implemented individually or as a complete solution. As a result, organizations can integrate these solutions into their existing environments to complement existing processes or develop new, more cost-efficient processes if these are not already in place.

ThinkVantage Technologies simplify the PC life cycle processes in the following ways:

� Improve IT resource utilization

� Improve IT budget usage

� Automate resource-intensive tasks

� Minimize help desk and desk side costs

� Reinforce best practices

� Deliver low total cost of ownership (TCO)

Image creation

Image deployment

Migration

Recovery Inventory Software dist Support

Retire

2 Using ThinkVantage Technologies: Volume 1 Creating and Deploying Client Systems

Figure 1-2 Simplifying the PC life cycle processes

The two-volume set of ThinkVantage Technology Redbooks covers the products that address each of the functional areas in the PC life cycle. These products are introduced in the following sections.

ImageUltra BuilderImageUltra Builder was designed to help simplify your image creation, deployment and management. This technology is designed to help enterprises save time and money and to stay productive with a do-it-yourself tool that can allow you to deploy as few as one image across your enterprise. By combining multiple languages, applications and operating systems into a single hard drive image, you help eliminate or reduce the need for manual application installation, hardware testing and support. This patent-pending technology lets you better control your IT environment, making deployments less painful, and lower IT costs.

ImageUltra builder allows for the separation of drivers and applications from a traditional image, unlike Symantec Ghost and PowerQuest Drive Image. By separating these components, as well as the OS, we greatly reduce the number of images that need to be kept. Since drivers and applications are updated, there is no need to open each traditional image to apply the updates. Customers already using Symantec Ghost or PowerQuest Drive Image can incorporate their images into ImageUltra Builder as either semi-portable or system-specific images.

ImageUltra™ BuilderImageUltra™ Services

Image Creation,Management

and Test

Backup/Recovery

CascadingDisposal

Install Client

Migrate Data and

Application Settings

Support

Software Updates

Asset Mgt /Inventory

SystemMigrationAssistant

IBM Director AgentSystem Information Center

Rescue & Recovery

Software DeliveryCenter

RemoteDeployment Mgr

SoftwareDelivery

Assistant

IBM DirectorIBM Director AgentAccess IBM

SecureData DisposalPC Recycling

Deploy Image

Chapter 1. Introduction 3

For more information regarding ImageUltra Builder, see Chapter 2, “ImageUltra Builder” on page 11.

System Migration Assistant (SMA)System Migration Assistant enables custom settings, preferences, and data to be migrated from a user's former PC to the new PC accurately, efficiently and effectively. When older computers are refreshed or new computers are introduced, moving user data and system settings to the new system becomes expensive and time-consuming. Removing the problems associated with migration is an important customer satisfaction issue.

SMA is discussed in Chapter 3, “IBM System Migration Assistant” on page 201.

Secure Data DisposalIBM Secure Data Disposal removes all data on a hard disk drive, protecting sensitive information when a drive is re-deployed or retired. After using this process, data will be non-recoverable.

SDD is discussed in Chapter 4, “Secure Data Disposal” on page 259.

Access ConnectionsIBM Access Connections is a connectivity assistant program for your IBM ThinkPad® computer that allows you to create and manage location profiles. Each location profile stores all of the network and Internet configuration settings that are needed to connect to a network infrastructure from a specific location such as home or work. By switching between location profiles as you move your computer from place to place, you can quickly and easily connect to a network without having to manually reconfigure your settings and restart your computer each time.

Access Connections is discussed in Chapter 5, “IBM Access Connections” on page 267.

Rescue and Recovery IBM Rescue and Recovery is a one-button solution that includes a set of self recovery tools to help users diagnose, get help and recover from a software crash, even if the primary operating system will not boot. It helps with everything from complete software failure to occasions when you need only to restore a corrupted or deleted file. And it's easily accessible from the Microsoft Windows desktop or by pressing the blue Access IBM button on supported IBM systems (or the F11 key on other personal computers).


For more information regarding Rescue and Recovery, refer to ThinkVantage Technologies: Volume 2 Maintaining and Recovering Client Systems, SG24-6060.

IBM System Information CenterSystem Information Center is a cost and resource effective inventory solution that complements and leverages the customer’s investment in ThinkVantage Technologies. Features included in System Information Center are easy browser accessibility, minimal resource usage, control of software license management and central management.

For more information regarding IBM System Information Center, refer to ThinkVantage Technologies: Volume 2 Maintaining and Recovering Client Systems, SG24-6060.

IBM Software Delivery CenterSoftware Delivery Center is a Java™-based Web-enabled software distribution solution that complements and leverages the customer’s investment in ThinkVantage Technologies. Software Delivery Center uses industry standard components, is simple to manage, easily integrates into an existing customer network infrastructure, is customizable, and is very cost effective both at the time of implementation and over the long term.

IBM Software Delivery Center is discussed in ThinkVantage Technologies: Volume 2 Maintaining and Recovering Client Systems, SG24-6060.

Access IBM and Access HelpAccess IBM and Access Help are comprehensive, on-board help and information centers for your computer. They travel with you, eliminating the need to carry reference manuals or user guides.

Access IBM and Access Help are discussed in ThinkVantage Technologies: Volume 2 Maintaining and Recovering Client Systems, SG24-6060.

Embedded Security SubsystemThe IBM Embedded Security Subsystem, available on select IBM computers, consists of the integrated security chip and IBM Client Security Software (download required). Working together, these components provide security not previously available. The integrated security chip provides hardware-based protection of critical security information, including passwords, encryption keys and electronic credentials. The security software provides the interface between security-aware applications and the functionality of the chip. In addition, it provides support for peripheral security devices that control access to the PC itself.


For more information regarding the Embedded Security Subsystem, refer to ThinkVantage Technologies: Volume 2 Maintaining and Recovering Client Systems, SG24-6060.

IBM DirectorIBM Director V4.1 is the newest release of the industry-leading client/server workgroup manager. IBM Director’s tools provide customers with flexible capabilities to realize maximum system availability and lower IT costs. With IBM Director, IT administrators can view and track the hardware configuration of remote systems in detail and monitor the usage and performance of critical components, such as processors, disks, and memory.

IBM Director is discussed in Implementing Systems Management Solutions using IBM Director, SG24-6188.

Remote Deployment ManagerRDM provides tools to simplify configuration and deployment of operating systems and applications. Adding a computer to the RDM database allows for remote installation, maintenance, and software updates on client computers.

1.2 ThinkVantage Technologies process improvementsUsing the ThinkVantage Tools can help optimize the PC life cycle to enhance current processes. The two volumes of Using ThinkVantage Tools are divided into creation/deployment and maintenance/recovery of the ThinkVantage Technologies. The tools discussed in these Redbooks are key contributors in deployment optimization. ThinkVantage Technologies allow PCs to be more than just clients

ThinkVantage Technologies provides optimization and cost avoidance solutions for the following:

� Simplified image complexity by delivering a hardware-independent imaging solution

� Improved application deployment by delivering a detached application deployment solution

� Rapid transition by delivering a smooth data migration solution

� “Down the Wire” recovery by delivering a managed system recovery and backup solution

� Life cycle ends with data removal by delivering a Secure Data Disposal solution


� Additional solutions for security, deployment, management, support, wireless and more.

Many organizations will relate to Figure 1-3 for each part of the processes defined. Implementation of the ThinkVantage Technologies will reduce cost and offer opportunities for companies as illustrated below.

Figure 1-3 ThinkVantage Technologies tools and simplification of PC life cycle processes

1.3 Implementing a ThinkVantage Technologies solutionTable 1-1 outlines the efforts required to implement the tools discussed in both books. It also outlines whether training is recommended or required to ensure a smooth implementation into an organization.You will notice that as a worst case scenario, it will take less than two weeks to get staff trained on all of the tools mentioned in the chart below. Many of the tools have optional training and can be learned through the use of this redbook or existing product documentation.

Image Creation Team Loading Team Install TeamEnd-User

Responsibility Help Desk/Desk-Side Install Team

1-3 day [update]3-4 weeks [compleximage]2-3 IT resources

20-40 minper client

2.5-3h persystem3-4 system/dayper IT resource

1-12hGenerate helpdesk calls

Resources needs to haveallocated fundsCOST of DOING business

20-60 minper client

1 day - 1 week1-2 IT resources

3-5 minper client

25-30 min persystem15-30 system/dayper IT resource

5-15 minSLA driven andautomated

50% cost reductionnot uncommonBetter resource usage

10-15 minper client

Image CreationManagement

and TestDeployImage

InstallClient

MigrateData and

ApplicationSettings

Backup/Recovery

Remote Support

Software Updates

Inventory

CascadingDisposal


Table 1-1 Implementing ThinkVantage Technologies

IBM PCD Tool People needed to implement

Process change required

Training needed

Imaging

ImageUltra Builder

2-5 Skilled Administrator for Large Enterprise Company

1 Skilled Administrator for Small Medium Business Company

Yes, to build image, but the deployment of image remains similar

Yes, Required2 day training

Software Delivery Center

1-3 Skilled Administrator for LE

1 Skilled Administrator for SMB

Yes, to regroup applications by line of business or dept.

Optional 1 day training

NetworkDeployment

Rapid Deployment Manager (RDM)

1-3 Skilled Administrator for LE

1 Skilled Administrator for SMB

No existing process with image deployment best practice

Yes, recommended 1 day training

MigrationSystem Migration Assistant (SMA)

1 Skilled Administrator for LE and SMB

No existing process with automated migration beat practice


RecoveryRescue and Recovery

1 Skilled Administrator for LE and SMB

Yes, to create hidden recovery partition on local hard drive



Management

IBM Director Agent

1-3 skilled Administrator for LE

1 skilled Administrator for SMB

No, existing process with system management best practice

Included in IBM Director training

IBM Director 1-3 skilled Administrator for LE


No, existing process with system management best practice

Yes, recommended 2 day training

System Information Center

1-3 skilled Administrator for LE


No, existing process with asset management practice

Included in IBM Director training

DisposalSecure Data Disposal

1 IT staff for LE and SMB No, existing process with Hard Drive Data Disposal best practice


Low Med High

IBM PCD Tool People needed to implement

Process change required

Training needed

Note: The scale is relative to the other ThinkVantage Technologies uptime and migration tools and not a measure of good, average and poor.



Chapter 2. ImageUltra Builder

IT departments are usually faced with the demanding task of building workstations for their end users. In addition, most business units have different requirements to perform their jobs. For an IT department to be successful, it must team with its users to identify what information, software and tools need to be loaded on a workstation.

One of the most popular ways of distributing this information is through the use of images which contain the contents for a workstation. Through the use of images, corporations can ensure their PCs are consistently functional without having to load every machine individually. IT departments use images to control the versions of software and drivers used throughout a company.

ImageUltra Builder is a unique tool that provides IT Departments with an easy-to-use interface which centralizes the creation, maintenance and deployment of all their images.

The following sections will take you through how the modular approach of ImageUltra Technology will help you manage all your corporate images within one unique interface. We will also discuss how ImageUltra Builder interacts with other image management tools such as Microsoft Sysprep and Symantec DeployCenter.

2


2.1 Image management todayAn image consists of several components: an operating system, applications, device drivers, and other related files needed to successfully run a computer. In most cases, Information Technology (IT) departments create images on source computers, extract the images and store them in a central location. They then deploy the images to multiple computers either across a network or from a set of image CDs. This enables an IT department to develop standardized images and control the versions of software and device drivers used throughout their company.

2.1.1 Current tools and procedures used to build and deploy images

Unattended Installation - Scripted � Unattended installations can be either a CD based installation or an

over-the-network installation on to the hard disk drive in a PC.

� Can be fully unattended or partially unattended using Answer files created using the UNATTEND.TXT file

� Answer files determine what defaults to provide or what information to allow users to provide (user name, domain etc.)

� Downside, can take hours to install

� High technical knowledge needed to create and maintain scripts.

� Distribution hardware requirement in an “over-the-network installation” environment

� Upside, can support multiple hardware

Disk Duplication - Cloning Some companies use cloning utilities to create and deploy their images. First, they create an image file that contains the contents of a drive. That image is then loaded onto different machines in a corporate environment.

� Primary benefit is to provide consistency of corporate desktops.

� Can be either CD based installation or an over-the-network installation.

� Must use 3rd party utility such as Symantec DeployCenter or Symantec Ghost to make drive or partition images.

� Cloning is supported by Microsoft when used in conjunction with Sysprep. For more information on Sysprep see section on “The use and importance of Microsoft Sysprep” on page 23.

� Downside, one clone image for one system model


� Clone images are effected by chipset level changes

� Upside, install can be very quick

2.1.2 Image complexity leads to image management problemsKeeping and maintaining images can quickly become very difficult as organizations get more complex. The number of languages, hardware types and operating systems can increase the number of images exponentially, making it difficult to maintain.

The major challenges most IT departments face are as follows:

� Reduction of time required to create and test images. Different departments have varying levels of complexity in the image. These varying needs of different groups in an enterprise often result in manual installation of applications by IT staff

� Finding ways to build and deploy images across a wider range of hardware.

� Reducing or minimizing the total number of images that have to be maintained.

� Use of multiple Operating Systems increases deployment and help desk costs and support for multiple languages required by large multinational companies increases complexity and cost of large rollouts

� Users make unauthorized modifications to their standard image(s), generating increased help desk calls and requiring additional IT time to re-image PCs

� Over time, images have to be updated or rebuilt from scratch

2.2 Image management using ImageUltra Builder

The purpose of the ImageUltra Builder program is to provide IT departments with the tools needed to develop, deploy, install, and maintain a variety of images efficiently.

Through new tools and techniques, the ImageUltra Builder program enables you to break down images into reusable subcomponents (called modules) and use tree structures called maps to construct your images. These images (referred to as Smart Images, see 2.5.1, “ImageUltra Builder terminology” on page 21 and 2.6, “ImageUltra Builder process to create a Smart Image” on page 32) can then be deployed across a broad range of hardware platforms. Each Smart Image component is stored in a central location called a Repository. ImageUltra Builder creates and uses the IBM service partition for deployment.The service partition

Chapter 2. ImageUltra Builder 13

contains different modules for the operating system, applications, and devices drivers, as well as a set of recovery tools.The service partition provides its own operating environment which is not dependent on the Windows operating system being present on any active partition. For non-ibm hardware, ImageUltra Builder will create the service partition for you.

Figure 2-1 outlines the life cycle of an ImageUltra Image.

Figure 2-1 ImageUltra Builder: life cycle of an ImageUltra Image

2.3 Image creation preparation process

The process outlined in this section make the entire imaging process more efficient and thorough. The information gathered prior to when the actual image creation project is initiated will be very beneficial and make the process more efficient. Once this preparation phase is complete, the involved teams will have the information they require to begin the project and all future imaging processes will become more organized and simplified, thus eliminating costs and fact finding each time a new image is required.

Repository

Import

Build

Deploy,Install

Import Image Import Image modulesmodules

Build custom Build custom modulesmodules

Operating system, application, and device driver (opt.) modules

Additional drivers,application modules

RepositoryMaps

Drag-n-drop modules

DeplyDeplyImageImage

modules to modules to Service Service PartitionPartitionCreate Image layout Create Image layout


� Determine the project scope, deliverables and schedules. Communicate this to all involved parties.

� A list of contact names and responsibilities for all team members should be created.

� A list of all global customer locations should be created.

� Allocate the standard hardware for image creation, testing and support.

� Outline the imaging and ThinkVantage tools that will be used in the image creation process and that will be installed on the PCs.

– ImageUltra Builder for imaging

– Rescue and Recovery for backup and recovery

– System Migration Assistant for transferring user settings

– IBM Software Delivery Center for post imaging application installations

– Access Connections and Active Protection System for IBM laptops (mobile computers)

– Update Connector™ for IBM driver updates

– Embedded Security Subsystem for security

– Access IBM for support and system information

� Organize communication team meetings to discuss the project during each phase.

– Connectivity

There are several steps that need to be taken before the technical teams can become fully engaged. Completing these up front will save time and effort once the project begins. All engaged team members should be setup with the following if applicable:

� Security IDs

� Network IDs

� Remote access IDs and software

� Badges

� Server location information supplied to all the team members. This would include project required server share names, application and storage shares.

If this has not been previously outlined, create a static location for all software and image storage. This will keep consistent all images, testing software and documentation.


2.3.1 HardwareThis section outlines the current and future PC hardware infrastructure.

� Create an outline of the current standard PC hardware and all legacy systems that are to be supported. This should include:

– Make/Manufacturer

– Model

– Part number

– A ratio of each model in production and if location or business units have unique hardware.

– Specifications for each model

– Determine if the hardware standards are standard models or if custom modifications been made. If true, what has been added or removed.

� Document information on where PCs are being purchased.

– Manufacturer direct

– A supplier

� Create an information package on the PC ordering schedule. This will help determine the imaging schedule for new image or image updates.

– Orders are placed every quarter

– Orders are placed Ad-hoc

� Determine a schedule for evaluating new PC models. This will also help your image creation schedule.

– Every quarter

– Every year

– Determined by manufacturer roadmap

– Is there a standard product family, such as ThinkPad or ThinkCentre.

� Determine if a driver catalog will be maintained for all production PC models and stored on local server. This can be done for IBM PCs by using the ImageUltra Builder driver maps or the Update Connector ThinkVantage products.

2.3.2 ImageThe image section helps determine the expectations and requirements for creating an image. It would be a best practice to determine which PC models and operating systems shall be maintained in the current and future environments.


� Which operating system will be required for imaging

– The Service Pack level

– Patches, updates

– Languages required

– The PC model/s that this image will support

– Acquire all operating system source and application licenses.

� Create an outline providing all specific OS configuration settings and/or preferences.This is the most time consuming aspect of the image creation process and having a detailed checklist will make this more efficient. Listed are a few examples of the information that should be gathered.

– Partitioning structure

– FAT32 or NTFS

– Standard applications installed

• Determine application groups for ImageUltra Builder Maps

– Security settings

• User

• System

– Directory structure - User Data

– Configuration settings

� Document all image specific settings for support reference and version control.

– Version, language, patches, build name.

– Create a unique image version identifier on your build for reference if needed.

• This can be done by editing the oeminfo.ini file for example and having this locally on each user PC.

� Determine which ImageUltra imaging type will be used to create the image

– You can use one type or a combination of all depending on your requirements

� Determine if a copy of the image will be stored in a hidden partition on the target system. This can be done with IBM tools on IBM systems.

– You can choose to have ImageUltra Builder copy all the image modules to a hidden partition on the PC.

– Use IBM’s Rescue and Recovery to create a backup of the entire image and create incremental backups


� Outline a final testing and approval process for the image prior to release into production.

� Determine a schedule for image updates or maintenance.

– How often will this be required

• Quarterly

• Monthly

– Log and test any required future changes to the image.

• Changes to configuration

• New standard applications or version updates

• Service Packs

• Patches

• Security updates

• Driver updates

� Communicate to the end user the data backup and recovery strategy

– IBM Rescue and Recovery

– IBM System Migration Assistant for user specific settings

2.3.3 ApplicationsThe application section covers the standard or unique applications on the production images.

� Create a matrix of all standard applications required on each image.

– Determine an application owner contact for supporting each application.

– Required languages

– Required versions

– Specific location/region applications

– Business Unit specific applications

– Acquire all application source and licenses.

– Verify that the application is certified to run on the standard image operating system.

� Determine if or which applications will need packaged installations for the image. All the applications will need to install silently using the ImageUltra Builder, or IBM Software Delivery Center products.

� Create installation and configuration instructions for each application.


� Determine an application testing and approval process for release on an image or stand alone distribution.

2.3.4 DistributionThe distribution section covers the integration of the image once approved for production.

� Determine the ImageUltra Builder distribution method for the image.

– CD or DVD media

– LAN

– WAN

– All

� If required, provide a storage location for archiving legacy images.

� Determine the location of image integration. Several scenarios can be used depending on new product rollouts or rebuilds.

– Locally

– A supplier

– IBM Image and Technology Center

� Determine a software distribution method for ad-hoc updates

– Security updates

– Hardware BIOS or driver updates

• IBM Update Connector

• IBM RDM

– Manufacturer patches or updates

• Access IBM

– Application updates

2.4 Installing ImageUltra Builder V2.01

ImageUltra Builder is a purchased product and not available via download.

2.4.1 Minimum RequirementsThe following information provides the minimum requirements for the ImageUltra Builder console (the computer on which you install the ImageUltra program):


� Operating system: Windows XP Professional Edition or Windows 2000

� Disk Space: 100 MB of available disk space to install the ImageUltra Builder program.

� Additional storage is required for the repository, which can be on the ImageUltra Builder console or on a shared disk.

� The amount of disk space required for the repository depends on the size and number of modules that will be stored in it. Repositories cannot span drives, so make sure you have enough storage for future growth.

Removable-media drives:

� CD or DVD drive for installation

� Diskette drive for the creation of Network Deployment Diskettes and Import Diskettes

� CD-RW drive for CD deployment

� Minimum networking speed: 10 Mbps; Ethernet or token ring

2.4.2 Installation procedure1. After executing the installation file, you will see the ImageShield Wizard for

IBM ImageUltra Builder.

2. Click Next.

3. At the Welcome to the IBM ImageUltra Builder Setup window, click Next.

4. Click Yes to agree to the license agreement to continue the installation.

5. Select the installation directory. Click Next.

6. Click Finish to complete the installation process.

7. Install ImageUltra Builder Patch 3.0. For the list of problems solved by this update please refer to the README.TXT file.

Download the patch and readme.txt from the following URL:

http://www.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-53846

2.5 ImageUltra Builder components and basic operations

This section describes the various processes and components associated with the ImageUltra Builder program and how they relate to each other. For more



step-by-step instructions on how to complete any of the processes described in this chapter, refer to the ImageUltra Builder help system.

Think of ImageUltra Builder technology as a mechanism for storing individual operating systems, applications, drivers and image utilities into separate bins that can be combined to deploy images in multiple combinations. Each separate item is easily accessible for updating and maintaining without having to modify or recreate an entire new image. This is the modular approach that ImageUltra Builder technology uses to simplify image creation, maintenance and deployments. The master bin that contains all of the modules is called a repository. The individual items are called modules.

The repository stores all the modules and deployment maps into a central location.

2.5.1 ImageUltra Builder terminologyThe following is a high-level description of the ImageUltra Builder terminology:

� Smart Image: An image that includes intelligence to configure itself based on operating system, language, hardware configuration, and user application sets.

� Repository: Contains all the ImageUltra Builder maps and modules necessary to build your Smart Image.

� Module: A reusable installation package for a single operating system, application, or device driver.

� Container: Special type of module that allows you to group other modules together into a single identifier. All modules must be of the same type.

� Base Map: Defines the menu structure and modules (operating systems and applications) contained in a Smart Image.

� Driver Map: Defines the device driver modules contained in a Smart Image.

� Filter: Runs during the installation process and allows you to automate decisions. Filters are DOS programs that have a true or false return value.

� Utility: Utilities are DOS programs that run during the service partition boot. ImageUltra Builder does not have any built-in utilities, but they are easy to create.

Important: A module is a packaged, compressed, self-contained unit that can be combined with other modules in the repository to make one or more images. Each application is a module, each device driver is a module, each operating system is a module, and so on.


� Network Sync: Network synchronization occurs at deployment and at first boot. It allows a client with a Smart Image to look for updated maps on the “network” (in the repository).

� IBM Customization Program: Program used to create semi-portable Smart Images (Sysprep).

� Hardware Independent Imaging Technology (HIIT): Intelligently detects the correct driver base to install for IBM desktops and IBM laptops.

� Hidden Protected Area (HPA): A hidden area on new model IBM desktop or laptop hard disks. The Hidden Protected Area, also referred to as parties, enables IBM to provide a disk-based recovery solution that provides greater flexibility and enhances the security for recovery data, diagnostics, and potential future applications.

� Build: Used when testing a module or map in ImageUltra builder. The map or module can be edited or changed.

� Promote: Used after a map or module has been thoroughly tested and is ready for production. Once a module is promoted to the gold state, it is locked and you can no longer make changes to that module. Promoting a module to the gold state helps ensure that the module will not be changed accidentally.

� Import: Imports maps or modules from another source into your repository. This can be from a set of IBM Recovery CDs, a directory, another repository, a service or IBM Hidden Protected Area (HPA) partition.

� Export: Exports maps or modules from a repository to an archive directory.

� Deploy: Creates a network boot floppy used during deployment or creates the file structure needed to create a set of distribution CDs.

� Replica: A copy or reproduction of work.

2.5.2 Image typesThere are three basic image types supported within the ImageUltra Builder tool. They are described below.

� Ultra-portable image: This type of image is installed via a Windows unattended process and contains hardware-independent operating-system modules developed by IBM. Application modules and device driver modules can be developed by IBM or created using the ImageUltra Builder. The IBM created modules can be imported via the hidden protected area (HPA), service partition or from a set of recovery CDs. These modules enable you to create an image that can be used across the IBM product line of Hardware Independent Imaging Technology enabled (HIIT-enabled) personal computers.


For a listing of IBM HIIT-enabled personal computers, visit the ImageUltra Web site at:

http://www.ibm.com/pc/support/site.wss/MIGR-44316.html

� Portable-sysprep image: This type of image is created by a third-party image-cloning tool, such as Symantec Ghost or Symantec DeployCenter, but modified by ImageUltra Builder tools to enable the installation of additional modules created and managed by ImageUltra Builder. An example of this would be a non-hardware dependent cloned sysprep operating system that adds model specific drivers and user-specific applications after the base operating system is installed. The additional modules can be device driver modules to enhance portability across various hardware platforms or application modules to provide additional flexibility to meet the needs of individual department application requirements.

� Hardware-specific image: This type of image is created by a third-party image-cloning tool, such as Symantec Ghost or Symantec DeployCenter. It is a self-contained monolithic image, which does not enable the installation of additional modules. All files, applications and device drivers are contained within the image itself. The hardware configuration of the target computer must be the same as the hardware configuration of the source computer used to create the image because of this.

A hardware-specific image is similar to a portable-sysprep image, but the differences are:

– It does not have the ability to append itself with additional modules. It is essentially a “snapshot” of a source computer hard disk after the Microsoft Sysprep program has been run.

– When deployed to a target computer, the hardware-specific image performs a limited hardware query, but the hardware it can support is limited to the device drivers that were provided by the source computer.

– A hardware-specific image requires that the source and target computers contain the exact same hardware with little or no variations. It also requires that any variation in applications be handled separately from the image-deployment process and image-installation process.

2.5.3 The use and importance of Microsoft SysprepIf you intend to use portable-sysprep images or hardware-specific images, you must have a thorough knowledge of the Microsoft Sysprep tool. Unlike ultra-portable images, portable-sysprep images and hardware-specific images are based on images created from a source computer that has gone through a Windows setup operation. Therefore, specific user and hardware information must be removed from the source computer using the Sysprep tool before the



image can be deployed to other computers. In contrast, ultra-portable images are created from modules provided by IBM and are installed via a Windows unattended process. If you intend to use ultra-portable images only, the Sysprep tool is not used.

2.5.4 Which image type is best for you?You can use one or all methods depending on your company infrastructure. Here are some examples:

� To maintain existing PCs for which you already have images, you might choose to convert existing hardware-specific monolithic images into modules that can be stored and deployed using the ImageUltra Builder program.

� If you are planning to install assorted models of IBM PCs and ThinkPads, you might consider developing ultra-portable images that can be used across the IBM product line regardless of hardware variations.

� If you plan to install a mix of PCs from various manufacturers, consider using the ImageUltra Builder program in conjunction with third-party image-cloning software to create portable-sysprep images that enable the installation of application or device-driver modules so that the image can be deployed across a wider range of PCs. Because Smart Images support all three types of images, you can use combinations of images within a single base map.

All three image types can be used by a corporation, as can any combination of the image types.

Figure 2-2 outlines the basic differences between the three image types.


Figure 2-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.

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 time50 min + (Windowsunattended install)

20 min + (Sysprep) 15 min + (Sysprep)

Integrated with HIIT modules andImageUltra™ Builder modules 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

Function

Image Type


• 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.

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.

2.5.5 Module categoriesIn 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 2.15, “Creating a base operating system hardware specific module” on page 78.

– 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 2.13, “Creating an operating system add-on module” on page 66.

– 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 partitioning modules in a base map to accomplish various results. When you use a partitioning module to create additional partitions with data, the module contains all of the information required to create the additional partition and all of the data to be placed in the additional partition. These types of partitioning modules are typically created using an imaging tool, such as Symantec Ghost or Symantec DeployCenter. See 2.14, “Creating a partitioning module” on page 77.

� Application modules: Each of these modules contains all of the components associated with a specific application program. Software applications such as Microsoft Office, Adobe Acrobat and IBM System Migration Assistant would be separate application modules. See 2.10, “Creating an application module from source files” on page 48.


– If you are building an ultra-portable image or a portable-sysprep image, you can use application modules.

– If you are building a hardware-specific image, you cannot use application modules when deploying the image. All applications must have been previously contained within the hardware-specific image when it was created.

� Device driver modules: Each of these modules contains all of the components associated with a specific device driver. There would be a separate device driver module for the IBM ThinkPad video driver or a ThinkCentre audio driver for example. 2.11, “Creating a device driver module from source files” on page 54.

– If you are building an ultra-portable image or a portable-sysprep image, you can use device-driver modules.

– If you are building a hardware-specific image, you cannot use device-driver modules in conjunction with that image. All device drivers must be contained within the hardware-specific image.

During the deployment process, you choose which base map and which driver map to deploy. This enables you to maintain device-driver modules and driver maps independently of the operating-system and application content defined by base maps. In addition to modules, the ImageUltra Builder program enables you to create containers in the repository.

� Container

A container is a special type of module that enables you to group other modules together under a single identifier. All modules in a container must be of the same type. For example, you might want to group all of the device drivers used for a specific machine type into a device-driver container. Or, you might want to group a Windows 2000 base operating-system module with all of its associated add-on modules into an operating-system container. The use of containers is optional, but you might find containers helpful when creating maps because you can simply inserting the container module into your map instead of inserting each individual module.

� Filters

Filters automate a decision during the installation process. You typically use filters to obtain hardware-related information from a target computer to determine if a specific module or set of modules should be installed. The ImageUltra Builder program provides filters that check the machine type, machine type and model number, hardware platform (mobile or desktop), and whether or not a computer is an IBM computer. You can also develop your own filters if needed.


Filters are DOS-based programs that run during the installation process. In most cases filters query the BIOS of the target computer, but they can query other devices that store identification information in a ROM or EEPROM module. For example, you might want to check for the presence of a PCI modem before installing a modem-related application program or you might want to check for a specific machine type to determine which device drivers should be installed.

� Utilities

Utilities are DOS-based EXE, BAT, or COM files that run during the installation process. For example, an installer might want to run CHKDSK to determine the size and condition of a hard disk before any files get installed. Utilities are copied to the service partition of the target computer during deployment, run during the installation process, but never get copied to the active partition of the target computer. You can incorporate utilities in a map to run immediately before the installation menus, immediately after the installation menus, or as a result of a selection in the installation menus. You determine how the utilities run and in what order.

The ImageUltra Builder program does not provide any utilities. If you want to include utilities, you will have to build your own utility modules.

To use a utility, you either assign a utility module to a base-map menu item or use the Before/After Menu tab in the Map Settings window for base maps.

� Base map

A base map is a deployment repository that contains only the operating systems, add on, partitioning and application modules that are required for a unique deployment. This can be accessed through the base maps tab in the ImageUltra Builder application. The base map is used to organize modules for deployment to install by language, business unit or any other business specific map that you create.

For example, you can create a base map named “XP Standard” that would include a US English Windows XP portable-sysprep module, the standard application modules that are required on every computer in your corporation and any other add on, partition, filters, container modules that are required. Modules can be copied from the main repository to any or all base maps thus giving a corporation one location to store their images.

For conceptual information about developing base maps, refer to the ImageUltra Builder Version 2.0 User Guide.

� Driver map

A driver map is the menu driven area that contains all of the driver modules. This can be accessed through the driver map tab in the ImageUltra Builder application. This can be used to insert all the driver modules for a model specific system under one map heading. The IBM ThinkPad T40 2373-75U


driver map, for example, could contain the audio, video and network driver modules. This can either be setup to display a manual menu selection window during installation or a filter can be added to automatically select which drivers the system requires.

� Repository

All maps and modules are stored in a repository. When the repository is viewed through the ImageUltra Builder interface, the maps and modules are identified by descriptive names that you create. The actual file names displayed in My Computer or a DOS window are assigned by the ImageUltra Builder program. The following is a list of file extensions and description used for the files in the repository:

– .CRI: Metadata about the module. This information is used within the ImageUltra Builder interface.

– .DMA: Driver maps

– .BMA: Base maps

– .IMZ: Compressed module source

2.5.6 Module Window TabsWhen creating and adding modules to the ImageUltra Builder repository, a window with multiple tabs will be presented allowing you to describe various properties for the module. Refer to Figure 2-21 on page 51. Following is a description of those tabs.

General TabThe general tab allows you to enter general information about the module. Module name, version number, description of module, and there is even a field to encrypt your module.

Languages TabBy checking a language and operating system box, ImageUltra Builder will check the operating systems and language during the deployment stage; if there is no match, the module will not be deployed.

Source TabIn the source tab you detail all commands and files necessary to the execution of a module.

� In the Source directory field, browse to the directory where the source file for this application is located. Example: C:\apps


� In the Silent install command field, browse to the executable file contained in your source directory. Example: C:\apps\wrar280.exe

� In the Parameters field, type your silent install switch. Example: /s.

� Close the Properties window, and when prompted, select Yes to save.

Filters TabFilters are usually DOS-based programs. Typically, they will be a .EXE or .BAT file. Once you have created your filter modules you can then apply them to other modules.

Example: Filter ISIBM will run a check to make sure the hardware this module is being deployed to is an IBM Machine.

Options TabThere are a number of fields on this tab that will allow you to control the installation behavior of the module:

Target locationThese fields define whether the application files should be copied to the target partition.

If you type a path in this field and you also provide a Silent install command on the source tab, the files will be copied to the target partition in addition to the application being installed.

If you type a path in this field and you do not provide a Silent install command on the Source tab, the files will be copied to the target partition, but the application will not be installed automatically.

BehaviorThese fields are used to control the module installation order.

� Install hook

– Install during auditboot (Default): This selection enables the module you are creating to be installed during the first boot after the Windows setup is complete.

– Install during customer first boot: This selection enables the module you are creating to be installed after the auditboot, upon successful completion of Windows setup.

– Install when customer chooses via desktop shortcut: This selection enables users to install the module after the image is installed by clicking a shortcut on the desktop. The ImageUltra Builder program copies the


module source files to a folder on the user partition and creates an icon on the desktop that links to the installation file.

� Install slot:

The install slot number determines when a module is installed in relation to other modules that are assigned during the same boot cycle. Install slot numbers range from 1 to 9. The higher the slot number, the later the module is installed.

Hardware Independent Imaging Technology (HIIT) behaviorThis field determines how Hardware Independent Imaging Technology behavior is implemented during the installation process. This field only applies to modules that you plan to include in a driver map. Typically, you do not want to modify this field unless there are unique circumstances regarding the module you are creating. The following are the choices associated with the HIIT behavior field:

� Normal device detection: This selection is intended for device-driver modules that are used in driver maps.

� Ignore HIIT processing: This selection is intended for unique application modules that are used in driver maps. For example, you might want to include an application that contains application files and device drivers. In this case, you can choose to put the module in both maps.

� Always install: This selection is intended for modules in a driver map that fail to install correctly during normal HIIT processing.

For INF installs only� INF installable: Mark this check box if the module you are creating is an INF

installable. This field is typically used for device drivers only.

� Relative location of INF files in the source: This field is activated only if the INF installable field is marked. This field requires an entry if INF files needed for this module are not located in the folder defined in the Source directory field of the Source tab. If you need to define a path, the path must be a relative path based on the root folder of the source files.

2.6 ImageUltra Builder process to create a Smart Image

The following ImageUltra Builder process steps to create a Smart Image are covered in more detail in the referenced sections:

� Create a repository (refer to 2.7, “Create a repository” on page 33)

� Import IBM Preload modules into your Repository (refer to 2.8, “Import IBM Preload modules into your repository” on page 39)


� Create custom modules - preparation (refer to 2.9, “Create custom modules - preparation” on page 45)

� Create an application module from source files (2.10, “Creating an application module from source files” on page 48)

� Create a device driver module from source files (refer to 2.11, “Creating a device driver module from source files” on page 54)

� Create a utility/filter module (refer to 2.12, “Create a filter/utility module” on page 64)

� Create an add-on operating system module (refer to 2.13, “Creating an operating system add-on module” on page 66)

� Create a partitioning module (refer to 2.14, “Creating a partitioning module” on page 77)

� Create a base-operating system Hardware Specific module (refer to 2.15, “Creating a base operating system hardware specific module” on page 78)

� Create a base-operating system Portable-Sysprep module (refer to 2.16, “Create a base operating system Portable Sysprep Image” on page 87)

� Customize an Ultra-Portable operating system module (refer to 2.17, “Customize an Ultra-Portable operating system module” on page 99)

� Create a base map module (refer to 2.18, “Create your base map” on page 103)

� Create a driver map 2.19, “Create a driver map” on page 123)

Once you have completed the above steps you can then deploy your Smart Image to the target systems. The following sections will take you through each of the steps in the above process.

2.7 Create a repository

The first task that must be completed after installing ImageUltra Builder is to create a repository.


1. Open ImageUltra by double-clicking the IBM ImageUltra Builder desktop icon. If this is the first time that ImageUltra is opened, the Welcome window will be displayed (see Figure 2-3). If the Welcome window is not displayed, click File, then click New Repository....

Figure 2-3 New Repository welcome window

Repositories can be imported or created later as needed.

The “best practice” for the number of repositories for a customer would be the use of one repository. By using one repository, the customer can easily pull modules from different builds into a new folder for a new system. Multiple repositories are possible and may be useful for business partners maintaining images for different customers for example.


2. After reviewing the Welcome window, click Next. You will see a window similar to Figure 2-4.

Figure 2-4 Create Repository

Provide a name for the folder that the repository will be stored in.

Tip: It is recommended that you keep the length (and simplicity) of your directory and share locations as short as possible. This reduces the chance for error in your scripts and also avoids any “directory length” limitations that might be imposed by the operating system.

ThinkVantage


3. Click Next. You will see a window similar to Figure 2-5.

Figure 2-5 Description

Provide a description for the new repository.

ThinkVantage



Figure 2-6 Repository ID

Since this is the first repository that is created, accept the default repository ID that is provided. Click Next.

5. Click Finish to complete the creation of the new repository.

Creating a new folder in the ImageUltra Builder repositoryTo keep the repository organized, it is recommended that different folders be created under the repository to store modules that are associated with different hardware platform. This makes finding and updating modules easier in the future. Since all of the folders are contained in the same repository, all of the modules from the different folders will be available to create the system build. To create a new folder, perform the following steps:

1. Open ImageUltra Builder.

Note: This window provides details of what the repository ID is and what it is used for.


Figure 2-7 Default repository

2. Right-click Repository (see Figure 2-7). You will see a window similar to Figure 2-8.

Figure 2-8 Insert Folder

3. Click Insert.

4. Click Folder. You will see a window similar to Figure 2-9 on page 39.


Figure 2-9 New Repository folder

5. Rename the new folder to a name that is readily associated with the hardware platform that include the recovery CD modules (see Figure 2-9). In this case, T40_Windows_2000 is the name of the folder where the T40 ThinkPad Windows 2000 Professional recovery CDs will be imported.

In the next section, we begin preparing the source files for a module.

2.8 Import IBM Preload modules into your repository

There are several ways of importing IBM Modules into your repository. The quickest and easiest way to import these modules is to use a recovery CD set provided by IBM. The recovery CDs contain all of the software including operating system, hardware device drivers and applications that come preloaded on an IBM system.

2.8.1 Importing modules from an IBM recovery CD set1. Create a new folder in your repository.

2. From the main menu click the Import button from the menu. You will see a window similar to Figure 2-10 on page 40.


Figure 2-10 Import wizard welcome window

3. Select A set of IBM Recovery CDs. Click Next.

This same procedure can be used to import modules into the repository from any of the sources listed in the figure above.


4. Insert the first CD of the IBM Recovery CD set.

Figure 2-11 Import modules - insert CD

5. Click Next.


6. Select all of the modules to be imported. Click Next.

Figure 2-12 List of available modules and maps


7. Select the destination folder and then click Next.

Figure 2-13 Destination folder


Figure 2-14 Import ready to proceed

8. Click Import to begin importing the selected modules and maps.

Figure 2-15 Insert CD #2

9. Insert CD #2. Click OK.

10.Click Next to begin importing from CD #2.

11.Select all of the modules to be imported. Click Next.

12.Select the destination folder and then click Next.

13.Click Import to begin importing the selected modules and maps.

14.Insert CD #3. Click OK.

15.Click Next to begin importing from CD #3.

16.Select all of the modules to be imported. Click Next.


17.Select the destination folder and then click Next.

18.Click Import to begin importing the selected modules and maps.

If the following window is displayed, click OK.

Figure 2-16 Overwrite confirmation

19.Click Finish.

2.9 Create custom modules - preparation

Any application, device driver, or add-on operating-system component that you intend to deploy as a module must be prepared to perform an unattended/silent installation. This is mandatory for all application and device driver packages that you wish to install as part of an ImageUltra Builder Smart Image.

Note: If there are existing modules and/or maps in the repository folder that you are importing to, you will be prompted by the following window


The method used to prepare an application for ‘silent installation varies depending on the installation mechanism being used.

Common tools used to generate silent install packages for your applications or device drivers are Windows Installer and InstallShield. We will have a look at both in the following sections.

2.9.1 Windows Installer - msiexec.exe fileMsiexec.exe is the Windows Installer executable that runs the Windows Installer service. The Windows Installer service installs and manages installation packages written to specific standards and stored as a database in files with the .MSI extension.

The Windows Installer reads the installation database, performs the installation and then monitors the installed software to ensure functionality. When an .MSI is opened, msiexec.exe reads the data stored in the database and builds an internal script. It then performs the actions in the script to complete the installation. Sometimes Install Packages pre-install Windows Installer as part of their installation package.

A transform is a special kind of Windows Installer file (.MST file) that customizes a Windows Installer installation package. You use it to change the installation in some way for a specific set of customers or users.

The Windows Installer service does allow installation package to be installed silently.

There are four User Interface Levels that can be used while installing a package:

1. NONE (Completely silent installation)

2. BASIC (Simple progress bar and error handling)

3. REDUCED (Authorized UI, wizard dialogs suppressed)

4. FULL (Authorized UI with wizards, progress bar, errors)

To run an installation package with silently, you need to use the following command:

Note:

� An unattended installation is one which does not require any user interaction.

� A silent installation is one which does not display any indication of its progress.


MSIEXEC /i Product.msi /qn

If your release settings include SETUP.EXE, you can run the following command:

SETUP.EXE /s /v"/qn"

Basic MSI projects do not create or read response files. To set installation properties for a Basic MSI project, use a command similar to the following:

MSIEXEC /i Product.msi /qn INSTALLDIR=D:\ProductFolder USERNAME=’Valued Customer"

See the documentation associated with the specific installation product if you encounter any problems.

2.9.2 InstallShieldInstallShield is a very commonly used application packaging system. Installation packages created using InstallShield recognize commands such as /s, /SMS /r etc. The installer itself is the setup.exe file. To ensure the application installs silently, you will need to generate a response file (.iss file) if one is not already present. Both of these files, plus any other files needed to install your package need to be stored in the same folder.

Figure 2-17 Setup.exe and setup.iss files must be in the same folder


How to generate a SETUP.ISS file1. Copy all source files for the application into an empty folder. Make sure you

maintain the folder structure that was provided on the software manufacturer’s distribution media. In the case of a .ZIP file, make sure you maintain the folder structure when you unzip the file.

2. Open a command prompt window.

3. Change to the folder that contains the application SETUP.EXE file.

4. At the command prompt, type SETUP -R and then press Enter.

Figure 2-18 Setup - R command to generate a new setup.iss file

5. Follow the steps to install the program. As you install the program, the keystrokes and mouse clicks are recorded in the new SETUP.ISS file. Because the values you type will be used on all target computers, you should use company-related information in place of any personal information for which you might be prompted.

6. When the installation is complete, the new SETUP.ISS file will be in the Windows folder for Windows XP and the WINNT folder for Windows 2000.

7. Copy the new SETUP.ISS file from the Windows folder into the folder that contains the application SETUP.EXE file.

Now that you have generated all necessary files to silently install your package, you can create a module in ImageUltra Builder from these source files.

2.10 Creating an application module from source files

For this example we will create an application module based on the application WinRAR. Steps to create an application module from your application source files:

Note: Newer versions of InstallShield might involve different steps.


1. Select the Applications tab (Figure 2-46 on page 76).

2. Right-click the space in the window, select Insert application.

3. Click Next to create a module. You will see a window similar to Figure 2-19 on page 49.

Figure 2-19 Create Module window

4. The module type Application will be pre-selected. Click Next.


5. In the Name field, type WinRAR. Do not choose to make this module a container.


6. Click Next.

7. On the next window, you will be asked if you would like to create this module with the same settings as an existing module. Click Next without selecting any modules.


8. Click Finish to complete the New Module Wizard.

The properties window for this module will now pop up on the General tab (Figure 2-21).

Figure 2-21 WinRAR: Application window

In the Version field, type 2.80.


9. Select the OS/Languages tab. The window shown in Figure 2-22 will be displayed.


Under the languages selection, click the relevant Languages and Operating Systems boxes that this module will be supported on. In our example we have selected Check All.


10.Select the Source tab. The window shown in Figure 2-23 will be displayed.


– In the Source directory field, browse to the directory where all the relevant files needed to silently install this application are located.

– Select your setup executable or your batch file for your application. In our example we browse to the wrar280.exe file.

– In the Parameters field, enter your silent install commands. In our example we have used /s which is an install shield command. The /s command will ensure that the response file gets called to automate the installation.

11.Close the Properties window, and when prompted, click Yes to save.

You will now see the new module under the Applications tab on the main console.

12.Right-click the module, select Build.

You will now see a status bar indicating the module building progress.


When the building process is finished, you will see a window that lists the script files that have been created. See Figure 2-24.

Figure 2-24 List of files associated with this build

13.Click Finish. The new module has now been created.

2.11 Creating a device driver module from source files

In this section, we will create a module that will install a device driver. There are two ways of installing a device driver. Either you use a setup.exe file or a information file (INF).

� A setup.exe file can install the base device driver along with any associated mini-applications.

� An INF file is a text file that specifies the files that need to be present or downloaded for your driver to run and allows customization of the installation procedure.

The following sections show how to install an audio driver using both of these methods.

2.11.1 Install SoundMAX audio driver from a setup.exe file1. Open your ImageUltra Builder Repository and select the location where you

wish to create your new device driver module.


2. Select the Device Drivers tab.

3. Right-click the space in the window, select Insert Device Driver. The New Module Wizard will now appear.

4. Click Next to start creating a module. You will see a window similar to Figure 2-25 on page 55.


Device Driver will be pre-selected.




6. In the Name field, type SoundMAX Audio Driver. Do not choose to make this module a container.

7. Click Next.

8. You will now be asked if you would like to create a module, with the same settings as an existing module. Do not select an existing module here. Click Next.


9. Click Finish to complete the New Module Wizard.

You will now see the module Properties window on the General tab.

Figure 2-27 SoundMAX Audio Driver: Device Driver

10.In the Version field, enter 5.12.01.3535. To find the version of the device driver, open the INF file associated with your driver. See Figure 2-28.


Figure 2-28 Device driver version information

11.In the Family field shown in Figure 2-27, select Audio.

Tip: When creating device driver modules it is highly recommend to enter the version of the driver being installed to help you keep track of different driver versions.


12.Go to the OS/Languages tab (Figure 2-29).

Figure 2-29 SoundMAX Audio Driver: Device Driver window

13.Under the Languages selection, click Check All. Under the Operating Systems selection, select Windows 2000, Windows 98, Windows Millennium, Windows XP Home and Windows XP Professional.


14.Go to the Source tab.

Figure 2-30 SoundMAX Audio Driver: Device Driver window

15.In the Source directory field, type c:\drivers\win\audio.

16.In the silent command field, type setup.exe.

17.In the Parameters field, type -s.

18.Close the Properties window. When prompted, select Yes to save the module.

You will see the module under the Device Driver tab on the main console.

19.Right-click the module, select Build.


20.When the build process is finished, you will see a window that lists the script files that have been created.

Figure 2-31 Review your scripts window

21.Click Finish. The module has now been built.

2.11.2 Install SoundMAX audio driver from an INF file1. Repeat steps 1 to 13 above.


2. Go to the Source tab and type in the location of where the INF file is stored, for example C:\Drivers.

Figure 2-32 Audio driver source file information


3. Click the Options tab and check the INF installable box.

Figure 2-33 Check the INF installable box in the Options Tab

4. Close the Properties window. When prompted, select Yes to save the module.


5. Right-click the module, select Build.

6. When the build process is finished, you will see a window that lists the script files that have been created.


7. Right-click the module, select Build.

8. Click Finish. The module has now been built.


2.12 Create a filter/utility module

Filters and utilities are usually DOS-based programs. Typically, they will be a .EXE or .BAT file. The process of creating either a filter or utility module is almost the same as for the other modules.

2.12.1 Example of a filterIn this example we will show how to use the IBM preload filter, IBM Hardware Platform Check, in an application module. In our example we will use this filter with the IBM Active Protection System application. This will check if the target system is a mobile system. If not, this application module will not be installed.

1. Open the application module.

2. Click the Filters tab.

3. Click the insert filter icon and select the ImageUltra 2.0 - IBM Hardware Platform Check (ismobile) module as below. See Figure 2-34

4. Click OK and save the module.


Figure 2-34 Add ISMOBILE filter to the Active Protection System module

When would you need to use this filter? For example, an application such as IBM’s Active Protection System, which is dependant on mobile hardware, and will not function on a desktop system, you can use this filter.

There are a few differences in the windows you will see:

� Since they are DOS-based, there is no need to select a supported operating system. There is just an option to select a language.

� On the Source tab, you only specify a source directory and an execution command with possible parameters.

These files do not install, so there is no need to specify a target path.


2.13 Creating an operating system add-on module

In this section, we will create an operating system add-on module, for Windows 2000 Service Pack 4:

1. Open the ImageUltra Builder console.

2. Select the Operating Systems tab.

Figure 2-35 IUB repository, operating systems tab

3. Right-click the space in the window and select Insert OS. You will see a window similar to Figure 2-36 on page 67.


Figure 2-36 Create new module wizard

4. Click Next to create a module.

Figure 2-37 Create module wizard, module type selection


5. In Figure 2-37, select Operating System as the type of module to create, then click Next.

Figure 2-38 Create module wizard, enter name window

6. In the Name field (Figure 2-38), type Windows 2000 Service Pack 4. Do not choose to make this module a container.

Note: A container is a group of modules. It is used to make the organization of modules easier. An example of a container would be a main operating system module, together with all patches and hot fixes that apply to it.



Figure 2-39 Create module wizard, replicate settings window

For our example, it is not necessary to select an existing module.



Figure 2-40 Create module wizard, operating system module type selection

9. Select Add-on operating system module.


10.Click Next. You will see a window similar to Figure 2-41.

Figure 2-41 Create module wizard, completion window


11.Click Finish. You will see a window similar to Figure 2-42.

Figure 2-42 Module properties, general tab

12.In the Version field, type SP4.

Note: You can assign a password to the module; this will prevent the module from being unpacked by any process other than an ImageUltra Builder process.


13.Select the OS/Languages tab. You will see a window similar to Figure 2-43.

Figure 2-43 Module properties, OS/Languages tab

14.Under the Languages selection, click Check All. Under the Operating systems selection, select Windows 2000.

Note: The ImageUltra Builder will check the operating systems and language during the deployment stage; if there is no match, the module will not be deployed.


15.Go to the Source tab. You will see a window similar to Figure 2-44.

Figure 2-44 module properties, Source tab

16.Click Browse next to the Source directory field, locate and select the c:\win2ksp4\i386 directory.

17.Click Browse next to the Silent install command, locate and select update.exe in the c:\win2ksp4\i386\update\ directory.

18.In the Parameters field, type -q -n -z.

The preinstall command runs before the Silent install command. An example of this would be a utility that creates a directory.

The postinstall command runs after the Silent install command. An example of this would be a utility that deletes a shortcut.


19.Go to the Options tab. You will see a window similar to Figure 2-45.

Figure 2-45 module properties, Options tab

20.Change the Install slot to 1. We want the Service Pack to install before any of the other modules.

21.Close the Properties window. When prompted, select Yes to save the module.

You will now see the new module under the Operating Systems tab on the main console (Figure 2-46).


Figure 2-46 Module creation finished

22.Right-click this new module, then select Build.

You will now see a status bar, indicating the module building progress.

23.When the building process is finished, a window will pop up listing the script files that have been created.

Figure 2-47 Scripts generated

24.Click Finish. The module has now been created.


2.14 Creating a partitioning module

A partitioning module is a special type of operating-system module that has the following purposes:

� To delete one or more user partitions before installing an image

� To create an additional data partition on the target computer beyond the C partition - see section below.

� To preserve one or more pre-existing data partitions on a target computer

� To disable the default partitioning behavior of the ImageUltra Builder program

By default, the ImageUltra Builder program automatically deletes all user partitions on the target computer as a starting point for installation. You can override the default behavior or make the behavior dependent on a menu selection through the use of partitioning modules.The ImageUltra Builder program provides three ready-to-use partitioning modules in the root node of the repository. With the help of an imaging cloning tool like Symantec DeployCenter, you can also generate your own partitioning modules using script files:

� DrivePrep - Delete All Partitions: This partitioning module is designed to delete all user partitions on the target computer hard disk before the new image is installed.

� DrivePrep - Delete C Partition Only: This partitioning module is designed to preserve pre-existing data partitions on a target computer and use the space previously used by the C partition for the new image.

� DrivePrep - Delete No Partitions: This partitioning module disables all partitioning activity generated by the ImageUltra Builder program and is used only in special cases with a Portable-Sysprep Image or Hardware-Specific Image that contains all formatting and partitioning instructions.

Tip: Once this module has been tested, you will want to promote it to a “gold” state. When a module is in gold state, it is locked and no additional changes can be made. This prevents unwanted modification of modules you know have been verified for functionality.

Important: Understand that the order in which these partitioning modules are installed is extremely important. You set the order in the Install Sequence tab of the base-map Map Settings window (see “Install Sequence tab” on page 118).


2.15 Creating a base operating system hardware specific module

Base operating system modules can be created from hardware specific images (industry standard images from Symantec Norton Ghost or DeployCenter) or portable-sysprep images.

2.15.1 Create and prepare the image file1. On a source computer, install the Windows operating system that you want on

your target computers. You can use any file system that you want.

2. Install any application programs that will be common across all of your target computers.

3. Use either Symantec DeployCenter or Ghost software to create the image. For more information on how to use Symantec DeployCenter with ImageUltra Builder refer to Chapter 2.21, “Using ImageUltra Builder and Symantec DeployCenter together” on page 139.

4. Store the image in its own folder. In the case of CD deployment, where you have to segment the image into CD-sized files, store all of the files in a single folder. Make sure the folder is in a location that is accessible by the ImageUltra Builder console.

5. Store the image-cloning tool that you used to create the image (Symantec Ghost or Symantec DeployCenter) in the same folder as the image file.

6. Store any batch files or script files that you may have created in the same folder as the image file.

2.15.2 Add the donor image to the ImageUltra Builder repository

Complete the following instructions to insert the module:


2. Select the repository. The location that the modules are placed in is not critical. The modules can be moved around and reorganized within the same repository just like files in a folder in Windows Explorer.

Tip: Refer to the section titled Creating Hardware Specific Images in the ImageUltra help file. This section provides useful information on using Symantec Ghost and Symantec DeployCenter.


3. Click Insert. You will see a window similar to Figure 2-48.

Figure 2-48 Insert Operating System

4. Click Operating System.

5. Click Next.

6. Select Operating System.

7. Click Next.

8. Type a name for this Operating System. For example, type:

Compaq Deskpro EN Windows 98se - Sales



Figure 2-49 OS module name



Figure 2-50 OS module type window

11.Select Base operating system module.

12.Select Hardware Specific from the Image Type pull-down menu.

13.Click Next.

14.Click Finish.

2.15.3 Setting the module attributesComplete the following instructions to edit the hardware-specific OS module:

1. The Operating System module that was just created will open for editing. If it does not, double-click the operating system module located in the right window of the ImageUltra Builder interface.


Figure 2-51 OS module general window

2. From the General tab, provide a version number for the newly created module. If this is the first version of this particular module, use 1.0.0.

3. In the Comments box, add text that details what this module is for. The operating system, hardware platform, business unit, language, date, who created the original image and who created the module for the image would all be useful information to include here.


4. Click the OS/Language tab.

Figure 2-52 OS/Language window

5. Select the languages and operating systems that this OS module supports. For our example, we selected English and Window 98.

Note: Since this is a hardware specific module based on a legacy image, realistically this module can only support one language and one OS. ImageUltra Builder does not test the image that is used for the module. It is the responsibility of the individual creating the module to insure the source image file is functional and that the language and operating systems that are selected for the module are supported by the legacy image that was used.


6. Click the Source tab. You will see a window similar to Figure 2-53.

Figure 2-53 Source window

7. Click Browse of the Source directory field and then select the legacy image file that will be deployed using this module.

8. Click Browse of the Silent install command field.

9. Select a batch file that has the execute command and switched required to install the legacy image.

10.Click Save to save the changes that have been made.

2.15.4 Build the moduleAfter all modifications to the module have been completed, the module must be built. The following steps show the procedure for building the OS module.

Tip: The asterisk after the module name in the title bar of the operating system module edit window indicates that the module has been modified and not saved yet.


1. Select the OS module that is ready to be built. See Figure 2-54

Figure 2-54 IBM ImageUltra Builder - [ThinkVantage: Repository] window

2. Click the Build button on the menu bar (see Figure 2-54).

3. A window into the source directory will open.

4. Select the image file for this module and click Open. Make sure you do not have any additional image files in this folder.

Figure 2-55 Build confirmation window

5. Click OK.

Figure 2-56 Build completion window


6. Click OK.

Now that the module is built, it can be deployed using one of the methods described in 2.20.4, “Deployment methods” on page 132.

This same process will be repeated for each of the legacy images that your company will be deploying using ImageUltra Builder.

Figure 2-57 Hardware Specific OS modules

Note: Ensure that the server on which the ImageUltra Builder repository resides has sufficient space to contain all of the modules. The hardware specific OS modules will be slightly larger than the original legacy images that they were created from since they contain the legacy image.


2.16 Create a base operating system Portable Sysprep Image

In summary, the characteristics associated with a Portable-Sysprep Image method using ImageUltra Builder and Symantec DeployCenter are:

� Semi-modular (supports the installation of separate application modules and driver modules to append the base OS image.

� Setup is run once on a source computer

� Sysprep cleans out user information and some hardware-specific information from the registry

� Performs a limited hardware query at the target computer (Windows plug-n-play)

� User information can be predefined

The benefits of the ImageUltra Builder and Symantec DeployCenter method are:

� Initial setup at the target computer is typically 10 minutes or less for a base OS image, plus the time it takes to install all application modules

� Portability of applications and device drivers (such as video, audio, network, etc.)

� Supports IBM and non-IBM computers

� Base operating system module can include service packs and large core applications (such as office suites), which speeds installation time

There are five main steps to creating a base operating system module based on a portable-sysprep image:

1. Make the IBM Customization Program accessible to the source computer

2. Create the portable-sysprep image on a source computer and create the image files

3. Add the portable-sysprep image to the ImageUltra Builder Repository

4. Setting the module attributes

5. Building the module from the image files

2.16.1 Installing the IBM Customization ProgramBefore you can create a portable-sysprep image, you must first make the IBM Customization Program (IBMCP.EXE) accessible to the source computer. The ImageUltra Builder program enables you to copy the IBM Customization Program


on a diskette, shared drive, or any other media to which the ImageUltra console has direct-write access.

1. Use Windows Explorer or My Computer to open the IBMCP folder in your repository.

2. Copy the IBMCP.EXE program to a diskette or to a shared drive that the source computer can access during the development of the image. If you use a diskette, label the diskette ImageUltra IBM Customization Program.

3. Do one of the following:

a. Provide an ImageUltra IBM Customization Program diskette to any personnel responsible for creating portable-sysprep images

b. Provide the path to the IBMCP.EXE program to any personnel responsible for creating portable-sysprep images.

2.16.2 Create the portable-sysprep image on a source computer Before you begin, make sure you put the IBM Customization Program either on portable media that is compatible with the source computer or a shared drive that the source computer is able to access after the operating system and other programs have been installed. See 2.16.1, “Installing the IBM Customization Program” on page 87” for more information.

To create and prepare portable-sysprep image source files, do the following:

1. On a source computer, use MS-DOS to format the hard disk as follows.

Insert the MS-DOS diskette into the source computer diskette drive and restart the computer.

2. Run FDISK.EXE and create a FAT32 primary partition. In most cases, you will want to use the entire hard disk except for the service partition.

3. Leave the MS-DOS diskette in the drive and restart the computer.

4. Format the primary partition using FORMAT C: /S

Tip: If you cannot remember the path to your repository, in the ImageUltra Builder Main window, click File and then click Open repository. The repository paths will be listed. You can use any repository.

Note: You must use an MS-DOS diskette for this step. Do not use Windows or PC-DOS to partition or format the hard disk. You can create an MS-DOS diskette from Windows 98, but be sure to also copy the FORMAT.COM and FDISK.EXE programs on the diskette.


5. Install the Windows operating system (Windows XP or Windows 2000) that you want on your target computers. Do not allow the Windows installation program to reformat the hard disk.

6. Access and run the IBM Customization Program (IBMCP.EXE). This program might be on portable media or a shared drive.

7. Sysprep preparation:

For Windows 2000:

– Obtain the Microsoft Sysprep program designed for your operating system.The Windows 2000 version of the Sysprep program is available from the Microsoft Web site at:

http://www.microsoft.com/windows2000/downloads/tools/sysprep/license.asp

– You will need the following files: SYSPREP.EXE and SETUPCL.EXE.

– Copy the SYSPREP.EXE and SETUPCL.EXE files into the C:\SYSPREP folder.

– If you are creating a Windows 2000 image, obtain the SHUTDOWN.EXE file from one of the following sources and copy it into the C:\IBMWORK folder:

• Windows NT® 4.0 Resource Kit Support Tools at:

http://www.microsoft.com/ntserver/nts/downloads/recommended/ntkit/default.asp

• Windows 2000 Resource Kit at:

http://www.microsoft.com/windows2000/techinfo/reskit/default.asp

For Windows XP

– Obtain the Microsoft Sysprep program designed for your operating system.The Windows XP version of the Sysprep program is available from the Microsoft Web site at:

http://www.microsoft.com

Or on the Windows XP CD in the \SUPPORT\TOOLS\DEPLOY.CAB file. You will need the following files: SYSPREP.EXE, SETUPCL.EXE, and FACTORY.EXE.

– Copy the SYSPREP.EXE, SETUPCL.EXE, and FACTORY.EXE files into the C:\SYSPREP folder.

8. The IBM Customization Program creates an empty TAG file for Windows 2000 (C:\IBMWORK\WIN2000) and Windows XP Professional (C:\IBMWORK\XPPRO). If you are making a Windows XP Home image, rename C:\IBMWORK\XPPRO to C:\IBMWORK\XPHOME.

9. If necessary, install any application that will be common across all of your target computers. If you have applications that you cannot make into a


http://www.microsoft.com




module, now may be a good time to install them. These application will then become part of your base operating system module.

10.Make any other modifications to the image that you feel are necessary for your custom installation.

11.To automate Sysprep do the following:

– Edit the C:\IBMWORK\PRODKEYP.FM file to include your Windows Product ID key. You will need to edit all three lines;

– You will also need to enter information into the USER SETTINGS of your Base Map. Please refer to “Create your base map” on page 103

12.Use the following procedure to modify the BOOT.INI file so by default, the source computer will boot to DOS instead of Windows:

a. From the Windows desktop, right-click My Computer and then click Properties.

b. Click the Advanced tab.

c. Click the Startup and Recovery button.

d. In the Default Operating System field, use the drop-down menu to select either DOS or Microsoft Windows, whichever is present.

Do not select Microsoft Windows 2000 Professional/fastdetect, Microsoft Windows XP Professional/fastdetect, or Microsoft Windows XP Home/fastdetect.

e. Click OK.

13.Run SYSPREP.EXE as follows:

a. Windows 2000: Run C:\SYSPREP\SYSPREP -quiet

b. Windows XP: Run C:\SYSPREP\SYSPREP.EXE -factory -quiet

14.Use either Symantec Ghost or Symantec DeployCenter software to create the image files. If you intend to deploy the image using CDs, make sure you use the tools provided with Ghost and Symantec DeployCenter to segment the image into files that can fit on CDs.

Note: This step is optional. You can include common applications as part of your operating-system module or you can build separate application modules and control them through your base map.

Important: For Windows XP, it is mandatory to run the -factory -quiet command.


15.Store the image file in its own folder. In the case of CD deployment, where you have to segment the image into CD-sized files, store all of the files in a single folder. Make sure the folder is in a location that is accessible to the ImageUltra Builder console.

16.Store the following files used to create the image (in our example we used Symantec DeployCenter) in the same folder as the image file.

– PQIMGCTR.EXE, PQIMGCTR.OVL PQDPLCTR.RTC

– Store any batch files or script files you may have created in the same folder as the image file.

2.16.3 Add the donor image to the ImageUltra Builder RepositoryComplete the following instructions to insert the module:


2. Select the repository. The location that the modules are placed in is not critical. The modules can be moved around and reorganized within the same repository just like files in a folder in Windows Explorer.

Note: When creating your image be sure to:

1. Store the image file, example T41WXP.PQI, in its own folder. Example: c:\Server\Images\T41WXP.PQI

2. Store the following ImageCenter files in the in the same folder as the image file.

– PQIMGCTR.EXE, PQIMGCTR.OVL, PQDPLCTR.RTC

3. Store any batch files or script files you may have created in the same folder as the image file

4. Make sure this folder is in a location that is accessible by the ImageUltra Builder console.

5. Any additional image files will be copied into this module.

6. Make sure only the above files are stored in this folder.


3. Click Insert. You will see a window similar to Figure 2-58.

Figure 2-58 Insert Operating System

4. Click Operating System.

5. Click Next.

6. Select Operating System.

7. Click Next.

8. Type a name for this Operating System. For example, type:

IBM T41 Windows XP Pro



Figure 2-59 Portable Sysprep OS module



Figure 2-60 OS module type window

11.Select Base operating system module.

12.Select Portable Sysprep from the Image Type pull-down menu.

13.Click Next.

14.Click Finish.

2.16.4 Setting the module attributesComplete the following instructions to set the portable sysprep OS module attributes.

1. The Operating System module that was just created will open for editing. If it does not, double-click the operating system module located in the right window of the ImageUltra Builder interface.


Figure 2-61 OS module general window

2. From the General tab, provide a version number for the newly created module. If this is the first version of this particular module, use 1.0.0.

3. In the Comments box, add text that details what this module is for. The operating system, hardware platform, business unit, language, date, who created the original image and who created the module for the image would all be useful information to include here.


4. Click the OS/Language tab.

Figure 2-62 OS/Language window

5. Select the languages and operating systems that this OS module supports. For our example, we selected English and Window XP Professional


6. Click the Source tab

Figure 2-63 Enter source parameters

7. Click Browse of the Source directory field and then select DeployCenter image file that will be deployed using this module.

8. Click Browse add select the executable for your imaging tool. In this example we selected the Symantec DeployCenter executable.

9. Enter the command and switches required to install this image.

10.Click Save to save the changes that have been made.

2.16.5 Build the module from the image filesAfter all modifications to the module have been completed, the module must be built. The following steps show the procedure for building the OS module.


1. Select the OS module that is ready to be built.

Figure 2-64 Select the operating system module you wish to build

2. Click Build from the toolbar.

3. A window will open pointing to your source directory.

4. Select the image file for this module and click Open (see Figure 2-65).

Figure 2-65 image file selection window

5. Click OK.


Now that the module is built, it can be deployed using one of the methods described in 2.20.4, “Deployment methods” on page 132.

2.17 Customize an Ultra-Portable operating system module

Ultra-portable modules are only available by importing them from an existing IBM Preload. There are several ways to import an Ultra-Portable module. Please refer to “Import IBM Preload modules into your repository” on page 39, for methods of importing modules into an ImageUltra Repository

Ultra-portable images are the most flexible for adapting to various hardware and software environments. Since ultra-portable images are only available through the use of existing operating system modules, customizations using additional ImageUltra Builder modules may be required. This section will illustrate the requirements for changing these files using additional modules to customize an image.

This example outlines the customization of the UNATTEND.TXT file.

Things you will need are:

� UNATTEND.TXT - Extract a copy from an existing IBM image. The files are located in the c:\i386 directory.

� A working base map - Modify an existing base map to include this enhancement.

Perform the following steps:

1. Create the C:\UNATTEND directory.

2. Copy your customized UNATTEND.TXT into that directory.

The UNATTEND.TXT below has the information which disables games and components not required.

3. Create an operating system add-on module with the following attributes:

Note: Refer to 2.13, “Creating an operating system add-on module” on page 66 for details on creating this type of module.


– Under the General tab in the Name field, type UNATTEND.TXT modification (see Figure 2-66).

Figure 2-66 General Settings for UNATTEND.TXT modification


– In Figure 2-67 under the Source tab in the Source directory field, type c:\unattend.

Figure 2-67 Source tab window


– In Figure 2-68 under the Target partition field, select C:.

– In the Path to copy installable files, type i386.

Figure 2-68 Identify File Destination

4. Select the appropriate languages and operating system. In this example, this means all languages and Windows 2000.

5. Build the module.


6. Add it to your base map. It should look like Figure 2-69 when complete.

Figure 2-69 Adding the new module to a base map.

2.18 Create your base map

Base maps control which operating systems, applications, and utilities are deployed as part of a Smart Image as well as the menu system seen at the target computer during installation. The tree structure of a base map varies depending on the type of image or images contained in the map and the specific needs of your organization. In any case, you must create a map entry in the repository before you construct the map tree structure.

Driver maps control which device drivers and hardware-specific applications are deployed as part of a Smart Image. Driver maps can be simple (specific to one machine type) or complex (designed for many machine types), depending on the needs of your organization.

In this example below we created an ImageUltra Builder Smart Image for Company TVT. It includes a base map and a driver map. The base map includes the two portable-sysprep donor images.The driver map supports multiple hardware platforms, in our example we created driver maps for ThinkCentre and ThinkPad.

In this section, we will create a base map. Complete the following instructions:

1. Go to the Base Maps tab (Figure 2-70).


Figure 2-70 ThinkVantage: Repository

2. Right-click in the window on the right and select Insert →Base Map. You will see a window similar to Figure 2-71.

Figure 2-71 New Map Wizard window


3. Click Next to proceed to the Create Map window (Figure 2-72).

Figure 2-72 Create Map window

4. Select Base Map and click Next.


5. In the Name field, type TVT Map.





7. It is not necessary to copy an existing map for our example, therefore, click Next.


8. You will see a window similar to Figure 2-75.


Network synchronization: The network-sync feature enables target computers to search for updated maps in the server repository. If a base map has been modified, with the addition on a new service pack module for example, the news modules will be injected into the service partition of the target computer.

We do not want to enable synchronization for this example.




To control the module behavior after deployment, you can select one of the following:

– Delete none: If after installation you want the service partition of the target computer to contain the complete Smart Image, click the Delete none radio button.

– Delete unused: If after installation you want service partition of the target computer to contain only the maps and modules required to recreate the installed image, click the Delete unused radio button.

– Delete all: If after installation you do not want any maps or modules in the service partition of the target computer, click the Delete all radio button.

For our example, we select Delete none.




11.Click Finish. You will now see the map under the Base Maps tab (Figure 2-78).

Figure 2-78 ThinkVantage: Repository window


12.Next, we will insert a menu item into the created map. Right-click in the window pane on the right. See Figure 2-79.

Figure 2-79 TVT Map: Base Map window

13.Select Insert →Menu item. You will see a window similar to Figure 2-80.


14.Type English in the box to name the menu item.

15.Next, select English in the left window and right-click in the window on the right, then select Insert →Menu Item.

16.Type Windows 2000 in the box to name the Menu Item.

17.Repeat Step 15 to add another Menu Item under the English item.


We will name this item: Windows XP.


18.Select Windows 2000 on the left and right-click in the window on the right, then select Insert →Operating System.

The Add Operating System window will appear (Figure 2-82).

Figure 2-82 Add Operating Systems window

19.Select Operating System container (Ultra Portable WIN2000) from the list and click OK.

Note: Our example repository contains both modules that have been imported from an IBM Recovery CD and the ones we created in 2.13, “Creating an operating system add-on module” on page 66.


20.Repeat Step 18 to insert another operating system module.

Figure 2-83 Add Operating Systems window

21.Select Windows 2000 Service Pack 4 from the list and click OK.

22.Select Windows 2000 on the left and right-click in the window on the right, then select Insert →Application.

The Add Applications window will appear.

Figure 2-84 Add Application window

23.Select WinRAR from the list and click OK.

24.Select Windows 2000 on the left and right-click in the window on the right, select Insert →Device Driver.

The Add Device Drivers window appears.


Figure 2-85 Add Device Drivers window

25.Select SoundMAX Audio Driver from the list and click OK. You will see a window similar to Figure 2-86.


2.18.1 Base map settingsIn the Map settings window for a base map, you will see eight tabs (see Figure 2-87).


Figure 2-87 Map settings window

General tabThe General tab lets you view the name and add comments about the map. You can also assign keywords, which are used in conjunction with deployment media (ImageUltra Builder deployment CDs or diskettes) to minimize the number of maps that can be selected during the deployment phase.

When the diskette or CD is started in a target computer, only those maps with matching keywords can be selected.

User Information tabThe User Information tab enables you to work with end-user settings that are required during the installation process.


These are typically the settings that you are prompted for during Windows setup or Sysprep mini-setup. They include:

� Administrator password

� Computer name

� DHCP configuration

� User’s full name

� Gateway

� IP address

� Workgroup

� Organization name

� Subnet mask

You can use the User Information tab to predefine default values, create custom prompts for the installer, or both. All defined user information is then presented to the installer near the beginning of the installation process, thereby minimizing the amount of time that an installer needs to be present during the installation process.

You can use this tab for base maps for ultra-portable and portable-sysprep images. Hardware-specific images do not have the capability of using the information on this tab and will ignore any user information defined on this tab.

Important: If you wish to automate your portable-sysprep installation, you must enter a value by default. Make sure you do not select the option to prompt the user.

� Administrator password

� Computer Name

� Full Name

� Workgroup


Figure 2-88 User Information

Before/After Menu Options tabThe Before/After Menu Options tab enables you to execute one or more utilities before or after the installation process at the target computer.

Using the Before/After Menu Options tab is optional. However, it may be helpful for certain tasks. For example, you may want to run FDISK to format and re-partition the target computer before making selections from the installation menus.


Figure 2-89 Before/ After menu options

Install Sequence tabThe Install Sequence tab enables you to define the order in which modules within the same install slot are installed.

Changing the order of module installation is optional. Usually, there is no need to change the module-installation order unless one or more of the following conditions exist:

� One or more modules have dependencies on other modules being installed first

� The image is not installing correctly

� You are installing a base-partition module

� You have modules that are colliding


Image Cleanup tabThe Image Cleanup tab determines which files will be stored in the service partition of the target computer after the image has been installed. The choices are as follows:

� Delete none: If after installation you want the service partition of the target computer to contain the complete Smart Image.

� Delete unused: If after installation you want service partition of the target computer to contain only the maps and modules required to recreate the installed image.

� Delete all: If after installation you do not want any maps or modules in the service partition of the target computer.

Figure 2-90 Image Cleanup settings


Network Options tabThe Network Options tab is used to specify network-sync enablement and the method of installation. The following is a listing of the fields on the Network Options tab:

� Use Network Sync: This check box enables you to update maps on target computers that have gone through deployment, but have not gone through the installation process. If you want the target computer to perform a network-sync operation (check for updated maps and modules over a network before installation) select the Use Network Sync check box.

� Direct-network install: This area enables you to choose how you want the Smart Image to be installed.

� The following describes the available selections:

– Yes: Click this radio button to configure the map for a direct-network installation. A direct-network installation deploys and installs the image directly over the network. The target computer requires a network connection throughout the entire process.

– No: Click this radio button to configure the map for a standard deployment with local installation. This option deploys the Smart Image to the service partition of the target computer either over the network or from an ImageUltra Builder distribution CD and the installation takes place locally without any dependencies on a network connection.

– Prompt the user when the image is deployed: Click this radio button to prompt the person at the target computer to select the method of deployment and installation as soon as the map has been selected.

Important: You will need DHCP services running on your repository server to use this method.


Figure 2-91 Network Options

Menu Appearance tabThe Menu Appearance tab provides various choices that enable you to customize the appearance of the menus that are seen on the target computer during the installation process.

� Color settings: This field enables you to customize the color of certain menu components seen during the installation process. The Item drop-down box enables you to select different aspects of the menu while the Color drop-down menu enables you to select which color you prefer.

� Layout settings: This field enables you to customize how menu information is presented during the installation process.

� Keyboard settings: This field enables you to customize some keyboard functions during the installation process. You can select following options:


– Previous menu key: Use the drop-down menu in this field to program which key enables the person performing the installation to navigate from the current menu entry to the previous menu entry.

– Exit menu key: Use the drop-down menu in this field to program which key enables the person performing the installation to exit the menu selection process.

– System menu keyword: If your map has a menu item that is set as a system menu, then text entered in this field will automatically take you to the hidden menu item. For example, if you type the word system_menu in this field, the word system_menu can be typed during the installation process. Then, the system_menu opens.

– Enable Ctrl-Alt-Del: Select this check box to enable the person performing the installation to use Ctrl-Alt-Del during the menu selection process.

Partition tabThe Partition tab enables you to define a custom size for the service partition. A custom service-partition size enables you to leave room for other products that share the service partition, such as the Rescue and Recovery program. By making allowances for extra space, you can substantially reduce the installation time normally required by these programs to resize existing partitions.


Figure 2-92 Base map partition settings

2.19 Create a driver map

There are some fundamental differences between base maps and driver maps. Unlike for base maps, the only components that are added to a driver map are menu items and device driver modules. Menu items in driver maps have no effect on the menus displayed at the target computer. The only purposes for menu items in a driver map are:

� To provide the developer with a mechanism for annotation

� To assign filters to one or more device driver modules


It is not always necessary to include a driver map as part of a deployable Smart Image. If you deploy an ultra-portable image or a portable-sysprep image to an IBM HIIT enabled target computer, you have the choice of:

� Using a driver map and managing all of the device driver modules required for the target computer.

� Not using a driver map and relying on the IBM provided device driver modules in the service partition or HPA of the target computer.

If you deploy a hardware-specific image to a target computer, any driver map deployed as part of that Smart Image will be ignored during the installation. The target computer requires all device drivers to be included in the hardware-specific image.

2.19.1 Driver Map settingsYou can view or modify the settings associated with a map by doing the following:

1. Open the map from the Repository window

2. Right-click anywhere in the right pane and select Settings. The settings dialog differs depending on whether the map is a base map or driver map.

In the Map settings window for a driver map, you will see only two tabs:

Tip: It may be a good idea to work with two driver maps in your Repository. One driver map for production and one for testing.


Figure 2-93 Driver Map settings window

� The General tab is the same as for the base map.

� The Network Options tab has one setting that is different from the Base Map settings:

Use driver map filter processing: Driver-map filter processing determines which device-driver modules get deployed to the target computer. When Driver-map filter processing is enabled (a check in the check box), only those device-driver modules that match the filter requirements are deployed as part of the Smart Image. When Driver-map filter processing is disabled (the check box is empty), all device-driver modules defined in the driver map are deployed as part of the Smart Image.

It may be a good idea when constructing Driver Maps to have one map for testing and one for production.

For conceptual information about constructing the driver-map tree structure, see ImageUltra Builder Version 2.0 User Guide.


2.20 Deploying images using ImageUltra Builder

Corporations can have multiple methods and requirements for deploying images. Scenarios may include network deployment, CD media or an integration center such as the IBM Imaging Technology Center. Only one method may be required, all methods or a combination of several. It can be extremely labor intensive to try to maintain, update and deploy these images every time a change is required. ImageUltra Builder can help simplify and streamline this process.

The Deploy selection within ImageUltra Builder opens the Deploy Wizard. The Deploy Wizard prompts you through the steps required to create a Network Deployment Diskette, or stand-alone Distribution CDs. The deployment diskette establishes a connection to the repository, provide an interface for selecting the desired maps, and deploy the appropriate maps and modules to the appropriate staging area (service partition, HPA, or network-staging folder). The stand-alone Distribution CDs contain all of the required maps and modules to deploy them to the target computer without using a network. A repository window must be open before this selection can be made.

2.20.1 Creating an ImageUltra Builder boot diskette To create a standard ImageUltra Builder network boot floppy for network or CD distribution:

1. Open the repository from where you will deploy.


2. Click the Deploy button or click Tools →Deploy. You will see a window similar to Figure 2-94.

Figure 2-94 ImageUltra Deploy Wizard Main window

3. Select your deployment method, network or from CD and click Next.

4. Select Yes I want to create my “ImageUltra deployment diskette” now and click Next. All data on the disk will be overwritten in the next step.

5. Click the Create Diskette button to make the boot floppy.


6. The date will be written to the diskette, select Yes or No to create additional copies and click Next. You will see a window similar to Figure 2-95.

Figure 2-95 Deploy Network Settings window

Depending on whether you chose to deploy via the network or CD, follow these steps:

Via the network: 1. In the appropriate fields, enter your specific information, if applicable.

– Location of the repository

– Connect As:

• User name

• Password (if required)

– TCP/IP address of the Server

– Locale

– Language and keyboard layout


– Keywords (allows only those maps with matching keywords to be selected from the repository)

2. Click the Read button to review the current settings on the floppy disk, Click the Write button if you edited the settings.

3. Click Next and Finish.

Via CD distribution:1. Select the base map and driver map you wish to deploy and click Next.

Figure 2-96 Deploy CD Map Locations

2. Specify a directory to copy the CD layout files to and click Next. The subdirectories will be named in sequence CD1, CD2, CD3, etc. You will then copy the corresponding contents of the subdirectories to your CDs using your CD creation software.

3. Select a CD size and click Create Image.

4. Click OK at the CDs were created successfully window and click Next.


5. View the location of the Smart Image and click Next.

6. Click Finish to exit.

2.20.2 Creating a bootable Network Deployment CD from a disketteTo speed up booting to the server, you could create a network boot CD instead of using your floppy disk:

� Create a Network Deployment Diskette as in 2.20.1, “Creating an ImageUltra Builder boot diskette” on page 126.

� Use the CDRW software of your choice to create a bootable CD.

� Copy all the files from the diskette to the CD.

2.20.3 Creating a custom network boot disketteIn this section, we will create a network boot diskette without using the ImageUltra process.

Adding new DOS network drivers to the deployment disketteCreate an ImageUltra Builder network driver package (.PCI file) as follows:

1. Download the DOS driver files for the new network card. These files usually have a .DOS file extension (only NDIS drivers are supported).

2. Create a PROTOCOL.INI file that will correctly load the driver and the TCP/IP protocol.

3. Create a PCI.TXT file that lists all of the PCI vendor and device IDs for the network cards for which this driver applies.

4. Create an INSTALL.BAT file to copy all of the necessary driver files into the %NETROOT%\CLIENT folder.

5. Create a LOADNIC.BAT file to load whatever device drivers are required to load the network driver.

Important: Do not click the Back Button at this point or you will have to complete the Create Image step again.


6. Create a REMOVE.BAT file to delete the driver files from the %NETROOT%\CLIENT directory.

7. Compress all of the file into a ZIP file; then change the .ZIP extension to .PCI.

8. Create the Network Deployment Diskette image from the ImageUltra Builder interface as usual (see the ImageUltra Help system for details).

9. Copy your new .PCI file into the \IBMNET\DRIVERS folder of the diskette. If there is not enough room on the diskette to accommodate the new .PCI file, delete one of the old .PCI files that you do not use from the diskette.

When you boot the updated Network Deployment Diskette, it will process all of the .PCI files in the \IBMNET\DRIVERS folder and detect the correct network card.

Creating your own Network Deployment DisketteIf you have a DOS boot diskette that already connects to the network for your environment, you can use this diskette to deploy images instead of using the Network Deployment Diskette created through the ImageUltra Builder program.

However, there are a few requirements that your diskette must meet before you can use it:

� Your diskette must create a RAM Drive with at least 10 MB of free space

� The Repository Tools folder must be included in the path

� The initial environment must be set to a minimum of 1024 bytes and the following environment variables must be set:

– RAMD=R: {the drive letter of the RAM drive}

– IUDRIVE=X: {the drive letter of the Repository drive}

– IUREPOS=Data\Files\Repos: {the directory of the Repository path}

Once your DOS diskette meets these requirements, boot your DOS diskette and connect to the Repository. Then, run DEPLOY.BAT to begin the ImageUltra deployment process.

Note: You probably will need to use the DYNALOAD command in the LOADNIC.BAT file. Most DOS drivers are loaded through the CONFIG.SYS file. DYNALOAD allows the driver to load later in the boot process as required by the ImageUltra Builder program. If the DYNALOAD command fails to load the .DOS driver, you will have to create your own deployment diskette.


2.20.4 Deployment methodsIn this section, we exercise the deployment methods.

CD distributionDirect deployment from Distribution CDs involves copying all modules defined in the selected base map and driver map to a set of CD-R or CD-RW discs. The first disc of the set is bootable. When started in the target computer, the CD copies the modules from the CDs to the service partition of the target computer and prepares the target computer for the installation process. If a service partition does not exist at the start of the deployment process, one is created.

Use the ImageUltra Builder Deploy Wizard to create a set of stand-alone Distribution CDs. Based on your responses, the Deploy Wizard prompts you through the steps required to create the CDs.

Typical steps include the following:

� Creating a Network Deployment Diskette

� Selecting the base map and driver map to be used

� Selecting the location where the CD files are to be stored

After all required questions have been answered, the Deploy Wizard creates individual folders for each CD in the location specified. You can then use the CD-RW software of choice to create the CDs. Because CD 1 must be bootable, and uses specific files from the Network Deployment Diskette, make sure you follow the instructions provided by the Deploy Wizard and the ImageUltra Builder help system for creating CDs for CD deployment.

Figure 2-97 shows the deployment process using an ImageUltra Builder Distribution CD and a local installation process, which uses a service partition as a staging area.

Tip: IBM Imaging Technology Center (IITC) can preload your workstations with your custom ImageUltra Builder configuration. This can enable immediate installation of a workstation without requirements for media or network connections. For more information on the IITC please refer to their web site.

http://www.pc.ibm.com/cbcc/cbccweb.nsf/Home



Figure 2-97 CD deployment

1. The first step in CD deployment is the creation of a set of ImageUltra Builder Distribution CDs, which is described above (for more information, see the ImageUltra Builder help system).

The person controlling the deployment starts the process by booting the target computer with an ImageUltra Builder Distribution CD.

2. The maps and modules contained on the set of CDs are copied to the service partition, which acts as the staging area for the complete Smart Image.

3. The person controlling the installation process starts the installation phase by making selections from the installation menus to define the image to be installed.

C Partition

Smart imageon dervicepartition

Final imageon C partition

UnpackedModules

Modules

Driver Map

Base Map

OSApps

Drivers

Modules

Driver Map

Base Map

Make menuselections to

define theimage to be

installed

Start targetcomputer withdistribution CD Unused

Modules

Driver Map

Base Map

Smart imageon staging area

(service partition)

Repository

Maps

Modules Unpack

Setup

Copy

23

4

5

6

Deployment Installation

Createdistribution

CD

1

Note: At this point, a message is displayed stating that the deployment phase is complete. The person controlling the deployment can either shut down the computer at this point and ship it to another location, or continue with the installation phase.


4. The modules required for the defined image are unpacked from the service partition onto the C partition.

5. The setup process begins. When the installation phase is over, the C partition contains the new image and the service partition contains the Smart Image, which can be used for client-side recovery.

Network deploymentThis method uses a bootable, DOS-based diskette or CD to establish a network connection between the target computer and the ImageUltra Builder module repository. Once the connection is established, you select which base map and driver map to use. Depending on your base-map settings, one of the following occurs:

� If you specified a direct network installation, a temporary network-staging folder is created on the network specifically for the target computer. The maps are copied to this folder and all modules that control the installation procedure are unpacked to this folder. When the installation process begins, the hard disk is prepared and all modules required for the image content are obtained from the repository and unpacked dynamically as they are needed. A direct-network installation requires a network connection throughout the deployment and installation process.

� If you specified a network deployment with local installation, all of the modules defined in the map are downloaded to the service partition of the target computer, and the target computer is prepared for the installation process. If a service partition does not exist at the start of the deployment process, one is created (for more information about service partitions, see the ImageUltra Builder Version 2.0 User Guide).

For direct network deployment (network deployment with local installation), you use the ImageUltra Builder Deploy Wizard to create either an ImageUltra Builder Network Deployment Diskette or an ImageUltra Builder Network Deployment CD. Based on your responses, the Deploy Wizard prompts you through the steps required to create the diskette or CD.

Note: An optional cleanup step can be defined in the base map Map Settings window to minimize the size of the service partition and keep only those files required for the installed image, or eliminate the service partition.


If you choose to make a CD, create the diskette first, and then use the CD-RW software of your choice to create the CD from the diskette. Because this CD is bootable, make sure you follow the instructions in the Deploy Wizard or ImageUltra Builder help system for creating a Network Deployment CD. Depending on the type of removable-media drive available at the target computer, use either the diskette or CD to establish a network connection between the target computer and the ImageUltra module repository. After the connection is established, select which base map and driver map to use. All of the modules defined in the map are downloaded to the service partition or HPA of the target computer, and the target computer is prepared for the installation process. If a service partition or HPA does not exist at the start of the deployment process, one is created.

The following illustration shows a direct-network installation, which uses a network-staging folder as a staging area.

Figure 2-98 Direct network installation

Complete the following steps:

1. The person controlling the direct-network installation starts the process by booting the target computer with an ImageUltra Builder Deployment CD or

Note: Providing user name and password information on the deployment media (diskette or CD) is optional. If you do not provide a user name and password when you create the deployment media, the person controlling the deployment process will be prompted for this information (if it is required to access the network) when the deployment media is started on the target computer. If you do provide a user name and password when you create the deployment media, it is stored in a flat text format on the deployment media, not in a secure format.

4

(Optional)Smart imageor copy ofinstalledimage


OSApps

Drivers

Modules

Driver Map

Base Map



installed

Selectbase map

and driver map Unused

Modules

Driver Map

Base Map

Staging area(Network-staging

folder)

Repository

Maps

Modules1 3

Unpack2

Unpackrequiredmodules

Unpack Copy (optional)

Setup


ImageUltra Builder Deployment diskette, and then selects the required maps from the repository.

2. A network-staging folder is created specifically for the target computer. The selected maps and a limited number of modules (only those required to control the installation process) are copied to the network-staging folder, which acts as a staging area for the installation process.

3. The person controlling the direct-network installation makes selections from the installation menus to define the image to be installed.

4. The modules required for the defined image are obtained directly from the repository and copied over the network to target computer C partition and the setup process begins.

5. When setup is complete, the C partition contains the new image.

Network deployment process with local installationThe following illustration shows the standard network deployment process with local installation. Notice that the service partition is used as the staging area for all maps and modules required for the Smart Image.

Note: Optionally, if a developer of the image specified that a service partition is to be created for client-side recovery purposes, the maps and modules are also copied to a service partition.


Figure 2-99 Standard network deployment

1. The person controlling the deployment starts the process by booting the target computer with an ImageUltra Builder Deployment CD or ImageUltra Builder Deployment Diskette, and then selecting the required maps from the repository.

2. The selected maps and all modules defined within the maps are obtained from the repository and copied over the network to the service partition, which acts as the staging area for the complete Smart Image.

3. The person controlling the installation process starts the installation phase by making selections from the installation menus to define the image to be installed.

C Partition

Smart imageon dervicepartition


UnpackedModules

Modules

Driver Map

Base Map

OSApps

Drivers

Modules

Driver Map

Base Map



installed

Selectbase map

and driver map Unused

Modules

Driver Map

Base Map

Smart imageon staging area

(service partition)

Repository

Maps

Modules Unpack

Setup

Copy

12

3

4

5

Deployment Installation

Note: At this point, a message is displayed stating that the deployment phase is complete. The person controlling the deployment can either shut down the computer at this point and ship it to another location, or continue with the installation phase.


4. The modules required for the defined image are unpacked from the service partition onto the C partition.

5. The setup process begins. When the installation phase is over, the C partition contains the new image and the service partition contains the Smart Image, which can be used for client-side recovery.

The advantages of CD deployment are speed and the flexibility of not having to be dependent on a network connection.

The advantage of network deployment is the assurance that the latest maps and modules will be installed if the network-sync function is enabled.

With the exception of a direct-network installation, the division between the deployment and installation is a single boot cycle. In many cases, deployment is done in one location and installation takes place in another location, typically at the end-user’s work area. When deployment is complete, you can shut down the target computer and prepare the computer for delivery to the end user’s work location for the installation to be completed.

In our fictitious Acme Holdings Inc. company (see 2.25, “Business case” on page 181), multiple deployments will be used.

� For new PC rollouts, a direct network deployment with local installation method will be used by an Integration Center.

� CD deployment will be used to send images to locations or users without a WAN or broadband connection.

The deployment method is flexible to meet the needs of any business or individual.

Note: An optional cleanup step can be defined in the base map Map Settings window to minimize the size of the service partition and keep only those files required for the installed image, or eliminate the service partition.

Note: Some large enterprises that use drive-duplication technology for mass production might want to replicate the drive at the end of the deployment process, prior to installation. In order for this drive-duplication process to work successfully, you must install the IBM Boot Manager on each drive after the drive has been duplicated. You can get the IBM Boot Manager installation tool (BMGRINST.BAT) from the TOOLS\BMGR folder of your repository. You must run BMGRINST.BAT during a DOS session.


2.21 Using ImageUltra Builder and Symantec DeployCenter together

The following sections include an overview of Symantec DeployCenter, as well as a step-by-step guide on how to use this tool with ImageUltra Builder.

2.21.1 Overview of Symantec DeployCenterSymantec DeployCenter Library provides you with proven solutions for system deployment and migration. With Symantec DeployCenter Library, you can deploy an exact image of a hard disk and deploy the image to multiple workstations. Symantec DeployCenter Library includes the following tools for windows deployment and managing image files.

ImageCenter The ImageCenter application uses SmartSector imaging to create an exact image of a hard disk or partition. That exact image can then be used to deploy Windows workstations, upgrade existing workstations, manage changing desktop environments, and quickly and easily back up and restore hard drives. With ImageCenter, you can create and restore a compressed image file of an entire hard disk or individual partitions of a hard disk on a local drive, across a network, or on a removable media device.

ImageCenter can be used to clone Windows 2000 and XP for installation on other machines. When doing so, you must consider the Security Identifier (SID). Improperly cloning a Windows 2000/XP workstation will result in your having another machine with the same SID which causes 2000/XP system conflicts. ImageCenter is compatible with Microsoft System Preparation Tool (SysPrep) to resolve SID conflicts.

Image ExplorerSimplify management of your image files with Image Explorer. Working within a single screen gives you total control of the image files you can access. You can view image file contents, copy image files, copy partitions within files, restore individual program and data files from the image, or add password protection to image files. Image Explorer also provides description capabilities, so you can easily identify individual image files and partitions.

Virtual Boot Environment a.k.a Virtual FloppyThe Virtual Boot Environment (VBE) allows DOS programs to execute from the hard drive on Windows 9X, Me, NT, 2000 and XP platforms as though they were running from a boot floppy. The VBE can be sent to a particular system remotely,


the system will boot into a temporary environment to run tasks such as capturing or restoring an image, and then boot the system back into the active operating system state. The benefits of this are there is no need to create bootable media and visit each system for new image deployment or updates.

The Virtual Boot Environment operates by temporarily replacing the Master Boot Record (MBR) boot code on the primary hard drive. Upon rebooting the computer, the new boot code loads and runs the programs stored in the VBE image file. This VBE consists of a loader program, disk I/O redirector TSR program, and a non-compressed floppy boot image file. The boot image file is created from a 1.44 MB or 2.88 MB format bootable floppy. It contains both the bootable OS files, network drivers and the user application programs just as would exist on a bootable floppy disk.

Upon booting, the VBE loader builds a RAM DRIVE in memory the size of the boot image file, copies the boot image file from the hard drive to memory and then loads and executes the boot sector within the boot image file. Under DOS, the A: drive is then used to reference the boot image file system just like when booting from a CD. The first physical floppy drive is accessed as drive letter B:.

The Virtual Boot Environment image file is a raw sector-by-sector representation of a floppy file system in either a 1.44 MB or a 2.88 MB floppy disk format. It contains everything that would exist on a bootable floppy disk (boot sector, FATs, directories, and files).

PowerCasting a.k.a. MulticastImageCenter combines SmartSector imaging technology together with Ethernet or Token Ring multicasting to provide a fast and robust method for deploying workstations. PowerCasting sends the Symantec DeployCenter Library Image file to one or more PowerCast clients simultaneously. The image file is sent only once by the server to all the client computers, rather than separately to each client. This decreases network traffic by eliminating duplicate restore processes when preparing multiple workstations and when performing computer rollouts and migrations.

The PowerCasting technology in conjunction with VBE is an ideal way to deploy multiple systems across your organization. You can include the Symantec DeployCenter Library imaging tools and scripts and appropriate network drivers as part of the VBE that allows multiple systems to pull an image from a central server. Because this task is performed remotely, it eliminates the need to visit the computer and boot using a floppy disk.

For detailed instructions on using PowerCasting please refer to the whitepaper titled The Benefits of using ImageUltra Builder and Symantec DeployCenter Library.


UnicastingThe Unicast feature lets you create and restore images using a network drive without mapping the drive. It consists of a Unicast server and a Unicast client, which reside on separate machines. You can specify all Unicast parameters on the command line of either the server or the client. The Unicast operation is a point-to-point and uses the TCP/IP protocol.

The Unicast server must be started prior to running the Unicast client or before trying to PXE-boot a client machine. Once the server has been started, you do not need to tend to it. You start all Unicast operations from the client by using a standard script file or the ImageCenter interface.

For detailed instructions on using Unicasting please refer to the whitepaper titled The Benefits of using ImageUltra Builder and Symantec DeployCenter Library.

PXE a.k.a Network BootPXE (Pre-boot Execution Environment), a component of Intel®'s Wfm (Wired for Management) specification, allows a computer's PXE-compliant network card to download and run a Virtual Boot Environment from the network prior to booting the operating system on the hard disk. Because this task is performed remotely, it eliminates the need to visit the computer and boot using a bootable floppy or CD.

2.22 Image development

This section will give an example on how to:

� Create your donor image

� Use PXE and Virtual Boot Environment to capture the donor image.

� Add the donor image to the ImageUltra Builder repository

� Create a ImageUltra Builder Smart image using the donor image as a base

� Clone a single ImageUltra Builder Smart Image

2.22.1 Create your donor imageFor a detailed explanation of how to create your donor image, please see section on “Create and prepare the image file” on page 78.


2.22.2 Use PXE and Virtual Boot Environment to capture donor imageTo use Symantec DeployCenter Pre-boot Execution Environment (PXE) for capturing the donor image you have to:

1. Confirm that you have installed the PXE services correctly

2. Confirm you have the correct Network drivers for your clients installed into boot disk builder

3. Create a Virtual Boot Diskette including the correct network driver for your donor system

4. Add your PXE virtual floppy to the PXE configuration utility

5. Add a CAPTURE IMAGE selection to the PXE client menu

6. Capturing the donor image

2.22.3 Confirm that you have installed the PXE service correctly1. Log onto the Windows server

2. Go to Start → Programs →Administrative Tools

3. Select DHCP

4. Locate the Scope Options

5. Ensure that the option 003 Router is installed

6. Ensure that the option name 060 ClassID is installed

Note: You will need to have a DHCP Server installed to use this cloning method. For our examples we used Windows 2000 Server.


Figure 2-100 DHCP scope options

7. Locate Start →Programs →PowerQuest DeployCenter 5.5 Tools

8. Ensure that the PXE Configuration Utility is installed

9. If none of these are available, install the PXE option provided with the DeployCenter media.

2.22.4 Confirm you have the correct Network drivers installed in boot disk builder

The Boot Disk Builder includes many predefined network drivers. In an event that the network driver you need for the client is not available you have to add it to the Boot Disk Builder.

The step-by-step description below will describe how you add your own driver to the Boot Disk Builder:

1. Record client’s network cards VIN identifier

a. Create a virtual floppy to help detect the VIN identifier

b. Import the virtual floppy into the PXE utility

c. Boot the client and record the VIN

2. Add the client network driver to the Boot Desk Builder


Record client’s network cards VIN identifierCreate a virtual floppy to help detect the VIN identifier: 1. Go to Programs →PowerQuest DeployCenter 5.5 →DeployCenter 5.5 →

Tools Boot Disk Builder

2. Select Standalone Boot Disk

Figure 2-101 Select Standalone Boot Disks

3. Select Next.


4. In the Run ImageCenter from section, select Do not Run ImageCenter.

Figure 2-102 Select option do not run ImageCenter

5. Select Next.

6. Select Virtual Boot Disk File.

7. Add the file name Detect Network Adapter.


Figure 2-103 Detect Network Adapter

8. Select Finish Click YES when you are asked to save these settings for future use.

9. Name the settings file Detect Network Adapter.

10.Click Save.

11.Click OK to confirm. You will be asked to save these settings for later use. Say yes and save these settings to the following directory: C:\program Files\PowerQuest\DeployCenter 5.5\BDBuilder\

12.Exit the BOOTDISK BUILDER.

13.Locate Start →Programs →PowerQuest DeployCenter 5.5 Tools.

14.Select PowerQuest VF editor.

15.Select File →Open.

16.Locate the Detect Network Adapter Boot Disk file (.vfd) you just saved.

Tip: Look in C:\program Files\PowerQuest\DeployCenter 5.5\BDBuilder for your Detect Network Adapter.vfd file.


17.Select Open

18.Delete the following files:

PQDOTASK.BAT

MOUSE.COM

Figure 2-104 Delete mouse.com and pqdotask.bat from your boot disk file

19.Highlight AUTOEXEC.BAT.

20.Select Extract. Accept the default. Ignore subdirectories.

21.Select a temporary directory from where the AUTOEXEC.BAT can be edited e.g C:\TEMP.

22.Click OK to save the file. Do NOT Close the PowerQuest VF Editor Window.

23.Locate C:\TEMP folder using the Explorer.

24.Select AUTOEXEC.BAT.

25.Right-click AUTOEXEC.BAT.

26.Select Edit.

27.Delete the line CALL PQDOTASK if it exists.

28.Add the word kicknic.


Figure 2-105 Add Kicnic to the AUTOEXEC.BAT file

29.Save AUTOEXEC.BAT.

30.Close the Notepad.

31.Open Windows Explorer.

32.Locate C:\Program Files\PowerQuest\DeployCenter 5.5\BD Build folder.

33.Copy KICKNIC.COM into the C:\TEMP directory.

34.Close the explorer window.

35.Open up the PowerQuest VF Editor window.

36.Select Image.

37.Select Inject.

38.Locate the C:\TEMP.

39.And select AUTOEXEC.BAT and KICKNIC.COM.

40.Select Open.

41.Confirm that you want to inject the two files into the Virtual Floppy.

42.Answer Yes to replace AUTOEXEC.BAT.

43.Save and close the PowerQuest VF Editor.

Import the Virtual Floppy into the PXE configuration Utility1. Open PXE Configuration Utility.

2. Select Add.

3. Locate Detect Network Adapter.vfd located in BDBUILD directory.

4. Highlight and select OPEN.

5. Select OK to confirm the addition.


Figure 2-106 Configuration Utility - Detect Network Adapter

6. Select PXE Client Menu tab.

7. Select Add.

8. Type Detect Network Adapter as the menu name.

9. Select Detect Network Adapter.1 and assign it to virtual floppy.

Figure 2-107 Add PXE Client - Detect Network Adapter 1

10.Click OK.


Figure 2-108 PXE client menu - Detect Network Adapter

11.Exit the configuration Utility.

Boot the client to detect the network VIN identifier1. Power on the client

2. Press F12 at boot time to activate the alternative boot menu

3. Highlight the correct PXE boot agent for the client

4. example: IBA 4.1.04 Slot 0240

5. The client will now boot to the DeployCenter PXE server

6. On the PXE menu select Detect Network Adapter

7. Press Enter

8. When the boot is completed you will see the VIN number at the bottom on the client screen. Example: PCI\VEN_8086&DEV_1031&REV_42&SUBSYS_02091014

9. Record that number on a piece of paper. This number will be used to add the correct network driver for your client into boot desk builder

10.Close the PXE Configuration Utility

Add the correct client network driver to the Boot Disk Builder1. Create a share called IMAGES on your server.

2. Download and extract the latest Network driver for your client and save on to a folder on your deployment server.


3. Open BOOT DISK BUILDER.

4. Select Microsoft TCP/IP Boot Disk.

Figure 2-109 Boot Disk Builder - Microsoft TCP/IP Boot Disk

5. Click Next.

6. Fill in the User Name and Password to logon to your Server Image share. In our example the user is: Admin, and the UNC path to the share is \\server\images with the drive letter i:


Figure 2-110 Boot disk builder - Network Login information

7. Click Next.


8. Leave the screen shown in Figure 2-111 as is.

Figure 2-111 Boot disk builder - run ImageCenter from BOOT DISK

9. Click Next.

10.Select Add.

11.Select Enter Drive Information manually.


Figure 2-112 Add Network Drivers - Enter driver information manually

12.Select Next.

13.Add the VIN Number you recorded earlier. In our example it is: PCI\VEN_8086&DEV_1031&REV_42&SUBSYS_02091014

14.Add the network adapter description.


Figure 2-113 Add network drivers - Network Adapter ID and description

15.Click Next.

16.Locate the network Adapter Driver Files you downloaded and extracted.

17.Locate the DOS directory.

18.Select the correct com-file. In our example it is IPXODI.COM.

19.Click Open.

20.The driver is now added to the Add network driver screen.


Figure 2-114 Add network drivers - ipxodi.com

21.Click Next.

22.Locate the Microsoft TCP/IP NDIS2DOS driver file. In our example it's a file called E100B.DOS.

23.Click Finish and the network adapter is now added to list of available drivers.


Figure 2-115 Boot Disk Builder - Select network adapter from list

24.Click Next

25.Leave default settings. We will now name the boot disk Capture Image

Create a Virtual Boot Diskette including the correct network driver for your donor system

1. Open Boot Disk Builder

2. Select Microsoft TCP/IP Boot Disks

3. Enter server login information

4. Click Next


5. Select Boot Disk and click Next

Figure 2-116 Select Boot Disk

6. Click Next

7. Select the network adapters you need from the list


8. Select Obtain an IP address from a DHCP server

Figure 2-117 Boot Disk Builder - Accept Default settings


9. On the screen shown in Figure 2-118, select Virtual Boot Disk, and name the boot disk CAPTURE IMAGE.

Figure 2-118 Boot Disk Builder - Select virtual boot disk file

10.Click Finish

11.Select Yes when asked to save this for future settings

12.Save these settings as Capture Image.vfd

13.Select OK to confirm saving

14.Select Exit to close the Boot Disk Builder

2.22.5 Add the CAPTURE IMAGE.VFD to the Configuration Utility1. Open the PXE Configuration Utility

2. Click the PXE Virtual Floppies Tab

3. Click Add →Browse →Software →Intel driver →Capture Image.vfd


2.22.6 Add CAPTURE IMAGE selection to the PXE Client menu1. Click the PXE client menu tab

2. Click Add →Type in CAPTURE IMAGE as the menu name

3. Select Capture Image 1 from list.

4. Click Save →OK →Exit.

5. We have now configured the DeployCenter PXE support to be able to manually capture an image of the ImageUltra Builder Donor system and save it onto the server shared image drive (I:).

2.22.7 Capturing the donor image Once you have prepared the donor system to be imaged, use the instruction below to create a donor image on the server.

1. Connect the donor system to the server.

2. Power on the donor system.

3. When you see the IBM image, pressing F12 the alternative boot menu.

4. Select the PXE boot option.

In our example we use the IBA 4.0.22 Slot 0240.

5. Press Enter.

6. When you see 'Please select from the following items:' select Capture Image by using the tab key.

7. Press Enter.

8. After a few second you will see the ImageCenter main menu screen.

9. Click Create Image.

10.Press Enter.

11.Type the name of your image file in the Image File:. Use the complete path and image file name. In our example we used H:\IUBWXP.PQI

12.Add a description of the donor image you are creating in the Image File Comments: field. This is version 1.1 that contains Windows XP Portable Sysprep image with the following changes, Updated MassStorage list in sysprep.inf.

13.Use the tab key to select Next.

14.On the Compress Image File screen, select High Compression.

15.Select Next.


16.The next screen contains the details of your donor image, hard drive size and image file to be saved and level of compression used.

17.Review the option under the Advanced Options button.

18.When you have reviewed all setting, click Finish.

19.ImageCenter will now start cloning your client image and store it as a donor image onto your network share.

20.When image capture is complete you will see a confirmation screen. Review the screen and confirm there where no errors during the image creation.

21.Close the ImageCenter

22.Power off the client.

23.The ImageCenter Donor image is now stored on the Image server and ready to be used by ImageUltra Builder

24.Copy PQIMGCTR.EXE, PQIMGCTR.OVL PQDPLCTR.RTC from the DeployCenter directory into the C:\IMAGES

25.The donor image is now ready to be added as an ImageUltra Builder

2.22.8 Add the donor image to the ImageUltra Builder repositorySee 2.16, “Create a base operating system Portable Sysprep Image” on page 87.

2.22.9 Create a ImageUltra Builder Smart Image using the donor image as a base

See 2.6, “ImageUltra Builder process to create a Smart Image” on page 32.

2.22.10 Re-clone an ImageUltra Builder after the Smart Image has been deployed into the Service Partition

PreparationIn this example we will deploy the ImageUltra Builder Smart Image to a client service partition. The client hard disk content is then cloned to an imaging server. The cloned image can then be uni- or multi-casted to multiple clients of the same configuration. This cloning method is very useful for large rollouts of the same system configuration.

Before beginning the cloing process you have to:

� Connect the client to the ImageUltra Builder Repository


� Use the ImageUltra Network deploy diskette to connect to the repository

Deploying the Portable-Sysprep Smart Image1. Power on the client

2. Make sure that the system boot from the IUB network deployment disk.

3. When the system completes the boot process the ImageUltra builder Choose an image to Deploy menu will be displayed.

4. Use the arrow keys to select the Base Map

5. Press Enter

6. On the Deploying Driver Map select Yes

7. Press Enter

8. Select the your Driver map

9. Press Enter

10.On the ImageUltra Deploy menu confirm your selection of Base map and Driver map.

11.Press Enter

12.When you are prompted for Direct Network Install, select NO. By selecting no you will then deploy all IUB modules into the service partition of the donor system.Press Enter

13.The system will launch an IUB deployment screen and reboot.

14.The system will reconnect to the IUB repository and begin copying the ImageUltra modules down to the donor system.

15.When completed you will see a message on the screen telling you that on the next REBOOT the system will install.

16.Remove the ImageUltra Builder Boot disk from the donor

17.Select EXIT

18.You have now successfully created the ImageUltra Builder donor system and it is now ready to be cloned to the image distribution server. See 2.22.2, “Use PXE and Virtual Boot Environment to capture donor image” on page 142 for more details on how to capture your image.


2.23 Image deployment

In this section we will look at:

� Unicast a cloned ImageUltra Smart Image (2.23.1, “Unicast a cloned ImageUltra Smart Image” on page 164)

� Multicast a cloned ImageUltra Builder Smart Image (2.23.2, “Multicast a cloned IUB Smart Image” on page 170)

2.23.1 Unicast a cloned ImageUltra Smart ImageIn this example we will create a virtual floppy that will deploy the cloned ImageUltra Builder Smart Image to a single system.

1. Open the PowerQuest Boot Disk Builder

2. Select Microsoft TCP/IP Boot Disk

Figure 2-119 Microsoft TCP/IP Boot Disk

3. Click Next


4. Fill in all your required login fields as shown in Figure 2-120.

Figure 2-120 Login settings

5. Click Next


6. Fill in your ImageCenter command line parameters. In our example below we used "/cmd=script.txt /img=basexp.pqi". See Figure 2-121.

The script.txt file contains you image install commands, and your BASEXP.PQI is your actual image file.

For details on using Symantec command line scripts please refer to the Symantec DeployCenter Guide.

Figure 2-121 Enter command line parameters -

The script file SCRIPT.TXT will be created using notepad as the last step in this example and will be saved into the \\server\images share.

7. Click Next


8. Select the network adapter driver for the client you will deploy to.

Figure 2-122 Select Network Adapter

9. Click Next


10.Leave the default selection of DHCP

Figure 2-123 Select the default option - DHCP

11.Click Next

12.Select the option to create a Virtual Boot Disk File

13.Save Virtual Boot Disk File as Unicast Deploy IUB Smart Image

14.Click Finish

15.Your virtual boot disk file, Unicast Deploy IUB Smart Image.vfd, will be saved by default into:

C:\Program Files\PowerQuest\DeployCenter 5.5\BDBUILD

16.Save your configuration for future use if requested.

17.Open the PowerQuest PXE Configuration Utility.

In the PXE Virtual floppies tab and click the Add button and browse to the folder where your .vfd file is stored.

C:\Program Files\PowerQuest\DeployCenter 5.5\BDBUILD\

18.Click OK.


.

Figure 2-124 Add Unicast Deploy IUB Script Image to PXE Configuration

19.The server is now setup to accept PXE requests to deploy the ImageUltra Builder Smart Image.

20.Before you start deploying the client, you will need to create a SCRIPT.TXT file.

For our example we used the following script file:

SELECT DRIVE 1DELETE ALLSELECT FREESPACE FIRSTCREATE /FS=UNFORMATTED /SIZE=15000 POSITION=BEGINNINGSELECT FREESPACE FIRSTSELECT IMAGE 1RESTORESELECT PARTITION LASTSET ACTIVEREBOOT

21.Now you can use the UniCast IUB Smart Image menu option to deploy the cloned IUB Smart image.

Power on your system and Press the F12 function key to select your network boot device and then press enter.

Example: IBA GE SLOT 0208 v12O2


2.23.2 Multicast a cloned IUB Smart ImageIn this example we will create a virtual floppy that will deploy the cloned ImageUltra Builder smart Image to multiple systems simultaneously using PowerCast.

1. Open the PowerQuest Boot Disk Builder

2. Select PowerCast Boot Disk

Figure 2-125 Select PowerQuest Boot Disk

3. Click Next


4. Fill in all of the required fields for Client start-up mode. In our example we used the following:

Connect to session: powercast1

PowerCast image to hard disk number: 1

Additional command line parameters: /PPR=FIRST /DSK=1 /NMD

See the Symantec DeployCenter Guide for details on these command line parameters.

Figure 2-126 Client start-up mode

5. Click Next


6. Select the required network adapter driver(s) required to support your target hardware.

Figure 2-127 Select Network Adapter

1. Click Next.


2. Leave the default select of DHCP and set the maximum number of PowerCast clients you will allow to be deployed simultaneously. In our example we used 10 clients. See Figure 2-128.

Figure 2-128 Client network properties

3. Click Next.


4. Select the option to create a Virtual Boot Disk file and enter the name of your virtual boot disk file as PowerCast IUB Super Image. See Figure 2-129.

Figure 2-129 Enter VBD file super image name

5. Click Finish

6. Save your configuration file for future use

7. Before adding the PowerCast IUB Super Image.vfd to the PXE Configuration utility you need to customize the autoexec.bat in the virtual floppy.

8. Open the PowerQuest VF Editor.


9. Open the PowerCast IUB Super Image.vfd file you have just created.

Figure 2-130 VF Editor window


10.Extract the AUTOEXEC.BAT into C:\Powerquest\Multicast directory

Edit the AUTOEXEC.BAT, by adding the line:

pqimgctr /cmd=i:\pscript.txt /nrd

Figure 2-131 Edit the autoexec.bat file

11.Save the AUTOEXEC.BAT to c:\program files\PowerQuest\DeployCenter 5.5

12.Close the notepad window

13.Delete the MOUSE.COM from the virtual floppy image

14.Add the following files into the virtual floppy image:

c:\program files\PowerQuest\DeployCenter5.5\pqimgctr.exe

c:\program files\PowerQuest\DeployCenter5.5\pqimgctr.ovl

c:\program files\PowerQuest\DeployCenter5.5\pqdplctr.rtc

c:\program files\PowerQuest\DeployCenter 5.5\autoexec.bat

Note: If while trying to add the above files you get a drive full error, go to the main menu and select Image →Change Format →select 2.88 mb


Figure 2-132 Change drive format

15.Save and exit the VF Editor

16.Add the virtual floppy file to the PXE Configuration Utility and build a menu called PowerCast IUB Smart Image. See “Add the CAPTURE IMAGE.VFD to the Configuration Utility” on page 160, for an example of how to do this.

17.Close the PowerQuest PXE Configuration Utility

18.Create a PSCRIPT.TXT using notepad including the following text.

SELECT DRIVE 1

DELETE ALL

DELECT FREESPACE FIRST

CREATE /FS=UNFORMATTED /SIZE=15000 /POSITION=BEGINNING

19.Add the PSCRIPT.TXT to the image share on the server. In our example this would be \\server\images.

20.You are now ready to start the PowerCast server.

21.Open up a command prompt on the PowerCast server and enter the following command:

PQPCS32.EXE /fsd=15 /pcthr=500


Figure 2-133 Command prompt to launch a PowerCast Window

22.Press Enter

23.This will open up the PowerCast window.

24.Enter the Session Name and browse to the image file.

In our example we used: Session Name: session1, Image File: BASEXP.PQI

25.Click Start to start the PowerCast services on the server.

26.Power-on the clients, press the F12 function key to boot the client to the network.

Example: IBA GE Slot 0208 v1202

27.Select the PowerCast IUB Super Image menu option to deploy the cloned IUB Smart image.

28.When the clients connect to the PowerCast server they will queue up and wait for the PowerCast to start.

29.When all of the clients have connected to the PowerCast session, click GO on the PowerCast Server Progress screen to deploy the cloned ImageUltra Builder Smart Image to the clients.

2.24 Software integration considerations

2.24.1 Integration with IBM Software Delivery Center (SDC)To enable Software Delivery Center for software distribution, ImageUltra Builder can be used to enable the agent. One problem that always comes up during the deployment of any software distribution tool is getting the agent installed on the clients. This is best accomplished by including the agent with the image. An application module can easily be created which will install the Software Delivery Center agent. The Software Delivery Center agent is installed using a program called esdsetup.exe. This setup can be included as part of the image and run silently using the following command:

esdsetup.exe /s


2.24.2 Integration with System Migration Assistant (SMA)SMA can easily be deployed as a module during an image load. This will allow for immediate restoration of user settings that may have been captured before a PC cascade or new system rollout. Create a silent install for the SMA tool as outlined below and create a module. Use the ImageUltra Builder tool to deploy the SMA module during your image installations. Once the image load is complete, run the SMA application and apply all of the saved user settings. The end user will have the same look, feel and data as with their previous system, saving valuable reconfiguration and down time.

To create a silent install of SMA, follow these steps:

1. For Windows NT 4.0 Workstation, Windows NT 4.0 Server, Windows 2000 Professional, Windows 2000 Server, Windows 2000 Advanced Server, or Windows XP Professional, log on to your computer as the administrator or as a user with local administrative rights.

2. Download SMA code and documentation from:


Please follow the instructions on the Web page to download this file.

3. Make sure there are no other setup programs running.

4. Launch the SMAsetup_<lang>.EXE program that you downloaded from the Internet, where <lang> stands for the language variation you are using. For instance, the English version of the executable is SMAsetup_en.exe.

5. Wait until you see the Welcome window. Then minimize the SMA setup window, or bring up the command or Explorer window without exiting the SMA setup.

6. Locate the pft*~tmp folder, where * stands for one or more random characters. If you’re running Windows 95, Windows 98, or Windows ME, you will find this directory in the C:\Windows\TEMP directory. On Windows NT 4.0 Workstation or Windows NT 4.0 Server, you will find this directory in the C:\Temp directory. On Windows 2000 Professional, Windows 2000 Server, Windows 2000 Advanced Server, or Windows XP Professional, you will find it in the C:\Document and Settings\<user name>\Local Settings\Temp\ directory.

Note: The Local Settings Folder may be hidden by default. Select Tools →Folder Options →View and click Show hidden files and folders if the Local Settings Folder is not displayed.



7. Copy the folder to the location where you want to keep the install files and rename it if you wish to do so (this folder location will be used in the next steps), then cancel SMA InstallShield setup.

8. From the command line, run setup -r on a system which has the same configuration as the system for which you are creating the silent install. The executable setup.exe is located in the setup directory you just copied in the Disk1 folder. This will create an InstallShield response file named setup.iss in the C:\windows or C:\winnt directory (depending on your operating system). For more information on the setup command, see various articles on silent installation at

http://support.installshield.com/

9. Now you are ready to install SMA in silent mode. To do so, copy the setup.iss file to the setup directory you created previously and from the command line run setup –s –SMS. Alternatively, you can run setup.exe -s –SMS –f1<path>\setup.iss, where the f1 parameter denotes the location of setup.iss file.

10.When the install has completed, open the setup.log file located in the setup directory and locate the ResultCode variable in the [ResponseResult] field. If Resultcode = 0, the installation completed successfully. Common error values are:

-3 Required data not found in SETUP.ISS file

-5 File does not exist

-8 Invalid path to the InstallShield response file

-12 Dialogs are out of order

2.24.3 IBM Rescue and RecoveryFor details on how to prepare and create a silent install module for IBM Rescue and Recovery, please refer to Section 2.3.4, “Silent Installation” in Using ThinkVantage Technologies: Volume 2 Maintaining and Recovering Client Systems, SG24-6060-01.

2.24.4 ImageUltra Builder with Symantec GhostWhen Ghost is used in conjunction with the ImageUltra Builder program, certain limitations must be considered. Symantec Ghost can clone partitions and drives.

Because the ImageUltra Builder program uses a service partition to store the Smart Image for certain types of installations, Symantec Ghost might encounter problems when attempting to set the size for multiple partitions or when installing a cloned drive. When defining partition sizes as a percentage, Ghost always uses



the full hard-disk capacity and does not take the presence of a service partition into account. As a result, Ghost might delete the service partition on the target computer. Defining absolute sizes can be equally problematic because drive sizes vary on target computers.

When using a cloned drive, two problems can occur:

� If a service partition exists on a source computer, Ghost includes this service partition as part of the image and will overwrite the service partition on the target computer. This results in a mismatch between the contents on the active partition of the target computer and the service partition of the target computer.

� If a service partition does not exist on the source computer, Ghost will assume that it can use the entire hard disk for the image, and will delete the service partition on the target computer.

Because it is so difficult to manage multiple partitions and cloned drives created by Ghost when a service partition is present, IBM supports the following implementations only:

� Restoring single-partition images produced by Ghost

� Restoring a single-partition, cloned-drive image as a single partition, not as a cloned drive. The silent install command in the Source tab of the Operating System window must be a batch file name, such as GHOST.BAT. Inside the batch file, you must use the following statements:

Gdisk.exe 1 /cre /pri /sure

ghost.exe -clone,mode=pload,src=image.gho:1,dst=1:1 -auto -sure -quiet -fx -batch

where image.gho is the name of your image.

Before you build the module, you must put the image files, the script file, and the batch file in the same folder.

2.25 Business case

This section describes a sample business environment and ImageUltra Builder usage scenarios.

2.25.1 Example organizationThe organization used in this section is named Acme Holdings Inc. (see Figure 2-134). This company has offices in New York, Toronto, London and


Madrid. The head office is located in New York where the main IT Development team also exists. The various sites are connected via T3 and T1 lines; this allows the locations to communicate with each other. Images using ImageUltra Builder are developed in New York where all updates are made to the “Master Repository”. For distribution, this information is replicated to local site replicas where system loads are performed.

The hardware in this organization consists of IBM and non-IBM workstations. Existing images, created using Symantec Ghost and Symantec DeployCenter, are currently used to prepare/reload these workstations. Acme Holdings Inc. would like to continue use of these images until those machines are retired.

Figure 2-134 Acme Holdings Inc.

As Acme Holdings Inc. migrates to full use of ImageUltra Builder (and supporting technologies), they will first add their hardware-specific images. Going forward, they will use Portable-Sysprep and UltraPortable imaging technology to deploy their new workstations in order to ensure that they have maximum flexibility.

As part of the maintenance process, the Master repository located in New York is replicated to support replicas (one in each location). This allows the support staff to access the images at each location without putting excessive loads over the WAN links.

Replica A Master Repository

T1

T3

T1Toronto2000Users

Replica B

London2000Users

Replica C

Madrid1000Users

Replica D

New York5000Users

T3T1


Service Partition: The purpose of the service partitionUsing the IBM ImageUltra method, you can select to deploy directly over the network or use a service partition. The service partition is a hidden partition on a hard disk from which the ImageUltra builder deploys the operating-system modules, application modules, device-driver modules, and a set of recovery tools. It also provides its own boot environment for image deployment, which has no dependency on the Windows operating system being present on any active partition. Because the service partition is protected from common read and writes operations as well as most viruses, it is a practical place to store recovery, backup, and installation files and tools.

The system partition is used for the following purposes:As shipped from the factory on IBM HIIT-enabled computers, the service partition provides a recovery mechanism to restore the contents of the hard disk to its factory-installed state. It also provides a vehicle for distributing IBM-developed modules that the ImageUltra Builder program can import. These modules can be a core OS modules created by IBM or a OS image created by Symantec DeployCenter and application and device drivers models provided by IBM for ImageUltra Builder.

As used by the ImageUltra Builder program, it is a storage area for deployed Smart Images and for the tools required to perform the image installation process. Smart Images replace the factory installed image files in the service partition. If a service partition is not on a target computer before a Smart Image is deployed, one is created during the deployment process.

2.25.2 Business case section 1 of 3: Using hardware specific imagesThis is an example of migrating from legacy images to hardware specific OS modules. In this business case, we will show how a large corporation migrates from an existing monolithic image process to a module system build process using ImageUltra Builder 2.0. The following table gives an overview of the current state and a three-phased approach to migrating to ImageUltra Builder.


Table 2-1 Acme Holdings Inc.

Existing State Phase I legacy systems

Phase II current systems

Phase III future systems

Method Legacy Ghost images

Hardware-specific using ImageUltra Builder

Portable-sysprep using ImageUltra Builder

Ultra-portable ImageUltra Builder

Operating Systems

Four:

� Windows 95c

� Windows 98

� Windows NT 4

� Windows 2000

older systems have 9x or NT4 and the newer systems have 2000 only

Three:

� Windows 95c

� Windows 98

� Windows NT 4

One:

� Windows 2000 on multiply vendor platforms

� Two modules containing the unique HALs are required to support the four systems

One:

� Windows XP on IBM hardware

Hardware platforms

Eight:

� Compaq EN desktop

� Toshiba Tecra 8100

� HP VL 8i

� IBM PC 300® PL

� HP VL 420


� IBM M40 NetVista™

� IBM T23 ThinkPad

Four:



� HP VL 8i

� IBM PC 300 PL

Four:

� HP VL 420


� IBM M40 NetVista


Two:

� IBM M50 ThinkCentre


Technology Legacy monolithic ghost images

Hardware Specific OS modules incorporating the existing legacy images

Sysprep OS module combined with modules for drivers, patches and applications.

Ultra-Portable OS module provided by IBM with all new systems combined with modules for drivers, patches and applications


Acme Holdings Inc. is typical of many large corporations. Acme Holdings Inc. has eight different hardware platforms, four laptops and four desktop models. The older four models have two different operating systems (OS) on them; this is a mixture of Windows 95, 98 and NT 4, while the newer systems only have Windows 2000 installed on them. This results in twelve unique hardware/OS combinations: ((4X2) +(4X1))=12. It would not be unreasonable for a large company to support up to ten different languages, but for our example we will use three; this results in 36 unique hardware/OS/language combinations. The final variable that must be addressed is the different business units. For image development and maintenance, a business unit is defined as any group of end

Business Units

Six:

� Sales

� IT

� Manufacturing

� Field

� Engineering

� Finance

Six:

� Sales

� IT

� Manufacturing

� Field

� Engineering

� Finance

Six

� Sales

� IT

� Manufacturing

� Field

� Engineering

� Finance

Six:

� Sales

� IT

� Manufacturing

� Field

� Engineering

� Finance

Languages Three:

� English - US

� English - UK

� Spanish

Three:

� English - US

� English - UK

� Spanish

Three:

� English - US

� English - UK

� Spanish

Three:

� English - US

� English - UK

� Spanish

Unique system combinations supported

216: One for each combination of hardware platform, business unit, and language.




Images to create

216 144 6 1


Phase II current systems

Phase III future systems

Method Legacy Ghost images

Hardware-specific using ImageUltra Builder

Portable-sysprep using ImageUltra Builder

Ultra-portable ImageUltra Builder

Note: The following process assumes that the reader has installed and configured ImageUltra Builder as detailed earlier in this document. It is also assumed that the reader has read and understands all of the details presented so far in this document concerning ImageUltra Builder.


users that have similar software application requirements. Acme Holdings Inc. has six business units but 20 or more would not be unrealistic. The end result is that 216 unique system builds must be maintained and supported.

The typical means to support these 216 unique combination is to create one monolithic image to use a tool such as PowerQuest Drive Image or Symantec Ghost for each unique combination. In this type of solution, each combination is built one at a time. Then a copy of the system is made using one of the tools listed above. This single file copy of the system is called an image.

The time is takes to build each one of these images varies greatly depending on the OS and the number, size and complexity of the applications required. An experienced image creator could reasonably create and test one image per day. At Acme Holdings Inc., it would take one person most of a year to create all of the 216 unique images or a large staff of image creators to create and maintain this number of images.

If one small change occurs, such as an OS patch needing to be added to the images, then each one must be recreated. There clearly must be a better way to create unique system builds. The issue is maintaining these images.

Acme Holdings Inc. has decided to use IBM ImageUltra to reduce the time and complexity of system building. IBM ImageUltra Builder V2.0 provides a means to significantly reduce the number and complexity of the system build process. This is done using a modular approach which can greatly reduce the number of unique modules that must be created.

Before introducing ImageUltra Builder to Acme Holdings’s build environment, we must determine how it will be used. First, we must determine which systems will benefit from the process the most and which system will be retiring in the near future. If a system is already three years old and only a few will be rebuilt each year then it is not efficient to create a new build for these types of systems. An example of this type of system would be a 300 Mhz PC running Windows 95 that was purchased in 1999. If this system fails, it will most likely be replaced.

In the event that it must be rebuilt, the existing image process that Acme Holdings Inc. is currently using would be able to return the system to its pre-failure state. After considering age, operating systems and performance, Acme Holdings Inc. has decided to move half of their systems to the new ImageUltra process and leave the older half with the current image process. The results are shown in Table 2-2 on page 187.


Table 2-2 Phase 1 and 2

This division from older systems to newer ones provides a logical migration point from the legacy imaging process to the new modular ImageUltra process. ImageUltra provides hardware-specific OS module support. This support provides a means to ease the transition and to introduce the Acme Holdings Inc. support staff to ImageUltra Builder.

Table 2-3 Phase 1

Phase 1 Phase 2

Systems Older legacy system Current systems

Operating Systems Windows 95,98se, NT 4 Windows 2000

Models � Compaq Deskpro EN

� HP VL 8i

� IBM PC 300 PL


� HP VL 420




technology hardware specific modules created from legacy images

sysprep OS module combined with modules for drivers, patches and applications

Unique system builds 144 unique images 6 unique OS modules used in 72 unique builds


Method Legacy Ghost images Hardware Specific using ImageUltra Builder

Operating Systems Three:

� Windows 95c

� Windows 98

� Windows NT 4

Three:

� Windows 95c

� Windows 98

� Windows NT 4

Hardware platforms Four:



� HP VL 8i

� IBM PC 300 PL

Four:



� HP VL 8i

� IBM PC 300 PL


Hardware Specific OS modules incorporating the existing legacy images


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

2.25.3 Business case section 2 of 3: Using portable-sysprep imagesIn 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 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

Business Units Six:

� Sales

� IT

� Manufacturing

� Field

� Engineering

� Finance

Six:

� Sales

� IT

� Manufacturing

� Field

� Engineering

� Finance

Languages Three:

� English - US

� English - UK

� Spanish

Three:

� English - US

� English - UK

� Spanish




Images to create 144 144


Method Legacy Ghost images Hardware Specific using ImageUltra Builder


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 2.16, “Create a base operating system Portable Sysprep Image” on page 87.

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 2-4 on page 190 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 2-4 Multi-language OS image

Acme Holdings Inc. has decided that they will keep their images language-specific. This means that they need to create and maintain six images, instead of two if they had opted for the multi-language images. Two of the major reasons that supported this decision for Acme Holdings Inc. were:

� Acme Holdings Inc. is just learning how to create sysprep images and

� They have developers with different language skills located in different countries.

This allows Acme Holdings Inc. to utilize the greatest number or developers at one time. As the development staff gets more proficient with sysprepped images they may decide to move to the multi-language images. The advantage of using the ImageUltra Builder process is that when the company does change to the multi-language images, the developer will only need to replace the existing OS modules with the new ones. No other modules will need to be recreated or modified.

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

Must rebuild entire image Only need to change impacted language image

distributed development and division of workload

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


Table 2-5 Phase 2

Existing State Phase 2 current systems

Method Legacy Ghost images Portable-sysprep using ImageUltra Builder

Operating Systems One:

� Windows 2000

One:

� Windows 2000 on multiply vendor platforms

� Two modules containing the unique HALs are required to support the four systems

Hardware platforms Four:

� HP VL 420




Four:

� HP VL 420





Sysprep OS module combined with modules for drivers, patches and applications.

Business Units Six:

� Sales

� IT

� Manufacturing

� Field

� Engineering

� Finance

Six

� Sales

� IT

� Manufacturing

� Field

� Engineering

� Finance

Languages Three:

� English - US

� English - UK

� Spanish

Three:

� English - US

� English - UK

� Spanish






A close look at Table 2-5 on page 191 will reveal that Acme Holdings Inc. is missing one key part of their system builds. There are no applications built into these six language-specific OS modules. All components of a unique system combination in ImageUltra are separate modules. We must now create application modules for each of the applications that our six business units require.

Business units and applicationThe following is a list of the business units and abbreviations used in the table below.

� common = applications that are installed on all systems

� 1 = Sales

� 2 = IT

� 3 = Manufacturing

� 4 = Field

� 5 = Engineering

� 6 = Finance

Table 2-6 shows the different applications and the business units that use them.

Table 2-6 Applications and business units

Applications Business Unit

Corel WordPerfect Office Suite 11 Common

Microsoft Internet Explorer 6.0 Common

Norton Antivirus Common

Lotus® SameTime Chat Common

AT&T Network Client 1,2,4

Time accounting Common

Lotus Notes® 4,5,6

Eudora e-mail client Common

Adobe PhotoShop 2

Adobe FrameMaker 2

Rumba host emulator 2,3,5,6

Adobe Acrobat reader Common


Each one of these applications must be made into an application module as demonstrated in 2.10, “Creating an application module from source files” on page 48. These application modules are reusable, so each application only needs to be made into a module once. This module can then be deployed to as many business units as required without any additional effort. This is accomplished through the use of maps. Refer to the Use driver map filter processing under 2.19.1, “Driver Map settings” on page 124.

Adobe Acrobat 2,5

Filezilla FTP client 2,5

Opera 7.11 web browser 2,5

Macromedia Dreamweaver Studio MX 2,5

DeLorme Street Atlas 1,4

Zone Lab firewall 1,2,4

Rarlab - WinRAR Common

Sun Java Runtime environment 1.4.1_03 Common

Nero CD creations 2

AutoCAD 2002 5

Pro-E CAD 5

Microsoft Java Virtual Machine 3809 Common

MiniTab statistical analysis 6

Vcom Fit-it Utilities 5 2

Xn-View picture editor 2,5

Microsoft Active Sync 1,2,4

IBM ImageUltra Builder 2 2

IBM System Migration Assistant 2

IBM Software Delivery Center 2

IBM Access Connections 1,2,4

IBM Software Delivery Center 2

VPN client 1,2,4

Applications Business Unit


The following window shows the map for a Windows 2000 portable-sysprep OS for the Spanish IT department.

Figure 2-135 OS map module

Figure 2-136 is the first menu window generated by the map shown in Figure 2-135.

Figure 2-136 Preview of OS map module - first window

The following is the second window generated by the OS map module shown above.


Figure 2-137 Preview of OS map module - second window

This is a folder containing application modules for use on the UK English version of Windows 2000.

Figure 2-138 Repository - UK English applications

The above figure shows the logic tree details for the base map showing desktop applications on UK English.


2.25.4 Business case section 3 of 3: Using ultra-portableIn the previous section, we demonstrated how Acme Holdings Inc. could use portable-sysprep images to move their Windows 2000 current systems from the old legacy imaging process to the ImageUltra modular process. Acme reduced 72 images into six portable image module to support the same 72 unique system configurations.

Acme Holdings Inc. is planning to migrate to Windows XP running on IBM-only hardware for all future PC systems. They could continue to use this same portable solution as they are now using for Windows 2000 but the move to IBM hardware offers a better solution. IBM provides a special ultra-portable OS module for use on IBM equipment. These ultra-portable modules are available for Windows 2000 and XP.

The advantage of the ultra-portable module over the portable-sysprep images is that the ultra-portable OS module can be used with any IBM system that supports Windows 2000 or XP. The HAL compatibility issues that we had to consider with the sysprep images are now resolved. With only two current portable-sysprep OS modules, this ultra-portability may not seem significant, but it really is. As new systems are introduced to Acme Holdings Inc.’s environment, the number of portable-sysprep modules will increase. Using the IBM provided ultra-portable OS module with the new systems will enable Acme Holdings Inc. to utilize a single OS module to support all of their new IBM laptops and desktops.

Migration to this new ultra-portable system will require much less effort than the migration from legacy images to the portable-sysprep system. This is because all of the time and effort that went into creating the application modules does not have to be duplicated. All of the modules in the ImageUltra Builder’s repository are can be used to build as many unique system configurations that are needed. The only modules that are different between the portable-sysprep and the ultra-portable are the OS modules. All other modules can be reused as needed.

In the future, Acme Holdings Inc. could start using the ultra-portable system for their older IBM models. To do this, they would replace the sysprep-portable OS module with the ultra-portable OS module and add any required driver modules for each IBM system that they need to support.


Figure 2-139 Repository - XP Ultra portable OS module


Table 2-7 Phase III

Existing State Phase III future systems

Method Legacy Ghost images Ultra-portable ImageUltra Builder

Operating systems Four:

� Windows 95c

� Windows 98

� Windows NT 4

� Windows 2000

Older systems have 9x or NT4 and the newer systems have 2000 only

One:

� Windows XP on IBM hardware

Hardware platforms Eight:



� HP VL 8i

� IBM PC 300 PL

� HP VL 420




Two:

� IBM M50 ThinkCentre



Ultra-Portable OS module provided by IBM with all new systems combined with modules for drivers, patches and applications

Business Units Six:

� Sales

� IT

� Manufacturing

� Field

� Engineering

� Finance

Six:

� Sales

� IT

� Manufacturing

� Field

� Engineering

� Finance

Languages Three:

� English - US

� English - UK

� Spanish

Three:

� English - US

� English - UK

� Spanish


This transformation at Acme Holdings Inc. did not happen overnight. This process took place over a three year time frame. The implementation of a new system build process was done through attrition. Older systems were rebuilt using the processes described above as system rebuilds were required or as systems were transferred to new users. The new systems would adopt the ImageUltra process the first time they were deployed.

Acme Holdings Inc. combined the use of ImageUltra Builder and the reduction of hardware and operating systems. This resulted in:

� Less time spent building and updating system builds

� Lesser cost of maintaining systems

� Greater standardization of platforms

� Single operating systems environment

The following table summarizes the changes that have taken place by moving from the legacy image system to the modular IBM ImageUltra Builder system of system build creation.

Table 2-8 Before and after comparison





Existing State Phase III future systems

Method Legacy Ghost images Ultra-portable ImageUltra Builder

Acme Holdings Inc. Before After

Unique system combinations 216 36

Hardware platforms 8 2

Operating systems 4 1

Images 216 1


The next section, 2.17, “Customize an Ultra-Portable operating system module” on page 99, will show that the UltraPortable image can be customized to meet any customer’s needs. The section, 2.8.1, “Importing modules from an IBM recovery CD set” on page 39, will demonstrate the ability to import the modules provided by IBM into the repository. This is the quickest and easiest means to populate the repository with the driver and OS modules needed for each system.

Features Legacy monolithic images

� Hardware dependent

� OS/drivers/applications are all included

� No reusable parts, any changes require complete recreation

IBM ImageUltra Builder

� Hardware independent

� OS/drivers/applications are modularized

� All modules are reusable.

� Individual modules can be modified independently

Acme Holdings Inc. Before After


Chapter 3. IBM System Migration Assistant

As corporations transition to new operating systems and platforms, one of the most time consuming tasks is the migration of user-specific information to a new workstation. How can an IT organization move information to a new PC without spending hours, if not days, to get a user to an operational state? Migration to Windows 2000 and Windows XP can present many challenges to an IT organization. What is the best way to get users functional in the least amount of time? Will the solution provide adequate flexibility for users to decide what information will be moved to the new PC? How can a complete solution be delivered while reducing costs?

System Migration Assistant (SMA) is a software tool that copies (or migrates) the look, feel and personalization settings of one computer to another. The look and feel, also known as the user’s work environment, is the way the user or company has set up various computer preferences such as desktop and network connectivity settings. System Migration Assistant can also migrate files, folders, and application settings.

System Migration Assistant is a valuable tool used to upgrade from an old computer to a new system. SMA can be used to set up a standard work environment for a company quickly and efficiently. This standardization helps reduce the time spent deploying new computers, it minimizes time spent solving problems, automates IT processes, and reduces the total cost of ownership.

3


System Migration Assistant provides significant savings in time for system administrators. The provided functionality virtually eliminates the need to physically configure each individual computer's desktop and working environment when deploying new machines.

Many organizations spend significant amounts of time preparing for PC rollouts. However, many often overlook migration of data and settings to a new workstation.

System Migration Assistant excels at assisting in the migration from one PC to another or from one operating system to another, or a combination of both. System Migration Assistant has the ability to migrate user data, application settings and operating system settings in an automated fashion.

This chapter discusses:

� “System migration and its effects on the organization” on page 203

� “Installation considerations” on page 205

� “System Migration Assistant installation” on page 208

� “Using System Migration Assistant” on page 211

� “Using SMA in batch mode” on page 239

� “Creating a command file template” on page 249

� “Peer to Peer mode” on page 251


3.1 System migration and its effects on the organizationThe first thing most people typically do when they receive a new PC is to transfer data and customize the look and feel of the PC to their preferences. A good business plan for migration needs to be created before any migration can take place. This is true regardless of who does the migration. If a standardized plan is not used to execute system migrations, end user productivity will be reduced, data loss can occur and the total cost of ownership of end user’s will increase. The organization benefits most if the system migration is done completely, quickly and accurately. A best practice approach to system migration will start with a corporate-wide standard location for user data. This will eliminate much of the inconsistencies of user defined data storage directories. This small step will greatly increase the success rate of any migration solution.

3.1.1 When is system migration required?In most scenarios, system migration is necessary to make the end user productive. Depending on the technology used throughout the organization, system migration requirements will vary.

� Citrix or Terminal services allow a PC to function like a thin client. In these scenarios, some system migration may be required for operating system settings and selected application settings and data. System Migration Assistant would be applicable in this scenario.

� Networked or stand-alone PC: most organizations fall into this category. The PCs have an operating system and local applications. The personal data is stored locally, on a network or both. SMA is most applicable in this scenario. This is the scenario that will be discussed throughout this chapter.

3.1.2 Who transfers the data and personalization of the machine?There are three common scenarios related to system migration:

� No user data, application or personal settings migrated

The IT department provides a new or cascaded machine with a unique network name, SID (Security Identifier) and the proper applications for a user. For the user to be fully functional, they will need the data from their old computer migrated as well as the application settings and personal settings.

Who will perform this transfer? If this is a experienced technical user, they may have the knowledge to transfer the data and settings manually over from their old computer to the new system. This is inefficient and time consuming.

If the end user is not familiar with migration processes, who will they turn to? In many cases, it will be the power user colleague who then is burdened with

Chapter 3. IBM System Migration Assistant 203

this as well. Now the productivity and indirect costs double as two people are involved. If the end user turns to the help desk, the help desk becomes involved as well. These scenarios can be avoided with a fully automated and accurate migration the first time around.

� Data transferred, but no application or personal settings migrated

Some organizations advise the user to save their data to a specific directory on the network or in a specific location on their drive such as a My Documents directory. When the PC upgrade/rollout occurs, the IT staff copies the My Documents directory over to the new PC. This works well for the data portion, assuming all the user data is present, which may not always be the case.

We still revert back to the first scenario on how the user- and/or application-specific settings will be migrated. Again, the end user may perform the remaining migration, involve a colleague or call the help desk. In each case, productivity is lost unnecessarily.

� All data, application or personal settings migrated

This is the ideal scenario. The IT staff has a complete checklist of what needs to be migrated in terms of user data, system settings, application-specific settings and personal settings. The IT staff performs this migration, but how accurately and how completely? The important question is how: Is the transfer done manually or are there tools to assist with this? If it is done manually, the longer the migration time, the more likely it is that the transfer is prone to errors. As a result, the duration of the process increases and user data may be lost.

The length of time it takes to properly migrate an old system to a new system will be affected by two important factors. The first factor is, the number of machines that can be migrated in any given time period. The quicker and more automated the process is the more machines per man hour can be migrated. The second point is cost. Hard costs are involved when internal IT staff or third parties are tasked to assist in the upgrade/rollout/migration. To maximize Return On Investment, a migration solution needs to minimize your migration costs. There are less tangible soft costs such as loss of productivity of end users while they customized new systems and the cost of recreating data if data loss occurs during migration.

From a business standpoint, it only makes sense to have migrations completed in a standardized, comprehensive, quick and accurate manner. This is where IBM System Migration Assistant excels.


3.2 Installation considerationsThis section of the chapter provided insight into the deployment and use of the System Migration Assistant product. This includes:

� “Supported operating systems and system requirements” on page 205

� “System Migration Assistant components” on page 206

� “Basic operations” on page 207

3.2.1 Supported operating systems and system requirementsSystem Migration Assistant can migrate a user’s work environment within and across operating systems. Figure 3-1 outlines which migration scenarios can be implemented.

Figure 3-1 SMA migration

Migration support for a given operating system includes all levels of service pack.

� This includes Windows 2000 Advanced Server.

� It is limited to the 32-bit version.

TO

FROM Windows 2000Professional

Windows 2000Server

Windows XPProfessional

Windows 95 OSR2 Yes No Yes

Windows 98 Yes No Yes

Windows 98 SE Yes No Yes

Windows NT 4.0Workstation Yes No Yes

Windows NT 4.0Server No Yes No

Windows 2000Professional Yes No Yes

Windows 2000Server Yes Yes No

Windows XPProfessional No No Yes


Be aware that you cannot migrate profiles between systems with different languages (for example, from an English system to a Japanese system). Also, there are a number of additional restrictions due to operating system incompatibilities. For details, see “Performing a Migration” in the IBM System Migration Assistant 4.2 User’s Guide, or refer to:


The following requirements apply to both source and target computers unless otherwise noted. A supported Windows operating system must be installed.

� There must be about 10 MB of hard drive space to install SMA. In addition, there must be adequate drive space for temporary variables. In most cases, 30 MB of temporary drive space will suffice.

� In general, connectivity between target and source computer is assumed for these examples. In particular, the target computer must have access to the profile file on the source computer. It is also possible to copy an SMA profile onto a removable medium, such as a CD-R, and to apply the profile to a target computer that is either stand-alone or a client of a network that cannot be connected to from the source computer.

� (For source computers only) There must be adequate space to store profiles. The size of a profile depends on the amount of settings and data you are migrating.

3.2.2 System Migration Assistant componentsDuring a migration, System Migration Assistant takes a snapshot of the work environment. It then uses the snapshot as a blueprint to duplicate your environment on one or more other computers. The computer that the snapshot is taken on is called the source computer. The computer that is migrated to is called the target computer. The source and target computers can be in different physical locations and/or in different time zones. Alternatively, the source and target computer can be the same computer, with System Migration Assistant used to back up and restore settings and files.

The System Migration Assistant tool contains the following files:

� SMA.EXE An executable that captures a variety of settings and files on a source computer, and copies these to a profile. The same executable is also used to apply the profile to a target computer.

� CONFIG.INI A configuration file used to customize the SMA.EXE executable, in particular its graphical user interface.

� SMABAT.EXE A command line interface executable for use in batch mode that is functionally equivalent to SMA.EXE



� COMMANDFILE.TXT A command file used to drive the capture and migrate process in a batch.

3.2.3 Basic operationsThis section describes the basic procedures you are likely to run with System Migration Assistant after you have installed the software. Later sections describe this functionality in detail.

SMA migrates the work environment of one computer to another in two steps:

1. In the first step, System Migration Assistant is customized to capture the desired settings and data. Then SMA copies these settings and files to a profile file. This is referred to as the capture phase.

2. In the second step, SMA uses the profile to copy the settings and files to the target computer. This is referred to as the apply phase.

Before deploying SMA, the company must decide which settings they wish to migrate. Multiple captures can be used on a single system. This would be useful in a corporate environment with multiple departments.

During the capture phase, you need to tell System Migration Assistant what to migrate on the source computer. This is the first step during any standard migration, including when it is run in batch mode. The following settings can be captured:

� Desktop settings - examples are the active desktop, colors, desktop icons, display, icon font, pattern, screen saver and wallpaper.

� Printer settings - this includes local and network printer settings.

� Network settings - examples are the computer description, computer name, TCP/IP configuration, mapped drives, dial-up networking settings, and shared folders and drives.

� Application settings - customization and configuration settings of various supported applications.

� Files - there is no limit to the number of files that can be captured as long as there is sufficient disk space to store the captured data. These can be copied to the same location on the target computer or relocated to a different directory.

� User profiles - both local and network user profiles.

During the apply phase, SMA copies the profile to the target computer. The entire profile can be applied or just selected components of the profile before copying it. This is the second step during any standard migration, including when it is run in batch mode.


3.3 System Migration Assistant installation System Migration Assistant V4 can install over previous versions of System Migration Assistant without the need to remove the older version.

To install System Migration Assistant, follow these steps:

1. For Windows NT 4.0 Workstation, Windows NT 4.0 Server, Windows 2000 Professional, Windows 2000 Server, Windows 2000 Advanced Server, or Windows XP Professional, log on to your computer as the administrator or as a user with local administrative rights.

2. Download the current version of the SMA compressed file from:


3. Please follow the instructions on the Web page to download this file.

4. Run the SMAsetup_<lang>.EXE program that you downloaded from the Internet, where <lang> stands for the language variation you are using. For instance, the English version of the executable is SMAsetup_en.exe.

5. The SMA Installation program will begin and display the Welcome window.

6. Click Next to continue with the setup program.

7. Accept the SMA License Agreement and click Yes to continue.

8. Choose where you want the program to be installed. Click Next to accept the default or Browse to select a different location. The following window shown in Figure 3-2 on page 209 will be displayed.

Note: If the information being migrated is data, the application may not be needed. However, if configuration files of an application are being migrated, then the application should be installed for the settings to be useful on the new machine.



Figure 3-2 SMA Select Program Folder window

9. Select the name of the SMA program folder. Click Next.

10.For Windows 95 and Windows NT 4.0 workstation/server, without any Service Pack, the comctl32.dll (Figure 3-3) must be updated. The install program will display the following notice before installing the update.

Figure 3-3 SMA Update Information Window

11.Click OK and follow the default selections to install the update.

12.Click Finish to complete the installation.

3.3.1 Uninstalling System Migration Assistant The following procedure permanently removes the SMA program files:


1. Select Control Panel.

2. Select Add/Remove Programs.

3. Select IBM System Migration Assistant 4.1.

4. Click the Change/Remove button.

5. Click Yes to confirm removal of SMA. The uninstall process will now start.

6. During the uninstall, it may prompt to remove unused shared files. Click either button depending desired file preservation need.

7. When the uninstall has completed, click the OK button to exit.

Uninstalling System Migration Assistant will not delete all files, these files will need to be manually removed if desired:

� SMA log files generated whenever SMA is run. These files are located at the root of the C: drive unless this was changed the default copy location. For a standard migration, the default location can be changed in the config.ini file. When a migration is run in batch mode, the location can be changed in the command file.

� Temporary files specific to SMA. These are located in the C:\sma\tmp directory unless this was changed the default location of these files in the config.ini and/or command file.

� SMA profiles files (for example, files with an .sma extension).

3.3.2 Silent installation creationTo create a silent install of System Migration Assistant, follow these steps:

1. For Windows NT 4.0 Workstation, Windows 2000 Professional/Server, or Windows XP Professional, log on to the computer as the administrator or as a user with local administrative rights.

2. Download the current version of the SMA compressed file from:


Follow the instructions on the Web page to download this file.

3. Make sure there are no other setup programs running.

4. Launch the SMAsetup_<lang>.EXE program that you downloaded from the Internet, where <lang> stands for the language variation that is being used. For instance, the English version of the executable is SMAsetup_en.exe.

5. Wait until the Welcome window is displayed. Then minimize the SMA setup window. Next bring up the command line interface or Windows Explorer window without exiting the SMA setup.



6. Locate the pft*~tmp folder, where * stands for one or more random characters. If you are running Windows 95 or 98, the folder will be in the C:\Windows\TEMP directory. On Windows NT 4.0 workstation/server, the folder will be in the C:\Temp directory. On Windows 2000 professional/server, or Windows XP Professional, the folder will be in the C:\Document and Settings\<user name>\Local Settings\Temp\ directory.

7. Copy the folder to a location that is can be easily located and rename it if desired (this folder location will be used in the next steps) then cancel the SMA InstallShield setup.

8. From the command line, run setup -r on a system that has the similar configuration as the system for which the silent install is being created for. The executable setup.exe is located in the setup directory that was just used in step. This will create an InstallShield response file named setup.iss in the C:\windows or C:\winnt directory (depending on the operating system). For more information on the setup command, see various articles on a silent installation at:


9. SMA is now ready for a silent mode install. To do so, copy the setup.iss file to the setup directory created previously and from the command line run setup –s –SMS. Alternatively, you can run setup.exe -s –SMS –f1<path>\setup.iss, where the f1 parameter denotes the location of the setup.iss file.

10.When the install has completed, open the setup.log file located in the setup directory and locate the ResultCode variable in the [ResponseResult] field. If Resultcode = 0, the installation completed successfully. Common error values are:

–3 Required data not found in SETUP.ISS file

–5 File does not exist

–8 Invalid path to the InstallShield response file

–12 Dialogs are out of order

3.4 Using System Migration AssistantSystem Migration Assistant migrates the custom working environment of one computer to another in two phases. During the capture phase, SMA settings are

Note: The Local Settings Folder may be hidden by default. Select Tools →Folder Options →View and select Show hidden files and folders if the Local Settings Folder is not displayed.



customized and the files to copy on the source computer are determined. During the apply phase, SMA copies these settings and files to a target computer. This section describes how to run these steps during a standard migration. Migration in batch mode is described in section Figure 3.5 on page 239.

System Migration Assistant is run by two different types of users with different goals in mind. Administrators typically use the program either to replicate (nearly) all the settings of a system or to set up a standard working environment. Regular users (without administrative rights) typically run the program to migrate their desktop and application settings as well as files to another machine. The full functionality of SMA is supported with the user logged into the system with local administrator rights. The following operating systems are fully supported as target systems.

� Windows 2000 Professional

� Windows 2000 Server

� Windows XP Professional

For more details on source and target system support, see Figure 3-1 on page 205. The other operating systems listed in Figure 3-1 on page 205 are supported as source systems only. When migrating from different operating systems, some settings cannot be migrated. Details on these operating system migration limitations are detailed in section 3.4.1, “Capturing settings and files” on page 213. SMA can migrate your desktop settings, application settings, and files, without administrative rights. To capture the following settings, the user must be logged into the system with local administrator rights.

� Computer name

� Computer description

� Shared folders and drives

� TCP/IP configuration

� Workgroup/Domain

Similarly, administrator privileges are required to capture and apply these settings:

� NTFS file permissions

� Registry settings

� User profiles

Note: Make sure to exit all other applications first. Other applications might interfere with the operations that SMA is trying to perform.


3.4.1 Capturing settings and filesThe profile file is the basis of a migration and is the main output of the capture phase. The profile contains all the settings and files to be applied to one or more target computers. During the capture phase settings and files are specified to be migrate. Before selecting the settings on the source computer, make sure that all to-be-captured settings are correct. Before using SMA for the first time read the rest of this section to see which settings can be captured. Be aware that general migration scenarios and restrictions apply as described in 3.2.1, “Supported operating systems and system requirements” on page 205. All migration scenarios across operating systems are not fully supported. Across language migrations are never supported.

The screen shots on the following pages reflect the options that are available in the default configuration of SMA. It is possible that your administrator made changes to the user interface. The interface can be configured for future use.

Start the SMA program on the source computer:

1. Log on to the system as the appropriate user.

2. Click Start →Programs →IBM System Migration Assistant →System Migration Assistant. The windows shown in Figure 3-4 will be displayed.

Figure 3-4 SMA main window

3. In Figure 3-4, click Next to start capturing settings and files from the source computer. The window shown in Figure 3-5 on page 214 will be displayed. At


any point the process can be stopped by selecting the Cancel button on the active window.

Figure 3-5 SMA Migration Options

4. Check the categories that need to be migrated. Select any number of categories but at least one selection must be made. For each category that is chosen, a window that allows the selection of individual settings will be displayed. When all desired selections have been made, click Next to continue. The window shown in Figure 3-6 will be displayed.


Figure 3-6 SMA Desktop Settings

5. Select individual settings or use the Check All and Check None options on the Edit menu to (de)select all settings. The following desktop settings can be migrated:

– Accessibility: Captures the accessibility settings for keyboard, sound, and mouse, as well as general accessibility settings.

– Active Desktop: Captures the active state.

– Colors: Desktop color and window colors.

– Desktop Icons: All desktop contents including folders and files shortcuts, icons, and icon positions.

– Display: Desktop width, height, and color depth.

– Icon Font: Captures the icon font.

Note: This window will only appear if the Desktop option was selected in the Migration Options window shown inFigure 3-5 on page 214.


– Keyboard: Keyboard repeat rate, cursor blink rate, and delay.

– Mouse: Left- or right-handed mouse settings, speed, and double-click time.

– Pattern: Desktop pattern.

– Screen Saver: Current screen saver settings.

– Send To Menu: Send To menu settings.

– Shell: View sort order, view type (larger icon, small icon), show/hide status bar/toolbar.

– Sound: Sound settings.

– Start Menu: Start menu commands.

– Task Bar: Docking edge, size, always-on-top, auto hide, show clock, show small icons in Start menu.

– Wallpaper: Desktop wallpaper.

– Window Metrics: Spacing and arrangement order of minimized windows, message dialog font, menu size, scroll bar sizes.

The following migration restrictions apply to the desktop settings:

– Accessibility: If migrating from Windows 95/98 to Windows 2000 Professional/Server, the ShowSounds, SoundSentry, and Stickykeys settings cannot be migrated.

– Active Desktop: To migrate the Active Desktop including the wallpaper, the wallpaper setting must be selected. Active Desktop is not supported for Windows XP Professional.

– Pattern: Patterns settings cannot be migrated from any operating system to a computer running Windows XP Professional.

– Screen Saver: Cannot migrate the screen saver if migrating from Windows 95/98 to Windows 2000 Professional.

– Shell: In order for the Windows Explorer shell settings to migrate properly, both shell desktop settings and the Microsoft Internet Explorer application settings must be migrated to migrate the shell settings. If Windows XP is the target system, the folder view settings (Large Icons, Tiles, Details, etc.) fail to migrate.

– Sound: to migrate sounds at least one sound selected in the Sounds and Multimedia window located in the Control Panel. If no sounds were used, for instance by selecting the No Sounds scheme in this window, these settings will not migrate successfully. In addition, sound files (for example, .WAV files) are not migrated when the sound option is selected. In most cases, this will not cause an issue since the operating systems uses many of the same sound schemes. If custom created sounds were created or


are using a sound scheme not known on the other operating system, then these sound files will need to migrated as well.

– Taskbar: to migrate a target computer running Windows ME or Windows XP Professional, the taskbar location will not be applied.

– Wallpaper: to migrate the wallpaper file that is of .jpg type, the Active Desktop setting must be captured in source in order to activate it on the desktop. Note that it is not necessary to capture the Active desktop setting when migrating wallpaper that is of .bmp file type.

– Desktop Icons: When migrating desktop icons from Windows 95 to Windows 98/SE, set the desktop to auto arrange icons for the icons to display properly on the target machine.

Figure 3-7 SMA Settings for Applications

6. In the window shown in Figure 3-7, select the application settings you wish to migrate.

By default, System Migration Assistant supports the migration of the customization and configuration settings of the following applications:

Note: This window will only appear if it was selected in the Application Settings option in the Migration Options window shown in Figure 3-5 on page 214.


– Acrobat Reader– ATT Net Client 4, 5– IBM Global Dialer– Lotus Notes 4, 5, 6– Lotus Organizer®– Lotus SmartSuite® – McAfee VirusScan– Microsoft Access– Microsoft Internet Explorer– Microsoft Office 97, 2000, XP– Microsoft Outlook 98, 2000, XP– Microsoft Outlook Express– Microsoft Project 2000– Microsoft Visio– MSN Messenger– NetMeeting– Netscape– NortonAnitVirus– WinZip

For Internet Explorer and Netscape Navigator, the customizations that the user has made to the browser are migrated. These include Bookmarks, Cookies, Favorites, History Folder, and AutoComplete. Similarly for the other applications, all customizations are captured that will enable the same look and feel on the target computer. This includes the address book and locally stored e-mail for Lotus Notes and Microsoft Outlook, but does not include separate data files such as spreadsheets and word documents in Microsoft Office 2000. Also note that the application itself is not migrated.

The following migration restrictions apply to the application settings:

– One of the application settings that can be migrated is the most recently used files (or history of files). In order for this setting to work, the corresponding files must be migrated and place them in the same directory path on the target computer as on the source computer used in“Capturing settings and files” on page 213.

– SMA does not create Netscape Navigator user profiles on the target machine when applying the applications settings of Netscape Navigator. These user profiles must be created prior to running the apply phase on the target computer. Make sure that the profile path for the user on the target computer is identical to the path of the corresponding user on the source computer.

– The data corresponding to the SmartCenter Drawers in Lotus SmartSuite (such as the data for the address book, calendar, and reminders) will only be captured and migrated successfully if it is stored in the default location on the source computer.


– For Internet Explorer, the status bar settings fail to migrate.

– Some applications do not support cross-version migrate. Most settings will not transfer in the following scenarios:

• Office 97 to Office 2000/XP (no settings migrate) • Office 2000 to Office XP (partial settings migrate) • Visio 2000 to Visio 2002 (partial settings migrate) • AT&T Net Client 4 to AT&T Net Client 5 (no settings migrate) • Lotus Notes 4 to Lotus Notes 5 (partial settings migrate) • Outlook 98 to Outlook 2000/XP (partial settings migrate) • Outlook 2000 to Outlook XP (partial settings migrate); for Outlook,

most key settings (mail file, address book, etc.) do migrate successfully.

Figure 3-8 SMA Printers Window

7. In the window shown in Figure 3-8, select the printers that are to be migrated. SMA will migrate the printer links and their drivers. SMA does not support the migration of local printers from a source computer running a different operating system than the target because of possible driver incompatibilities. Network printers are supported when migrating to a different operating system as long as the print queues are located on a Windows server.

Note: This window will only appear if the Printers option was selected in the Migration Options window shown in “SMA Migration Options” on page 214.


8. Click Next. The windows shown in Figure 3-9 will be displayed.

Figure 3-9 SMA Network Settings window

9. As shown in Figure 3-9, select the individual Network settings or use the Check All and Check None options on the Edit menu to (de)select all settings. The network settings you can capture are:

– TCP/IP Configuration:

• IP/Subnet/Gateway: IP address, subnet mask, and default gateway.

• DNS Configuration: the Domain Name Server search order, domain suffix search order, and Host Domain.

• WINS Configuration: Windows Internet Name Service configuration.

– Network Identification:

• Computer Name: network computer name.

• Computer Description

• Domain/Workgroup name

Note: This window will only appear if the Network option was selected in the Migration Options window shown in Figure 3-5 on page 214.


– Other:

• Mapped Drives

– Dial-up networking: Remote Access Services configuration phone book entries for Dial-up networking.

– Shared Folders/Drives

– ODBC Data Sources: ODBC data sources. Migrates any user-defined ODBC data source definitions, but not the database files themselves.

The following migration restrictions apply to the network settings:

– If the source machine’s TCP/IP configuration is set to obtain an IP address automatically, theses settings can be captured by selecting the IP/Subnet/Gateway option. Applying these settings on a target computer will activate DHCP. This option can be deselected during the apply phase, but it cannot be edited in the network settings in the Editable Network Settings window. The corresponding fields will be grayed out.

– If the source machine’s TCP/IP configuration is set to static IP addresses, you can edit the TCP/IP address, subnet mask, and default gateway during the apply phase. The TCP/IP address as well as the network computer name must be unique on the network and are thus likely candidates for editing. In order to edit these settings during apply, these settings must capture here.

– If the source machine is a member of a domain and the target machine will be a member of the same domain, first create a new computer account for the target machine on the domain. If there’s already an account for that machine on the domain, the computer account must be recreated. For Windows 2000 Server and Windows 2000 Advanced Server systems, make sure to select the Allow pre-Windows 2000 computers to use this account check box if this situation applies.

– If migrating a PerSys profile on a dual-home target system, SMA will only migrate the network settings of the first network card.

– SMA will not migrate network adapter settings or any other hardware settings.


10.Click Next in Figure 3-9 on page 220 to proceed to the next window shown in Figure 3-10.

Figure 3-10 SMA File Selection window

The hard drive(s) on the source machine need(s) to be scanned before this window can become fully available. While SMA is scanning, a message window pops up indicating the scanning status. Please wait until this process has finished.

In the File Selection window, any selection of files and folders can be transferred. If you check a folder for migration, its entire contents are selected including files and the content of subfolders. If applicable, the Capture NTFS Settings check box will be present. The NTFS settings will be captured unless it was deselected.

As files or folders are selected, a message similar to the one shown in Figure 3-11 on page 223 may be displayed.

Note: This window will only appear if the Files and Folders option was selected in the Migration Options window shown in Figure 3-5 on page 214.


Figure 3-11 SMA Application Information Window

This message appears when a file that might cause migration problems is selected. In the default setup, SMA will display this warning when an application-related file with a .dll, .exe, or .com extension are selected.

SMA is designed to migrate application settings and not entire applications. Most applications created for use on Windows use many registry and shared dll files to run properly. Only applications that are sell contain in the applications installation directory can be migrated form the source to the target system. The best practice solution for moving an application is to first to capture the settings on the sources system. Then install the application on the target system Finally use SMA to apply these captured settings and customizations to the target system.

For this reason, it is strongly recommended that no files in the root of c: be selected otherwise the entire contents of the C: drive be selected. Since this will select all files, including all operating system files this will cause migration issues during both the capture and apply process. Use ThinkVantage Technologies to easily install and maintain operating systems as well as install additional applications. For more information, see:

http://www.pc.ibm.com/us/think/thinkvantagetech.html

Notice that if the source computer does not have the same disk drive layout as the target computer, plan to use an alternate destination for files and folders. Changing target locations is described next.

Important: Do not migrate Windows operating system files from a source to a target computer. This will cause a severe malfunction of the target computer. You must have the Windows operating system must be installed on the target system before using System Migration Assistant.



Figure 3-12 SMA File Selection redirect window

11.To redirect an individual file, check the file, right-click the name (or press shift-F10), and choose one of the options in the pop-up window (see below). To redirect all files in a folder, select the folder, right-click the name, and choose one of the options in the pop-up window. All files in this folder and included subfolders will be relocated according to the option you choose, and the new location will appear in bold italics in the destination field of the to-be-relocated files (but not folders).

If a selected file or folder is right-clicked on, a window will pop up with three options: My Documents, New Path and Original Path.

If My Documents is selected, a window similar to Figure 3-13 on page 225 will appear providing three options.


Figure 3-13 SMA My Documents Destination window

Those options are:

– Remove folder name(s) and place the file(s) directly into “My Documents”. If selected, the file will be copied directly to the “My Documents” folder.

Example:

C:\MyDir\sample.txt to My Documents\sample.txt C:\MyDir\SubDir\abc.doc to My Documents\abc.doc

– Keep the current folder name(s) and place as subfolder(s) of “My Documents”. If selected, the file’s original path will be preserved when the file is copied to the “My Documents” folder.

Example:

C:\MyDir\sample.txt to My Documents\MyDir\sample.txt C:\MyDir\SubDir\abc.doc to My Documents\MyDir\Subdir\abc.doc

– Change the folder name(s) and place as subfolder(s) of “My Documents”. If selected, the file will be copied directly to a subfolder in “My Documents”. Enter the name of this subfolder in the field below the corresponding radio button.

Example:

C:\MyDir\sample.txt to My Documents\Migrated\sample.txt C:\MyDir\SubDir\abc.doc to My Documents\Migrated\abc.doc

If New Path... is selected, a window similar to Figure 3-14 on page 226 will be displayed, providing two options.


Figure 3-14 SMA New Path Destination window

Those options are:

– Keep current folder(s) and place as subfolder(s) of: The file’s original path will be preserved when the file is copied to the subfolder whose name must be entered in the field below the corresponding radio button.

Example:

C:\MyDir\sample.txt to C:\Migrated\MyDir\sample.txt C:\MyDir\SubDir\abc.doc to C:\Migrated\MyDir\SubDir\abc.doc ..

– Place file(s) into the following folder: The file will be copied directly to the subfolder whose name you must enter in the field below the corresponding radio button.

Example:

C:\MyDir\sample.txt to C:\Migrated\sample.txt C:\MyDir\SubDir\abc.doc to C:\Migrated\abc.doc

If the Original Path is selected, it will undo destination changes.

During a standard migration, when a file is relocated to a folder that already has a file with that name, the existing file will be overwritten. It is also possible to prevent the overwriting of existing files. When existing files are not to be overwritten, the base name of the to-be-relocated file will be appended with _01 to prevent overwriting of the file already present. For example, the file sample.txt will be renamed sample_01.txt. Additional duplicate files will be given the addition _02, _03, and so forth.

For shortcut (.lnk) files only, SMA will change the hard-coded pathname when the referred-to files or folders are redirected.


12.Click the Search button in the File Selection window to find files or folders. You will see a window similar to Figure 3-15.

Figure 3-15 SMA file selection search window

The following options are available:

– Search for. Type the full or partial file name. The use of (*) wildcard to match zero or more characters or the (?) wildcard to match exactly one character is supported.

– Search In. In the drop-down box, select the location to start the search from. Select one or all hard drives.

– Search Now. Click this button to start the search process. SMA will look for files and folders matching the entered string in the requested location and all its subfolders. The search routine is not case-sensitive. Results are given as follows:

• Origin. Shows the files found including the full path. Click the check boxes to select the files are to be migrated.

Note: Files that make references to file or folder locations using hard-coded pathnames will likely not work when the referred-to files or folders is redirected. Hard-coded pathnames might occur in batch files (.bat, .cmd) and configuration files (.ini, .cfg). Exercise caution when using the redirect functionality.


• Type. Shows the file type.

• Destination. Shows the planned location of the files on the target computer. By default, this field is blank, indicating that the files will have the same path on the target computer as it has on the source computer. However, users can select alternate destinations by right-clicking the corresponding cell on the destination panel.

• Size. Shows the size of the file.

• Date. Shows the date and time of the file.

• Check All. Click this button to select all files shown in the search panel.

• Clear All. Click this button to deselect all files shown in the search panel.

13.Click Close. Click the Association tab the window shown in Figure 3-16 will be displayed.

Figure 3-16 SMA File Selection window

The Association tab organizes files by file type instead of by drive location. All files of the same type can be selected or select any combination of individual files and/or file types. Just as with the Hierarchy tab, these can be redirected and use the search for files and folders.

Note: Click the Search button in the File Selection window to find files or folders.


14.Click Next. The window shown in Figure 3-17 will be displayed.

Figure 3-17 SMA User Profiles window

15.Select the user profiles that is to be migrated. SMA will migrate the user-specific settings stored in the profile plus the contents of the “My Documents” folder of that user. For a local profile, the user password is not migrated. Instead the password is reset to the user name.

SMA does not support the migration of user profiles from a source computer running Windows 95 or Windows 98 to a target computer running Windows 2000 Professional, or Windows XP Professional.

For Windows 2000 and Windows XP, you not only need to have administrative privileges when migrating user profiles, but your user account must also have the “Act as part of the operating system” privilege. When attempting to migrate a user profile to a target system, SMA will create the required privilege, but the migration will not succeed because a reboot is required after this privilege is set. To resolve, reboot the system and run SMA again, or set up the privilege manually, and then reboot the system to and SMA. This setting is found in the Local Security Policy of the system.

Note: This window will only appear if the User Profiles option was selected in the Migration Options window shown in Figure 3-5 on page 214. The profiles of the currently logged on user and the guest account are never shown.


16.Click Next. The window shown in Figure 3-18 will be displayed.

Figure 3-18 SMA User Profile Locations

This window has the following options:

– Peer to Peer file transfer check box. This option is discussed in detail in “Peer to Peer mode” on page 251

– Password protect check box. Select this option to password protect the profile. In our example, we put a check in the check box.

– Save As. Provide the name of the profile by using this button or type a file name including the full path in the field next to the button.

– Notes about this migration: Comments may be entered in this panel. The maximum number of characters that can be entered is 1024 characters.

17.Click Next when you have filled in all other fields; you will be asked to enter and confirm a password (Figure 3-19 on page 231). The password must be between 4 and 16 characters long.

Note: On rare occasions, invalid characters might appear at the end of the file name. This issue can be easily resolved by manually deleting these characters.


Figure 3-19 SMA Password Protect window

18.Click OK. To go to the next window show in Figure 3-20

Figure 3-20 SMA Copy Progress window

19.SMA now copies the settings and files to the profile file. This may take a few minutes, depending on how many settings and files are being copied. When finished the window shown in Figure 3-21 on page 232 will be displayed.


Figure 3-21 SMA Migration Summary window

20.When the profile file has been created, a summary is provided. The summary reports whether any errors occurred and mentions the location of the log file. The contents of this log file can be displayed by selecting the log radio button. There is an option of saving the summary information. Click Finish to exit.

3.4.2 Applying settings and filesDuring the second phase of the migration process, the settings and files are applied to the target computer.

Start the SMA program on the target computer:

1. Log onto the target system with the same username and password that was used for the capture phase.

2. From the Windows Desktop, click Start →Programs →IBM System Migration Assistant →System Migration Assistant. The window shown in Figure 3-22 on page 233 will be displayed.


Figure 3-22 System Migration Assistant window

3. Select Apply captured settings and files to this computer and click Next. The window shown in Figure 3-23 will be displayed.

Figure 3-23 SMA Profile Location


4. Click Open and select the profile file that is to be applied. Notes about this profile will be displayed in the notes panel. The profile can be edited by selecting Edit Selections and clicking Next. If the profile file is password protected, a prompt will be displayed to enter a password.

5. Click Yes to migrate the printer settings or click No to deselect the printer settings.

6. The desktop settings selected during the capture phase are shown. The option of deselecting one or more of these options is provided. These options are shown in Figure 3-24.

Figure 3-24 SMA Applying Desktop Settings

7. The application settings selected during the capture phase will be shown. There is the option of deselecting one or more of these settings.

8. The network settings selected during the capture phase will be shown. There is the option of deselecting one or more of these settings.

Note: This window/option will only appear if you captured printer settings and clicked the Edit Selection check box in the Profile Location window.

Note: The following windows will only appear if the information was captured during the initial migration.


9. The Editable Network Settings window will be shown. This window will only appear if any editable network settings were captured and the Edit Selection check box in the Profile Location window was selected.

10.In the window shown below, the values of various network settings can be edited. The fields of network settings that were not captured in this profile or that are not editable in this network configuration will be grayed out.

Figure 3-25 SMA Applying Captured Printers

11.Select the printers that are to be migrated. SMA will migrate the printer links and their drivers. SMA does not support the migration of local printers from a source computer running a different operating system than the target. Network printers are supported when migrating to a different operating system. If migrating a target computer to the same domain as the source computer and are keeping the source computer operational, the IP address must be changed, but the domain name can remain the same.

Either the computer name or the domain name can be applied but, not both at the same time. To migrate both settings, first copy one setting, and then run apply again with the other setting.


12.The files and folders selected during the capture phase are shown in Figure 3-26. There is the option of deselecting one or more selections. Files with an invalid path name for the target computer are given in red. These conflicts must be resolved before proceeding.

Figure 3-26 SMA File Selection Hierarchy tab

13.The destination can be changed for the to-be-copied files for the target computer. For more information on how to use these functions and possible problems that can occur as a result of redirection, see the IBM System Migration Assistant 4.1 User’s Guide.


Figure 3-27 SMA File Selection - Path Location

14.Click the Search button to find a specific subset of files and folders. For more information on how to use these functions, see the IBM System Migration Assistant 4.1 User’s Guide. Note that the Search in the drop-down box only allows a search within the given profile.

Figure 3-28 SMA Applying Search window


15.If the Association tab is selected, files selected during the capture phase are organized according to file type rather than by drive location. There is the option to deselect, search, and redirect files and folders.

Figure 3-29 SMA File Selection - Association Tab

16.The user profiles selected during the capture phase will be shown if it was selected this in the initial capture. There is the option of deselecting one or more of these user profiles.

17.SMA is ready to start copying the to-be-migrated settings. Click Yes to start the copy process or click No to re-edit the profile or cancel the migration process.

18.If the Domain setting were selected to migrate shown in Figure 3-5 on page 214, a window will be shown and will prompt you for a User ID and password. The user must have at least account operator privileges in the domain. Remember that a new computer account must be created prior to applying the profile.

19.The Printers Migration window will be shown if you selected the Printers option in the Migration Options window shown in Figure 3-5 on page 214 was selected. Select the printers that are to be migrated. SMA will migrate the printer links and their drivers. SMA does not support the migration of local printers from a source computer running a different operating system than the target. Network printers are supported when migrating to a different operating system.


20.SMA will now copy the settings and files to the target computer. This may take a few minutes, depending on the size of the profile file.

If applying a SMA 2.2 profile, the percent completed progress bar does not faithfully represent the actual percentage done. This issue is most noticeable on target machines running Windows XP Professional. However, the profile is being applied correctly. Wait until the copy process has finished and the Migration Summary window appears.

21.When the settings and files have been applied to the target computer, the summary screen will appear. Any errors are given in the summary. Click the Log button to get a detailed overview of the migration process. Click Finish to exit SMA.

22.Depending on the settings that were applied, SMA will be prompt to reboot the computer in order for the changed settings to take effect.

3.5 Using SMA in batch modeThis section describes how to perform a migration in an unattended fashion. The same settings and files can be migrated in batch mode as during a standard migration, and the two modes can even be used interchangeably. The same logon considerations apply to batch mode migration as to a migration via the user interface.

The name of the batch mode executable is SMABAT.EXE, located in the <drive>:\Program Files\IBM\SMA directory.

The syntax of the command is: SMABAT

{(/c cmdfile [/n smafile]) | (/a [cmdfile] /n smafile) | (/e smafile)} [/o logdir] [/t tmpdir] [/p smapwd] [/s tsmpwd] [/jdu userid /jdp pwd] [/v]

Important: Clicking the Cancel button will halt the copy process, but does not undo the changes that have already been made. This will leave the computer with some of the changes and file migrations complete, but others not. In the worst case, it could leave the computer in an inconsistent state requiring reinstallation of the operating system. Do not cancel the copy process unless absolutely necessary.

Note: Before running SMA during the capture or apply phase, please make sure to exit all other applications first. Other applications might interfere with the operations that SMA is trying to perform.


Table 3-1 describes the primary parameters of the SMABAT.EXE command.

Table 3-1 SMBAT.EXE parameters

Following is additional information on the primary parameters along with descriptions of additional optional parameters.

/c cmdfile Capture the settings and files. You must specify the full path and the name of the command file. Optionally, you can specify the /n parameter with the full path and the name of the profile file. You must specify either the /c, /a, or /e parameter when running SMABAT.

/a [cmdfile] Apply the settings and files. You must also specify the /n parameter with the full path and the name of the profile file. You can optionally specify the full path and the name of the command file to deselect settings prior to copying the profile to the target computer. You must specify either the /c, /a, or /e parameter when running SMABAT.

/e smafile Extract the command file used to create the profile. You must specify the full path and the name of the profile. You must specify either the /c, /a, or /e parameter when running SMABAT.

/n smafile Provide the full path and the name of the profile file.

Function Syntax What it does

Capture /c cmdfile /n smafile

where� cmdfile is the fully qualified file name of the

command file� /n smafile is an optional parameter that

specifies an alternative profile, and smafile is the fully qualified name of the profile.

Captures the files and settings specified in the command file and creates a profile. By default, the profile is written to the directory that is specified in the command file. You also can write the profile to an alternative directory.

Apply /a cmdfile /n smafile

where� cmdfile an optional parameter that specifies

a command file� /n smafile is an optional parameter that

specifies an alternative profile, and smafile is the fully qualified name of the profile.

Applies the files and settings specified in the profile. You also can select to run a command file against the profile before it is applied to the target system.

Extract /e smafile

where smafile is the fully qualified name of the profile.

Extracts the command file used to create a profile.


/o logdir Provide the full path and the name of the log file directory. This parameter is optional.

/t tmpdir Provide the full path and the name of the temporary SMA directory. This parameter is optional.

/p smapwd Provide the password that will be used to password protect the profile during capture or that is required to access the profile during migration. This parameter is optional.

/s tsmpwd Provide a TSM password. This parameter is optional. This is an advanced featured described in Migration with Tivoli® Storage Manager.

/jdu userid and /jdp pwd Provide a user name and password to enable access to the domain. The user must have at least account operator privileges in the domain. These parameters are required only during the apply phase when you migrate the domain setting. When used, both parameters must be provided. You must also create a new computer account prior to applying the profile.

/v Enables verbose logging in the SMA log files. This can be helpful to resolve migration problems.

The command file guides the execution of the command, especially during capture. The next sections describe the role of the command file in detail.

3.5.1 System Migration Assistant capture phase in batch modeDuring the capture phase, SMABAT.EXE reads the contents of the command file and creates a profile file. An example of a capture command is:

SMABAT /c C:\MyCommandFileDir\TheCommandFile.txt

As the example shows, the command file completely drives the capture process. SMA provides a default command file, <drive>:\Program Files\IBM\SMA\commandfile.txt, which you can use as a template to create your own version.

The remainder of the section explains the various commands in the command file. SMA will process these commands in the exact order in which they appear in

Note: Edit the command file with care. A semicolon should precede all comments in the file. SMA does not treat the text in this file in a case sensitive fashion. If the command file has syntax errors, error messages will be written to standard output but processing continues. However, depending on the nature of the error, the actual results might differ significantly from the intended behavior.


the file. In the command file, each command is described in a separate section clearly marked with a beginning and end, namely [<command>_start] and [<command>_end]. One or more parameters and their values can be entered between these markers, with each parameter-value pair placed on a separate line.

Example:

[transfer_mode_start] transfer_mode = selective [transfer_mode_end]

The same settings can be migrated in batch mode as through the user interface. File migration is functionally equivalent in both modes, but the batch mode has a unique method of selecting files and folders, involving inclusion and exclusion on the basis of various characteristics. These procedures are described last.

The commands, with the exception of those driving file migration, are:

� Password To specify a password, provide a value for plain_password. The maximum password length is 16 characters and the minimum is 4 characters. If a password is provided on the command line, the value in the file will be ignored.

The functionality of the parameter encoded_password is beyond the scope of the documentation.

� Transfer_Mode This has two possible values, for example, selective or mass. You must specify one of these values. Remember that selective refers to the standard migration.

� Profile_Path_and_Name The full path and the name of the profile file. For example:

[profile_path_and_name_start] output_profile = C:\sma_profiles\newprofile.SMA [profile_path_and_name_end]

The value entered here will be ignored when you specify a profile name on the command line.

� TSM This is an advanced feature for use with Tivoli Storage Manager

� Desktop To select a desktop setting, type 1, otherwise type 0 or leave unspecified. The following desktop settings can be set:

– accessibility– active_desktop– colors– desktop_icons– display– icon_font


– keyboard– mouse– pattern– screen_saver– sendto_menu– shell– sound– start_menu– taskbar– wallpaper– window_metrics

� Network To select a network setting, type 1, otherwise type 0 or leave unspecified. The following network settings can be set:

– ip_subnet_gateway_configuation– dns_configuration– wins_configuration– computer_name– computer_description– domain_workgroup– mapped_drives– shared_folders_drives– dialup_networking– microsoft_networking

� Registry You can migrate registry values and keys. This is an advanced feature described in “Migrating Registry Settings” of the IBM System Migration Assistant 4.1 User’s Guide.

� Applications Enter one or more supported applications. In the specified section, put in the application family name, as specified in the example in the commandfile.txt found in the SMA installation directory.

Example:

[applications_start] Lotus Notes Lotus SmartSuiteMicrosoft OfficeMicrosoft Outlook[applications_end]

� UserProfiles. For local profiles, type computer_name\username. For network profiles, type domain_name\username. To tell SMA to capture all of the user profiles, set GetAllUserProfiles = 1.

Example:

[userprofiles_start] GetAllUserProfiles = 1


[userprofiles_end] -- or -- [userprofiles_start] JANESCOMPUTER\administrator MYDOMAIN\janed [userprofiles_end]

� MigrationNote Enter comments about the profile. You can use up to 1024 characters.

� Misc_Settings Various miscellaneous settings can be selected here:

– bypass_registry This parameter is only interpreted during the apply phase. For details, see “Applying in Batch Mode” of the IBM System Migration Assistant 4.1 User’s Guide.

– quota Leave unspecified, or specify a value in megabytes to restrict the amount of uncompressed data that can be captured in a profile.

– printers Enter 1 to select the printer settings, otherwise enter 0. This value must be specified.

– capture_ntfs_attribute Enter 1 to capture the NTFS attributes, or enter 0 or leave unspecified.

– user_exit After SMA finishes, the executable specified here (including full directory path) will be launched. This value is optional.

– overwrite_existing_files Enter 0 to prevent the overwriting of existing files, or enter 1 or leave unspecified to overwrite existing files during a selective migration.

– temp_file_location SMA will write temporary files to this directory. The default location is C:\sma\temp. It is possible to use a shared location on another system. If a temporary directory is specified on the command line, the value in the command file will be ignored.

– log_file_location SMA will write log files to this directory. The default location is the C: drive. It is possible to use a shared location on another system. If a log file directory is specified on the command line, the value in the command file will be ignored.

– alternate_print_driver_location Specify an alternate location of printer driver files. This parameter is optional.

– removable_media Enter 1 to enable the use of removable media, or enter 0 or leave unspecified.

– AutoReboot Enter 1 to have SMA reboot automatically at the end of a target side migration. The default value is 0. If you leave it unspecified, the system will not reboot.


� Editable_Connectivity This section is only interpreted during the apply phase. See “Applying in Batch Mode” of the IBM System Migration Assistant 4.1 User’s Guide.

File migration in batch mode is driven by three file selection and three file deselection commands, as well as a special command that acts on drives. You can use any number of file selection and deselection commands and create any sequence. SMA processes these commands in strict serial order. For instance, if a file inclusion command is followed by a file exclusion command which is in turn followed by a file inclusion command, SMA will include files on the basis of the first command, then it will exclude files from the resulting set on the basis of the exclude command, and then it will include files from the original set of scanned files on the basis of the third command. Changing the order of commands can dramatically affect the final outcome.

SMA will select and deselect files on the basis of the original location of files and folders on the source computer. File redirection statements are stored in the profile and are interpreted during the apply phase after file deselection commands have been processed. The processing of file and folder names is not case sensitive. For file names but not path names, you can use the asterisk (*) wildcard that matches zero to many characters, and the question mark (?) wildcard that matches exactly one character. All file migration commands are optional.

The file handling commands are:

� Exclude_Drives Enter the drive(s) that is/are not going to be scanned, such as the C: drive. When you exclude a drive, none of the files stored on that drive can be selected. If you use this command, it must be placed at the beginning of the file migration section.

� IncludeFile With this command, you can search for all files that match a particular pattern in a specific folder, but not in its subfolders. Wildcards are allowed in the file name only and logical names such as “My Documents” are not allowed. Optionally, you can place these files in a new folder on the target machine. Wildcards are not allowed in the name of the new location but logical names are allowed.

Example:

[includefile_start]

Note: The Automatic reboot feature is not supported in batch mode on a Windows 98 or ME target system. The user must manually close the SMABAT command window and manually reboot the system.


;Copy all files in the folder C:\Documents and Settings\JohnD\My ;Documents\* and place these ;in the same location on the target machine. Notice that the actual ;physical path of the My ;Documents folder must be used here. C:\Documents and Settings\JohnD\My Documents\* ;Copy all .cpp files in the D:\MyCode folder and put these in My ;Documents\MyCode on the ;target machine D:\MyCode\*.cpp, My Documents\MyCode [includefile_end]

� IncludePath With this command, you can select a folder and copy its contents including subfolders and their contents. Optionally, you can relocate your selection on the target machine. Wild card characters are not allowed in this command.

Example:

[includepath_start];Copy the entire contents of My documentsMy Documents;Copy everything starting the folder C:\Project_1\Lab23\1998\WhiteMice, and ;copy this;to the target machine in My Documents\WhiteMiceC:\Project_1\Lab23\1998\WhiteMice, My Documents\WhiteMice[includepath_end]

� IncludeFileDescription With this command, you can search for all files that match a particular pattern on part of or the entire machine. If desired, you can relocate these files and preserve or remove the directory structure.

The syntax is

<File Name>,[<Start Location>],<New Location>,[{P | R }]

where

<File Name> This is the name of a file without the path. Wildcards are allowed. This parameter is required.

<Start Location> The search starts here. The location and all its subfolders will be searched. The start location can be a drive letter, a folder, or the logical locations “My Computer” or “My Documents” (on applicable operating systems only). It cannot have wildcard characters. This parameter is optional. If left unspecified, SMA will search “My Computer”, excluding the CD-ROM and network drives.

Note: The logical name “My Documents” is translated to the correct physical location on the drive. “My Documents” is not used on Windows 95, Windows NT4.0 Workstation or Windows NT4.0 Server.


<New Location> This is the folder to which the files will be copied. The folder will be created on the target machine if necessary. It can be the root of a drive such as the C:\ drive, or a logical location such as “My Documents”. It cannot have wildcard characters. This parameter is required.

P | R Preserve/Remove path. You can specify one of these parameters. If the option is Preserve, the path of the file (from the root of the drive) is preserved and recreated on the target machine starting in the folder specified in <New Location>. If the option is Remove, the file will be stripped from its original path and will be placed directly in the folder specified in <New Location>. This parameter is optional. If left unspecified, the path will be preserved

Example:

[includefiledescription_start];Get all files ending in .doc, and put them directly in the My Documents ;folder, i.e. remove the ; original paths. *.doc,, My Documents,R ; Get all files ending in .xls located in the folder C:\acctng or its ;subfolders, and put them in ; C:\Accounting\LastQuarter\Spreadsheets, preserving the original directory structure.;The new location for files and folders directly located in the C:\acctng ;folder will be C:\Accounting\LastQuarter\Spreadsheets\acctng *.xls, C:\acctng, C:\Accounting\LastQuarter\Spreadsheets, P [includefiledescription_end]

� ExcludeFile With this command, you can deselect one or more files in a specific folder but not its subfolders. This command has just one parameter, file name, which must be specified with the full path. Logical paths are not supported and wildcards are only allowed in the file name. For instance, C:\Docs\*.tmp will remove all files with a .tmp extension from the C:\Docs folder.

� ExcludePath With this command, you can deselect all files and folders located in a certain folder. This command has just one parameter, folder location, which must be specified without wildcards. For instance, C:\Windows will remove everything in that location, including subfolders and their contents.

� ExcludeFileDescription With this command, you can exclude all files with a certain name. Wildcards are allowed but a path name is not allowed. Optionally you can start the search from a certain location of the directory structure onward, that is, that folder and all its subfolders. Logical names are allowed. If the location is not specified, all selected files will be searched.

Example:

[excludefiledescription_start] ; Select all files matching the specified pattern, located in the My ;Documents ;folder or its subfolders. *_old.doc, My Documents


[excludefiledescription_end]

3.5.2 System Migration Assistant apply phase in batch mode During the apply phase, SMABAT.EXE copies the contents of the profile onto the target computer. An example of an apply command is:

SMABAT /a /n C:\sma_profiles\receptionists.sma

In this example, the selected profile is applied as is to the target computer without any changes. It is also possible to edit a profile prior to applying it, as is shown in the following example:

SMABAT /a C:\MyCommandFile\EntryLevelReceptionistCommandFile.txt /n C:\sma_profiles\receptionists.sma

In this example, SMA applies the profile receptionists.sma after some changes have been made as described in the command file EntryLevelReceptionistCommandFile.txt.

The command file that is used during the apply phase has the same syntax as the file used during the capture phase, although some of the commands behave differently. During the apply phase, you can only make changes to a given profile. For instance, if your profile includes all desktop settings but you don’t want to apply the active desktop to a given target computer, you can deselect that option by typing active_desktop = 0 in the desktop settings section of the command file. However, if your profile does not include printer settings, you cannot include printer settings by entering printers = 1 in the miscellaneous settings section of the command file. In order for deselection to be successful, you must know which settings were stored in the profile.

Similarly, when the profile includes a selection of files, you can exclude some or all, but you cannot select a file that is not included in the profile. In order for deselection to be successful, you must know which files are in the profile, as this information is not readily available in the original command file. Remember that SMA processes file exclusion commands assuming the original location of files and folders on the source computer prior to interpreting redirection statements.

During copying, when a file is relocated to a folder that already has a file with that name, the base name of the to-be-relocated file will be appended with _01 if the overwite_existing_files parameter in the command file is set to not overwriting. For example, the file sample.txt will be renamed sample_01.txt. Additional duplicate files will be given the addition _02, _03, and so forth.

During the apply phase, these commands exhibit special behavior:

� Exclude_Drives This command is ignored.


� Misc_Settings

bypass_registry Enter 1 to deselect all registry settings, or enter 0 or leave unspecified.

� Editable_Connectivity You can edit the values of various connectivity settings. Remember that you must have these settings included in the profile in order to edit them. The parameters, whose equivalents during a standard migration are described in detail in “Editable Network Settings” in the IBM System Migration Assistant 4.1 User’s Guide, are:

– computer_name

– computer_description

– ip_address

– subnet

– gateway

– domain_workgroup

3.6 Creating a command file template SMA is designed such that batch mode migration and migration executed via the user interface can be used interchangeably. In fact, when SMA is run through the user interface, SMABAT.EXE is invoked in the background to do the actual creation of the profile during capture and to copy the files and settings during apply.

One advantage of this design is that the profiles produced in either mode are the same. For instance, if you at one point created a profile in batch mode but at a later time are uncertain about the settings and files captured, you can open the profile and examine its contents through the user interface.

Another advantage of this design is that you can use the user interface to create a command file template for use in batch mode. Rather than creating an actual profile, SMA is run through the user interface to capture the types of settings that you want to capture. This information is written to a command file, which you can then use to capture a profile in batch mode. In other words, you can create this template file once and then use it repeatedly to capture the actual settings of different source computers. Although the specific settings that you migrate will depend on the source computers’ environment, the kind of settings that you migrate will be the same across your entire organization. File migration information is not written to this template, because file handling is driven differently in the two modes. To create a command file template, follow these steps:


1. With a text editor, open the <drive>:\Program Files\IBM\SMA\config.ini file.

2. Locate the Just_Create_Command_File option. Add Yes after the equal sign.

3. Locate the Command_File option and change the default name and location of the template file, for example C:\MyCommandFiles\Win2KCommands.txt. Remember the default set by SMA, that is, C:\CommandFile\Commands.txt or the default location of your choice.

4. Close and save the new config.ini file

5. Start SMA.EXE and run the capture phase. Notice that the Files and Folders check box on the Migration Options page does not appear, nor does the corresponding File Selection window. The Profile Location window is used to capture the location and name of the profile in the template file, although no actual profile will be created.

6. Edit the <drive>:\Program Files\IBM\SMA\config.ini file and change the Command_File variable back to the default location, that is, C:\CommandFile\Commands.txt, or the location of your choice. This will prevent your template file from being overwritten the next time you run SMA. If applicable, also reset the Just_Create_Command_File option.

7. (Optional) If you want to add specific file inclusion and exclusion routines, edit your template file and make the desired changes.

8. On the source computer, run the batch program in capture mode using your new template file and create the profile. Apply this profile to one or more target computers in batch mode. If desired, repeat this step for different combinations of source and target computers.

Note: For more detailed examples of file migrations, reference the IBM System Migration Assistant 4.1 User’s Guide. In the User Guide there are excellent examples of how to customize the standard migration, migrate registry settings, migrate additional application settings and use SMA with Tivoli Storage Manager.

Tip: SMA can be integrated into a ImageUltra Builder module. Create a DOS batch file (.bat) file to call the executable and place the script, executable and SMA installation package into the module.


3.7 Peer to Peer modePeer to Peer migration is a new function that has been implemented in the latest versions of IBM System Migration Assistant. This function allows you to automatically transfer all the items you have selected through a network without having to store the .sma file anywhere. IBM System Migration Assistant will automatically find the other machine based on a profile name. When the machines are connected together, IBM System Migration Assistant will take care of the file transfer between them. This is extremely useful when a network infrastructure or external media is not available for storage.

The Peer to Peer mode of migration is typically up to 3 times faster than the client/server mode described in previous sections. For example, in a test environment, a 5 gigabyte migration took 70 minutes in client/server mode (over a 100 Mbyte Ethernet switched LAN), while taking 24 minutes in Peer to Peer mode (using a 100 Mbyte Ethernet cross-over cable).

The implementation process illustrated in Figure 3-30 on page 252 also includes some optional components as part of the migration process:

� Remote Deployment Manager (RDM) (previously known as LCCM). Refer to the redbook Using the System Installation Tool Kit to Streamline Client Rollout, SG24-6178.

� Rescue & Recovery - Refer to the redbook Using ThinkVantage Technologies Volume 2: Maintaining and Recovering Client Systems, SG24-6060.

Important: Both machines must be connected to the same network or with a crossover cable to make the Peer to Peer feature work.


Figure 3-30 Automated migration process

The following scenario illustrates the GUI method of using the Peer to Peer feature.

Start SMA on the source machine. Proceed with the steps as described in 3.4.1, “Capturing settings and files” on page 213.

After you have completed the selection of the elements that you would like to migrate on the source machine, you will arrive at the window shown in Figure 3-18 on page 230. This is the same window shown in Figure 3-31.

Load target machinewith image

(IUB)

Prepare sourcemachine formigration

�Read migration guideAccess internal web sitefor additional migration info

�

�UnpackConnect to powerConnect to Corp. network

�

�

�UserIDDomainetc.

�

�

Connectsystems with

crossovercable

Capture datafrom source

machine(SMA)

�Captured datais stored on thetarget machine

Connect toCorp. network

Migration completed

Restorecaptured data

(SMA)

Validate Clienton Network

Install newIBM Client

Initiate backup(R&R with RR)

Select apps toinstall (SDA)

Note: Since there are two machines that are connecting to each other, one machine will work as a source and the other machine will work as a target. In the rest of this text the name “source machine” is used for the machine that you want to migrate from, and the name “target machine” is used for the machine that you would like to migrate to.


Figure 3-31 Peer to Peer file transfer

1. On the menu shown in Figure 3-31, check the check box named Peer to Peer file transfer. The Save as button will be grayed out as soon as you check this box. If you check the box next to Password protect, you will also be able to set a password for the transfer for enhanced security. When you have checked one or two of those boxes, click Next.

Figure 3-32 Password box

2. If, and only if, you selected the check box next to Password protect, the window shown in Figure 3-32 will be displayed. The password must be at


least 6 characters long, and it cannot have identical consecutive characters. It is important that you remember this password since it must be used on the target machine. When you have filled in the password twice, click OK. A new window that looks like Figure 3-33 will appear.

Figure 3-33 Profile name

3. If you did not select the check box next to Password protect previously, the window shown in Figure 3-33 will be the next window displayed. If you selected Password protect in step 1, this will be the window that you come to after filling in the password as described in the previous step.

On this window, you must fill in a unique name for the profile you are going to transfer from the source machine to target machine. It is very important that it is unique since this is the name the machines will use to find each other on the network. If several concurrent transfers use the same profile name, IBM System Migration assistant will not be able to separate them from each other. In our example, we have used “yourprofilename” as an example. This can be changed to any name as long as you remember it to fill it in on the target computer.

4. Fill in the desired profile name and click OK. A new window that looks like Figure 3-34 on page 255 will be displayed.

Important: The profile name must be unique and should only be used on the source and target machine. Concurrent transfers with the same profile name is not possible.


Figure 3-34 Connection message

5. On the window in Figure 3-34, click OK.

You are now almost finished with everything that you should do on the source machine. It is now time to configure the target machine for the transfer. On the target machine start up IBM System Migration Assistant as described in 3.4.2, “Applying settings and files” on page 232.

1. From the start menu select Apply captured settings and files to this computer as shown in Figure 3-22 on page 233. This will bring you to a window shown in Figure 3-35.

Figure 3-35 Target machine Peer to Peer window


2. On the window in Figure 3-35 check the box next to Peer to Peer file transfer. The Open button will be grayed out. You also have a second check box, Edit Selections, which allows you to edit what items in the supplied information from the source machine that you would like to be processed on the target machine. Select one or two of the check boxes and click Next.

Figure 3-36 Password prompt

3. If, and only if, you entered a transfer password on the source machine, the window in Figure 3-36 will be the next window to appear after you click Next in the previous step. If you did not select to use a password on the source computer, this window will not appear. You will not be able to migrate any data without the correct password. Type in the exact same password as used when you selected the password on the source computer (see step 2 on page 253). Click OK.

4. If, and only if, you selected the check box next to Edit Selections in step 2 on page 256, the Edit Selections window will appear. For more information about how to use this window, refer to Figure 3-23 on page 233.

Figure 3-37 Peer to Peer connection established

5. The next window to appear is the window shown in Figure 3-37. Since it is connecting through a network, it might take some seconds for this window to appear after you have finished your last command. Usually, this connection takes 10-5 seconds to be established. Click OK on this message. If you do not get this confirmation message, go through the following checklist to determine what may be wrong.


– A firewall is blocking the communication. Review your firewall settings on both the source and the target machine. Remember to check the built in firewall in Windows XP if you are using it.

– You have not clicked OK on the message on the source computer shown in Figure 3-34 on page 255 as described in 5 on page 255. Click OK as described in that step.

– Your network is not connected properly between the computers. Check the connectivity between the computers.

– You have taken too much time on the target computer, and a timeout has occurred. You can avoid this by waiting to click the OK button in Figure 3-34 on page 255 (as described in step 5 on page 255) until you are ready to work with the target computer.

6. After you have confirmed the connection between the machines, the source machine will start the upload of the selected information from the source machine to the target machine. The time it takes will vary depending on how much data that is to be transferred. Remember that you can easily select several gigabytes of data on the source machine and it will take a while to transfer all that information.

Figure 3-38 Start processing

7. After the transfer is finished, the message box shown in Figure 3-38 will appear. If you would like to start processing the information (in other words, start changing appearance or data) on the target machine, click Yes. All the selected information would then be placed in the correct location. If you click on No, the information will be stored locally ready for manual processing later on. The .sma file will usually be stored in C:\SMA\TEMP\yourprofilename.sma where yourprofilename is the same as what unique id you gave to the transfer.

The most common way of using Peer to Peer transfer is to start processing immediately by clicking Yes in Figure 3-38. If you click Yes, a new window will appear on both the target and the source machine that looks like Figure 3-39.


Figure 3-39 Summary

8. On the window shown in Figure 3-39, you will get a log and a summary of what has happened during the transfer and processing of the information. This information can also be stored as a file for later reference by clicking the Save as button. Click Finish to exit IBM System Migration Assistant. On the target machine, a new message box that looks like Figure 3-40 will appear.

Figure 3-40 Reboot after processing

9. After processing the information IBM System Migration Assistant has gathered from the source computer, you will need to restart the target machine. This is due to changes in the system that will not appear before you reboot. You therefore have to click Yes in the message box shown in Figure 3-40. After a reboot, the machine should contain the information you sent to it. Check the log/summary if something is missing. Log files are usually stored in C:\ as a .log file.


Chapter 4. Secure Data Disposal

During the retirement phase of the PC life cycle, many companies dispose of their PCs without proper removal of confidential data. This can cause a serious concern as information on the hard disks can be retrieved by unauthorized people. What does this mean? Many companies think that formatting a hard disk will remove and destroy the data on hard disks. They are unaware that confidential data can still be retrieved from these systems.

In most operating systems (Windows XP, Windows 2000, Windows 95, Windows NT, Windows 98, Linux, etc.), files that are deleted are not necessarily erased. In many cases, the only thing erased is the logical link to the file. IBM’s tool for Secure Data Disposal is known as SCRUB3. SCRUB3 is indifferent with respect to the operating system on a hard disk. It will ensure that any critical data is permanently removed from a PC before it is disposed.

Whether a PC is being cascaded in an organization or being retired, IT organizations will benefit from the following:

� Data, programs, and any possible viruses will be destroyed on a PC before a new image is loaded.

� Sensitive and/or confidential information will be destroyed permanently.

This chapter provides information regarding the use of the tool and how some practical applications of it can be implemented.

4


4.1 Secure Data Disposal: the toolIBM’s SCRUB3 utility permanently erases information on a hard disk so it will not be retrievable by anyone else. The utility allows for different levels of security depending on the nature of the data that is on the hard disk.

Various organizations will use this tool in either the retirement phase or when they need to cascade machines within an organization to ensure confidential information is kept secure.

This is a DOS-based utility that can be executed through the RDM 4.11 console or from a DOS command prompt.

4.1.1 Using SCRUB3.EXESCRUB3 offers the ability to erase information at different security levels. Systems which do not have sensitive data can have their disks cleared in very little time. Other situations may deal with sensitive information. In these scenarios, where the information is paramount, high levels of deletion can be selected to ensure that the information will never be restored to undesired viewers.

Command syntaxSCRUB3 [/?] | [[/Q=NO] [/S=NO] { /D=<drive> | /D=ALL } { /L=<level> | /W=<writes> } ]

The following is a list of the various levels of data disposal that can be achieved through the use of the SCRUB3 executable.

Table 4-1 Various levels of data disposal

/Q=NO This parameter causes the program to display a maximal number of messages on STDOUT. It is intended to be used for in-the-field debugging only, and a customer should normally not use this parameter. If present, this parameter should be the first (for example, leftmost) parameter.

/S=NO Upon completion of this procedure, scrub3 will leave a signature on the drive as an indicator of what level of data disposal has completed on the system. This parameter, /S=NO, causes the program not to write the scrub signature to the disk(s) that will be erased.

/D=<drive> Use this form of the /D parameter if you want to erase only one hard drive that is installed on the system computer. The value <drive> is the hard disk drive number of the drive that you want to erase. 1 is the first hard disk drive, 2 is the second hard disk drive, etc. There is no default value for this parameter. The /D parameter is required.


/D=ALL Use this form of the /D parameter if you want to erase all hard disk drives that are installed on the system computer. There is no default value for this parameter. The /D parameter is required.

/L=<level> The value <level> is the security level of the disposal operation. There is no default value for this parameter. Exactly one of the /L parameter or the /W parameter is required. It must have one of the following values (see below).

/L=1 Limited security. The first 63 sectors on the drive (includes Master Boot Record), the last two sectors on the drive, and the first 100 sectors on each partition are overwritten with a 0x0000 pattern (for example, each pair of bytes on the sector is overwritten with this pattern). This operation is very fast. The hard disk drive will not be usable via standard I/O methods. However, this is not a secure operation in an absolute sense, since it leaves most of the partitions on the hard drive unchanged.

/L=2 Medium security. All sectors on the drive are overwritten one time with a 0x0000 pattern (for example, each pair of bytes on the sector is overwritten with this pattern). This operation is relatively slow, since it involves many write operations. Actual speed depends on the size and speed of the target hard disk drives.

/L=3 High security. All sectors on the drive are overwritten four times with the following patterns (in this order): a random pattern, the bit-wise complement of that random pattern, a different random pattern, and a 0x0000 pattern (that is, each pair of bytes on the sector is overwritten with these patterns). This operation is quite slow, and it takes four times as long as a /L=2 operation.

/L=4 DOD-compliant (Department of Defense) security. All sectors on the drive are overwritten 7 times with the following patterns (in this order): a random pattern, the bit-wise complement of that random pattern (three times, each with a different random pattern), and a 0x0000 pattern (for example, each pair of bytes on the sector is overwritten with these patterns). This operation is quite slow, and it takes seven times as long as a /L=2 operation.

/W=<writes> The value <writes> is the number of times each sector is overwritten (done <writes> - 1 times with a random pattern, before a final write with a 0x0000 pattern). <writes> is an integer greater than 1 and less than 100. There is no default value for this parameter. Exactly one of the /L parameter or the /W parameter is required.

/? This parameter causes the program to display a concise description of its execution syntax on STDOUT and then to terminate execution. If you run SCRUB.EXE with no parameters, it will display this same output. /? causes all other parameters to be ignored.

Chapter 4. Secure Data Disposal 261

For all parameters, you can use a leading dash (-) instead of the leading slash (/), and you can use a colon (:) instead of the equal sign (=).

Return codesTable 4-2 Return codes

ExamplesHere are several examples of executable syntaxes.

SCRUB3 /L=1 /D=ALL

Overwrites the Master Boot Record, the first 100 sectors of each partition, and the drive’s last two sectors on every hard disk drive installed on the system computer. The pattern used for the write operation is 0x0000. None of the data on any of the drives can be accessed with standard methods. However, a program that uses low-level BIOS read functions can read most of the data on these drives successfully.

SCRUB3 /Q=NO /D=2 /L=2

Overwrites every sector on hard disk drive number 2 with a pattern of 0x0000. None of the other hard disk drives installed on the system computer is changed. Debug messages are displayed in the command window (for example, on STDOUT), along with all the standard messages that this program produces.

SCRUB3 /D=ALL /L=2

Overwrites every sector of every hard disk drive installed on the system computer with a pattern of 0x0000. None of the data on any of the drives is recoverable. This is the normal way to run SCRUB3.EXE.

SCRUB3 /D=ALL /L=3

Overwrites every byte on every sector of every hard disk drive installed on the system computer four times. None of the data on any of the drives is recoverable. This is not the normal way to run SCRUB3.EXE. It takes an extremely long time to run. However, overwriting four times provides good protection from attempts to recover data with specialized sensitive electronic equipment.

SCRUB3

Upon completion, scrub3.exe will return the following:

Return Code Description

0 The program terminated normally, with no errors.

16 The program terminated with errors.


Writes a syntax description in your command window (for example, on STDOUT).

4.1.2 Performance considerationsThe time required to complete each SCRUB3 task differs. If the level of security needs to be more robust, additional time will be needed to complete the task

This section will quantify the times required to complete each task. In a production environment, use the commands below to test a handful of machines to identify the times required to run the secure data disposal process.

Machines used:

� NetVista M41 (6792-24U) - 1.8 GHz, 40 GB HDD, 256 MB RAM� ThinkPad T40 (2372-75U) - 1.5 GHz, 40 GB HDD, 256 MB RAM

The table below illustrates the time required to complete some of the levels of SCRUB3. Tests were performed on a T40 ThinkPad and M41 NetVista. Performance will vary based on the size/speed of the hard disk and PC.

Table 4-3 SCRUB3.EXE test times, in minutes

To gather the times required to execute SCRUB3.EXE on specific workstations, use the following command lines:

Example 4-1 DOS batch file for capturing execution times.

scrub3 /Q=NO /L=1 /D=ALL >level1.txtscrub3 /Q=NO /L=2 /D=ALL >level2.txtscrub3 /Q=NO /L=3 /D=ALL >level3.txtscrub3 /Q=NO /L=4 /D=ALL >level4.txt

Running this batch file from a DOS boot disk will provide you with four files that can be used to gather the execution times of SCRUB3.EXE.

The time required to complete the task will be captured under “Total program execution time (minutes)”.

M41 T40

Level 1 0.02 0.05

Level 2 19.15 32.77

Level 3 (DoD-compliant) 76.57 130.95

Level 4 (DoD-compliant) 133.98 229.07


Example 4-2 Data file from SCRUB3.EXE output (partial) with progress indicator

IBM Secure Data Disposal Utility v2.0 (RDM v4.11)

Licensed Materials - Property of IBM Successfully overwrote 100 sectors.Total program execution time (minutes): 0.0166667

IBM Secure Data Disposal UtilityReturn code ..... 0Execution Complete.

Writing sectors for Secure Data Disposal0% 50% 100%°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°ÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛ

4.1.3 Practical applicationImplementing secure data disposal is relatively simple. The only criteria that need to be established is how the application will be executed and the level of security. Some examples are as follows.

Table 4-4 User types and applications of SCRUB3

4.1.4 Running Secure Data Disposal through RDMComplete the following instructions to run Secure Data Disposal:

1. Connect the client to the network.

User Type Data Sensitivity

Description

Call Center Employee

LOW This user only checks the status on inventory for customers. The information is non-confidential and is only accessed through a Web interface. Since there is no risk of data exposure, this machine can be erased using the following command:

SCRUB3 /L=1 /D=ALL

HR Employee HIGH This user handles sensitive employee data on a regular basis. This information has been deemed confidential and needs to be erased when the PC is retired. The following command would be used for this example:

SCRUB3 /D=ALL /L=2Level 2 is the “normal” way to use SCRUB3.EXELevel 3 or Level 4 execution can be used if DoD-compliancy is required.


2. Start the client and select F12 to boot to network.

3. Upon completion, the system will appear in the director console.

4. Drag and drop the client to the selected secure data disposal level. Refer to Figure 4-1.

5. Select Run Systems... .

6. The client will start; complete the task you have selected, and power off.

Figure 4-1 Running SCRUB3 on a workstation using RDM



Chapter 5. IBM Access Connections

This chapter describes the installation and implementation of the IBM Access Connections tool.

In this chapter, the following topics are discussed:

� “Overview” on page 268

� “Prerequisites” on page 270

� “Creating IBM Access Connections profiles” on page 275

� “Customization and advanced features” on page 298

� “Enabler for Administrator Profile Deployment Feature” on page 320

5


5.1 OverviewIBM Access Connections is a connectivity assistant program for your IBM ThinkPad® computer that allows you to create and manage location profiles. Each location profile stores all of the network and Internet configuration settings that are needed to connect to a network infrastructure from a specific location such as home or work. By switching between location profiles as you move your computer from place to place, you can quickly and easily connect to a network without having to manually reconfigure your settings and restarting your computer each time. The location profile also allows users to specify different default printers, default home pages for Internet Explorer and security settings for specific locations and to start different applications automatically in different locations.

The network connection can be made using a modem, a wired network adapter (Ethernet or Token Ring), a broadband device (Digital Subscriber Line (DSL), cable modem, or Integrated Services Digital Network (ISDN), satellite connection devices, and wireless network adapter. Virtual Private Networking (VPN) connections are also supported.

By switching between location profiles, as users move their computers from place to place, they can quickly and easily connect to a network without having to manually reconfigure settings or restart the computer each time. IBM Access Connections also allows the user to view and connect to Bluetooth devices and to set Bluetooth security options. It enables the quick switching of network settings and Internet settings by selecting a location profile.

Summary of changes for Version 3.30� Supported for Windows XP service pack2.� Support for LEAP-TKIP wireless authentication for the following wireless

adapters.– IBM Dual-Band Wi-Fi Wireless Mini-PCI Adapter– IBM 11a/b/g Wireless LAN Mini PCI Adapter– IBM 11b/g Wireless LAN Mini PCI Adapter– Intel(R) PRO/Wireless 2200BG Network Connection

� Support for AES on the following wireless adapter.– Intel(R) PRO/Wireless 2200BG Network Connection

� Support for WPA/TKIP on the following wireless adapter.– Cisco Systems Mini-PCI Wireless LAN Adapter.

Summary of changes for Version 3.20� Support for Access Connections Windows Logon feature (Single Sign On) in

the following profiles.– LEAP profile


– PEAP profile� Support for Boot time connect feature in the following profiles.

– No WEP profile– Static WEP profile– WPA-PSK profile

� Support for EAP-TTLS and PEAP-GTC wireless authentication for the following wireless adapters.– IBM Dual-Band Wi-Fi Wireless Mini-PCI Adapter or IBM 11a/b/g Wireless

LAN Mini PCI Adapter– IBM 11b/g Wireless LAN Mini PCI Adapter– Intel(R) PRO/Wireless LAN 2100 3B Mini PCI Adapter– Intel(R) PRO/Wireless 2200BG Network Connection

� Support for Automatic Ethernet Profile switching in limited user privileges mode.

Summary of changes for Version 3.10� Support for installing another language of Access Connections from

Operating System language.

Summary of changes for Version 3.00� Added network diagnostics and auto error recovery feature.� Support location profile switching using Fn+F5 Hotkey and on screen display.� Support for WINS setting.� Support for PEAP(MS-CHAP-V2) on IBM Dual-Band Wi-Fi Wireless Mini-PCI

Adapter, IBM 11a/b/g Wireless LAN Mini PCI Adapter and Intel (R) PRO/Wireless LAN 2100 3B Mini PCI Adapter.

� Support for CKIP on Intel (R) PRO/Wireless LAN 2100 3B Mini PCI Adapter.� Support for AES on IBM Dual-Band Wi-Fi Wireless Mini-PCI Adapter and IBM

11a/b/g Wireless LAN Mini PCI Adapter.� Support for Automatic wireless network switching before windows logon for

profiles using static WEP configuration and LEAP for Cisco card.� Enhance Automatic Ethernet network switching by saving multiple sets of

Ethernet port information.� Support for Vodafone Mobile Connect WAN card and Sony Ericsson GC82

WAN card.� Enhanced profile deployment to export 802.1x profile (Win XP).� Enhanced profile deployment in user mode to import profiles silently.� Support for quick setup of new location profiles.� Support for IBM Mobility Client software.� Support for creating a disconnect icon on the desktop.� Support for excluding IE homepage changes when a profile is switched.� Support for deleting the active location profile.� Add an option to not save the new location profile after connecting using Find

Wireless Network.

Chapter 5. IBM Access Connections 269

� Support for the multi-language package.

5.2 PrerequisitesBefore installing IBM Access Connections, you must consider where it will be installed and what network profiles you will want to create. The following is a list of system considerations and limitations that must be considered before installing IBM Access Connections.

� Operating systems supported:

– Microsoft’s Windows 2000– Microsoft’s Windows XP

� Language-independent: can be used with any language system

� Requires 12.48 MB of hard disk drive space

� Supported on the following ThinkPad systems:

– A20m, A20p, A21e, A21m, A21p, A22e, A22m, A22p, A30, A30p, A31, A31p

– G40– R30, R31, R32, R40, R40e, R50, R50p, R51– S31– T20, T21, T22, T23, T30, T40, T40p, T41, T41p, T42, T42P– X20, X21, X22, X23, X24, X30, X31, X40

NOTE: This program is language independent and can be used with any language system. IBM Access Connections Version 3 is supported only IBM systems. Future releases will provide limited compatibility with non-IBM hardware via a generic NDIS interface.

5.2.1 Hardware and security cross-referenceTable 5-1 provides a cross-reference between supported hardware and security settings.

Table 5-1 IBM Access Connections V3.10 dependent driver versions

Systems with Wireless Adapters

Required Driver Version or higher

Supported Wireless Configurations

Static WEP 802.1x EAP and PEAP (MS) Cisco LEAP WPA WPA-PSK

Mini PCI cards:

Intel(R) PRO/Wireless LAN 2100 3B Mini PCI Adapter Driver: 1.2.3.14

Yes Yes Yes YesNote 1

YesNote 1


Notes for Table 5-1:� Note 1: If configuring these settings “using IBM Access Connections...” in the

wireless settings page, there is no need for installing Windows WPA Hotfix. But if you are “using Windows...” option in the wireless settings page, then install Q826942 or latest hotfix (WPA Supplicant update rollup package in Windows XP).

� Note 2: For systems running Microsoft Windows XP, if you use 802.1x authentication with EAP-TLS but do not use WPA-TKIP configuration, IBM recommends you uninstall Windows XP Hotfix Q826942 (WPA Supplicant update rollup package in Windows XP) or Q815485 (WPA Wireless Security Update in Windows XP).

To check if the Q826942 or Q815485 is installed and to uninstall it:

1. Start Windows XP and logon with administrative privileges.

2. Click Start, then click Control Panel.

3. Click Add or Remove Programs.

4. Click Windows XP Hotfix (SP2) Q826942 or Windows XP Hotfix (SP2) Q815485 if it is listed under Currently installed programs.

Intel(R) PRO/Wireless LAN 2200BG Mini PCI Adapter Driver: 8.1.0.25 Yes Yes Yes Yes

Note 1Yes

Note 1

IBM Dual-Band,11b/g, and 11a/b/g Wireless Mini-PCI Adapter

Driver: 3.1.102.23Yes Yes Yes Yes

Note 1Yes

Note 1

Cisco Systems Mini PCI Wireless LAN Adapter

Driver: 3.8.26Firmware: 5.417Aironet Client utility: 6.03.011

Yes Yes YesNote 4

No No

IBM High Rate Wireless LAN Mini PCI Adapter III

Driver: 2.00.09.2228

Yes YesNote 2

No No No

IBM High Rate Wireless LAN Mini PCI combo card

Driver: 3.04.205/c20

Yes YesNote 2

No No No

PC Cards:

11A/B/G Wireless LAN CardBus Adapter

Driver: 3.1.1.54Note 6

Yes Yes YesNote 3

YesNote 1

YesNote 1

Cisco Aironet 340 Series PC card and Cisco Aironet 350 Series PC card

Driver: 8.2.4Firmware: 4.25.23Note 5

Yes YesNote 2

YesNote 4

No No

802.11A Wireless LAN CardBus Adapter Driver: 2.0 Yes Yes

Note 2No No No

Systems with Wireless Adapters

Required Driver Version or higher

Supported Wireless Configurations

Static WEP 802.1x EAP and PEAP (MS) Cisco LEAP WPA WPA-PSK


5. Click Remove and follow the instructions in the window.

NOTE: The above action will remove all the fixes within the update rollup package, Q826942. You may need to reinstall the other specific hotfixes you expect for this rollup package.

For systems running Microsoft Windows 2000, if you would like to use 802.1x authentication with EAP-TLS, stop the Microsoft Wireless Configuration service if already installed. To check if the service is installed and to stop it:

1. Start Windows 2000 and logon with administrative privileges.

2. Click Start, point to Settings, then click Control Panel.

3. Double-click Administrative Tools then Services.

4. Double-click Wireless Configuration if it is listed.

5. Change Startup type to Disabled if it is not.

6. Click OK.

� NOTE 3: Cisco compatible cards does not currently support LEAP with windows user name and password or temporary user name and password options for LEAP configuration.

� NOTE 4: To use LEAP, reinstall the Cisco Aironet Client Utility v5.02 or later with the LEAP authentication feature selected. Run SETUP.EXE to install the Utility and choose the “LEAP” option at the Select Options menu of the installer. The Cisco Aironet Client Utility is contained in an additional package, “Wireless LAN Software for Cisco Wireless LAN Mini PCI Card for Windows 98/Me/NT 4.0/2000/XP for ThinkPad”.

If IBM Client Security Software (CSS) is installed and “to manage pass phrase using User Verification Manager for logon authentication” is enabled, reinstall the Utility (Cisco Aironet Client Utility) again after the IBM Client Security Software is installed.

� NOTE 5: IBM recommends to contact Cisco Systems, Inc. to get the latest device driver.

� NOTE 6: Driver version 3.1.1.54 is required with Access Connections 3.21. Before installing the IBM 11a/b/g Wireless CardBus Adapter driver, IBM Access Connections needs to be uninstalled. Install Access Connections after drivers are installed.

If you are using the device driver version 2.4.1.21 on Windows XP, there is the following limitation: When a LEAP profile is connected, you cannot create an 802.11x EAP-TLS profile. If you would like to use both EAP-TLS and LEAP profiles, please create an EAP-TLS profile first, and then create a LEAP profile. Then, you can use both profiles.


NOTE: The IBM 11a/b/g Wireless CardBus Adapter cannot be used on IBM ThinkPad systems equipped with an internal Intel(R) PRO/Wireless LAN 2100 3B Mini PCI Adapter at the same time.

5.3 InstallationThe following section details the extraction and installation of IBM Access Connections. There are two types of installation. The first type is “Automated Installation” on page 274 and the second is the “Manual installation” on page 274. The automated process is used by companies that need to install IBM Access Connections on a large number of systems or that wish to insure that Access Connections is installed in a customized directory. Both types of deployment allow for the use of predefined profiles made with IBM Access Connections’ administration tool.

5.3.1 Extraction of source filesBefore any installation can take place, the IBM Access Connections setup files must be downloaded and extracted to a temporary file.

1. To begin the installation process, download the compressed self-extracting executable file named acconwin.exe from the following URL:

http://www.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4ZLNJB

2. Run the self-extracting executable file named acconwin.exe to extract installation files.

3. Accept the terms of the license agreement; then click Next to proceed.

4. Select a temporary location to extract the installation files; then click Next.

Click Finish to complete the extraction of the installation files. Note where the files were extracted.

Proceed with either “Automated Installation” on page 274 or “Manual installation” on page 274.

Note: If IBM Access Connections is already on the system, it must be removed before proceeding with the installation process detailed below. Please see Section 5.7, “Troubleshooting” on page 332 for details on removing IBM Access Connections.



5.3.2 Automated InstallationThe automated installation provides a means of installing IBM Access Connections without any user intervention.

Note: For more information on automating the installation of this application, refer to the chapter on IBM Software Delivery Center in Using ThinkVantage Technologies Volume 2: Maintaining and Recovering Client Systems, SG24-6060-03.

Execute the following steps to complete the automated installation process:

1. Start Windows 2000/XP; log on with administrative privileges.

2. If customized predefined profiles are to be used, copy the two files to the same directory that IBM Access Connections was extracted to.

3. Extract the IBM Access Connections drivers to the hard disk drive.

4. Click Start, then click Run.

5. Type the following:

\\directory that IBM Access Connections was extracted to\start /WAIT setup.exe -s -SMS -f2%temp%\setup.log

6. Click OK.

If an automated installation package is used to install IBM Access Connections, skip to 5.4, “Creating IBM Access Connections profiles” on page 275.

5.3.3 Manual installationThe manual installation of IBM Access Connections is useful to users who want to control the installation directory or need to understand the installation settings to develop an automated process. After the installation files have been extracted, the installation can begin.

1. Run the Setup.exe file from the location where the files have been extracted.

2. When the welcome window opens, click Next to continue the installation.

3. Choose an installation location; then click Next to continue.

4. Select the program folder then click Next.

5. Insure the installation information is correct; click Next to continue.

Tip: There will be no indication that the installation has finished. The system will not restart automatically. The system needs to be restarted before IBM Access Connections is first used.


6. If prompted to restart, select Yes, I want to restart my computer now. Click Finish. The computer must be restarted before the application can be used.

5.4 Creating IBM Access Connections profilesIn this section, we will configure IBM Access Connections for a wireless network profile. The example that follows depicts a typical use of IBM Access Connections. In this example, the user has a workgroup connection, perhaps used for a home network, and an IBM LAN/WAN connection, for use at work. In the section that follows, we will show how the wireless LAN profile is set up and then how to switch between this profile and other profiles on the system.

5.4.1 Creation of a location profile using detailed setupComplete the following instructions to set up the wireless LAN connection with VPN support using the detailed setup routine:

1. Start IBM Access Connections from the Windows Start menu:

For Windows 2000:

– Start →Programs →Access IBM →IBM Access Connections

For Windows XP:

– Start →All Programs →Access IBM →IBM Access Connections.

Figure 5-1 on page 276 will be displayed.


Figure 5-1 Welcome to IBM Access Connections!

2. Click Next on the Figure 5-1 on page 276 window. Figure 5-2 on page 277 will be displayed.


.

Figure 5-2 Choose Your Connection Type

3. Name the location profile and choose the connection type; for our example we will use the following:

– Name of location: Home - Wireless network– Type of Network Connection: Wireless LAN (802.11)– Optional Settings: Select check box “Virtual Private Network (VPN)

connection.– Insure that “Quick Setup” is not selected

4. Click Next. The Figure 5-3 on page 278 will be displayed.

Tip: As demonstrated in 5.4.2, “Quick setup for location profile creation” on page 292, the Quick Setup will reduce the number of steps from ten down to three.


Figure 5-3 Choose Your Wireless Adapter

5. If you wish to choose a network adapter that is not listed, click the Show All Network Adapters button. After the correct adapter is selected, click Next. You will see a window similar Figure 5-5 on page 280.


Figure 5-4 Edit Your TCP/IP Settings.

6. At this point you can manually set the IP address information or select Obtain an IP address automatically and Obtain DNS server address automatically. Click Next. The window as show in Figure 5-5 on page 280 will be displayed.


Figure 5-5 Edit Your Advanced DNS Settings

7. Select Use the current Advanced DNS settings. If no DNS suffix settings are available, look up the local DNS suffix settings in the TCP/IP properties or contact an appropriate support group for assistance. Click Next.


Figure 5-6 Edit Your Wireless Network Settings

8. Make the changes to the wireless network settings as required.

An SSID (Service Set Identification) of ANY says that IBM Access Connections will try to connect to any available WLAN that is broadcasting its SSID.

Click Next to continue to the window shown in Figure 5-7 on page 282.

Note: For more information concerning the wireless network settings, refer to the section in the help file labeled Edit your wireless settings. The help file can be accessed by clicking the Help button.


9. The Edit Your Internet Explorer Proxy Settings page is used to set the home page and proxy settings for each location profile.

Figure 5-7 Edit Your Internet Explorer Proxy Settings

10.To configure a proxy server, select the I want to use the following Internet Explorer proxy settings with this location profile button. Then select This location requires a proxy server, and click Proxy settings... The following window will be displayed.


Figure 5-8 Proxy settings

11.Following is an example of a proxy setup:

a. Enter the proxy IP address in the field Proxy address to use.

b. Enter the port number. For this example we used 8080 but, it can be whatever port the proxy server requires.

c. In this example we have checked the box Use the same proxy server for all protocols but, if the addresses are different for different protocols then these proxy addresses can be different.

d. Mark the check box Bypass proxy server for local addresses this setting will allow all address requests that are for the local network to bypass the proxy server.

12.Click OK then click Next to proceed to the Edit Your Security Settings window shown in Figure 5-9 on page 284.


Figure 5-9 Edit Your Security Settings window

13.In this window you can select whether or not the this location profile will support internet connection sharing, Windows firewall settings and file sharing. Click Next in Figure 5-9 to continue.

Important: It is recommended to disable file and printer sharing and internet connection sharing to enhance the security of the system If your system is running a software firewall or if it is connected to the internet through a hardware firewall device, then the firewall option in Figure 5-9 should be left unchecked. If no other firewall is protecting the system then it is recommended that this option be checked to enable the Windows XP firewall.


14.If printers are installed, the following window as shown in Figure 5-10 will be displayed.

Figure 5-10 Printer Setup

15.Choose a default printer for each profile.

Attention: The window shown in Figure 5-10 will only be displayed if there is at least one printer installed. Otherwise Figure 5-11 on page 286 will be displayed.


16.The window shown in Figure 5-11 provides a means to have programs automatically started when different location profiles are selected.

Figure 5-11 Program Setup

17.If you want to have a program to start automatically, click Add Program. In the example that follows in Figure 5-12 on page 287, a Web browser will start when the wireless connection is selected.


Figure 5-12 Choose Program

18.Select the executable file that you wish to run, then click Open. The newly selected program will be displayed in the window similar to Figure 5-13 on page 288.

19.Additional applications can now be added.

Tip: Do not select a program that is already opened at Windows system startup. This will cause errors as Windows tries to run two copies of the same program.


.

Figure 5-13 Program setup - done

20.Clicking the Special Settings button will start programs before a connection is enabled. This would be useful for starting a firewall program before an Internet connected profile is enabled. Figure 5-14 shows where you would add such a program.


.

Figure 5-14 Special Settings window

21.Click OK in Figure 5-14 to continue.

Note: the window shown in Figure 5-14 is used to start programs before the connection changes or to change settings before the connection profile changes.


22.The window in Figure 5-15 will be shown since we selected VPN in Figure 5-2 on page 277.

Figure 5-15 Edit Your VPN Settings

23.In this window, configure the VPN software the is required for this connection. Select Next when finished. The window shown in Figure 5-16 on page 291 will be displayed.


Figure 5-16 Save Your Location Profile

24.Click save in Figure 5-16 to save the information. The pop-up window shown in Figure 5-17 will be displayed.

Figure 5-17 apply profile pop-up

25.Click Yes to switch to the new profile immediately or click No to save it only without changing your current connection to the newly created one.


If you clicked Yes to apply the newly created location profile a status pop-up windows similar to Figure 5-18 will be displayed.

Figure 5-18 Connection status box

26.Applying new settings status. Click Close to remove the status box when finished.

5.4.2 Quick setup for location profile creationTo simplify the process of creating location profiles, IBM Access Connections provides the Quick Setup option in the Choose Your Connection Type window (refer to Figure 5-2 on page 277). This option captures the current connection information and imports it into the newly created IBM Access Connections location profile. This feature reduces the number of steps from ten to three for creating a new location profile.

1. To begin, connect to the network that you wish to use in IBM Access Connections.

2. Then open IBM Access Connections. A window similar to Figure 5-19 on page 293 will be displayed.


Figure 5-19 Main interface window Connection Status

3. Click Manage Location Profiles... to continue. The Manage Location Profile window shown in Figure 5-20 on page 294 will be displayed.


Figure 5-20 Manage Location Profile window

4. Select New... in Figure 5-20 to continue. The Figure 5-21 will be displayed.


Figure 5-21 Choose Your Connection Type - Quick Setup

5. Name the location profile and choose the connection type; for our example we will use the following:

– Name of location: Work - Wired– Type of Network Connection: Wired LAN (Ethernet)– Optional Settings: Do not select check box “Virtual Private Network (VPN)

connection.– Select “Quick Setup”

6. Click Next. The Figure 5-3 on page 278 will be displayed.


Figure 5-22 Choose Your Network Adapter

7. The Disconnect From the network when I switch to a different profile option will disconnect the current network when you switch to a new one. Click Next to go to the next window displayed in Figure 5-23 on page 297.


Figure 5-23 Save Your Location Profile - Work Wired LAN

8. After reviewing the profile details in Figure 5-23. Click Save to save this information into a location profile.

9. Click Yes to switch to the new profile immediately or click No to save it only without changing your current connection to the newly created one.

10.If you clicked Yes to apply the newly created location profile, a status pop-up windows similar to Figure 5-17 on page 291. When finished, the Location Profile list will look similar to Figure 5-24 on page 298.


Figure 5-24 Manage Location Profiles - three profiles

11.From the options shown in Figure 5-24 you can edit, delete, copy and make new location profiles using either the standard setup or the quick setup routine.

5.5 Customization and advanced featuresThe following section will show how to further customize IBM Access Connections. This information will be used after the profiles are created on the system. The following items will be covered in this section.

� 5.5.1, “IBM Access Connections Connection Status window” on page 299� 5.5.2, “Location switching” on page 301� 5.5.3, “Global Settings...” on page 304� “Status messages provided by the tray icon” on page 314� “Switching between profiles” on page 315


� “Fn+F5 key display” on page 317

5.5.1 IBM Access Connections Connection Status window

Figure 5-25 Connection Status

The window shown in Figure 5-25 is the main interface for IBM Access Connections.

Top toolbar menuThe following tasks can be started from the toolbar at the top of the main interface window.

� Network

– Diagnostics - used to troubleshoot network issues.– Exit Access Connections - exits the program.

� Location Profiles


– Create New Profile... - launches the location profile creation wizard.– Disconnect Current Profile... - disconnects the system from the current

location profile.– Manage Profiles... - opens the mange profile interface window. More

details are given on this in section “Managing Location Profiles” on page 306.

– Export Profiles... - creates a location profile .loc file containing the profiles that are currently configured on the system.

� Wireless Network

– Enable Wireless Radio - turns on the wireless radio that is configured for the current location profile.

– Find Wireless Networks... - scans for available wireless networks. More information is given on this in 5.6, “Enabler for Administrator Profile Deployment Feature” on page 320.

– Disable All Wireless Radios - turns off all wireless radios on this system.

� Location Switching

– Switch Ethernet and Wireless Location Profiles Automatically - opens the Location Switching configuration window. This feature is discussed in greater detail in the section titled 5.5.2, “Location switching” on page 301

� Bluetooth

– Enable Bluetooth Radio - enables the systems bluetooth radio.– Launch Bluetooth Places... - Opens the Windows Explorer folder that

contains the Bluetooth Places folder.– Bluetooth Security - Opens the Bluetooth Security.– Bluetooth Security help - Opens the IBM Access Connections help to the

Bluetooth security section.

� Options

– Global Settings... these settings are detailed in the section titled 5.5.3, “Global Settings...” on page 304.

– Preferences - permits you to customize sound and animations.

� Help

– Help - Opens the IBM Access Connections Help file as shown in Figure 5-7 on page 282.

– About - displays the IBM Access Connections version information.

Bottom tool buttons� Manage Location Profiles... Provides a windows to edit, delete, copy and

create new location profiles.

� Find Wireless Network... Provides a wizard to locate new wireless networks.


� Close Closes the Connection Status window but, leave IBM Access Connections running.

� Help Launches the IBM Access Connections help system.

5.5.2 Location switchingLocation switching allows IBM Access Connections to automatically switch between different Ethernet and / or wireless network adapters.

To configure Location switching:

1. From the IBM Access Connections Connection Status window click Location Switching on the top menu bar shown in Figure 5-26.

Figure 5-26 Connection Status - Location Switching

2. Click Switch Ethernet and Wireless Location Profiles Automatically to open the location switching window shown in Figure 5-27 on page 302.


Figure 5-27 Wireless location switching

3. The window shown in Figure 5-27 allows you to configure wireless switching.

The priority list allows you to define which wireless location profile will be made active when your computer is in range of multiple wireless networks or when more than one location profile uses the same wireless network name.

4. From this window you can select the Ethernet tab to configure switching of the wired profiles. This window is shown in Figure 5-28 on page 303.


Figure 5-28 Ethernet location switching

5. From Figure 5-28 you can set how IBM Access Connections switches between wired Ethernet locations.

Select between two different options:

– Automatically use the adapter with the fastest available network connection

– Automatically use the adapter with the highest defined priority level

6. By clicking the Ethernet Location Switching Details... button, a window similar to the on shown in Figure 5-29 on page 304 will be displayed.


Figure 5-29 Details for Ethernet Location switching

This list is populated by the comment pop-up dialog window similar to the one shown in Figure 5-30

Figure 5-30 location profile connections comment popup window

The comment window in Figure 5-30 allows you to add comments to each connection profile. These comments will be added to the list in shown in Figure 5-29 on page 304.

5.5.3 Global Settings...The Global Settings tab allows you to configure settings that apply to all users of the computer. To go to the Global Settings tab, click Options on the top menu bar


in the IBM Access Connections Connection Status window shown in Figure 5-26 on page 301. Then click Global Settings...

Figure 5-31 Options - Global Settings

� Allow all users of this system to switch to any existing location <default> unchecked: If this option is checked, all users on the system will be able to switch location profiles

� Show wireless status icon in task tray <default> checked: Removing the check from the box will remove the wireless status icon from the Windows task tray.

� Display the progress indicator window when a profile is being applied <default> checked: The status progress windows will not be shown if this box is unchecked.


� Allow selection of location profiles with Fn+F5 On Screen Display menu <default> checked: Removing the check from the box will disable the ability to change locations in the Fn+F5 on-screen display.

� Disable the Bluetooth radio when a location profile that users a wireless LAN adapter is applied <default> unchecked: Checking the box disables the Bluetooth radio when a location profile is selected that uses a wireless adapter.

5.5.4 Managing Location ProfilesFrom the main Connection Status window shown in Figure 5-32 select Manage Location Profiles... to work with existing location profiles.

Figure 5-32 Main connection status window

1. After selecting Manage Location Profiles..., a window similar to Figure 5-33 on page 307 will be displayed.


Figure 5-33 Manage Location Profiles

2. You may click Delete to remove a profile, Copy to duplicate a profile, Edit to modify a profile and New to make a new profile. Click Close to exit.

3. The edit feature can also be accessed by clicking on the images shown as part of the network picture in the Connection Status window as shown in Figure 5-34 on page 308.


Figure 5-34 Connection Status window with mouse-over pop-up

The window shown in Figure 5-35 on page 309 will be displayed when you click on the network interface card in the picture shown in Figure 5-34.


Figure 5-35 Modify profile - adapter tab

From this window, you can modify the network card or select a different tab to work with another part of the current location profile.

5.5.5 Wireless network considerationsIBM Access Connections can support a wide range of both wired and wireless network configurations. Before setting up a wireless connection in IBM Access Connections, you need to disable Window’s control over wireless Devices. Complete the following steps:


1. Start →Connect To →Wireless Network Connection. A window similar to Figure 5-36 will be displayed.

Figure 5-36 Window’s Wireless Network Connection

2. In Figure 5-36, click the Advanced... button. A window similar to Figure 5-37 on page 311 will be displayed.


Figure 5-37 Wireless Network Connection Properties

3. Insure that the selection box labeled Use Windows to configure my wireless network settings is not checked. If it is checked, uncheck it. Then click OK to apply this setting.

4. The system is now ready to use IBM Access Connections to manage all wireless network connections.

Find Wireless NetworkThe Find Wireless Network button is a button that is accessible from many windows in IBM Access Connections. This function is used to find all available wireless networks that are in a reachable distance from your computer. By clicking this button, a new window will pop up that allows you to see the available wireless networks. That window will look similar to Figure 5-38 on page 312, but it will contain the wireless networks that are within reach from your machine.


Figure 5-38 Find Wireless Network

If your network list is empty, or you are missing some networks that should be within reach, try to click the Re-Scan button. After some seconds your list should be refreshed.

This menu will contain all WLANs, including the ones that you already have a profile for. If you select a wireless network that already has a profile, it will try to use the existing profile and not make a new one.

This menu contains some different facts about the different reachable networks:

� Network Name

This is the SSID (Service Set Identification) of the WLAN your are connecting to. If you try to connect to an access point that has its SSID broadcast disabled, you will need to set up the profile manually. If you have a profile for the WLAN from before (even though the SSID broadcast is disabled) it will use the existing profile.

An SSID is a 32-character unique identifier attached to the header of packets sent over a WLAN that acts as a password when a mobile device tries to connect to the wireless access point. The SSID differentiates one WLAN from another, so all access points and all devices attempting to connect to a specific WLAN must use the same SSID. A device will not be permitted to join the WLAN unless it can provide the unique SSID.


An SSID is also referred to as a network name because essentially it is a name that identifies a wireless network.

� Wireless Mode

This field describes what wireless mode that access point is running at. Available speeds are 802.11b, 802.11a and 802.11g.

� MAC Address

This field tells you the MAC address of the wireless access point. If you are in doubt of what access point it really is you can compare this MAC address with the actual address of the access point.

� Encryption

This field tells you if some type of encryption is enabled on the access point. If it is enabled you will have to make the profile manually and add the required authentication to that profile. If you try to connect to a WLAN with encryption enabled and there is no existing profile for it you will get a message that looks like Figure 5-39 on page 313

Figure 5-39 WLAN encryption error

If you would like to connect to a network without any encryption, these are the steps on how to do it:

1. Find your desired network in the list (see Figure 5-38 on page 312)

2. Check the round check box next to the network name. The Connect button should now be available, and not grayed out.

3. Click the Connect button. If there is a profile for that WLAN from before in IBM Access Connections it will use your existing profile. If you do not have any profile for it, you will get the message shown in Figure 5-40.

Figure 5-40 Save profile


4. If you want to save this profile click Yes. The profile will be stored by IBM Access Connections until you delete it. If you click No, the profile will only be stored until the next time you log off/on again. It will be visible in your Manage Location Profiles window (see Figure 5-33 on page 307) until you do so. This is quite nice if you connect to a public hotspot or similar kind of WLAN. If you click Yes on all these hotspots, your profile list will become quite large after a while.

If you require more help than stated in this text, you can always click the Help button to get more information.

5.5.6 Access Connections Help and tray iconsThe IBM Access Connections help utility can be accessed from most of the interface windows. This launches a separate window similar to the on shown in Figure 5-41.

Figure 5-41 IBM Access Connections Help

Status messages provided by the tray iconThe tray icon provides a menu that allows for switching between profiles, accessing the manage location profile window and status feedback concerning the currently selected profile connection.

The tray icon is located next to the clock in the taskbar on the Windows desktop.


Figure 5-42 Tray icon

Figure 5-43 shows the mouse-over status popup window for wireless LAN connections. This popup is displayed when the cursor is held over the Access Connection tray icon.

Figure 5-43 Mouse-over status window

The wireless LAN icon menu is shown in Figure 5-44. This menu can be accessed by clicking on the wireless status tray icon shown in Figure 5-45.

Figure 5-44 Wireless LAN icon menu

The wireless status tray icon indicates the status of the wireless LAN connection.

Figure 5-45 wireless status tray icon

Switching between profilesThe icon menu or the manage location profile window may be used to connect, switch, or disconnect from the configured profiles.

To access the icon menu, click the tray icon shown in Figure 5-42. This will display the tray icon menu shown below. The tray icon menu can be used to connect to a different network connection. Right-clicking on the Access Connections tray icon provides the exit option.


Figure 5-46 Icon menu

The tray icon menu can be used to connect and disconnect a network connection.

The application interface can be accessed using the icon or the start menu by selecting Launch IBM Access Connections.

Figure 5-47 Connection Status - operational


The application interface can be used to connect, disconnect or switch profiles.

From the window shown in Figure 5-47 on page 316 and Figure 5-48 you can work with currently active profiles and ones that are not connected.

Figure 5-48 Connection Status - Disconnected

5.5.7 Fn+F5 key displayOn all new ThinkPads, there is a preloaded function that allows you to turn on/off the different antennas in you ThinkPad. With the release of Access Connections V3.0 this utility has been upgraded to support switching between the different profiles you have configured in Access Connections. By using this feature you will have an easier way to access your profiles than through the normal procedures.

The prerequisites for this function is the same as for IBM Access Connections.


If all the required software is installed on your ThinkPad, you can start this program by holding down the Fn key and the F5 key at the same time. Some seconds after pushing these keys you will get a window that looks similar to Figure 5-49.

Figure 5-49 Wireless Radio

There are two main tabs. Which tab you start up on depends on what tab you where on the last time you closed the application. You might therefore start at the tab similar to Figure 5-50.

Note: The FN+F5 feature requires you to have the hotkey features installed on you ThinkPad. Hotkey features must be at version 1.03.0391 or newer. If you do not have the hotkey features installed you can find them under your machines download page at




Figure 5-50 Location Profile

You can easily switch between these to tabs by just clicking on the Location Profiles or the Wireless Radio, or by pushing the key highlighted on the menu item (L for Location Profile and W for Wireless Radio).

The menu that is most important to Access Connections is the tab named Location Profile (Figure 5-50). On this tab you can see the different location profiles that you have created in Access Connections. Select your desired profile by clicking on it. A green square will appear on the profile that is currently in use. It will also be mentioned on the top of the different profiles.

The Fn+F5 function provides a limited number of options. It is designed to be a simple way to select profiles and to control the different wireless antennas on your ThinkPad. These are the options that are available on the Location Profile tab (Figure 5-50):

� Find Wireless Network

By selecting this button you will get a new window similar to Figure 5-38 on page 312 that allows you to see all the wireless networks that are in a reachable distance away from your computer.

� Fn+F5 Settings

Clicking this button will bring up a windows similar to Figure 5-51 on page 320. This menu will allow you to remove the possibility to select IBM Access Connections profiles, and you can change the way the on/off function of the radios works. If you remove the possibility to change profiles in the


Fn+F5 program you will only be able to access the Wireless Radio menu. The Location Profile menu will not be shown

Figure 5-51 Fn+F5 Settings

� Close

This will close the Fn+F5 program

These are the menu options that are available on the Wireless Radio menu (Figure 5-49 on page 318):

� 802.11 Wireless Radio

If you have a 802.11 Wireless Radio built into your machine this option will show up. Press the button to the right of the text to turn it on or off.

� Bluetooth Radio

If you have a Bluetooth Radio built into your computer this option will show up. Press the button to the right of the text to turn it on or off.

� All Off

This option turns off all the built in radios in your machine.

5.6 Enabler for Administrator Profile Deployment Feature

If you would like to silently install the program and/or the profiles, you will need to use an administrator function in IBM Access Connections. To be able to use this


feature, you must download additional software from IBM. Once this feature is installed, you will get a new menu item in your IBM Access Connections main window. From this menu you are able to generate installation packages for the desired profiles. These packages can easily be integrated into a new installation or they can be rolled out to update the existing profiles on the desired clients.

This feature must be installed after IBM Access Connections is installed and IBM Access Connections must be in a working state.

The IBM Access Connections: Enabler for Administrator Profile Deployment Feature can be downloaded from the following Web site:

http://www.ibm.com/pc/support/site.wss/document.do?lndocid=ACON-DEPLOY

Click the link on the bottom that says Click here for the Administrator Profile Deployment Feature registration and download site.You will be asked for a username and a password. If you do not have username or password, you are able to register for one at the site. This registration is free. The same link also contains some additional information on how to perform the profile distribution.

When you have downloaded the IBM Access Connections: Enabler for Administrator Profile Deployment Feature you must execute the file to install the software. This is the procedure to install the IBM Access Connections: Enabler for Administrator Profile Deployment Feature:

1. In the first menu you will get a quick description of what the program is for. Read the text and click Next.

2. Read through the license agreement carefully. If you accept the terms in it, click I accept the terms in the license agreement and click Next.

3. On the next page you will have the possibility to change the location of where you would like to install the file. This location has to reflect the actual location of where you have installed IBM Access Connections. The default location is C:\Program Files\ThinkPad\ConnectUtilities. As soon as you have the correct location click Next.

4. The next page will tell you that the installation is finished. Close that window by clicking Finish.

Perform the following steps to start the IBM Access Connections: Enabler for Administrator Profile Deployment Feature.

Click Start →Run, and enter

C:\Program Files\Thinkpad\ConnectUtilities\AdmEnblr.exe

Change the path so that it reflects your correct path for where the application is installed.



When you start the program with the procedure above, you will see the window shown in Figure 5-52.

Figure 5-52 IBM Access Connections: Enabler for Administrator Profile Deployment Feature

To enable the profile distribution menu in IBM Access Connections you must click Enable Administrator Feature button in the IBM Access Connections: Enabler for Administrator Profile Deployment Feature. When you have clicked that button, the text on it will change to Disable Administrator Feature. If you want to disable it click that button.

After you have enabled the administrator features you must close and open IBM Access Connections. If the window is open while you run the IBM Access Connections: Enabler for Administrator Profile Deployment Feature, the new menu items will not be reflected until you do so.

When you open IBM Access Connections again, you will see a window that looks similar to Figure 5-53 on page 323. You should now see a new menu item named Profile Distribution.


Figure 5-53 IBM Access Connections with Profile Distribution

These new menu items are the items you will use to make or change a deployment profile. To create a new deployment profile, click the menu item Profile Distribution (as seen on Figure 5-53), and then Create Distribution Package. You will then enter into a window that looks like Figure 5-54 on page 324.


Figure 5-54 Create Distribution Package

This menu contains all the different profiles that you have in Access Connections. Click on the box next to the desired profile to select it. The second option you have is the possibility to change the way the user can control the selected profiles after they have been deployed. This can be selected under the User Access Policy drop down lists. On the selected profiles you can select between the following alternatives:

� Deny all changes/Deny deletion

� Deny network setting changes/Deny deletion

� Deny all changes/Allow deletion

� Allow all changes/Allow deletion

You can have different policies on all the selected profiles. By selecting these policy settings you can make installations of IBM Access Connections that


contain some business critical policies that you do not want to be deleted or changed.

The next item in the Create Distribution Package window is the Include Distribution Control List with this package menu. If you check the box next to it, the Define Distribution Control List button will be enabled. If you click on that button a new window will appear that looks like Figure 5-55.

Figure 5-55 Define Distribution Control List

In this window you can define which machines are allowed to install these profiles. Only systems with the authorized serial numbers can import the package file you make.

By default the Authorized Serial Numbers window is empty. You can add serial numbers by typing them in manually in the Individual Serial Number field followed by the Add button. If you manually enter the serial numbers you can only add one serial number at the time. If you have a list of machines in a database or something that you are able to export into a text file, you can use the Group of


Serial Numbers alternative. For example this list can be extracted from IBM Director.

If you would like to import a list of serial numbers (or make a group) you can do that by selecting the Group of Serial Numbers check box followed by clicking the Create Group button. You will then see the following window.

Figure 5-56 Create Group

You will need to enter a group name. Make sure that the name reflects the selected machines. In that way it will be easier to make changes to it, or to alter it afterwards. After giving your group a name, you can either manually insert serial numbers using the same procedure as described for single serial numbers, or you can import from a file. If your would like to import from a file, just press the Import from files… button and you will get a window similar to Figure 5-57 on page 327.

Tip: If you are importing serial numbers from a file, the file you are importing from can only have one serial number on each line. Only the serial number should be on that line, nothing else.


Figure 5-57 Import Serial Numbers

Navigate to the location where you have the file, select it, and then select Open. The list should appear in the field marked Serial numbers in group. Verify that the list is correct, and select OK to save it to your group (see Figure 5-56 on page 326).

The next menu item on the main menu (see Figure 5-54 on page 324) is the Include Client Configuration Policy settings with this package alternative. This alternative allows you to select different options on how IBM Access Connections should behave after the profile is deployed to it. These options include things like import and export of profiles and alternatives on selection of network detections. If you would like to use it, check the box next to the text and then click Define Client Configuration Policy. This will bring you to a new window shown in Figure 5-58 on page 328.


Figure 5-58 Define Client Configuration Policy

There are 7 main options that you can select in this window.

� Do not allow clients to become an Access Connections administrator

By checking this box you will disable the possibility for the user to become an IBM Access Connections administrator. They will not able to change any of the settings that the administrator has included.

� Include currently configured global settings

By checking this box, the Global Settings button will be available. You will also get the possibility to select Do not allow clients to change global settings. If you select that box, ordinary users will not be able to change their global settings. If you click the Global Settings button, a new window will pop up. This window is almost identical to the Global Settings window you can open from the main menu in IBM Access Connections. For more information about the different selections, refer to t 5.5.3, “Global Settings...” on page 304. The only option that is different from that Global Settings window is the possibility


to change the way your Bluetooth antenna reacts when you resume from sleep state on your machine. If you look at Figure 5-59 you will see that you have the possibility to set the Bluetooth antenna to on or off state when it resumes from a sleep state. Changing this option will only affect machines that are equipped with a built in Bluetooth radio

Figure 5-59 Global Settings

� Do not allow clients to import location profiles unless included in a distribution package

Selecting this option will prevent the users from being able to import any other locations than the ones that are given to them by a person that has the IBM Access Connections: Enabler for Administrator Profile Deployment Feature installed, and that has made a new profile package through that tool.

� Do not allow clients to export location profiles


Removes the option that allows the user to export profiles. This can help you prevent users from giving away the network settings or wireless settings to somebody that should not have them.

� Do not allow clients to create location profiles

If you want to be in total control of what profiles the users have on their computers, check this option. Only imported profiles will be available in IBM Access Connections. Users cannot create new profiles on their machine, but they can still change the existing profiles if you have not disabled that feature as well. If you want to disable changes as well, you will have to change that in the Create Distribution Package window (see Figure 5-54 on page 324).

� Disable automatic location profile switching features

Selecting this option disables the feature that automatically detects what network you are on and selects the right profile for that network.

� Disable Find Wireless Network function

Selecting this option will disable the function that allows you to find any wireless network within a reachable distance.

After you have set all the different options in all the described windows, you are ready to make a profile package out of it. When you return to the Create Distribution Package window (Figure 5-54 on page 324), click OK. A passhprase window will appear that looks like Figure 5-60.

Figure 5-60 Enter Passhrase

Fill in the password that you would like to use and then click OK. Take note of what password you used so that you have it for later deployments. A new window will appear that looks like Figure 5-61 on page 331.


Figure 5-61 Export Location Profiles

Select the desired location and type in the desired name. Remember where you put the file. You will need it later.

After making the profile packages, you are ready to install or update the machines you want. You now have two alternatives on how to put these profiles out on different machines. One is to deploy an installation with the profiles included and the other alternative is to update an existing installation.

If you would like to deploy an IBM Access Connections installation with the profiles included, perform the following procedure:

1. When you start the program file for IBM Access Connections, you will be prompted to state where you would like to put the installation files. The default location is C:\DRIVERS\W2K\ACCON but you can change it. Remember where you put the installation files.

2. You will now need to copy two files from you Access Connections folder. The files you need are the .loa file (that you made in the Create Distribution Package utility) and a .sig file that is located usually in the same folder. The .sig file is very important. This file contains the passphrase that you typed in when you made the profile package. The .sig file is usually named ___.sig. The .loa file is named what you called when you saved it (see Figure 5-61).


These two files must be copied to the same folder as the rest of the Access Connections installation files.

3. When all the files are gathered, you can either start a manual installation by starting the setup.exe, or you can do an unattended setup by using

setup -s -sms

(This is described in 5.3.2, “Automated Installation” on page 274 and in 5.3.3, “Manual installation” on page 274)

If you would like to deploy new or changed profiles after you have installed IBM Access Connections on a machine, you should use the following procedure:

1. Make a new profile package. It is very important that you use the same password as you used the first time. That will ensure that the profile is loaded.

2. Create some type of a script that copies the new .loa file and the .sig file to the location where IBM Access Connections is installed (or you can do it manually). The default location is C:\Program Files\ThinkPad\ConnectUtilities but you might have changed it.

3. When you have copied the files to that location close IBM Access Connections completely (or reboot).

4. Start IBM Access Connections again and your new profile(s) or setting(s) should be included

Making profiles in IBM Access Connections is quite easy. The thing you have to remember is the location of the different files. The .loa file and the .sig file are the two most important files in this process.

5.7 TroubleshootingThis topic is covered in the help file for this tool. The help file can be accessed using the Help menu item located at the bottom of the IBM Access Connections application window, or the file may be manually opened. The help file is named QCONNECT.CHM and is located in the installation directory.

5.8 Reference material� The application can be downloaded from the following URL:

http://www.ibm.com/pc/support/site.wss/migr-4zlnjb.html

� The help file QCONNECT.CHM is located in the installation directory after the application is installed.


http://www.ibm.com/pc/support/site.wss/migr-4zlnjb.html

� IBM Access Connections: Enabler for Administrator Profile Deployment Feature:





Chapter 6. Active Protection System

This chapter covers the Active Protection System (APS) that is available on many new ThinkPad models.

The Active Protection System features an integrated motion sensor (accelerometer) that continuously monitors movement of the ThinkPad notebook. Like an airbag’s sensor, it can detect sudden changes in motion and temporarily stop the hard drive to protect it from some crashes due to everyday notebook accidents. It provides up to four times greater impact protection than systems without this feature. This can be of great benefit especially in highly mobile systems which are at continual risk of being dropped and damaged.

6


6.1 Active Protection System OverviewThe IBM Hard Drive Active Protection System protects your hard disk drive when the shock sensor inside your ThinkPad computer detects a situation that could potentially cause damage to your hard disk drive. Damage to the hard disk drive generally results from physical shock to the hard disk drive.

One type of physical shock, called operating shock, occurs when the disk is in operation. During operation, the drive head is typically over the drive platters reading and writing data. When a physical shock to the drive occurs during operation, the head and the platters can come into contact causing both components to be damaged.

The second type of shock, called non-operating shock, occurs when the head is in the unloaded position, or not positioned over the platters. When a physical shock occurs in the non-operating state, the head can contact the ramp when it is positioned over it and damage the ability of the head to read and write data to the hard disk drive. That is where IBM’s Active Protection System comes into play. The following information describes the design and implementation of this technology.

6.2 Supported ThinkPad modelsAt the time this redbook was written, the following ThinkPad models included the Active Protection System hardware feature:

� ThinkPad R50, R50p, R51

� ThinkPad T41, T41p, T42, 42P

� ThinkPad X40

The required APS software is preinstalled on these systems and is supported with Microsoft Windows 2000 and Windows XP only. Updates to the APS software and installation instructions are available for download at:


Important: The IBM Hard Drive Active Protection System protects only the primary hard disk drive on computers using Windows® XP® or Windows® 2000®. The protection system does not support protection of any secondary hard disk drives, including those installed in an UltraBay. The active protection system functions with the 2.5" hard disk drive provided by IBM due to special customization.



6.3 Active Protection System sensor statusThe APS software monitors the accelerometer sensor information and displays the sensor status in the system task tray. See Figure 6-1.

Figure 6-1 APS system tray icon

The following states of system status are illustrated using the system tray icon:

Table 6-1 APS icons and system states

When the system senses a potential damaging event, the popup window shown in Figure 6-2 will be displayed and the hard drive will be stopped temporarily to protect the system from shock.

Icon System status

The shock sensor is disabled. In this state, shock sensor monitoring is not enabled and hard drive active protection is not activated.

The shock sensor is enabled, but no shock is detected. In this state, shock sensing is enabled and monitoring the shock condition. The active protection system does not detect any shock condition and the internal primary hard disk drive is operating normally.

The shock sensor is enabled and the head of the primary hard disk drive is unloaded due to shock condition. In this state, the computer has detected the shock condition and the head of the primary hard disk drive is unloaded to protect the hard disk drive from physical damage.

The shock sensor is enabled. Repetitive vibration is detected that does not cause the head in the hard disk drive to be unloaded. The shock sensor is set to temporarily ignore frequent repetitive shocks such as those experienced when in a train or automobile.

The shock sensor is enabled. The protection system has been manually suspended and low-level shocks will be ignored for a specified time. If severe shocks are detected while the system is in this state, the hard disk drive is stopped.

Chapter 6. Active Protection System 337

Figure 6-2 Hard disk warning message

6.4 User interface and task tray applet The APS application program is installed as part of the IBM Hard Drive Active Protection System driver package on Windows 2000 and Windows XP ThinkPad platforms. Once this package is installed, an icon can be added to the system tray but checking the Show active protection icon on the system tray See Figure 7-4.

The user can remove the system tray icon by right-clicking in the system tray and selecting Remove Active Protection Icon from the System Tray. See Figure 6-3.

Figure 6-3 Remove APS icon from system tray

The system tray icon can also be removed by clearing the Show active protection icon in the system tray check box. See Figure 6-4 on page 340.

The application installs the following components:


ShockPrf.sys: kernel mode device driver for prediction algorithm and hard disk drive control

Shockmgr.sys: kernel mode driver for miscellaneous operation

Sensor.dll: application interface dll

TpShCPL.cpl: control applet

TpShocks.exe: task tray application

TpShCPL.dll: bitmap resource file for this application program

TpShPrm.hta: promotion pop-up window

TpShPrm.gif: animation for promotion pop-up window

TpShPrm.jpg: banner picture for promotion pop-up window

Use the task tray menu to enable and disable the active protection system. Select Enable Hard Drive Active Protection on the system task tray to enable the shock detection and protect the primary hard disk drive from damage.

6.5 Description of Active Protection System propertiesThe active protection system is enabled by default whenever the computer is operating. It is automatically disabled while the computer is:

� Loading the operating system

� Entering Standby or hibernation mode

� Resuming normal operation after being in standby or hibernation mode

� Being shut down

� Turned off

To view and modify the APS configuration windows and system properties, do any of the following:

� Double-click the APS icon in the system tray

� Click Start → All Programs → Access IBM → IBM Active Protection

� Open the Control Panel and double-click IBM Active Protection

The APS properties window is displayed. There are three tabs available on the APS properties window. Overall APS configuration is performed using the Configuration tab. See Figure 6-4.


6.5.1 APS properties Configuration tab

Figure 6-4 Active Protection System properties Configuration tab

� Enable Active Protection System check box:

If this check box is selected, the IBM Active Protection System is enabled. If a shock is detected, the computer stops the hard disk drive operation to protect the drive from physical damage. The default setting is enabled.

To adjust the sensitivity to shock detection, use the slider to accommodate your sensitivity preference.

� Adaptively ignore frequent repetitive shocks check box:

Select this option to avoid frequent stops of the hard drive when you use the computer in an environment where the shock sensor is likely to detect repetitive, low-level shocks, such as those experienced when riding on a train or airplane. If enabled, this option functions when the number of hard disk drive stops caused by the protection system responding to low-level shocks exceeds a specific number within a certain amount of time (stop threshold). After the stop threshold is exceeded and the shock sensor detects a stable environment, the protection system will begin to temporarily ignore the low-level shocks. Once the shock sensor detects a stable environment for an


extended amount of time, this option will be reset so that the stop threshold must again be exceeded in order for the protection system to begin ignoring low-level shocks. When it is enabled, the protection system will always stop the hard disk drive when heavy shocks are detected.

� Allow me to manually suspend Active Protection System check box:

If this check box is selected, you can make the protection system stop its operation temporarily for a specified length of time. During that length of time, the protection system ignores low-level shocks. If severe shocks are detected while the system is in this state, the hard disk drive is stopped. Select your preferred suspend time from the drop down box.

� When hard drive is stopped check box, prompt me to manually suspend the Active Protection System:

Select this check box if you want to see a pop-up message for manually suspending the protection system when low-level shocks or repetitive vibrations are detected. The pop-up message will be displayed above the Active Protection System icon on the system tray.

� Show active protection icon on the system tray check box:

If the check box is selected, the icon showing the status of the shock sensor is displayed in the system tray.

� Allow only users with Administrator privileges to modify settings for the Active Protection System check box:

If this check box is selected, you must have Administrator privileges to configure the following settings:

– Checkbox for enabling the IBM Active Protection System

– Checkbox for temporarily ignoring repetitive, low-level shocks

– Checkbox for suspending the Active Protection System for a specified length of time

– Checkbox for configuring the privileged settings of the Active Protection System


6.5.2 APS properties Real-time Status tabA real-time display of the APS status and physical orientation of the ThinkPad is shown in the Real-time Status tab. See Figure 6-5.

Figure 6-5 APS Real-time Status tab

Additional explanation and views of the Real-time Status tab are covered in 6.6, “APS Real-time Status in action” on page 343.


6.5.3 APS properties About tabThe About tab on the APS Properties window lists the version information of the APS software installed on the system.

Figure 6-6 APS About tab

6.6 APS Real-time Status in actionThe following series of figures show the Real-time Status window in various states of APS activity.


6.6.1 No shock detectedFigure 6-7 shows the Real-time Status window during normal activity with no shocks detected by the APS. Note that the icon shown on the ThinkPad screen in the figure matches the APS icon that is displayed in the system tray area (see Figure 6-1 on page 337).

Figure 6-7 No shock detected


6.6.2 Repetitive shock detectedFigure 6-8 shows the Real-time Status window during normal activity with the repetitive shock detection feature enabled (see Figure 6-4 on page 340 for information on how enable or disable the repetitive shock detection feature). Note that hard drive activity continues during these repetitive shocks.

Figure 6-8 Repetitive shock


6.6.3 Repetitive shock detectedFigure 6-9 shows the Real-time Status window during activity that has caused APS to stop hard drive activity and unload the disk head. When a stable state is detected the hard disk activity returns to normal.

Figure 6-9 Shock detected


6.6.4 Free fallFigure 6-10 shows the Real-time Status window during a period when the ThinkPad is in a free fall. The APS has stopped hard drive activity during the fall. Note that the actual orientation of the ThinkPad during the fall is indicated on the Real-time Status display. The APS motion sensors are used to properly display the real-time orientation of the ThinkPad on the Real-time Status window. Even minor shakes and ThinkPad movements will briefly modify the orientation of the ThinkPad in the figure.

Figure 6-10 Shock detected

By the way, the ThinkPad survived the fall.

6.7 IBM Active Protection System designThe active protection system prevents damage to your hard disk drive by moving the read/write heads of the hard disk drive to areas that do not contain data when the shock sensor detects computer tilt, vibration, or shock. There are two types of hard disk drives. The first spins down the motor after unloading the head. The second does not spin down the motor, but does unload the head. The hard disk


drive is less vulnerable to damage when it is not in operation. Since the hard disk drive cannot be accessed while the head is unloaded, it may seem to the user that the drive has stopped. In reality, the disk access request has been temporarily suspended at the disk driver position so that the disk head can remain unloaded until a stable situation is detected. The suspended disk access request is then released and passed to the disk and the hard disk drive to normal operation.

The active protection system uses a combination of hardware and software components. The hardware component is a motion sensor, or accelerometer, embedded in the motherboard which continually senses system orientation and movement. The software component receives and interprets signals from the accelerometer, differentiates between potentially harmful movements and repetitive motion, and signals the hard drive to stop when a potentially damaging event is predicted. The software component also includes a system tray icon and properties window.

6.7.1 Head unloading for increased hard disk drive shock tolerance As a result of extensive testing with the computer lid both open and closed, IBM has found that in typical drop accidents either from the knee or a desk to a concrete floor, the internal hard disk drive is protected by the durable ThinkPad shell so that the received shock level to the hard disk drive does not exceed 800G or 800 times the force of gravity. Since 800G is the maximum rating of shock tolerance of the hard disk drive with the head unloaded, the hard disk drive can be rescued from most accidents in typical usage if the disk head is unloaded prior to receiving the shock impact. Head unloading can take 300 to 500ms, and the average duration after detecting a free-fall situation is 300ms. Therefore, it is too late to start head unloading after detecting the free-fall situation. This makes it necessary to concentrate on the behavior of the machine prior to a drop. The initial behavior acts as a prediction of the impending accident. In general, the duration of the predicting event is much longer than the actual free-fall. This enables the active protection system to respond to the impending accident prior to receiving the shock. The machine posture or system orientation is constantly checked by monitoring acceleration and using a prediction algorithm to statistically analyze recent behavior in typical usage. Head unloading is initiated by degrees of tilt, acceleration, or shock. The degrees at which head unloading occurs are adjusted and fine-tuned every time a proper prediction is applied for the current motion. The disk drive head remains unloaded until detecting a stable environment for approximately one to four seconds depending upon the amount of excessive acceleration at the beginning of the current shock or posture change. The Real Time Status window in the Active Protection System Properties (see Figure 6-7 on page 344 through Figure 6-10 on page 347) will give you a live view of the computer’s physical movements.


6.7.2 Use of prediction algorithm The active protection system employs a heuristic learning algorithm to track system orientation. The Shock Manager, a system thread created by the Shockprf.sys of a kernel mode device driver, analyzes the variations in acceleration and collects system orientation data into the Shock History Database. The collected data is then used to tune sensitivity and predict excessive shocks. This tuning is important in minimizing the disk performance penalty caused by prediction failures. Once the Shock Manager detects a certain variation which may be equivalent to one usually seen just before receiving an excessive shock, the Shock Manager stops the hard disk drive immediately.

The sensitivity to predict a shock varies depending on usage conditions. In general, the more stable the ThinkPad computer stays, the more sensitively the Shock Manager behaves. The Shock Manager focuses its attention on the current acceleration variation and the weighted average in the recent past. The log is used to minimize intrusive operation during normal usage of the computer. If the hard disk drive head is unloaded after detecting a potentially harmful situation, the user can shorten the current head-unloading period up to 1 second on the condition that a calm state, stable enough to remove the risk of a drop, continues for at least one second and at the same time mouse movement activity for more than 200ms is detected thereby informing the active protection system that this is not a drop situation.

The design of the active protection system allows for certain shocks or vibrations that fall within a span of accepted or normal motion and does not repeatedly stop the hard drive when this level of motion is detected. You can select a check box in the properties window to temporarily disable hard drive protection while repetitive motion or vibration is detected. This feature is particularly useful when the ThinkPad computer is used on a plane or train and repetitive vibration is expected.

6.8 SummaryThe IBM Hard Drive Active Protection System can greatly improve overall system reliability by providing hard drive protection from shock. Using the latest technology to constantly monitor the movement of your ThinkPad computer, users can feel confident that their data will be protected in the event of a drop or similar potentially damaging event.

The active protection system is enabled by default whenever the computer is operating. It is automatically disabled while the computer is:

� Loading the operating system


� Entering Standby or hibernation mode

� Resuming normal operation after being in standby or hibernation mode

� Being shut down

� Turned off

6.8.1 Summary of features� Enable/Disable feature

User can manually enable and disable the active protection system using the software user interface.

� Automatic ignore feature

Sometimes the user is in an environment that has associated vibration (such as in a car or airplane where the entire vehicle vibrates). In these environments, the vibration may be transmitted to the ThinkPad computer. The Automatic Ignore feature is helpful in this situation. This feature is enabled by default, but the user can manually change choice at any time via the software utility.

� Cancel feature for impulse-type vibration

This feature cannot be manually controlled by the user. The Shock Manager ignores impulse-type acceleration change so as to minimize prediction failures. An adaptive low-pass filter function inside the Shock Manager performs this function.

� Heuristic sensitivity tuning feature

This feature cannot be manually controlled by the user. The sensitivity for shock prediction is dynamically changed depending on body posture change with received shocks, vibrations and user input activities.

� Administrative lock

This feature restricts users without Administrative system rights from changing the Active Protection System properties.


Chapter 7. Implementing ThinkVantage Technologies

The IBM ThinkVantage Technologies create a competitive advantage that will help your organization succeed. Addressing the PC life cycle, your workstations can become less dependent on IT staff or user intervention for basic tasks such as deployment, backup, security and more, thereby freeing resources which can be refocused on driving business success.

The tools discussed in this redbook are key contributors in deployment optimization. ThinkVantage Technologies allow PCs to be more than just “clients”.

7


7.1 Implementation planningWhen delivering a solution to your organization, it is very important to plan every aspect of a technology project. Quite often, implementations are successful because more time was spent planning than implementing. This can include long term plans to ensure your environment will be manageable.

Successful planning requires a clear knowledge of the environment as well as clearly defined targets. When delivering a solution that involves the PC life cycle, the entire process must be included. Many organizations spend significant amounts on initial deployment without considering the costs. For example, after a machine has been deployed:

� What is the cost of getting that machine working again if the operating system fails? How will the machine be reloaded?

� How will user data be migrated?

� How will image updates and changes be implemented?

� How will you dispose of the workstation when it is no longer useful?

There are numerous things to keep in mind when developing a long term solution for your organization. Using ThinkVantage Technologies will offer maximum value when implemented with a strong long term plan and objective.

The following sections will help you consider some elements before you complete your plan.

Organizational complexity and image managementHow many images are in your organization? Is this something your IT organization spends a lot of time managing? What is involved in keeping the current image environment?

Image management can quickly become a nightmare as complexity increases. Figure 7-1 on page 353 shows how implementing ImageUltra Builder with Ultra Portable images can benefit from DOE (Dynamic Operating Environment) and HIIT (Hardware Independent Imaging Technology). The representation is common to what might be seen in a large bank environment.


Figure 7-1 ImageUltra large bank example

Application complexityHow many applications are in your organization? Who uses them?

This can be one of the most challenging questions. Clearly defining which applications are common within business units is half the battle. By having this information, you'll be able to plan the best solution for using IBM Software Delivery Center (SDC) and ImageUltra to manage deployment of those applications. For more information of IBM Software Delivery Center, see Using ThinkVantage Technologies: Volume 2 Maintaining and Recovering Client Systems, SG24-6060-03.

As displayed in Figure 7-1, SDC can be used to complement ImageUltra Builder in the process of reducing the number of images in an environment.

System recoveryWould a system recovery solution help in your environment? Do you have many remote (or home office) users?

4 mobile systems5 desktop systems

Token RingEthernet

WindowsNTWindows2000

1 SDCpackageX X X = 36

images

SDC is currently available and consolidates workgroup specific applications into one package


Token RingEthernet

ImageUltra DOE

X X X = 18 images

1 ImageOneX X = 1 image

ImageUltra - can consolidate multiple OS's and languages into one singel image as an ongoing solution for new IBM hardware

- allows for platform independence by abstracting the drivers from the preload image

ImageUltra withappropriate driversto support unique system configurations

Large Bank Example


Token RingEthernet

WindowsNTWindows2000

Model Bank ImageWhsl Bank ImageCorporate ImageTrader

X X X = 144 images

1 SDCpackage

1 SDCpackage

Chapter 7. Implementing ThinkVantage Technologies 353

Using a tool like Rescue and Recovery can help ensure your users can recover from an image failure quickly without having to wait for a technician. Often, a user can be up and running in minutes.

How do I link Rescue and Recovery into ImageUltra Builder?

In this book, we discuss how to set up Rescue and Recovery so a user (or technician) can initiate the silent installation process (through ImageUltra Builder). This is particularly useful when you would like to ensure the user's workstation is fully configured before running the installation process. This will ensure the base backup on the machine is fully customized for that particular user.

Vendor and platform standardizationWhen an organization limits the vendors and platforms they purchase, they benefit from:

� Purchasing power - leverage greater volume purchases if you are getting things from a reduced number of vendors

� Simplification of compatibility - your support organization will benefit from reduced testing times when determining compatibility of software, drivers, etc.

� Vendor management - less time required for managing your vendors as the number is reduced

� Support - you may save money on any service contracts that need to be duplicated between vendors

� Reduction of the amount of testing when integrating new hardware peripherals or software

� Product knowledge- training support staff on fewer hardware/software platforms makes it easier to provide consistent service

A homogeneous environment will be easier to maintain and to lower the cost of ownership. Standardization enhanced with the ThinkVantage Tools offers an unparalleled solution for managing your environment.

Removing existing imaging applicationsCan I get rid of my existing cloning program?

If you plan to use UltraPortable images only, you can get rid of external imaging tools. However, in mixed hardware environments, you'll need to keep an imaging tool to deploy machines.

UltraPortable solutionWhy do I need an UltraPortable solution?


The UltraPortable solution provides the greatest flexibility for different hardware types. Portable Sysprep images can sometimes have problems with installing on machines that have differences in core chipsets.

Handling migrationHow does SMA work in this process?

There are many ways SMA can be integrated into the process. In ImageUltra Builder, SMA can be run in batch mode to import a users profile. In addition, IBM Director can also be used to run the migration process as a task.

7.2 ThinkVantage TechnologiesThe following sections outline the various ThinkVantage Technologies components.

ImageUltra BuilderImageUltra Builder allows for the creation of one single SMART image that can be easily updated and deployed across an organization. This modularity allows for easy updates and simplified testing as the build processes for unchanged modules will always be consistent.

Some benefits you’ll see are as follows:

� Reduction in the number of images within an organization. This will vastly reduce the efforts required to maintain “image libraries”.

� ImageUltra Builder will allow for integration of existing images. Any existing images can be loaded into the repository. This can be extremely helpful for legacy workstations in the environment.

� Ease of implementation. The modules are showcased in a console that allows for easy identification.

� Flexibility. By supporting existing imaging technologies, organizations can gradually transition to a SMART (that is, UltraPortable) image through the standard attrition process. Another alternative is to replace PCs using a “big bang” deployment. Customers have seen that cost reductions through platform standardization can greatly offset the initial costs of the hardware required for this process.

� IT organizations will find the repeatable build process an excellent way to ensure the support organization is getting the same standards across a company.


� Administrators can easily determine what is loaded by the ImageUltra Builder through the graphical interface. This can save time over traditional imaging technologies where each individual image must be located to determine its contents.

� Multiple deployment options are possible via Network or CD distribution to fit your business requirements.

System Migration AssistantDuring the procurement of a new PC, migration of data and settings is often the most time consuming part of the task. By automating the migration process through the use of SMA, settings and data will not be overlooked.

Using SMA will allow end-user data, Windows settings and “application personalities” to be transferred to a new machine. During the process, the end-user can also validate the data to be captured before it is downloaded to the new environment.

Some benefits users will experience are as follows.

� Reduction in cost for migration to new clients

� Enabling the control of service level agreements through:

– Consistent migration results

– Reduction of help center calls because of possible misconfigurations often associated with manual migrations

� Ability to perform migration tasks on their own using the SMA tool, relieving burden on IT resources.

The following example allows migration to occur without the requirement for network/external storage. It also illustrates where SMA is implemented in the deployment process.


Figure 7-2 Example of an Automated Migration Process

Secure Data Disposal Using secure data disposal will allow for a simplified method of clearing data from a workstation before it is cascaded or retired. A technician can simply start the process and walk away. The process will safely remove all the data and provide a signature to notify completion.

As discussed in this book, secure data disposal provides peace of mind when protecting confidential information is paramount. The tool can be run stand-alone, which is excellent in situations where the workstations have already been removed from a corporate infrastructure. Furthermore, RDM can also be used to apply the secure data disposal on workstations attached to the network environment.

Ensuring the removal of confidential data can easily result in large data savings by protecting your intellectual capital. Furthermore, when an IT technician removes all the data from a machine, all applications are cleared too. In instances where a machine is being redeployed, this can also protect an

Load new IBM Clientsystem with image

(IUB)

Prepare oldclient for

migration

�Read migration guideAccess internal web sitefor additional migration info

�

�UnpackConnect to powerConnect to Corp. network

�

�

�UserIDDomainetc.

�

�

Connectsystems with

crossovercable

Capture dataon old Client

(SMA)

�Captured datais stored onthe new client

Connect toCorp. network

Migration completed

Restorecaptured data

(SMA)

Validate Clienton Network

Install newIBM Client

Initiate backup(R&R with RR)

Select apps toinstall (SDA)


organization from software license exposures that may occur from loading the same applications on multiple workstations.

7.3 Migration/rollout scenariosIn this section, we will show different possible scenarios to demonstrate how ThinkVantage Tools can be used together.

7.3.1 PC migration or upgradeIn this section, we will show in an example how a migration or an operating system upgrade can be done by using the different ThinkVantage Tools.

For example, a user has a ThinkPad 600 with Windows 98. He will be receiving a ThinkPad T40 with Windows XP. Or another example: a company wants to use the ThinkVantage Tools to upgrade from Windows NT to Windows XP.

The process steps shown here briefly describe the steps to follow for a migration. See the corresponding chapters in this book and Using ThinkVantage Technologies: Volume 2 Maintaining and Recovering Client Systems, SG24-6060 for detailed use and configuration of the ThinkVantage Tools.


Table 7-1 ThinkVantage Technologies migration process steps

Process steps ThinkVantage Tool used

To Do

1.) Image creation ImageUltra Builder 1. Choose the image type you want to use with ImageUltra Builder.

2. Integrate the System Migration Assistant as a software module into your ImageUltra Builder image.

3. Integrate the Software Delivery Center client as a software module into your ImageUltra Builder image.

4. Integrate the Software Delivery Center as a software module into your ImageUltra Builder image.

5. Integrate the System Information Center client as a software module into your ImageUltra Builder image.

6. Integrate Access IBM as a software module into your ImageUltra Builder image.

7. Integrate Access connections as a software module into your ImageUltra Builder image. Keep in mind that Access connections is only supported on specific ThinkPads.

8. Integrate Embedded Security Subsystem as follows, to your ImageUltra Builder image:a. Create driver modules for the SM bus driver and the

LPC bus driver.b. Create a software module for the IBM Client security

software.Refer to “Supported IBM models” in the Embedded Security Subsystem chapter of Using ThinkVantage Technologies: Volume 2 Maintaining and Recovering Client Systems, SG24-6060 for which IBM systems ESS can be installed.

2.) User data and user settings migration

System Migration Assistant

1. Install on the old pc system, System Migration Assistant.2. Run System Migration Assistant.3. Place the SMA profile file to a network share.

3.) Image deployment

� ImageUltra Builder

� Remote Deploy Manager

We have several possibilities to deploy the image to a client system. 1. Creating a ImageUltra Builder boot floppy.2. Creating a ImageUltra Builder distribution CD set.3. Creating a custom network boot floppy.4. Creating your own network deployment boot floppy.5. With Remote Deploy Manager, we have the possibility to

replace the boot floppy. We can remotely wake up a PC system, send a virtual boot floppy to it and deploy the image.

4.) Install client ImageUltra Builder When the image is deployed to the service partition on a PC system, the installation process will automatically start from the service partition on the local PC system.


These are some necessary steps to perform for a successful migration of PC systems with ThinkVantage Technology tools.

7.3.2 PC rollout scenarioIn this section, we will show in an example how a PC rollout can be done using the different ThinkVantage Tools.

As an example, we can take a customer that purchased new IBM hardware.

The process steps here show briefly the things to do for a rollout. See the corresponding chapters in this book and ThinkVantage Technologies: Volume 2 Maintaining and Recovering Client Systems, SG24-6060 for detailed use and configuration of the ThinkVantage Tools.

5.) Software distribution


Distribute and install Rescue and Recovery with Software Delivery Center. Rescue and Recovery will do a base backup after the installation.

6.) Restore user data and user settings


1. Run System Migration Assistant on the client system.2. Restore the SMA profile file from the network share.

7.) Backup Rescue and Recovery

When the user data and settings are correctly on the client system, run Rescue and Recovery for creating the first incremental backup.

8.) Inventory System Information Center

Run or schedule the System Information Center agent on the client system.


To Do


Table 7-2 ThinkVantage Technologies rollout process steps


To Do’s

1.) Image creation ImageUltra Builder When a customer purchases new IBM hardware, we have the advantage that we can import the service partition from the systems. In this case we will use ultra portable images.1. Import service partitions from the systems and create

the corresponding operating system, driver and application modules.

2. Integrate the Software Delivery Center client as a software module into your ImageUltra Builder image.

3. Integrate the Software Delivery Center as a software module into your ImageUltra Builder image.

4. Integrate the System Information Center client as a software module into your ImageUltra Builder image.

5. Integrate Access connections as a software module into your ImageUltra Builder image. Keep in mind that Access connections is only supported on specific ThinkPads.

6. Integrate Embedded Security Subsystem as follows, to your ImageUltra Builder image:a. Create driver modules for the SM bus driver and

the LPC bus driver.b. Create a software module for the IBM Client

security software.Refer to “Supported IBM models” in the Embedded Security Subsystem chapter of Using ThinkVantage Technologies: Volume 2 Maintaining and Recovering Client Systems, SG24-6060 for which IBM systems ESS can be installed.

2.) Image deployment

� ImageUltra Builder

� Remote Deploy Manager

We have several possibilities to deploy the image to a client system. 1. Creating a ImageUltra Builder boot floppy.2. Creating a ImageUltra Builder distribution CD set.3. Creating a custom network boot floppy.4. Creating your own network deployment boot floppy.5. With Remote Deploy Manager we have the possibility

to replace the boot floppy. We can remotely wake up a pc system, send a virtual boot floppy to it and deploy the image.

3.) Install client ImageUltra Builder When the image is deployed to the service partition on a PC system, the installation process will automatically start from the service partition on the local PC system.


These are some necessary steps to perform for a successful rollout of PC systems with ThinkVantage Technology tools.

7.3.3 Help desk scenarioIn this section, we will show an example scenario in which ThinkVantage Tools can be integrated into a help desk.

Large enterprises have a help desk to support end users. The help desk has a trouble ticket tool to open trouble tickets for users who have a problem with their PC system.

It is possible to use some of the ThinkVantage Tools for integration into a help desk tool system. We assume for this example that SMA, Software Delivery Center, Rescue and Recovery, System Information Center and IBM Director Agent are used on the client systems. See Table 7-3 on page 363 for an example scenario:

4.) Software distribution


Distribute and install Rescue and Recovery with Software Delivery Center. Rescue and Recovery will do a Base Backup after the installation.

5.)Prepare the system for the user

Bring the PC system to the end user and finalize the configuration.

6.) Backup Rescue and Recovery When the user data and settings are correctly on the client system, run Rescue and Recovery to create the first incremental backup.

7.) Inventory System Information Center

Run or schedule the System Information Center agent on the client system.


To Do’s


Table 7-3 Help desk scenario example

7.4 IBM Director and System Information Center scenario

In a scenario with IBM Director and System Information Center, customers have the advantage that one database can be used for both tools.

For example, let’s say a customer wants to use IBM Director for server systems, because he needs server systems management capabilities only on server systems. Client systems management is not needed. So the customer installs the System Information Center agent on desktop, laptop and server computers to gather the asset information. The IBM Director agent will be installed only on

Action Tool used

1. A user calls the help desk, concerning an Outlook problem with his PC system. The user received the following error message when Outlook was started. Outlook caused an invalid page fault.

2. The help desk opens a trouble ticket for the problem in the help desk tool. Based on the inventory information from System Information Center, the supporter can see what PC system the user has and what software and versions are installed on the users computer.

� Help desk Tool

� System Information Center

3. The help desk accesses the user’s computer remotely to see the problem.

IBM Director Agent

4. The help desk decides to reinstall Outlook.

5. The help desk starts SMA to back up the users desktop settings and data.


6. The help desk uses Software Delivery Center to reinstall Outlook on the users computer.


7. The help desk restores users settings and data with SMA. System Migration Assistant

8. The help desk starts outlook and checks the settings and whether everything is working correctly.

9. The help desk initializes an incremental backup with Rescue and Recovery.

Rescue and Recovery

10. The help desk closes the trouble ticket. Help desk tool


server systems. For more information on IBM Director, see Implementing Systems Management Solutions using IBM Director, SG24-6188.

In the following figure, we see a possible scenario structure with System Information Center and IBM Director.

Figure 7-3 System Information Center and IBM Director scenario

System Info Gatherer agent

Centralized database for: - System Info Center

- IBM Director

IBM Director server delivers theserver management capabilities.

PC system Server system

IBM DirectorServer

System InformationCenter Server

System Info Gatherer agent

IBM Director agent

System Info Center serverdelivers the asset management capabilities.C


acronyms

AD Asset Depot

AES Advanced Encryption Standard

ANSI American National Standards Institute

API application programming interface

APS Active Protection System

ATAPI Advanced Technology Attachment Packet Interface

BEER Boot Engineering Extension Record

BIOS Basic Input/Output System

BSOD blue screen of death

CA Certificate Authority

CAPI cryptographic application programming interface

CHS cylinders, heads, sectors

CISC Complex Instruction Set Computer

CSS Client Security Software

DLL dynamic link library

DLT digital linear tape

DSL Digital Subscriber Line

EAP Extensible Authentication Protocol

ECC error checking and correcting

EEPROM Electrically Erasable Programmable Read Only Memory

EFS Encrypted File System

ESD electronic software distribution

ESS Embedded Security Subsystem

Abbreviations and

© Copyright IBM Corp. 2004. All rights reserved.

FFE File and Folder Encryption

GIF CompuServe Graphics Interchange Format

GINA Graphical Identification and Authentication

GSK Global Security Toolkit

GUI Graphical User Interface

HDD Hard Disk Drive

HPA Hidden Protected Area

HTML Hypertext Markup Language

IBM International Business Machines Corporation

IDE Integrated Drive Electronics

IE Internet Explorer

IP Internet Protocol

ISDC IBM Software Delivery Center

ISIC IBM System Information Center

ISO international Standards Organization

ITSO International Technical Support Organization

IUB ImageUltra Builder

JDBC Java database connection

JDK Java Development Kit

JRE Java Runtime Environment

LBA Logical Block Addressing

LDAP Lightweight Directory Access Protocol

LEAP Lightweight Extensible Application Protocol

LPC low pin count

LTO linear tape open

MBR Master Boot Record

365

MDAC Microsoft Data Access Components

MSCAPI Microsoft Crypto API

MSI Microsoft Software Installation

NDIS Network Driver Interface Specification

NIC Network Interface Card

NLS National Language Support

NTFS New Technology File System

OEM Original Equipment Manufacturer

PARTIES Protected Area Runtime Interface Extension Services

PEAP Protected Extensible Authentication Protocol

PKCS Public Key Cryptographic Standard

PKI Public Key Infrastructure

PTA Personal Trust Agent

PXE Pre-boot Execution Environment

RAID Redundant Array of Inexpensive Disks

RDM Remote Deployment Manager

RISC Reduced Instruction Set Computer

ROI Return on Investment

RSA Rivest, Shamir, and Adleman

RTE Java Runtime Environment

SCSI Small Computer Systems Interface

SDA Software Delivery Assistant

SDC Software Delivery Center

SDD Secure Data Disposal

SDK Software Developer’s Kit

SID Security Identifier

SMA System Migration Assistant

SMBIOS Systems Management Basic Input Output System

SQL Structured Query Language

TAM Tivoli Access Manager

TCG Trusted Computing Group

TCO total cost of ownership

TCPA Trusted Computing Platform Alliance

TFTP Trivial File Transfer Protocol

TKIP Temporary Key Integrity Protocol

TLS Transport Layer Security

UDB Universal Database

USB Universal Serial Bus

UVM User Verification Manager

VBE Virtual Boot Environment

VPN Virtual Private Network

WEP Wireless Equivalent Privacy

WINS Windows Internet Naming Service

WPA Wi-Fi Protected Access

WMI Windows Management Instrumentation

XML eXtensible Markup Language


Related publications

The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this redbook.

IBM RedbooksFor information on ordering these publications, see “How to get IBM Redbooks” on page 369. Note that some of the documents referenced here may be available in softcopy only.

� Using ThinkVantage Technologies: Volume 2 Maintaining and Recovering Client Systems, SG24-6060-03

� ThinkVantage Technologies: Using Software Delivery Center, REDP-3976

� Implementing Systems Management Solutions using IBM Director, SG24-6188

� Using the System Installation Tool Kit to Streamline Client Rollout, SG24-6178

Other publicationsThese publications are also relevant as further information sources and are provided with the product CD-ROM:

� ImageUltra Builder Version 2.0 User Guide


� IBM System Migration Assistant 4.2 User’s Guide


� IBM Access Connections Deployment Guide


Online resources and educationThese Web sites and URLs are also relevant as further information sources:

� ImageUltra Builder patches






� Hardware Independent Imaging Technology (HIIT) enabled PCs


� Microsoft Sysprep program


� Windows NT 4.0 Resource Kit Support Tools


� Windows 2000 Resource Kit


� IBM Imaging Technology Center (IITC)


� System Migraton Assistant code and documentation


� InstallShield support


� Microsoft Office XP administrative service pack

http://www.microsoft.com/office/ork/xp/journ/oxpupdte.htm

� Hiddensoft AutoIt software

http://www.hiddensoft.com

� Wise software packaging

http://www.wisesolutions.com

� ThinkVantage Technologies


� Access Connections code and documentation


� Hotkey driver for ThinkPad systems


� IBM Access Connections: Enabler for Administrator Profile Deployment Feature code


� Active Protection System support












http://www.microsoft.com/office/ork/xp/journ/oxpupdte.htm

http://www.hiddensoft.com

http://www.wisesolutions.com





� Introduction to IBM ThinkVantage Technologies: Security

http://www.pc.ibm.com/training/txw14.html

� Introduction to IBM ThinkVantage Technologies: Wireless


� Introduction to IBM ThinkVantage Technologies: Migration and Recovery


� Using the IBM ThinkVantage Technologies

http://www.pc.ibm.com/training/ezi10.html

� IBM ImageUltra Builder Workshop

http://www.pc.ibm.com/training/txi06.html

� IBM Rescue and Recovery with SMA Workshop


� Implementing IBM Client Security Workshop


� Implementing and Securing a Wireless LAN


How to get IBM RedbooksYou can search for, view, or download Redbooks, Redpapers, Hints and Tips, draft publications and Additional materials, as well as order hardcopy Redbooks or CD-ROMs, at this Web site:

ibm.com/redbooks

Help from IBMIBM Support and downloads

ibm.com/support

IBM Global Services

ibm.com/services

Related publications 369



http://www.ibm.com/support/

http://www.ibm.com/support/

http://www.ibm.com/services/

http://www.ibm.com/services/




http://www.pc.ibm.com/training/ezi10.html






Index

Aaccelerometer 335, 337, 348Access Connections 4, 267–333

11a/b/g Wireless LAN Mini PCI Adapter 268–26911b/g Wireless LAN Mini PCI Adapter 268–269automatic program startup 286–287Bluetooth 268, 300, 306, 320, 329default printer 285Dual-Band Wi-Fi Wireless Mini-PCI Adapter 268–269Enabler for Administrator Profile Deployment Feature 320–332Encryption 313Fn+F5 key display 317global settings 304–306installation 273–275location profile 275–298

detailed setup 275–292quick setup 292–298

location switching 301–304MAC Address 313managing location profiles 306–309Mini-PCI Wireless LAN Adapter 268network connections

broadband 268cable modem 268Digital Subscriber Line 268Ethernet 268Integrated Services Digital Network 268Token Ring 268Virtual Private Networking 268

Network Name 312prerequisites 270–273profiles 275–298proxy settings 282–283security settings 283–284Service Set Identification 281, 312–313

defined 312status window 299–301switching between profiles 315Wireless 2200BG Network Connection 268–269

© Copyright IBM Corp. 2004. All rights reserved.

Wireless Mode 313wireless network considerations 309–314

Access Help 5Access IBM 5Active Protection System 335–350

accelerometer 335, 337, 348configuration 340–341design 347heuristic learning algorithm 349motion sensor 335, 348real-time status 342–347

administrator password 116Aironet Client Utility 272always install 32application module 195application modules 48–54

ImageUltra Builder 27, 29APS

See Active Protection SystemAsset Depot 363–364

with IBM Director 363–364audio driver

ImageUltra Builder 28auditboot 31

Bbase map settings 114–123base maps 30, 123

creating 103–123defined 21, 103defined in ImageUltra Builder 29

base operating system hardware specific modules 78–86base operating system modules

ImageUltra Builder 27base-partition module 118Before/After Menu Options tab

base map settings 117behavior 31BIOS 29Bluetooth 268, 300, 306, 320, 329broadband 268

371

Ccable modem 268Call Center Employee 264CHKDSK 29Cisco Systems, Inc. 272CKIP 269color settings 121comctl32.dll 209compressed module source 30computer name 116container 68

defined in ImageUltra Builder 28ImageUltra Builder 28–29

core chip set 26custom modules 45–48

DDepartment of Defense-compliant 261, 263DeployCenter 11–12, 23, 27, 77–78, 87, 90–91, 97, 139–142, 166, 171, 182–183

ImageCenter 139overview 139

deploying images 126–138deployment methods 132–138

CD distribution 132network deployment 134

deployment repositoryImageUltra Builder 29

device driver modules 23, 54–63, 124ImageUltra Builder 28

DHCP configuration 116Digital Subscriber Line 268direct-network install

network options tab 120disks 6DOS window 30DOS-based programs 29Drive Image 3, 186driver map 29–30, 32

create 123defined 29, 103

driver map filter 125driver map settings 124–125DSL

See Digital Subscriber Line

EEAP-TLS 271–272

EEPROM 29Embedded Security Subsystem

overview 5Enabler for Administrator Profile Deployment Fea-ture 320–332encoded_password 242end-of-life disposition 1Ethernet 268

Ffile extensions

.BMA 30

.CRI 30

.DMA 30

.IMZ 30file migration 245filter/utility modules 64–65filters

defined 31, 64defined in ImageUltra Builder 28ImageUltra Builder 29

first boot 31Fn+F5 key display

Access Connections 317

Ggateway 116general tab

base map settings 115driver map settings 125

Ghost 3, 12, 23, 27, 78, 90, 180, 182, 186considerations 180

gold 77

HHardware Independent Imaging Technology

behavior 32defined 22enabled 22, 124integration 26

hardware-specific image 23, 26, 124Hidden Protected Area 22, 124HIIT

See Hardware Independent Imaging Technolo-gy

HIIT-enabled 26HPA


See Hidden Protected AreaHR Employee 264

IIBM Customization Program 87, 89IBM Director 6, 363–364

with Asset Depot 363–364IBM PCD Tool 8IBM PCs 24IBM Preload modules 39–45IBM ThinkPad 28ignore HIIT processing 32image cleanup tab

base map settings 119image creation 3image deployment 3image maintenance

ImageUltra Builder 26image management 3image types 22–24

hardware-specific image 23portable-sysprep image 23selecting the best for you 24–27ultra-portable 22

ImageCenter 139image-cloning software 24image-cloning tool 23ImageUltra Builder 3, 8, 11–200, 361

application modules 48–54base map settings 114–123base maps

creating 103–123defined 21, 29, 103

base operating system hardware specific mod-ules 78–86container 28core chip set 26custom modules 45–48deploying images 126–138deployment methods 132–138

CD distribution 132network deployment 134

deployment repository 29device driver modules 54–63driver map

create 123defined 29, 103

driver map settings 124–125

filter/utility modules 64–65filters 29

defined 28Hardware Independent Imaging Technology

defined 22integration 26

hardware-specific image 26IBM Preload modules 39–45image maintenance 26image portability 25–26image types 22–23

hardware-specific image 23portable-sysprep image 23selecting the best for you 24–27ultra-portable 22

installation time 26InstallShield 47map settings

Base map 114Driver map 124

modulecatagories 27defined 21

modulesapplication 27, 29base operating system 27container 29

defined 28device driver 28operating system 27operating system add-on 27partitioning 27, 29

network-staging folder 136operating system add-on modules 66–76partitioning modules 77portable-sysprep image 25–26

creating 88repository 29

creating 33–39defined 21, 30file extensions 30

Smart Image 13, 21, 24, 45creating 32–125definition 21Sysprep 22

suported operating systems 26supported hardware 26system board 26ultra-portable image 26–27

Index 373

utilitiesdefined 29

Windows 2000 images 26Windows Installer 46Windows XP images 26

imaging 8INF installable 32INF installs 32install sequence tab

base map settings 118install slot 32installation time

ImageUltra Builder 26InstallShield 47integrated security chip 5Integrated Services Digital Network 268Internet 1, 4IP address 116ISDN

See Integrated Services Digital Network

Kkeyboard settings 121

Llayout settings 121LEAP 268–269, 272

Mmap settings

Base map 114Driver map 124

memory 6menu appearance tab

base map settings 121color settings 121keyboard settings 121layout settings 121

menu driven area 29menu items 123metadata 30Microsoft Sysprep 23, 89migration

when is it required? 203who performs the transfer? 203

module behavior 109module categories

ImageUltra Builder 27modules

application 48–54base operating system hardware specific 78–86custom 45–48defined 21device driver 54–63filter/utility 64–65IBM Preload 39–45operating system add-on 66–76partitioning 77

motion sensor 335, 348msiexec.exe 46My Computer 30

NNetwork Boot 141network deployment 8network infrastructure 4network options tab

base map settings 120driver map settings 125

network synchronization 108network options tab 120

network-staging folder 136normal device detection 32

Ooperating system add-on modules 66–76

ImageUltra Builder 27operating system modules 27, 70

ImageUltra Builder 27organization name 116OS modules 196

Ppartition tab

base map settings 122partitioning modules 77

ImageUltra Builder 27, 29PC life cycle 1, 6, 259PEAP 269Peer to Peer 251–258

defined 251portable-sysprep image 23, 25–26, 87, 124

creating 88


PowerCast 140, 170, 173, 177–178PowerCasting 140

overview 140PowerQuest

Drive Image 3, 186Pre-boot Execution Environment 141–142, 148, 161

capture donor image 142pre-deploy planning 1processors 6PXE

See Pre-boot Execution Environment

RRDM

See Remote Deployment Managerread only memory (ROM) 29Redbooks Web site 369

Contact us xvreference manual 5relative location 32Remote Deployment Manager 6, 260, 264

console 260repository

creating 33–39defined 30defined in ImageUltra Builder 21file extensions 30ImageUltra Builder 29

Rescue and Recovery 122overview 4

return on investment (ROI) 2

Sscript files 76SCRUB3 259, 262–265

See also Secure Data Disposalcommand syntax 260defined 259Department of Defense-compliant 261, 263examples 262high security 261in-the-field debugging 260limited security 261Master Boot Record 261medium security 261performance considerations 263scrub signature 260

security level 260signature 260

SDCSee Software Delivery Center

Secure Data Disposal 4, 259–265See also SCRUB3command syntax 260Department of Defense-compliant 261, 263examples 262high security 261in-the-field debugging 260limited security 261Master Boot Record 261medium security 261performance considerations 263Remote Deployment Manager 260, 264scrub signature 260security level 260signature 260viruses 259

security-aware applications 5service partition 124, 181, 359, 361Service Set Identification 281, 312–313

defined 312SETUP.ISS 48, 180, 211

generate 48silent install command 31, 74silent installation 46

defined 46SMA

See System Migration AssistantSMABAT.EXE 239, 241, 248Smart Image 13, 21, 24, 45, 120, 124–125, 136

creating 32–125definition 21Sysprep 22

Software Delivery Assistant xviiSoftware Delivery Center xvii, 178, 353, 362

overview 5SoundMAX audio driver 54, 61source directory 74SSID

See Service Set Identificationsubnet mask 116supported hardware

ImageUltra Builder 26supported operating systems

ImageUltra Builder 26Symantec

Index 375

DeployCenter 11–12, 23, 27, 77–78, 87, 90–91, 97, 139–142, 166, 171, 182–183

ImageCenter 139overview 139

Ghost 3, 12, 23, 27, 78, 90, 180, 182, 186considerations 180

Sysprep 116Sysprep tool 23system board 26System Information Center 362

overview 5System Migration Assiatant

installationsilent 210

silent install 210System Migration Assistant 4, 201–258

alternate_print_driver_location 244apply phase 207, 212

applying settings and files 232–239batch mode 248–249

basic operations 207batch mode 239–249bypass_registry 244capture phase 207, 211, 213

batch mode 241–248capturing settings and files 213–232

capture_ntfs_attribute 244cmdfile 240command file template 249

profile file 249components 206

COMMANDFILE TXT 207CONFIG INI 206SMA EXE 206SMABAT EXE 206

desktop settings 242editable_connectivity 245Exclude_Drives 245ExcludeFile 247ExcludeFileDescription 247ExcludePath 247file handling commands

Exclude_Drives 245ExcludeFile 247ExcludeFileDescription 247ExcludePath 247IncludeFile 245IncludeFileDescription 246IncludePath 246

file migration 245IncludeFile 245IncludeFileDescription 246IncludePath 246installation 208–211log_file_location 244logdir 241migration

when is it required? 203who performs the transfer? 203

MigrationNote 244Misc_Settings 244network setting 243overwrite_existing_files 244Peer to Peer 251–258

defined 251profile file 254

plain_password 242printers 244profile file 206–207, 213, 231–232

apply phase 207batch mode 242capture phase 207command file template 249location 234Peer to Peer 254

quota 244registry values 243removable_media 244smafile 240smapwd 241supported application migration 217supported operating systems 205system requirements 205tmpdir 241transfer_mode 242tsmpwd 241UserProfiles 243verbose logging 241with ImageUltra Builder 179

Ttarget location 31ThinkCentre 28ThinkPad 24ThinkVantage Technologies 1–2ThinkVantage Tools 2Tivoli Storage Manager 242


Token Ring 268tree structure 103

Uultra-portable image 22–23, 26–27, 124ultra-portable module 196ultra-portable system 196unattended installation

defined 46uninstalling SMA 209user guides 5user information tab

base map settings 115utilities 99

defined in ImageUltra Builder 29

VVBE

See Virtual Boot Environmentvideo driver

ImageUltra Builder 28Virtual Boot Diskette 142

create 157Virtual Boot Environment 139–142Virtual Private Networking 268viruses 259VPN

See Virtual Private Networking

WWEP 269When is system migration required? 203Windows 2000

Access Connections 270Active Protection System 336ImageUltra Builder 20, 28, 89Secure Data Disposal 259Service Pack 4

ImageUltra Builder 66System Migration Assistant 205, 212

Windows 2000 images 26Windows 95

Secure Data Disposal 259System Migration Assistant 205

limitation 229Windows 98

Secure Data Disposal 259

System Migration Assistant 205, 217limitation 229

Windows Installer 46Windows NT 4.0

Secure Data Disposal 259System Migration Assistant 205

Windows NT 4.0 Resource Kit Support Tools 89Windows XP

Access Connections 270Active Protection System 336ImageUltra Builder 20, 89Secure Data Disposal 259System Migration Assistant 205, 212

Windows XP images 26WinRAR 48, 193wireless network considerations 309–314workgroup 116WPA Supplicant 271WPA-PSK 269WPA-TKIP 271

Index 377


(1.0” spine)0.875”<->

1.498”460 <->

788 pages

Using ThinkVantage Technologies: Volume 1

Creating and Deploying Client Systems

®

SG24-7045-01 ISBN 0738491462

INTERNATIONAL TECHNICALSUPPORTORGANIZATION

BUILDING TECHNICALINFORMATION BASED ONPRACTICAL EXPERIENCE

IBM Redbooks are developed by the IBM International Technical Support Organization. Experts from IBM, Customers and Partners from around the world create timely technical information based on realistic scenarios. Specific recommendations are provided to help you implement IT solutions more effectively in your environment.

For more information:ibm.com/redbooks

Using ThinkVantage Technologies: Volume 1Simplification of the PC life cycle process with ThinkVantage Technologies

Simple deployment in complex corporate environments

Use of ThinkVantage Technologies to lower costs

ThinkVantage Technologies bring your IBM PCs one step closer to being self-configured, self-optimizing, self-protecting, or self-healing, to help save you time and money throughout the life of your systems. In short, ThinkVantage Technologies let you focus your attention on your business, rather than on your computer. ThinkVantage Technologies are software tools designed to help customers drive down IT support costs (in particular, the cost of a PC in managing and supporting systems after its initial purchase), increase security and decrease the complexity of today’s IT infrastructure.

This series of Redbooks will help you install, tailor and configure the IBM ThinkVantage Technologies on IBM and OEM desktops.

Using ThinkVantage Technologies, Volume 1: Creating and Deploying Client Systems describes how to create and deploy client systems. The tools covered include:- ImageUltra Builder- System Migration Assistant- Software Delivery Assistant- Secure Data Disposal- Access Connections- Active Protection System

Back cover


