Front cover IBM Platform Management for nagement for ... · International Technical Support Organization IBM Platform Management for Windows July 2004 SG24-7050-00

ibm.com/redbooks

Front cover

IBM Platform Management for nagement for Windows dows

Felix ZalcmannAlbert Chan

Andrew BoltonAnthony Shapiro

Installation of the Platform Management for Windows solution

Configuration of the Windows client and server provisioning

Packaging software applications for distribution

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


International Technical Support Organization

IBM Platform Management for Windows

July 2004

SG24-7050-00

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

First Edition (July 2004)

This edition applies to Version 4, Release 0 and 02 of IBM Platform Management for Windows (product number 6949-15M).

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

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xv

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviiTrademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xixThe team that wrote this redbook. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xixBecome a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxComments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi

Chapter 1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.2 Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.3 What is covered in this book? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.4 What is out of scope? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.5 Reference material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.6 Platform Management for Windows architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.6.1 Platform Management for Windows system overview . . . . . . . . . . . . . . . . . . . . . . 61.6.2 Platform Management for Windows configuration database. . . . . . . . . . . . . . . . . . 61.6.3 Platform Management for Windows end-to-end flow . . . . . . . . . . . . . . . . . . . . . . . 7

1.7 Target environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.7.1 Server environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.7.2 DHCP services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.7.3 Workstation environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 2. Installing Platform Management for Windows . . . . . . . . . . . . . . . . . . . . . . . 132.1 Installation process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.1.1 Microsoft Windows 2003 Server domain controller setup . . . . . . . . . . . . . . . . . . . 142.1.2 Installing support applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.1.3 Security settings modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.1.4 Adding an alias for bbcdb to the DNS server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.1.5 Platform Management for Windows: Setup and maintenance . . . . . . . . . . . . . . . 172.1.6 Configuring Platform Management for Windows: Database setup . . . . . . . . . . . . 182.1.7 Configuring the Platform Management for Windows CID tree . . . . . . . . . . . . . . . 222.1.8 Installation of the Platform Management for Windows tools . . . . . . . . . . . . . . . . . 242.1.9 Installing Platform Management for Windows Phase 2 applications. . . . . . . . . . . 31

2.2 Starting the Platform Administration Center (PAC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352.3 Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Chapter 3. Workstation installation using Platform Management for Windows . . . . . 493.1 The mechanism of the BootDisk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503.2 Creating a BootDisk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513.3 Installing the workstation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603.4 Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Chapter 4. Server install using Platform Management for Windows Phoenix tool . . . 67

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

4.1 The Phoenix tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684.2 Creating a server installation BootDisk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694.3 Server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784.4 Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Chapter 5. Packaging Standard for Platform Management for Windows. . . . . . . . . . . 835.1 Platform Management for Windows software packages . . . . . . . . . . . . . . . . . . . . . . . . 845.2 Phase 2 Application packaging template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845.3 Using the packaging template for application packaging . . . . . . . . . . . . . . . . . . . . . . . 85

5.3.1 Expanding the packaging template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855.3.2 Registering the application in the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895.3.3 Testing the new application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

5.4 Platform Management for Windows Package Builder . . . . . . . . . . . . . . . . . . . . . . . . . . 925.5 Adding packages to an existing group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 935.6 Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Chapter 6. Offline installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 956.1 Offline installation (operating system only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

6.1.1 Boot images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 966.2 Offline installation for 3AServices.com . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

6.2.1 Exporting the Platform Management for Windows database . . . . . . . . . . . . . . . . 976.2.2 Preparing the media with the source files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

6.3 Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Chapter 7. CID synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1117.1 Master CID installation for srv01.3aservices.com . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1127.2 Master CID configuration for srv01.3aservices.com . . . . . . . . . . . . . . . . . . . . . . . . . . 1187.3 Slave CID Installation for srv02.3aservices.com. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1237.4 Verifying master/slave relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1267.5 Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Chapter 8. Hardware integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1298.1 Client hardware integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

8.1.1 Add network support to the BootDisk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1308.1.2 Create a new response file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1338.1.3 Build client and identify missing drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1338.1.4 Add drivers to the CID server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1408.1.5 Build client with OEM-supplied drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

8.2 Server hardware integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1418.2.1 Explanation of hardware200x.ini and adapter200x.ini . . . . . . . . . . . . . . . . . . . . 1428.2.2 Update Phoenix tool with new server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1478.2.3 Add support for third-party mass storage drivers . . . . . . . . . . . . . . . . . . . . . . . . 1488.2.4 Build server with newly added hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

8.3 Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Chapter 9. Platform Management for Windows Web interface . . . . . . . . . . . . . . . . . . 1519.1 Installing and configuring the Web interface for 3aservices.com . . . . . . . . . . . . . . . . 152

9.1.1 Configuring Microsoft’s Active Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1529.1.2 Installing the Web interface components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1629.1.3 Configuring Microsoft’s Internet Information Server . . . . . . . . . . . . . . . . . . . . . . 1659.1.4 Configuring the look and feel of the Web interface . . . . . . . . . . . . . . . . . . . . . . . 1739.1.5 Web-Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1849.1.6 Installing applications from the Web interface. . . . . . . . . . . . . . . . . . . . . . . . . . . 189

9.2 Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

iv Installation, Configuration, and Packaging Using Platform Management for Windows

Chapter 10. Technology integration preview: Integrating IBM ImageUltra Builder. . 19310.1 IBM ImageUltra Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

10.1.1 Requirements for IBM ImageUltra Builder v2.2. . . . . . . . . . . . . . . . . . . . . . . . . 19410.1.2 Installing IBM ImageUltra Builder v2.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19410.1.3 Common ImageUltra terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19610.1.4 Configuring IBM ImageUltra Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19610.1.5 Testing the build process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

Chapter 11. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

Appendix A. Tools to implement the Platform Management for Windows solution . 223Using Package Builder to add an application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

A.0.1 Package Builder requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224A.0.2 Using Package Builder with CID synchronization. . . . . . . . . . . . . . . . . . . . . . . . 224A.0.3 Registering the application in the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228A.0.4 Testing the new application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

Appendix B. Using system log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233System log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234Log file sequencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239How to get IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Contents v

vi Installation, Configuration, and Packaging Using Platform Management for Windows

Figures

1-1 Platform Management for Windows basic architecture . . . . . . . . . . . . . . . . . . . . . . . . 51-2 Platform Management for Windows system overview . . . . . . . . . . . . . . . . . . . . . . . . . 61-3 Platform Management for Windows configuration database . . . . . . . . . . . . . . . . . . . . 71-4 Platform Management for Windows end-to-end flow. . . . . . . . . . . . . . . . . . . . . . . . . . 81-5 3AServices.com. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92-1 3aservices.com environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132-2 Modifying default domain controller settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162-3 Adding an alias for bbcdb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172-4 Platform Management for Windows setup and maintenance . . . . . . . . . . . . . . . . . . 182-5 Platform Management for Windows configuration and maintenance. . . . . . . . . . . . . 192-6 PMfW options: Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192-7 PMfW Database: Active Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202-8 PMfW conditions check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202-9 Configuring Active Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212-10 Successful account creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212-11 CID tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222-12 Configuring standalone CID Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232-13 CID configuration completed successfully . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232-14 Welcome Platform Management for Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242-15 Selecting the PMfW tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242-16 Installing the Platform Administration Center. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252-17 Using Facade and Platform Administration Center . . . . . . . . . . . . . . . . . . . . . . . . . . 262-18 Customer Information panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262-19 Selecting Installation Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272-20 Installing the Phoenix tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272-21 Customer Information panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282-22 Phoenix tool setup type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282-23 Installing BootDisk configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292-24 BootDisk configurator information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292-25 Installation directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302-26 Start Menu Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302-27 BootDisk Configurator v2.0 / v2.02 setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312-28 Welcome to Platform Management for Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . 312-29 Installing Phase 2 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322-30 Selecting Phase 2 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322-31 Database logon screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332-32 Verify applications are registered. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332-33 Application packages (operating systems) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342-34 Platform Administration Center Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352-35 Platform Administration Center - Child forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362-36 Platform Administration Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372-37 CID access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382-38 Creating Master CID Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392-39 Creating a default group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402-40 Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412-41 Selecting products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422-42 Creating a target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422-43 New target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

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

2-44 Search for CID Server screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442-45 Groups and products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452-46 Selecting default group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462-47 Creating multiple targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472-48 List of created targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483-1 Generating an original PMfW v4.0 BootDisk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513-2 Creating the disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523-3 Configure the BootDisk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523-4 Configuring all components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533-5 Starting the 10 configuration steps of a BootDisk in sequence . . . . . . . . . . . . . . . . . 533-6 Editing CCserver.db. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543-7 Editing BBdomain.db . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543-8 Target name mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553-9 Database server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563-10 Operating systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573-11 Operating systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573-12 Slots.lst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583-13 Network settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593-14 Global settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593-15 Run in Real Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603-16 Formatting workstation hard disk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613-17 Select a Detected Network driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613-18 TCP/IP parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623-19 Successful connection to Z: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623-20 Select Hardware in the list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633-21 3aservices.com . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633-22 Enter a computer name for the target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643-23 Applying packages on target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643-24 Windows XP Professional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654-1 Windows 2003 Server Ticket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704-2 New server ticket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714-3 Full mode view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724-4 Slot applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734-5 Diskman Configuration 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744-6 Diskman Configuration 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754-7 Diskman Configuration 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 764-8 Write Ticket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774-9 Disk creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774-10 Disk created. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784-11 Create a new target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784-12 Run in Real Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794-13 Formatting server hard disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794-14 Select a Detected Network driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 804-15 Windows 2003 Server setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 804-16 Platform Management for Windows Bootstrap Loader . . . . . . . . . . . . . . . . . . . . . . . 814-17 Windows 2003 setup continues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814-18 Final reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825-1 Platform Management for Windows package wrapper . . . . . . . . . . . . . . . . . . . . . . . 845-2 Packaging template directory structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855-3 Creating a directory structure for Norton Antivirus. . . . . . . . . . . . . . . . . . . . . . . . . . . 865-4 Identify all files with ibm.packagetemplate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875-5 Search and replace with new package information . . . . . . . . . . . . . . . . . . . . . . . . . . 875-6 Files for symantec.nav.7_61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

viii Installation, Configuration, and Packaging Using Platform Management for Windows

5-7 File structure for CID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895-8 Adding Products using the Platform Administration Center . . . . . . . . . . . . . . . . . . . . 895-9 Product description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 905-10 Product listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 905-11 Select groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 935-12 Selecting products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 946-1 Offline installation directory structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 966-2 Platform Administration Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 986-3 Platform Administration Center - Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 996-4 Copy Database Wizard - Specify How to Copy and Log-File Path . . . . . . . . . . . . . . 996-5 Copy Database Wizard - Specify Target Database . . . . . . . . . . . . . . . . . . . . . . . . . 1006-6 Create MS Access Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1006-7 Copy Database Wizard - Specify Global Copy Attributes . . . . . . . . . . . . . . . . . . . . 1016-8 Copy Database Wizard - Select Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1016-9 Copy Database Wizard - Select Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1026-10 Copy Database Wizard - Select Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1026-11 Copy Database Wizard - Select Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1036-12 Copy Database Wizard - Select Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1036-13 Copy Database Wizard - Select Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1046-14 Copy Database Wizard - Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1046-15 Copy Database Wizard - Select Web-Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1056-16 Copy Database Wizard - Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1056-17 Copy Database Wizard - Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1066-18 Platform Administration Center - Target database. . . . . . . . . . . . . . . . . . . . . . . . . . 1066-19 OffLine directory structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1086-20 OffLine directory structure expanded. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1096-21 Boot devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1107-1 Platform Management for Windows configuration and maintenance utility . . . . . . . 1127-2 PMfW options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1137-3 Configure synchronized CID tree. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1147-4 Create Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1147-5 Please Confirm screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1157-6 CID Tree Synchronization - Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1157-7 CID Tree Synchronization - Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1167-8 CID Tree Synchronization - Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1167-9 Configuration Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1177-10 CID setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1177-11 Platform Administration Center - Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1187-12 Platform Administration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1197-13 CID Synchronization plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1197-14 Synchronized CID Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1197-15 CID Network Controller Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1207-16 Platform Administration Center [Synchronized CID Servers]. . . . . . . . . . . . . . . . . . 1207-17 Platform Administration Center [Synchronized CID Servers] copying files . . . . . . . 1217-18 Enter what files to copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1217-19 Refreshing the CID synchronization servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1227-20 Platform Administration Center [Synchronized CID Servers]. . . . . . . . . . . . . . . . . . 1237-21 CID Synchronization - Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1247-22 CID Synchronization - Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1247-23 Configuration Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1257-24 CID Setup - Configure synchronized CID Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1257-25 Platform Administration Center [Synchronized CID Servers]. . . . . . . . . . . . . . . . . . 1268-1 Exit to DOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Figures ix

8-2 BootDisk network support files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1328-3 Other devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1348-4 Update driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1358-5 Welcome to the Hardware Update Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1358-6 Choose your search and installation options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1368-7 Hardware Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1368-8 Select the device driver you want to install for this hardware . . . . . . . . . . . . . . . . . 1378-9 Install from disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1378-10 Select the device driver you want to install for this hardware . . . . . . . . . . . . . . . . . 1388-11 Finish . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1388-12 Successfully installed driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1398-13 Successful install of devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1408-14 Successful install of devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1418-15 Network connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1448-16 Network adapter properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1448-17 Connection properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1458-18 Adapter properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1468-19 Copy mass storage driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1489-1 Active Directory Users and Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1539-2 Creating a new Organization Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1549-3 New Object - Organization Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1549-4 Active Directory Users and Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1559-5 New Object - Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1559-6 Active Directory Users and Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1569-7 New Object - User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1569-8 New Object - User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1579-9 WebAdmin Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1589-10 WebAdmin Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1589-11 Select Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1599-12 Active Directory Users and Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1609-13 Select Users, Computers or Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1609-14 IBMBB properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1619-15 Select WebAdmins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1619-16 Permission Entry for IBMBB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1629-17 PMfW Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1639-18 WinZip Self-Extractor - BlueWEB.exe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1639-19 C:\Program Files\php listing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1649-20 Internet Information Services (IIS) Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1659-21 Default Web Site Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1669-22 Application Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1669-23 Add/Edit Application Extension Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1679-24 Application Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1679-25 Default Web Site Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1689-26 Add Content Page - index.html . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1689-27 Add Content Page - index.php. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1689-28 Default Web Site Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1699-29 Internet Information Services (IIS) Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1709-30 New Web Service Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1709-31 Add file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1719-32 New Web Service Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1719-33 Web Interface - Setup and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1729-34 IBM BlueWEB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1739-35 Web Interface - Logon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

x Installation, Configuration, and Packaging Using Platform Management for Windows

9-36 Web Interface - standard administrative settings. . . . . . . . . . . . . . . . . . . . . . . . . . . 1759-37 Web Interface - Managing Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1769-38 Web Interface - Managing Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1779-39 Web Interface - WEBpacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1789-40 Web Interface - Advanced administrative settings. . . . . . . . . . . . . . . . . . . . . . . . . . 1799-41 Web Interface - Edit News Bulletin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1809-42 Web Interface - Edit Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1819-43 Web Interface - BlueWEB Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1829-44 Platform Administration Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1859-45 Platform Administration Center - Web-Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1859-46 Platform Administration Center - New Web-Pack . . . . . . . . . . . . . . . . . . . . . . . . . . 1869-47 Platform Administration Center - Search Products . . . . . . . . . . . . . . . . . . . . . . . . . 1879-48 Platform Administration Center - Assigned Products. . . . . . . . . . . . . . . . . . . . . . . . 1879-49 Platform Administration Center - Search Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . 1889-50 Platform Administration Center - Authorized Groups. . . . . . . . . . . . . . . . . . . . . . . . 1899-51 Web Interface -Add New Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1909-52 Web Interface -Add New Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1919-53 Web Interface - Software On Demand. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1919-54 Web Interface - Installation Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19210-1 Install Shield Wizard for IBM ImageUltra Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . 19510-2 Choose Destination Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19510-3 IBM ImageUltra Builder icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19610-4 Create Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19710-5 Open ImageUltra repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19710-6 Browse for repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19810-7 IBM ImageUltra Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19810-8 Repository Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19910-9 Platform Management for Windows folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20010-10 Create Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20110-11 Name the module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20110-12 Select the PMfW template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20210-13 Viewing the newly created module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20210-14 Building a module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20310-15 Review the scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20410-16 Create Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20410-17 Naming the module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20510-18 Unattend.txt template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20610-19 Build the custom unattend.txt module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20710-20 Review your scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20710-21 Creating a Base Map for 3aservices.com . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20810-22 Using PMfW Template for base map creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20910-23 3aservices.com base map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21010-24 Add the operating system to the base map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21110-25 Adding the operating system and Unattend.txt . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21110-26 Base map settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21210-27 Customizing User Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21310-28 Changing the default user name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21410-29 Deploy over network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21510-30 ImageUltra Deploy Diskette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21510-31 Repository location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21610-32 Network information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21610-33 “Connect As” information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21710-34 Create BootDisk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Figures xi

10-35 Create application module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21810-36 Create Module - PMfW Platform Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21910-37 PMfW template platform preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21911-1 Package Builder - General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22511-2 Package Builder - Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22511-3 Application Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22611-4 Copy source code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22611-5 Select setup program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22711-6 Generate files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22711-7 Successful file creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22811-8 Adding Products using the Platform Administration Center . . . . . . . . . . . . . . . . . . . 22811-9 Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22911-10 Product listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

xii Installation, Configuration, and Packaging Using Platform Management for Windows

Tables

1-1 Server configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101-2 DHCP address configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101-3 DHCP scope options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101-4 Workstation environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102-1 Server configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142-2 DHCP address configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142-3 DHCP scope options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144-1 Customization files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684-2 SRV02 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694-3 UNATTEND.TXT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714-4 DCPROMO.TXT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726-1 Source preperation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1079-1 Server configuration srv03.3aservices.com. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1529-2 Web Interface file copying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1649-3 Server connection settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1829-4 Common BlueWEB settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1829-5 Version Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1839-6 Theme settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1839-7 News text values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1839-8 Link lists values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184B-1 System log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

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

xiv Installation, Configuration, and Packaging Using Platform Management for Windows

Examples

3-1 wpat01.loc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505-1 request.txt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 915-2 symantec.nav.7_61.ref.3103.log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 918-1 VENDOR-ID and DEVICE-ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1318-2 E100B.INI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1328-3 NDIS.PCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1328-4 NDIS.TXT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1328-5 Update pc-model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1338-6 Update pc-crole . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1338-7 Set oempnpdriverspath to empty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1338-8 Update oempnpdriverspath with location of OEM-supplied drivers . . . . . . . . . . . . . 1418-9 hardware2003.ini . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1428-10 Information from IBMPCI.EXE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1438-11 Adapter2003.ini . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1468-12 Adding a server to hardware2003.ini . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1478-13 Adding a server to hardware2003.ini . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1478-14 txtsetup.oem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1498-15 Add a new adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1498-16 Adapter settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14910-1 3aervices.com UNATTEND.TXT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20611-1 request.txt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23011-2 rarlab.winrar.3_30.red.3103.log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

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

xvi Installation, Configuration, and Packaging Using Platform Management for Windows

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

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

IBM Eserver®Redbooks (logo) ™iSeries™xSeries®Domino®ImageUltra™

IntelliStation®IBM®Netfinity®Redbooks™Redbooks (logo)™ServeRAID™

ThinkPad®ThinkVantage™Tivoli Enterprise™Tivoli®

The following terms are trademarks of other companies:

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

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

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

xviii Platform Management for Windows: Installation, Configuration, and Packaging

Preface

This IBM® Redbook targets those who have the need to standardize the way they deal with their Microsoft® Windows® platform. This redbook will help you to install, tailor, and configure the new IBM Platform Management for Windows solution.

IBM Platform Management for Windows is designed to help customers reduce their cost of managing a client or a server in a Microsoft Windows environment, in order to increase the security and to decrease the complexity of the IT infrastructure.

IBM Platform Management for Windows is a common Windows platform for large-scale rollout of Windows 2000 and XP to clients, and Windows 2000 and 2003 to servers. Platform Management for Windows can either be used stand-alone or tightly integrated with systems management frameworks such as Tivoli® or Microsoft SMS. It is targeted towards customers having anything between 100 and 100,000 clients, and 5 to 500 servers.

IBM Platform Management for Windows is integrated with the IBM ThinkVantage™ tools such as IBM ImageUltra™ Builder, and contains a set of additional automated deployment tools and procedures for roll out of clients, servers, and platform infrastructure components. It also includes an LDAP, or Active Directory-based data repository for customer platform parameters, and tools for Windows 2000/XP administration.

Platform Management for Windows is based on innovative and truly dynamic software distribution technology (which is totally hardware-independent, contrary to usual “imaging-based” methods), and inherently supports many different server, desktop, and notebook models from a wide variety of manufacturers.

This redbook provides a broad understanding of the architecture, design, and design guidelines that will help you to manage a Microsoft® Windows platform from a client and server perspective. It will cover the provisioning and platform management of the following operating systems: Microsoft® Windows 2000, Microsoft® Windows XP, Microsoft® Windows 2000 Server, and Microsoft® Windows 2003 Server on IBM and OEM systems.

The team that wrote this redbookThis redbook was produced by a team of specialists from around the world working at the Global Windows Platform Development Center, Vienna, Austria.

Felix Zalcmann is the Global Offering and Product Manager of IBM Platform Management for Windows with the Strategy & Design Authority of Strategic Outsourcing, IBM Global Services in Europe. He started his career as an IT manager of the Greatest Austrian Tradeshow company before joining IBM Global Services in 1997 as an IBM ̂iSeries™ instructor. He has held the following positions in IBM Global Services before taking over his actual role: Europe Middle East Africa e-business hosting Services Technical Offering Manager and Central and Eastern Europe ITS Offering Manager for Infrastructure and Systems Management Services. He is the co-author several IBM Redbooks™ covering Domino® for iSeries topics. He is a frequent speaker and presenter at international technical meetings and trade shows in the USA and Europe.

Albert Chan is an I/T Architect for Strategic Outsourcing, IBM Global Services in Canada. He has 11 years of IT experience and has worked with IBM for the last three years. He specializes in working with customers to develop systems management solutions. Recently,

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

he has worked with international teams to optimize standard methodologies for delivering services to customers. He is a co-author of the redbook Using ThinkVantage Technologies: Volume 1 - Creating and Deploying Client Systems Client Systems, SG24-7045-00. He holds a bachelor’s degree in Economics and Computer Science from the University of Toronto. He is a Microsoft® Certified Systems Engineer (MCSE) and IBM ̂Certified Expert for xSeries®.

Andrew Bolton is an SOE Consultant in the National Operating Systems Integration team in Sydney, Australia. He has ten years experience working in IT. As an SOE Consultant for IBM Australia, Andrew specializes in the design and deployment of Microsoft® operating system builds. He holds a bachelor’s degree in Information Technology from Charles Sturt University in Australia. He is a Microsoft® Certified Systems Engineer (MCSE) and Citrix Certified Administrator (CCA).

Anthony Shapiro is an Distributed Client Support (DCS) IT Specialist for the Client Technology team for Strategic Outsourcing, IBM Global Services, Sweden. He has seven years of experience working in IT, mainly within the finance sector. As a DCS IT Specialist, Anthony specializes in the design and implementation of end-user platforms based on Microsoft® Windows operating systems. Currently, he is providing consultancy services to several major Platform Management for Windows implementation projects. Anthony is evolved with the Nordic implementation of Platform Management for Windows, helping Strategic Outsourcing optimize and standardize Microsoft® Windows Server and Workstation platforms.

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

From the IBM Global Windows Platform Development Center, Vienna, Austria in alphabetic order:

Philippe DeplanqueHans EggerHans GugliaAndreas LandauerGerald PapeMarkus RaditschClaus ReichelFranz A. StefanMaximilian StrablegMax Zeilinger

From the International Technical Support Organization (ITSO) San Jose:

Maritza M. Dubec- Technical Editor

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.

xx Platform Management for Windows: Installation, Configuration, and Packaging

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:

� 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. JLU Building 107-23605 Highway 52NRochester, Minnesota 55901-7829

Preface xxi

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

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



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

xxii Platform Management for Windows: Installation, Configuration, and Packaging

Chapter 1. Introduction

The NetWorkStation Management service offering for client and server platforms today is often based on Microsoft Windows operating systems.

Although each customer is unique, very often these platform build projects have the same requirements concerning hardware, applications, and mode of operation.

Instead of using the same standards for all platforms, most of these projects create their own platform development teams, often with limited experienced developers. Once the development of such platforms is finished, the team usually disappears.

This results in three major issues:

� Lack of quality and stability of the platform; all teams make the same mistakes on all the projects.

� New experience and knowledge disappears at the end of the project.

� Total costs of development are very high.

The objective of Platform Management for Windows is to bring together the best-of-breed and best practice approach, methods, and tools for Windows platform management. The Platform Management for Windows community works to constantly improve the methods and tools for Windows platform management by leveraging the capabilities of our teams and products across the global and multi-product IBM organization.

Platform Management for Windows is a set of designs, design guidelines, tools, and a set of ready-to-use applications for installing clients and servers.

The outcome is focused on reducing costs and efforts by speeding up tasks for:

� Designing the solution� Developing the platform “images” for clients and servers� Deploying clients and servers� Maintaining and supporting clients and servers

1

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

Platform Management for Windows highlights� Covers automatic rollout of clients (desktops, notebooks) and servers (resulting in

significant synergy effects)

� Uses flexible and dynamic Windows native install, instead of cloning for a maximum of HW-independence

� Is not a rollout-only solution, but covers the whole lifecycle of clients and servers - true Platform Management.

� Has full Microsoft Windows 2003 Server support, including automatic rollout

� Does not require any dedicated servers, but uses file storage anywhere on the network (also through Linux Samba) or local hard disk, CD-ROM, DVD

� Supports pull functionality through the new Web interface. Includes a wide range of standard business applications

� Has an image repository available for sharing in organizations

� Can be easily enhanced through customer-specific applications through the Platform Management for Windows packaging standard

� Provides flexible, role-based installation mechanisms (role, location, business unit, language)

2 Platform Management for Windows: Installation, Configuration, and Packaging

1.1 AssumptionsThis redbook is targeted for IT specialists who are involved in client and server deployment techniques. We assume that the reader has good knowledge of the Microsoft Active Directory infrastructure. The reader should be aware of software distribution concepts and also be familiar with basic operating system installation techniques.

Windows Scripting Host (WSH) is used for the scripts that make up the Platform Management for Windows solution, so it is assumed that the reader also has an understanding of Windows scripting and the different tools used to produce scripts.

You can use the solution as is, but the examples of source code from our scripts may need to be modified to customize the solution. The solution is flexible enough to support any sort of naming standard for machines in use at the customer site.

1.2 ObjectivesOur objectives are to provide a real-world scenario that can be used and expanded on by:

� Guiding new users through the steps needed to install and configure Platform Management for Windows

� Explaining the different tools and functions

� Showing the integration of other independent solutions with Platform Management for Windows

� Describing common pitfalls during installation and configuration

� Discussing undocumented tips and tricks

1.3 What is covered in this book?We cover the different features and topics, which combined, make up the Platform Management for Windows solution:

� Platform Management for Windows configuration and maintance utility

User interface for installing the different components of Platform Management for Windows

� Platform Administration Center (PAC)

The PMfW Platform Administration Center is the administrative focal point for all Platform Management for Windows tools and utilities.

� BootDisk Configurator

An interface for building bootdisks

� Phoenix tool

An application for building and configuring server tickets and boot disks.

� Online and offline configuration

Note: Following the step-by-step instructions in this book should provide the user with a functional Platform Management for Windows environment that can be used for test purposes.

Chapter 1. Introduction 3

Exporting the Platform Management for Windows databases to removable media for installation at low bandwidth or disconnected sites.

� Platform Management for Windows Web interface

Interface for pull software distribution through the Web.

� CID synchronization

Configuration, installation, and distribution (CID) servers are SMB compatible file shares that are used to store product packages. The synchronization tools allow automatic replication of these CID packages between an arbitrary number of CID servers.

� Hardware integration

Adding new hardware to the hardware portfolio

� Packaging

Packaging applications using the Platform Management for Windows standard

� Integration of independent solutions

Using IBM ImageUltra builder with Platform Management for Windows

1.4 What is out of scope?The following subjects are considered too large to be included in this book. Where possible, a reference to related reading material is given:

� Microsoft Active Directory

http://www.microsoft.com/windows2000/technologies/directory/ad/

� Windows scripting host

http://msdn.microsoft.com/archive/default.asp?url=/archive/en-us/dnarwsh/html/msdn_wsh_wp.asp

� IBM Directory Server Version 5.1 Installation and Configuration Guide

http://www-1.ibm.com/support/docview.wss?rs=0&context=SWI20&q1=ibm+directory+server&uid=swg27002425&loc=en_US&cs=utf-8&cc=us&lang=en

� IBM Redbook

An Introduction to Tivoli Enterprise™, SG24-5494

� IBM Redbook

Using ThinkVantage Technologies: Volume 1 Creating and Deploying Client Systems, SG24-7045

1.5 Reference materialThe following material can provide the user with detailed information regarding Platform Management for Windows. These documents can be found on the distribution media:

� PMFW 4.0 - Packaging Standard V3.0� PMFW 4.0 - Software distribution� PMfW 4.0 - Technical background� PMFW 4.0 - Tools and utilities� PMFW 4.0 - User’s guide� PMFW 4.0 - What is new



1.6 Platform Management for Windows architectureThis section outlines the Platform Management for Windows components, which support the distribution of software products to Platform Management for Windows clients.

As shown in Figure 1-1, the basic architecture of Platform Management for Windows is a framework-based solution that offers methods and functions that assist in building a customer platform. While Platform Management for Windows itself will provide all the basic functionalities right out of the box, it only shows its full potential when it is adapted and enhanced according to the specific customer needs.

Platform Management for Windows delivers the major building blocks necessary to build Windows-based platforms for clients and servers while still being open and adaptable to entirely fulfill the customer needs.

Figure 1-1 Platform Management for Windows basic architecture

Phas

e 0

Phas

e 2

Stea

dy-S

tate

Phas

e 1

PMfWSoftware Packages

CID Treeand IUB

Repository

LDAP/ADSDatabase

Phoenix

PlatformAdministration

Console

Web InterfaceUser Pull

Web Interface

Systems Management Environments(Tivoli, SMS, ...)

Pristine SetupProcess

1

1

Slot Modules(Diskpart)

(DNS)(DHCP)

(Systems Mgmt Endpoint)[...]

Pristine SetupProcess

Software InstallationDispatcher (SID)

Valid in Pristine SetupProcess AND Steady-State

Delta Checker

ImageUltraBuilder

Imag

eUltr

a

Plat

form

Man

agem

ent f

or W

indo

ws

PMfW

Faç

ade


1.6.1 Platform Management for Windows system overviewAs shown in Figure 1-2, the system overview of Platform Management for Windows is a management and a deployment part. The management part consists of the user interfaces, which pass their request through the access layer to the central management site.

Figure 1-2 Platform Management for Windows system overview

1.6.2 Platform Management for Windows configuration databaseThe Platform Management for Windows configuration database is held in an LDAP tree. The database contains information on targets, groups, and products. This information is used to deliver and install applications to Platform Management for Windows clients and servers.

Figure 1-3 shows an example of a LDAP tree. Some details have been omitted for the sake of simplicity.

Central Management Site

User Interfaces

PACPhoenixCID SyncBootDisk ConfigConfig and Maintenance

Access Layer

CID Tree (FileStorage)

External Systems Management Environment(For example, Tivoli)

Central Database Access

PMfW ConfigurationDatabase (LDAP)

CID Tree SynchronizationConfiguration Component

Remote Location PMfW Target

PMfW ConfigurationDatabase

(Relational)



...(OR)...

CID Tree Synchronization

CID Synchronization

PMfW ConfigurationDatabase

(Relational)

PMfW Client Component

The target computersmight have excerpts fromthe CID Tree and/or theConfiguration databaselocally to empowermobile users.


Figure 1-3 Platform Management for Windows configuration database

1.6.3 Platform Management for Windows end-to-end flowThe automated pristine set-up process (pristine installation) provides a convenient way to roll out or reinstall machines with very little user interaction. To perform a pristine installation means to provide a boot medium to the target (either a diskette or a CD-ROM or a network boot image), boot it, and enter some general information needed to identify that client in the configuration database. After the information is entered, the target will perform a fully automated installation and configuration of the appropriate software packages. After the automated pristine installation has finished, the target can be handed over to the user, and no further customization or configuration steps have to be performed.

Figure 1-4 shows that the end to end flow for targets installing with Platform Management for Windows is divided into four stages.


Figure 1-4 Platform Management for Windows end-to-end flow

1. Phase 0

a. The target boots using diskette, CD-ROM, DVD-ROM, network services, or other removable media.

b. The target connects to the CID or repository share, and presents a menu to the user.

c. The user makes several choices to configure the target.

d. An unattended installation is started.

2. Phase 1

a. The critical slot applications are installed.

b. A connection to the Platform Management for Windows configuration database is made.

c. The target information is supplied.

d. Group and product configuration for the specific target is resolved.

3. Phase 2

a. A connection is made to the Platform Management for Windows configuration database.

b. The target information is supplied.

c. Installation source, logon credentials, and product configuration are resolved.

d. Product installation is initiated using the information supplied by the Platform Management for Windows configuration database.

4. Target ready state

PMfW Target

Phase 0Windows OS

Steady-State Platform MgmtSoftware Applications

Phase 2Software Applications

Phase 1Slot Modules, SysMgmt


a. The target is ready to receive software packages through software distribution, Platform Management for Windows BlueWeb Web interface, or any other software distribution tool in place (such as Tivoli or SMS).

1.7 Target environment

As shown in Figure 1-5, throughout this book we will be using a target environment based on a simple Microsoft Active Directory domain model running Windows Server 2003 standard edition.

The fictitious company 3AServices consists of one root domain (3AServices.com).

Domain name resolution and DHCP services will be supplied by the domain controller located in the root domain. This domain controller will also host the master copy of the CID file structure.

The second controller will host a replicated copy of the CID structure while a member server of this domain will run the Web services needed for the Platform Management for Windows Web interface.

All servers are situated on the same local area network (LAN), though several of the targets in the domain do not have reliable LAN connections, and will therefore be installed through removable media.

Figure 1-5 3AServices.com

Attention: The installation of Platform Management for Windows in 3aservices.com is based on the release 4.0 of Platform Management for Windows.

SRV02Domain ControllerSlave CID Server

SRV03Member Server

IISBlueWEB

3AServices.com

SRV01Domain Controller

DNSDHCP

PMfW DatabaseMaster CID Server

Computer Computer Computer Computer Computer Computer


1.7.1 Server environmentAll servers are running the Windows Server 2003 standard edition. Table 1-1 shows the basic server configuration. Unless specified in this book, all values are default. The operating system is installed to the C:\ partition, and where applicable the D:\ partition is used to house the CID file structure.

Table 1-1 Server configuration

1.7.2 DHCP servicesDHCP will be used to supply IP addresses to all targets installed on the LAN.

The DHCP address configuration is shown in Table 1-2.

Table 1-2 DHCP address configuration

The configured DHCP scope options are shown in Table 1-3.

Table 1-3 DHCP scope options

1.7.3 Workstation environmentAll target workstations will be installed with Windows XP Professional SP1. Unless specified in this book, all values are default. The operating system is installed to the C:\ partition. The used workstation environment is shown in Table 1-4.

Table 1-4 Workstation environment

Server Name Role IP Address Hardware

srv01.3AServices.com Root domain controllerDNS servicesDHCP servicesMaster CID repository

10.1.0.10 IBM Netfinity® 4500512 Mb memory36 Gb disk

srv02.3AServices.com Second domain controllerSlave CID repository

10.1.0.11 IBM X series 330

srv03.3AServices.com Member serverIISPlatform Management for Windows Web interface

10.1.0.12 IBM Netfinity 4500512 Mb memory36 Gb disk

Scope 10.1.0.0

Address Pool 10.1.0.100 > 10.1.0.200

Option Name Vendor Value Class

003 Router Standard 10.1.0.10 None

006 DNS Servers Standard 10.1.0.10 None

015 DNS Domain Name Standard 3AServices.com None

Workstation Name Format Manufacturer Model

WKS01 Desktop IBM IntelliStation®


WKS02 Desktop Compaq EVO D300

WKS03 Desktop Dell PowerEdge 500SC

WKS04 Mobile IBM T30

WKS05 Mobile Compaq Armada M300

WKS06 Mobile Dell Latitude C800

Workstation Name Format Manufacturer Model



Chapter 2. Installing Platform Management for Windows

IBM Platform Management for Windows (PMfW) can be customized based on your organizational needs. This can range from simple standard installations of the Platform Management for Windows environment to highly complex scenarios. The purpose of the chapters is to compile a basic installation that will allow for custom-tailoring within your organization.

This chapter provides detailed instructions for installing Platform Management for Windows in 3aservices.com, based on the environment shown in Figure 2-1.

Figure 2-1 3aservices.com environment

2

SRV02Domain ControllerSlave CID Server

SRV03Member Server

IISBlueWEB

3AServices.com

SRV01Domain Controller

DNSDHCP

PMfW DatabaseMaster CID Server

Computer Computer Computer Computer Computer Computer


2.1 Installation process3aservices.com will be setting up a Platform Management for Windows environment. The next steps will cover the following tasks to accomplish this:

1. Set up a Microsoft Windows 2003 Domain Controller.

2. Install the Microsoft Windows support applications (Microsoft Windows 2000 Resource Kit and Microsoft Windows Support Tools).

3. Create an alias called bbcdb on the DNS server. This alias will be used by Platform Management for Windows targets (servers and clients) to connect to the configuration database.

4. Prepare the Windows domain.

5. Prepare the directory server.

6. Set up a CID server (configuration installation and distribution server).

7. Install several software packages on the CID server.

8. Customize the installation using the Platform Administration Center (PAC) tool.

2.1.1 Microsoft Windows 2003 Server domain controller setupThis section outlines the setup required for the 3aservices.com Microsoft Windows 2003 server that will be used for the installation of Platform Management for Windows.

3aservices.com is using a standard Microsoft Windows 2003 Server installation with the following customizations:

� Two hard disk partitions (C: and D:) are configured, where C: contains the Microsoft Windows 2003 Server operating system. D: will be used for the Platform Management for Windows environment.

� The following Microsoft Windows 2003 Server configuration (Table 2-1) is used.

Table 2-1 Server configuration

� The used DHCP address configuration and the DHCP scope options are shown in Table 2-2 and Table 2-3.

Table 2-2 DHCP address configuration

Table 2-3 DHCP scope options

Server name Role IP address Hardware

srv01.3AServices.com Root domain controllerDNS servicesDHCP servicesMaster CID repository


Scope 10.1.0.0

Address pool 10.1.0.100 > 10.1.0.200

Option name Vendor Value Class

003 Router Standard 10.1.0.10 None

006 DNS Servers Standard 10.1.0.10 None


2.1.2 Installing support applicationsInstall the following Microsoft Windows support applications, as they will be needed later on:

� Microsoft Windows 2000 Resource Kit� Microsoft Windows Support Tools from the Windows 2003 Server CD (\support\tools)

3aservices.com will be using the Microsoft Windows 2003 Server operating system. If using Windows 2000, install the Windows 2000 support tools.

2.1.3 Security settings modificationOur 3aservices.com will modify some of the security settings on their domain controllers to allow workstations connecting during an installation to function. By default, the security settings of Microsoft Windows 2003 domain controllers require server message block (SMB) signing and encryption. Older clients (such as DOS workstations, etc.) do not have SMB packet signing enabled, and are therefore not able to communicate with a Microsoft Windows Server 2003 domain controller without the following changes.

On the Microsoft Windows 2003 domain controllers, the following setting must be modified under the Default Domain Controller Security Settings (Figure 2-2).

Start the default domain controller security settings and change the following settings (see Figure 2-2).

Microsoft Network Server: Digitally Sign Communications (always) -> DISABLED

015 DNS Domain Name Standard 3AServices.com None

Option name Vendor Value Class

Note: When installing the items above, accept the default installation directories. The installation described in this book will use these default directories.

Chapter 2. Installing Platform Management for Windows 15

Figure 2-2 Modifying default domain controller settings

Run GPUPDATE.EXE from a command prompt to apply changes.

2.1.4 Adding an alias for bbcdb to the DNS serverMachines that will be installed using Platform Management for Windows will first search for a server that is registered with their system:

Registry key: HKLM\System\BlueBase\SWD\DBServer

This server is the configuration database server that contains all the Platform Management for Windows configuration and software distribution data. If this key contains an incorrect value, the installation of the target will not work.

Furthermore, if no registry key is found for DBServer, the machines will search for bbcdb. To ensure the machines will find the server that contains the Platform Management for Windows

Important: Features within Platform Management for Windows requires authentication to the domain controller at the DOS level. In order to do this, the digitally sign communications must be disabled. See http://support.microsoft.com/default.aspx?scid=kb;en-us;811497

and

http://support.microsoft.com/default.aspx?scid=kb;en-us;823659

for more information.

Tip: GPUPDATE.EXE is a Microsoft utility that is used to update group policy settings. It is used to manually update any changes that are made to group policies. This still does not force an immediate update of the local settings. So, allow a few minutes to pass.




configuration and software distribution data under both circumstances, the following alias has to be created in the DNS server.

Add a new alias for bbcdb, which will provide name resolution to the configuration database server.

In this example, bbcdb will point to srv01.3aservices.com as shown in Figure 2-3.

Figure 2-3 Adding an alias for bbcdb

2.1.5 Platform Management for Windows: Setup and maintenanceThe environment has now been prepared for the installation of Platform Management for Windows. The following section will provide the steps required to install the solution.

Insert the Platform Management for Windows Setup and Maintenance CD. The screen shown in Figure 2-4 will appear (run Setup.exe if this screen does not appear).

Important: It is important to have a Platform Management for Windows license key before the installation commences.


Figure 2-4 Platform Management for Windows setup and maintenance

These are the steps:

1. From the Platform Management for Windows Setup and Maintenance screen, click Install PMfW Setup.

2. From Install PMfW Configuration and Maintenance, click Install.

3. At the Welcome Screen, click Next.

4. Read and accept the license agreement, then click Next.

5. From the Enter Customer Information and Install PMfW for all users screen, click Next.

6. Select Complete Install and click Next.

7. From the Ready to Install Program screen, click Install.

8. From the Install Shield Wizard Completed screen, click Finish.

9. Click Exit to close the main installation screen.

2.1.6 Configuring Platform Management for Windows: Database setupThis section deals with the Platform Management for Windows Database setup. 3aservices.com will set up the database for Active Directory:

1. To setup the database, click Start ->All Programs ->IBM PMfW ->PMfW Configuration and Maintenance

2. From the Welcome screen, click Next, and the screen in Figure 2-5 is shown.


Figure 2-5 Platform Management for Windows configuration and maintenance

3. The PMFW Options screen will appear. Select DATABASE and click Next as shown in Figure 2-6.

Figure 2-6 PMfW options: Database

4. From the PMfW Database window, select Microsoft Active Directory and click Next, as do not use the IBM Tivoli Directory Server in our example. See Figure 2-7.


Figure 2-7 PMfW Database: Active Directory

5. We have installed the Microsoft Windows Support Tools in an earlier step, so click Next on the PMfW Conditions check panel to proceed as shown in Figure 2-8.

Figure 2-8 PMfW conditions check

6. From the AD Configuration window, enter the following information to set the Active Directory configuration for Platform Management for Windows, and click Configure as shown in Figure 2-9:

– SWD UserID: 3ASERVICES\SWDDISK– SWD Password: Passw0rd– Confirm Password: Passw0rd


Figure 2-9 Configuring Active Directory

7. When the Please Confirm window is shown, click YES to confirm account creation.

– This part of the installation creates the SWDDSK ID with the password provided. A series of DOS windows will appear during the account creation process.

8. If the account creation has completed properly, you will see a GREEN status box Finished configuring database(AD)... as shown in Figure 2-10. Click Exit.

Figure 2-10 Successful account creation

9. Click Yes to confirm the exit.


2.1.7 Configuring the Platform Management for Windows CID treeTo configure the Platform Management for Windows configuration, installation and distribution (CID) tree, follow the steps described below:

1. Click Start -> All Programs -> IBM PMfW -> PMfW Configuration and Maintenance

2. From the Welcome window, click Next.

3. From the PMfW Options window, select CID Tree (do not select Synchronized) and click Next as shown in Figure 2-11.

Figure 2-11 CID tree

4. From the CID setup window, enter the following information and click Configure:

– CID User: 3ASERVICES\SWDDSK– Password: Passw0rd– CID Path: D:\CID


Figure 2-12 Configuring standalone CID Server

5. From the Create Directory window, click YES.

6. From the confirmation window, click YES to check the SWDDSK ID.

7. Take note of the green status box CID configuration completed successfully. Click Exit.

Figure 2-13 CID configuration completed successfully

8. Click YES to exit.


2.1.8 Installation of the Platform Management for Windows toolsTo install and configure the Platform Management for Windows tools, please follow the following steps:

1. Click Start ->All Programs ->IBM PMfW ->PMfW Configuration and Maintenance.


Figure 2-14 Welcome Platform Management for Windows

3. The next screen you see is the PMfW Options window, select PMfW Tools, click Next as shown in Figure 2-15.

Figure 2-15 Selecting the PMfW tools


Installing the Platform Administration Center (PAC)The next steps describe the installation of the Platform Administration Center as one of the Platform Management for Windows Tools:

1. From the PMfW Tools window, click Platform Administration Center (PAC); see Figure 2-16.

Figure 2-16 Installing the Platform Administration Center

2. This will lead you to the Welcome screen, click NEXT.

3. From the Using Facade and Platform Administration Center window, read the message and click Next as shown in Figure 2-17.

Note: The Platform Management for Windows tools do not have to reside on the server. We recommend installing these tools on a machine where the administrator will be working. Our example will install these tools on the same machine as the server.


Figure 2-17 Using Facade and Platform Administration Center

4. When the licence agreement pops up, accept the license agreement and click Next.

5. The Install Shield Wizard shows now the Customer Information window, click Next as shown in Figure 2-18.

Figure 2-18 Customer Information panel

6. In Figure 2-19, select Complete for the setup type and click Next.


Figure 2-19 Selecting Installation Type

7. On the next screen, click Install to commence installation.

8. After a successful installation, click Finish.

Installing the Phoenix toolTo install the server configuration tool Phoenix, you have to follow the steps described below:

1. From the PMfW Tools windows, click Phoenix as shown in Figure 2-20.

Figure 2-20 Installing the Phoenix tool

2. From the IBM PMfW Phoenix welcome window, click Next.

3. Accept the license agreement for the Phoenix tool and click Next.


4. Enter customer information and click Next; see Figure 2-21.

Figure 2-21 Customer Information panel

5. From the Setup Type window in Figure 2-22, select Complete for the setup type and click Next.

Figure 2-22 Phoenix tool setup type

6. In the following windows, click Install to commence installation.

7. After a successful installation, click Finish.


Installing BootDisk configuratorTo install the BootDisk configurator as part of the Platform Management for Windows tools, follow the steps described below:

1. In the PMfW Tools windows in Figure 2-23, click BootDisk configurator.

Figure 2-23 Installing BootDisk configurator

2. This will guide you to the Setup Window, click Next

3. Read the important information and click Next; see Figure 2-24.

Figure 2-24 BootDisk configurator information

4. When the option to select the Destination Directory is shown in Figure 2-25, accept the default and click Next.


Figure 2-25 Installation directory

5. Accept the default on the Select Start Menu Folder screen and click Next, as shown in Figure 2-26.

Figure 2-26 Start Menu Folder

6. Click Install to commence installation.

7. When the setup has finished, the screen is shown as in Figure 2-27. Uncheck Launch Application now and click Finish.

Note: The installation path must not contain spaces.


Figure 2-27 BootDisk Configurator v2.0 / v2.02 setup

8. From the PMfW Tools window, click BACK. (This will return you to the PMfW Options screen.)

2.1.9 Installing Platform Management for Windows Phase 2 applicationsThe next steps describe what needs to be done to install Platform Management for Windows Phase 2 applications:

1. Click Start ->All Programs -> IBM PMfW ->PMfW Configuration and Maintenance.


Figure 2-28 Welcome to Platform Management for Windows


3. From the PMfW Options window, select Phase 2 Applications and click Next.

4. Under Locate Source to execute (as shown in Figure 2-29) click Launch to start the PackageInstaller.exe.

Figure 2-29 Installing Phase 2 Applications

5. Select ibm.cleanup.1_0.ref.3100 and ibm.shutdown.ref.1_102.3100, and assign the installation options as in the following illustration; see Figure 2-30:

– ibm.cleanup.1_0.ref.3100 - Install, Register in Dat, Assign Multiple– ibm.shutdown.1_102.ref.3100 - Install, Register in Dat, Assign Multiple

Figure 2-30 Selecting Phase 2 Applications

6. Click OK.


7. When presented the Logon to the Database window as shown in Figure 2-31, log on as Administrator and click OK.

Figure 2-31 Database logon screen

8. From the Package Installer window, click NO to not display the log file.

Figure 2-32 Verify applications are registered

Attention: Do not click OK as in Figure 2-32. Clicking OK will restart the selected package installation.


9. Insert the Platform Management for Windows Application Packages CD, and click Browse beside Source Directory for Packages.

10.Select the location of the package files from CD. They will be in the Software Packages directory on the CD. For this installation, the files are in E:\Software Packages.

11.Select the following and click 3rd Party Code, as shown in Figure 2-33:

– Windows 2003 Server

<ms.w52.srvstd_sp0.os.3200> - Install, Register in Dat, Operating Syst

– Windows XP Professional

<ms.wxp.pro_sp1.os.3200> - Install, Register in Dat, Operating Syst

The packages will copy from CD. This will take several minutes.

Figure 2-33 Application packages (operating systems)

12.Enter the login information for the database. Click OK.

13.From the Package Installer window, click NO to not display the log file.

14.Click Exit.

Note: The bottom left of Figure 2-32 on page 33 shows... registered OK. This confirms that the packages were installed.

Tip: To refresh the CD contents on the screen, click Browse (beside Source Directory for Packages). This will update the information on the current screen.

Important: You must agree to the End User License Agreements (EULAs) to continue with the installation.

Attention: Do not click OK. Clicking OK will restart the selected package installation.


15.Click Exit to complete Install Phase 2 Applications.

16.Click Yes to confirm the exit.

2.2 Starting the Platform Administration Center (PAC)To start using the Platform Administration Center tool, the following steps must be performed:

1. Click Start -> All Programs -> IBM PMfW -> Platform Administration Center.

2. In the Platform Administration Center Login screen shown in Figure 2-34, enter the user information and click OK.

Figure 2-34 Platform Administration Center Login

3. When presented the Checking License-Key window, click OK.

4. Enter Import License Key. Browse for your license key. Click OK when complete.

5. The Platform Administration Console will appear.

Tip: Click Tools -> Options from the file menu and check Child Forms - Activate already open Container Form of a Type (do not always open a new one). This will prevent multiple screens of the same task opening in the PAC. See Figure 2-35.


Figure 2-35 Platform Administration Center - Child forms

Configuring the system defaults of the PAC1. Click System Defaults from the left pane as shown in Figure 2-36.


Figure 2-36 Platform Administration Center

2. Click the CID Access tab.

3. Enter the following information; see Figure 2-37 on page 38.

– Password: Passw0rd– Userid: @3AServices.com (do not replace swddsk in the user ID text box)


Figure 2-37 CID access

4. Click Save.

5. Answer YES when asked to change the default user ID and password.

6. Click Close.

Configuring CID servers1. Click CID Servers from the Platform Administration Center.

2. Click New.

3. Enter the following information, as shown in Figure 2-38:

– Name: SRV01– Description: Master CID Server


Figure 2-38 Creating Master CID Server

4. Click Create.

5. After creation, click Close.

Setting up groupsThe next steps describe how to set up groups in the Platform Administration Center, and how to assign products to groups:

1. Click Groups from the Platform Administration Center.

2. Click New.

3. Enter the following information from the Group Details tab; see Figure 2-39:

– Name: Default – Description: Default Application Group


Figure 2-39 Creating a default group

4. Click Create.

5. After creation, click Close.

6. Repeat these steps to create a group with the following values:

– Name: Final – Description: Final Group

7. Select the Final group as shown in Figure 2-40.


Figure 2-40 Groups

8. Click Open.

9. Click the Assigned Products tab.

10.Click Add.

11.Click Search, as shown in Figure 2-41.

12.Select:

– ibm.cleanup.1_0.ref.3101– ibm.shutdown.1_102.ref.3100


Figure 2-41 Selecting products

13.Click OK.

14.Click Close.

The groups have now been created.

Creating a targetWhen creating target entries, follow the steps described below:

1. Click Targets on the left pane of the Platform Administration Center.

Figure 2-42 Creating a target

2. In the Targets windows shown in Figure 2-43, click New.

Tip: The final group needs to be created to include ibm.cleanup and ibm.shutdown. The cleanup package should be applied last in the process. We recommend that it is followed by a shutdown so that all of the changes take effect.


Figure 2-43 New target

3. To create a target with the name WKS01, enter the following information in the next screen:

– Name: wks01– Click Search.

This leads you to the Search CID Server screen, as shown in Figure 2-44. Click Search, select SRV01 (as this is our CID server), and click OK.


Figure 2-44 Search for CID Server screen

4. After the target entry is created and the information is presented on the screen, click the Groups and Products tab, as shown in Figure 2-45.

Note: There will be some STOP errors at the bottom of the screen. These errors will disappear when the item is created correctly.


Figure 2-45 Groups and products

5. Click Additional Groups and Products (highlight this item); see Figure 2-45.

6. Click Add to add an additional group to our target.

7. Click Search and select Default (see Figure 2-46).


Figure 2-46 Selecting default group

8. Click OK.

9. Click OK on the PAC Information page. Here the group Default has been added as a primary group.

10.Click Create.

11.To add the final group as second group to the target, click again Add.

12.Click Search, select Final.

13.Click OK.

14.Click Close.

Return to “Creating a target” on page 42 to create a server named SRV02 by following the steps above.

Create multiple targetsMultiple targets can be created using the Create Multiple Targets based on...

1. Select WKS01.

2. Click Create Multiple... and the Create Multiple Targets based on... screen will be shown as in Figure 2-47.

3. Enter the following information:

– Target-Name-Prefix: WKS– Number of Digits: 2

Note: Selecting more than one group before a primary group is added will result in the following information message:

More than one group has been selected. Only one Group can be added as a primary group.

Note: The STOP errors have now disappeared.


– Start with: 2– End with: 10

Figure 2-47 Creating multiple targets

4. From the PAC Question window, click YES.

5. From PAC Information Message window, click OK.

Return to “Create multiple targets” on page 46 to create multiple servers based on SRV02 by following the steps above.

When complete, your targets list will look like Figure 2-48.


Figure 2-48 List of created targets

2.3 SummaryThis chapter has covered the installation process required to use the Platform Management for Windows environment, and the first configuration settings using the Platform Administration Center. 3aservices.com is using this setup to build up their environment.


Chapter 3. Workstation installation using Platform Management for Windows

The purpose of this chapter is to take the user through the steps required to set up Microsoft Windows 2000 or Microsoft Windows XP workstations. It describes the BootDisk configurator and shows how it is used to create a workstation BootDisk. Once the workstation BootDisk is created, we explain the workstation build process.

3


3.1 The mechanism of the BootDiskThe Platform Management for Windows workstation installation is based on the unattended installation feature of the Windows operating system. It relies on an input file such as unattend.txt, which provides all required parameters to the operating system at the time of installation.

The unattend.txt file will be dynamically built by the BootDisk and updated with items like the computer name etc. so that the workstation installation process can complete silently.

All required input files for the workstation installation are stored in the CID tree in each operating system image folder at .\3\ms.w2k\pro.sp4\202\rsp (the example given is for Windows 2000 Professional).

Every Platform Management for Windows workstation operating system image is delivered with a preconfigured set of supported machine types.

All hardware specific settings are stored in a file using the file type 8.3: machinetype.txt.

Location specific settings like proxy, keyboard, time zone, product key, and so on are stored in the location files. Platform Management for Windows delivers two template location files in the .\rsp folder: wpat01.loc and wpat02.loc.

The hardware file and the location file contain sections and values of the MS unattended section and value set. A detailed description of all available keys for a specific operating system is shipped with the respective operating system (deployment document).

The final response file will be generated by the BootDisk merging and adapting the hardware file (*.txt) and the location (*.loc) file. It will be stored in the c:\bbtemp folder during execution of the boot diskette (automated process).

3aservices.com will update the D:\CID\3\ms.wxp\pro.sp1\202\rsp\wpat01.loc as shown in Example 3-1 (changes in bold).

Example 3-1 wpat01.loc

; PMfW 4.0 - Windows XP Professional client; pc-loc= domain = 3AServices.com; BEGIN of "country settings"

[userdata]fullname= 3aservicesorgname= 3aservicescomputernameproductkey="xxxxx-xxxxx-xxxxx-xxxxx-xxxxx"

[guiunattended];EncryptedAdminPassword = yes;use the encryption tool (Hashpwd.exe) in Deploy.cab of Windows OPK CD.adminpassword="Passw0rd"

timezone=110oemskipwelcome=1

Note: In maintenance release 4.02, the name of each operating system image folder was changed from .\3\ms.w2k\pro.sp4\200\rsp to .\3\ms.w2k\pro.sp4\202\rsp (the example given is also Windows 2000 Professional).


autologon=nooemskipregional=1

[identification]joindomain = "3Aservices.com"

domainadmin = "[email protected]"domainadminpassword = "Passw0rd"...<file continued>

3.2 Creating a BootDiskThe next steps will guide you through the process necessary to create a Platform Management for Windows BootDisk. This BootDisk will be used during the workstation pristine installation:

1. Double click the BDConf. V2.2 icon on the Windows desktop.

2. Select option 1- Generate an original PMfW v4.02 BootDisk as shown in Figure 3-1 and press Enter.

Figure 3-1 Generating an original PMfW v4.0 BootDisk

3. Now insert a blank floppy into drive A: and click OK.

Note: The screen as illustrated in Figure 3-2 is an self-extracting executable that creates the image of the BootDisk for the Original PMfW v4.02 BootDisk.

Chapter 3. Workstation installation using Platform Management for Windows 51

Figure 3-2 Creating the disk

4. When this step is completed, click Quit.

5. To configure the previous created BootDisk, select 4 - Configure the BootDisk, as shown in Figure 3-3 and press Enter.

Figure 3-3 Configure the BootDisk

6. On the next screen shown in Figure 3-4, select 1 - Configure All (this will guide you through all the possible options presented on the screen). Press Enter.


Figure 3-4 Configuring all components

7. Select OK to execute the ten configuration steps as shown in Figure 3-5.

Figure 3-5 Starting the 10 configuration steps of a BootDisk in sequence

8. Press Enter to update the CID server list file. This option updates the file a:\config\ccserver.db, which contains the names of the code servers; see Figure 3-6.

Note: CCserver.db = CID Server definition (SRV01 in our case).


Figure 3-6 Editing CCserver.db

9. On the next screen, enter the server name SRV01.

10.Select Upd to update.

11.Press ESC to write the changes.

12.Press Enter to update the ADS software distribution root list file, as shown in Figure 3-7. This option updates the file a:\config\bbserver.db that contains the name of the domain.

Figure 3-7 Editing BBdomain.db

Note: BBDdomain=Domain name (3aservices.com)


13.On the next screen, enter the domain name: 3aservices.com

14.Select Upd to update.

15.Press ESC to accept changes.

16.Press Enter update the target name mask list file. This option updates the file a:\config\computer.db that the masks of the computer names that will be used during the installation of workstations such as WKS0x.

17.Enter WKS as shown in Figure 3-8 and select Upd.

Figure 3-8 Target name mask

18.Press ESC to accept changes.

19.On the next screen you can see the Bbcdb.db=Database Server configuration. There are no changes required. Press ESC as shown in Figure 3-9. This option updates the file a:\config\bbcdb.db that contains the names of the database servers that will be used during the installation phases 1 and 2. The default value is bbcdb and is used by 3AServices.com.

Note: Computer.db = Target name mask (prefix)


Figure 3-9 Database server

20.On the next setting Release.db=Different operating systems on server. Select Windows 2000 SP4 and press Enter as shown in Figure 3-10. This option updates the file a:\config\release.db that contains the paths of the operating systems that can be installed on a workstation through the boot diskette.

Note: This information will only be used if the option Get OS’s List from the CID server has been unchecked in the global settings of the boot diskette. This option is checked by default so that the BootDisk configurator uses the information included in the 0index.txt file located in the root directory of the CID server instead of the a:\config\release.db file.

This can be useful if the CID servers in your environment carry different sets of information. However, it is necessary to create the 0index.txt files on the CID servers for this to function.


Figure 3-10 Operating systems

As we only want to include the Windows XP Client SP1 configuration, we will remove the other possible configurations.

21.Select Windows 2000 Client SP4 and press Enter. Select del.

22.When complete the screen will look as Figure 3-11. Press ESC.

Figure 3-11 Operating systems

23.As the next step, you will see SLOTS.LST in a text editor; see Figure 3-12. This is the list of slot applications that will run after completion of Phase 0. This list will be left as default for now. Press F3 to exit. This option updates the file called a:\config\slots.lst that contains the name of the slot applications that will be installed during Phase 1 according to the


sequence described in this file. An external editor (e.exe) has been included to simplify the update process for this file.

Figure 3-12 Slots.lst

24.Now the LMHOSTS configuration is presented. Leave this blank and press ESC.

25.Select NO for adding more lines to the LMHOSTS.

26.The Default.PRO - Network Settings screen as shown in Figure 3-13 is presented. Use the following values:

– Logon as: swddsk– Password: Passw0rd– Machine Name: BB-

– Workgroup: 3aservices– Check Skip identification dialog.– Click Save as shown in Figure 3-13.

Note: Using BB- let the BootDisk generate a random name.


Figure 3-13 Network settings

27.On the next screen (the Global Settings screen) click Save. See Figure 3-14.

Figure 3-14 Global settings


28.This leads you to the last configuration step, the national language support during the boot process. Select 1 - United States and press ESC.

29.Press ESC to exit the BootDisk configurator.

3.3 Installing the workstationIn the next steps you will see the way of building a Microsoft Windows workstation using our preconfigured BootDisk:

1. Insert the disk created by the BootDisk configurator into the target workstation.

2. Power on the workstation.

3. Select Run in Real Mode and press Enter as shown in Figure 3-15.

Figure 3-15 Run in Real Mode

4. Enter 5000 Megabytes for size and press Enter.

5. Press Enter to select Full HardDisk 1 Fdisk/Format; see Figure 3-16.

Tip: If you are familiar with the BootDisk and want to minimize user input during the installation process, you can try to set the following parameters:

� Automatic Timeout = 1 second� Short Timeout = 1 second� Long Timeout = 1 second

Apply changes by clicking Save.

(This tip will not be used in Chapter 3.3, “Installing the workstation” on page 60.)


Figure 3-16 Formatting workstation hard disk

6. Press Enter to select FDISK32. The machine will reboot.

7. The hard disk will be formatted directly after the reboot.

8. Select Network and press Enter.

9. In Figure 3-17 you can see that your network adapter will be detected.

Figure 3-17 Select a Detected Network driver

10.The TCP/IP parameters screen will be displayed. As we are using DHCP, no input is required; click OK.


Figure 3-18 TCP/IP parameters

11.The workstation is now contacting the CID server and if successful, dive Z: will be mounted as shown in Figure 3-19, click OK.

Figure 3-19 Successful connection to Z:

12.Press Enter at the Operating System to install message. This will select the Windows XP Client SP1, because of our selection in the screen shown in Figure 3-10 on page 57.

13.Now select your PC model type from the hardware list and press Enter as shown in Figure 3-21.


Figure 3-20 Select Hardware in the list

14.When the Windows Profile is requested as in Figure 3-21, select domain=3aservices.com and press Enter.

Figure 3-21 3aservices.com

15.In the PMfW Additional Information screen, type WKS01 as the Target Computer Name, 01 as the suffix, and press Enter. See Figure 3-22.


Figure 3-22 Enter a computer name for the target

16.The unattended Windows XP setup will start and continue on its own.

17.Platform Management for Windows will apply additional packages assigned to this workstation. In our example, ibm.cleanup and ibm.shutdown will be applied as shown in Figure 3-23.

Figure 3-23 Applying packages on target

When these steps are completed, you should see the following screen. Our workstation WKS01 is ready to be used.

Note: Make sure this target has been created in the Platform Management for Windows configuration database. Every workstation that will be set up with Platform Management for Windows needs to be configured in the Platform Management for Windows configuration database prior to the installation. See “Creating a target” on page 42.


Figure 3-24 Windows XP Professional

3.4 SummaryIn this chapter we configured the bootdisk with the Platform Management for Windows BootDisk configurator. This bootdisk was configured to access both the CID server and the Platform Management for Windows configuration database. Once connected, the user was prompted to supply the hardware type, domain information, and computer name.

With this information the bootdisk started an unattended installation of Microsoft’s Windows XP Professional, connected the computer to the 3aservices.com domain, and installed the Platform Management for Windows slot applications.

These slot applications, among other things, provided the workstation with full connectivity to the Platform Management for Windows configuration database, which in turn provided the computer with a list of applications that should be installed.



Chapter 4. Server install using Platform Management for Windows Phoenix tool

The purpose of this chapter is to take the user through the steps required to set up the server SRV02.3AServices.com in our environment. It will describe the Platform Management for Windows Phoenix tool, and shows how it is used to create a server BootDisk for SRV02. Once the server BootDisk is created, we explain the server build process, and do an install as the operating system Microsoft Windows 2003 Enterprise Edition on SRV02.

4


4.1 The Phoenix toolThe Phoenix tool is used to create server tickets. A server ticket contains all information necessary to automate the installation of a Microsoft Windows 2000 or Microsoft Windows 2003 server. The Platform Management for Windows Phoenix tool automates the setup and configuration of the following:

� Microsoft Windows 2003 Standard Server� Microsoft Windows 2003 Enterprise Edition� Microsoft Windows 2000 Server� Microsoft Windows 2000 Advanced Server� Domain Naming Services (DNS)� Dynamic Host Configuration Protocol (DHCP)� DCPROMO� Preparation for software distribution

Once the server ticket is configured, it is used to create a server BootDisk. This BootDisk is then used to build the server unattended.

There are two versions of the Platform Management for Windows Phoenix tool included:

� Phoenix Full Mode� Phoenix Wizard

The Platform Management for Windows Phoenix tool uses a database and customization files to run.

The database is used to map dependencies within the Microsoft Windows automated answer file (UNATTEND.TXT). The UNATTEND.TXT file has many possible configurations. For instance, if you set a network adapter with a static IP address, the information in the database will not allow you to also set DHCP for the same network adapter using the Platform Management for Windows Phoenix tool. Another example is if you are building a member server, the tool will not continue if the JoinDomain option is empty.

The customization files that are used by the Platform Management for Windows Phoenix tool are shown in Table 4-1.

Table 4-1 Customization files

Note: The Phoenix wizard can only modify a limited number of parameters (such as network parameters) of an already existing ticket. It is mainly used to configure a set of similar servers quickly.

INI File Name Description

ploc200x.iniwloc200x.ini

The ploc200x.ini file consists of sets of definitions. Each set of definitions contains values for the unattend.txt keys and values for the Phoenix specific keys. This ini.file can be modified with any common text editor.Contains location specific information (ploc is used by Phoenix Full andwloc is used by Phoenix Wizard). These files can be adapted to coverthe user’s needs.

hardware200x.ini Contains server hardware specific information like the path to the OEM PnP drivers and the addresses of the PCI slots

adapter200x.ini Contains information regarding third party mass storage drivers for SCSI or RAID adapters that are not natively supported by Windows 200x

slot200x.ini Contains information about available slot applications


Our scenario uses the Platform Management for Windows Phoenix tool to create a server ticket for SRV02. SRV02 will be a domain controller in the 3AServices domain with the configuration shown in Table 4-2.

Table 4-2 SRV02 configuration

4.2 Creating a server installation BootDiskThis section explains the steps required to create a server installation BootDisk with the Platform Management for Windows Phoenix Tool. This BootDisk will be used to set up SRV02 in the 3aservices.com domain:

1. To start the Phoenix tool, click Start -> All Programs -> IBM PMfW -> Phoenix Full.

2. Select Windows 2003 from the Operating System Family for the new ticket dropdown box, as shown in Figure 4-1.

Tip: The Platform Management for Windows Phoenix tool can be customized to support additional:

� Hardware configurations� Site location parameters � Special adapter configurations � User slot applications.

Detailed information on adding these customizations can be found in the corresponding online help file.

Server Name Role IP Address Hardware

srv02.3AServices.com domain controller 10.1.0.11 IBM X series 330768 Mb memory19 Gb disk

Important: We used an IBM ̂xSeries 330 with no RAID adapter. The hardware used in your environment may not be supported by the Platform Management for Windows Phoenix tool out of the box. If this is the case, refer to 8.2, “Server hardware integration” on page 141 for details on adding new hardware. The hardware used must also have at least 8 GB available on the first disk.

Chapter 4. Server install using Platform Management for Windows Phoenix tool 69

Figure 4-1 Windows 2003 Server Ticket

3. Click Continue.

4. Enter the following values into the PMfW Phoenix - New Ticket window. See Figure 4-2:

Server Name SRV02Hardware type* IBM e-Server xSeries 330PCI Slots of Network adapter OnBoardEthernetRaid adapter* No AdapterLocation Full Mode Sample 5 (New Member DC)Operating system Windows 2003 ServerRole in domain Additional DC in a Domain (Replica DC)*These values are dependent on the hardware used in your environment.


Figure 4-2 New server ticket

5. Click Continue.

6. Enter the values we define in Table 4-3 and Table 4-4 into the PMfW Phoenix - Full Mode View window, as shown in Figure 4-3.

Table 4-3 UNATTEND.TXT

Section Key Value

GuiUnattended AdminPassword Passw0rd

UserData ProductKey <valid product key>

Proxy Use_Same_Proxy No

Branding BrandIEUsingUnattended Yes

LicenseFilePrintData AutoMode Perseat

Identification JoinWorkgroup workgroup

params.MS_TCPIP.Adapter1 DefaultGateway 10.1.0.10

params.MS_TCPIP.Adapter1 DNSDomain 3aservices.com

params.MS_TCPIP.Adapter1 DNSServerSearchOrder 10.1.0.10

params.MS_TCPIP.Adapter1 IPAddress 10.1.0.11


Table 4-4 DCPROMO.TXT

Figure 4-3 Full mode view

7. Click Continue.

params.MS_TCPIP.Adapter1 SubnetMask 255.255.255.0

Section Key Value

DCInstall Password Passw0rd

DCInstall ReplicaDomainDNSName 3aservices.com

DCInstall SafeModeAdminPassword Passw0rd

DCInstall UserDomain 3aservices.com

DCInstal UserName administrator

Note: Notice the warning and stop messages in Figure 4-3. This is the dependency checking invoked through the database connected to the tool. Once all dependencies have been confirmed, the messages will disappear.

Section Key Value


8. From the PMfW Phoenix - Slot Applications window, highlight Facade from the Slot Functions frame. Then highlight Diskman from the User defined Slot Functions frame as shown in Figure 4-4.

9. Now click Add so that the Diskman can run as a slot application during the installation process.

10.Highlight Diskman from the Slot Functions frame; type config in the Details for Diskman frame.

Figure 4-4 Slot applications

11.Click Configure in the Details for Diskman frame.

12.This will lead you to the PMfW Phoenix - Diskman Configuration window. Select E as value from the First Removable drop down list as shown in Figure 4-5.

Note: Diskman is a slot application used to configure disk management. In this scenario, we use Diskman to create a second partition D: and set the CDROM drive to E:.


Figure 4-5 Diskman Configuration 1

13.Click Add Disk in the Details for Diskman frame.

14.This will bring you to the Details for Disk 0 frame. Type 0 (zero) in the Details for Disk 0 frame, as shown in Figure 4-6.



15.To add the primary partition for SRV02, click Add Primary Partition.

16.Set the value of the Size in MB field to 0 (zero) and select D in the Drive Letter drop-down list of the Details for Disk 0/Primary Partition frame. See Figure 4-7.



17.Click Previous to return to the PMfW Phoenix - Slot Applications window.

18.To move on to our final step, creating the BootDisk, click Continue.

19.Insert a blank floppy disk into the disk drive.

20.At the PMfW Phoenix - Write Ticket window, check Adapter1 in the Select IP frame. See Figure 4-8.

21.Enter the following values into the Configurator Details frame fields:

CC Server SRV01LDAP Root 3aservices.comLM Host Addition 10.1.0.10LAN User Password Passw0rdVerify Passw0rd

Note: Setting the size in MB to 0 will create a partition that uses the remaining space on the first disk.


Figure 4-8 Write Ticket

22.Now we can write on the disk. To do so, click Create Disk.

23.This will run a self restorable Ardi floppy disk image. As we have already entered the disk, click OK to write the image to the disk, as shown in Figure 4-9.

Figure 4-9 Disk creation

24.Click OK at the Disk Created! No Error occurred message box. See Figure 4-10.


Figure 4-10 Disk created

25.To create our server SRV02 as a software distribution target in the Platform Management for Windows database, click Yes at the Create a new target in the database using Platform Administration Center? message box. See Figure 4-11.

Figure 4-11 Create a new target

26.Arriving back in the PMfW Phoenix - Write Ticket window, click Exit to exit the Platform Management for Windows Phoenix tool.

The creation of the server build BootDisk for our server SRV02 is now complete. In the next section we will install server SRV02 using our configuration setting.

4.3 Server installationThis section explains the steps required to install the Windows 2003 operating system to the server. The BootDisk created in 4.2, “Creating a server installation BootDisk” on page 69 will be used to build the server. When completed, we will have successfully built the server SRV02 in our 3aservices.com domain.


1. Insert the BootDisk created by the Platform Management for Windows Phoenix tool into the target server.

2. Power on the server.

3. If prompted, press the space bar to boot from the floppy.

4. When presented the Platform Management for Windows BootDisk 2.2 welcome screen, select Run in Real Mode and press Enter as shown in Figure 4-12.


Figure 4-12 Run in Real Mode

5. When requested to select the destination drive preparation mode, enter 5000 Megabytes for size, select Full HardDisk 1 Fdisk/Format and press Enter. See Figure 4-13.

Figure 4-13 Formatting server hard disk

6. If there is existing data on the hard drive a message will be displayed to select FDISK32. Click FDISK32 The machine will reboot.

7. If prompted, click FORMAT32.

8. When the formatting process is done, select Network and press Enter.

9. In Figure 4-14 you can see that your network adapter will be detected.


Figure 4-14 Select a Detected Network driver

10.Select a detected network driver and press Enter (select a card that is physically connected to the network).

11.The Windows 2003 server setup will continue on its own, as all other configuration settings are included on the BootDisk and the Platform Management for Windows database.

12.After copying the setup file to the hard disk, the server will reboot. See Figure 4-15.

Figure 4-15 Windows 2003 Server setup

13.Do not press any keys at the message shown in Figure 4-16. Installation will continue on its own.


Figure 4-16 Platform Management for Windows Bootstrap Loader

14.The Windows 2003 server installation continues. The server reboots multiple times. No interaction is required, as shown in Figure 4-17.

Figure 4-17 Windows 2003 setup continues

15.The installation of the operating system (Phase0), the installation and execution of the configured slot applications (Phase1) of the installation will complete.

16.If additional applications for the target have been configured in the Platform Management for Windows database, the Facade will be displayed, as shown in Figure 4-18. Facade will install Phase 2 applications and as last step the server will reboot.


Figure 4-18 Final reboot

17.The installation and configuration of the Windows 2003 server operating system on SRV02 in the 3aservices.com domain is complete.

18.When the logon panel is presented after the reboot, we can log on to the server.

4.4 SummaryIn this chapter we created a server ticket for SRV02.3AServices.com using the Platform Management for Windows Phoenix tool. Server tickets are used to automate the installation of a server. We used this ticket to create a server BootDisk. The server BootDisk was then used to install and configure the Windows 2003 server in the 3aservices.com domain.


Chapter 5. Packaging Standard for Platform Management for Windows

This chapter describes the Platform Management for Windows compliant software package standard and its usage in distributing software.

When using Platform Management for Windows as software distribution tool, it is important that a standard packaging process is followed. This standard ensures that people building software packages have a consistent basis to build upon.

5


5.1 Platform Management for Windows software packagesPlatform Management for Windows software packages are involving three components as shown in Figure 5-1:

1. Software Distribution (SWD) Wrapper - The first part of the installation calls from the client the SWD Wrapper on the CID server where the installation is started and the process is monitored. The packages are copied to the workstation where they are extracted and a commit script is executed. The commit script includes the package name and the extension for the response file name. This is information is then passed to the installer script.

2. Installer Script - The Installer script performs the product installation (as well as any additional configuration requirements). Control is passed back to the Software Installation Dispatcher (SID) and eventually back to the systems management layer. The Installer Script contains information about the actual installation procedure. Other information is included in the Platform Management for Windows Facade.

3. Platform Management for Windows Facade - The Facade provides all the information necessary for performing the Installer Script. It interfaces with the Platform Management for Windows database containing the target configuration information.

Figure 5-1 Platform Management for Windows package wrapper

5.2 Phase 2 Application packaging templateTo simplify the creation of Phase 2 application packages in the Platform Management for Windows environment, there is a packaging template that can be used, which is included. This template helps to create Platform Management for Windows packaging standard compliant Phase 2 application packages.

The name of the template is ibm.packagetemplate.1_0.ref.3103 (located on the Platform Management for Windows setup and maintenance CD), and is designed to make package development as easy as possible. To fit the packaging of many standard software products, features can be customized and preconfigured.

The folders in the packaging template are as shown in Figure 5-2.

Platform Management for Windows Package Wrapper

SWD Wrapper

Platform Management for WindowsInstaller Script

Setup.exe /qn /s ...

Plat

form

Man

agem

ent f

orW

indo

ws

Faça

de D

LL

Plat

form

Man

agem

ent f

orW

indo

ws

Dat

abas

e

Note: In maintenance release 4.0.2, the packaging template name is changed to ibm.packagetemplate.1_0.ref.3104.


Figure 5-2 Packaging template directory structure

The folder structure description:

� \doc - This folder contains the README and PRODUCT file. The README file contains information on how to create a new package, and is also the README template (for your personal customization)

� \img - This folder holds the application source files for the package.

� \rsp - The folder contains the response files as required by the product being installed.

� \scr - This folder contains the install script and copycode.cmd.

The “fast start” section contained within the top section of the template allows for configuration of many common applications including:

� Service packs� Software compression tools� Readers and viewers

More details are provided in 5.3, “Using the packaging template for application packaging” on page 85 for the use of the packaging template.

5.3 Using the packaging template for application packaging3aservices.com would like to add the Norton Antivirus software product as one of their applications to be distributed using Platform Management for Windows. This section will show you how to add the application and create the necessary package information using the packaging template.

5.3.1 Expanding the packaging templateThe Platform Management for Windows packaging template is located on the Platform Management for Windows setup and maintenance CD.


Tip: For creating the file and directory structures for an application, the Package Builder can speed up this process. See Appendix , “Using Package Builder to add an application” on page 224.

Chapter 5. Packaging Standard for Platform Management for Windows 85

1. Copy the packaging template from the Platform Management for Windows setup and maintenance CD to a folder on your local workstation as follows:

copy d:\software packages\ibm.packagetemplate.1_0.ref.3103.exe c:\temp

where c:\temp is the name of the folder that will store the files

2. Execute:

c:\temp\ibm.packagetemplate.1_0.ref.3103.exe

Two directories will extract from the packaging template executable as follows:

– \3– \filepack

3. Rename the folders created as follows:

c:\temp\3\ibm.packagetemplate.1_0 to c:\temp\3\symantec.nav.7_61c:\temp\filepack\ibm.packagetemplate.1_0.ref.3103 to c:\temp\filepack\symantec.nav.7_61.ref.3103

The directory structure will look Figure 5-3 when complete.

Figure 5-3 Creating a directory structure for Norton Antivirus

4. Search for the string ibm.packagetemplate in C:\TEMP using Windows Search. Use the search for:

A word or a phrase in the file: ibm.packagetemplate


Figure 5-4 Identify all files with ibm.packagetemplate

5. Edit each file in Figure 5-4 using Notepad. Use the EDIT --> REPLACE command to replace all instances of ibm.packagetemplate.1_0 with symantec.nav.7_61 as shown in Figure 5-5.

Figure 5-5 Search and replace with new package information

6. Rename all of the files in Figure 5-4 to include symantec.nav.7_61 (except the original template file). The file structure will look like Figure 5-6 when complete.


Figure 5-6 Files for symantec.nav.7_61

7. Edit the FAST START CONFIGURATION section of packagetemplate.vbs to include the following:

– gSetupProgr = “NAV761CE.EXE”– gSetupParam = ““

8. Rename packagetemplate.vbs to nav.vbs.

9. Copy the source code NAV761CE.EXE to C:\temp\3\symantec.nav.7_61\ref.3103\img

10.Copy both C:\temp\3 and c:\temp\filepack to D:\CID\ on SRV01.

The CID server file structure will look like Figure 5-7.

Note: 3aservices.com has used Install Shield to package Norton Antivirus Corporate Edition with their customizations for their environment. NAV761CE.EXE is the application source that will install silently in the 3aservices.com environment.

Important: In all of the files found in Figure 5-4, the phrase ibm.packagetemplate.1_0 must be replaced with symantec.nav.7_61 for BOTH file names and file contents.


Figure 5-7 File structure for CID

5.3.2 Registering the application in the databaseThis section explains how the application must be registered in the database so it can be used by Platform Management for Windows:

1. In the Platform Administration Center tool, click Configuration Data.

2. Then click Products as shown in Figure 5-8.

Figure 5-8 Adding Products using the Platform Administration Center

3. From the Products window, click Search.


4. Then click New.

5. This will lead you to a screen like Figure 5-10. Enter the following information and click OK:

– Name: symantec.nav.7_61.ref.3103– Description: symantec.nav.7_61.ref.3103

Figure 5-9 Product description

When complete, the new product should appear in the Product Listing as follows in Figure 5-11.

Figure 5-10 Product listing


The product has now been added to the Platform Management for Windows database. It can now be used for deployment.

5.3.3 Testing the new application Now that the product has been registered in the database, we will test the installation on a workstation. WKS01 will be used in our test, it was created using Platform Management for Windows.

1. Create a file named request.txt using Notepad. It should include the following line as shown in Example 5-1.

Example 5-1 request.txt

symantec.nav.7_61.ref.3103

2. Copy request.txt to C:\MAINT\SWD

3. Wait 30 seconds. The file should disappear from this directory as it is processed by the WKS01 workstation.

4. The silent installation should commence and when complete, the application should be visible from:

Start -> Programs -> Norton Antivirus Corporate Edition

5. To verify a successful installation, check C:\MAINT\SWD\LOG. There should be a file named symantec.nav.7_61.ref.3103.log as shown in Example 5-2. The following return code shows that the installation completed properly:

19.02.2004 15:20:46 --- * end exit. RC = 0

In addition, take note of the installation command to ensure that it is installing the way we have requested:

19.02.2004 15:18:30 --- **** STARTING INSTALL PROGRAM. (X:3\symantec.nav.7_61\ref.3103\img\NAV761CE.EXE)

Example 5-2 symantec.nav.7_61.ref.3103.log

19.02.2004 15:18:29 --- * OPENING INSTBOT 3.0 log file for >symantec.nav.7_61.ref.3103<19.02.2004 15:18:29 --- Got following argument(s) from commit script: symantec.nav.7_61.ref.3103 NONE19.02.2004 15:18:29 --- connecting >X:< to CID19.02.2004 15:18:29 --- using >[email protected]< to connect To >SRV01<19.02.2004 15:18:29 --- ** InstCommand: C:\WINNT\system32\cscript.exe X:3\symantec.nav.7_61\ref.3103\scr\nav.vbs symantec.nav.7_61.ref.310319.02.2004 15:18:29 --- STARTING - product script...19.02.2004 15:18:29 --- -----------------------------------------------------------

Tip: Testing can also be forced immediately from a Platform Management for Windows workstation by mapping to the CIDAREAS on SRV01 to run the following script:

(where drive X: is mapped to SRV01\D$) X:\CID>cscript x:3\symantec.nav.7_61\ref.3103\scr\nav.vbs symantec.nav.7_61.ref.3103

When complete, there will be some return codes on the screen. For this particular package, we can verify the package completed with return code 0 from the following line:

Product: symantec.nav.7_61.ref.3103 returned RC: 0

During the development of a package, it can often be much easier to make a call directly to the package.


19.02.2004 15:18:30 --- * OPENING product.vbs log file for >symantec.nav.7_61.ref.3103< on WKS0119.02.2004 15:18:30 --- ** begin install procedure19.02.2004 15:18:30 --- Got following argument from commit script: symantec.nav.7_61.ref.310319.02.2004 15:18:30 --- **** CREATE RSP FILE for Product: symantec.nav.7_61.ref.3103 | RSP file: C:\maint\swd\rsp\symantec.nav.7_61.ref.3103.rsp | Original file name: 19.02.2004 15:18:30 --- **** Cheking for: NAV761CE.EXE19.02.2004 15:18:30 --- Ok.19.02.2004 15:18:30 --- *** begin switch Terminal Server...19.02.2004 15:18:30 --- This is not a TerminalServer in Application mode. No need to switch user.19.02.2004 15:18:30 --- *** end switch Terminal Server.19.02.2004 15:18:30 --- **** STARTING INSTALL PROGRAM. (X:3\symantec.nav.7_61\ref.3103\img\NAV761CE.EXE )19.02.2004 15:20:43 --- **** FINISHED INSTALL PROGRAM (0).19.02.2004 15:20:43 --- *** begin switch Terminal Server...19.02.2004 15:20:46 --- This is not a TerminalServer in Application mode. No need to switch user.19.02.2004 15:20:46 --- *** end switch Terminal Server.19.02.2004 15:20:46 --- ** end install procedure19.02.2004 15:20:46 --- * begin FinishPackage...19.02.2004 15:20:46 --- Creating version (VER) file.19.02.2004 15:20:46 --- Increasing product install counter in registry.19.02.2004 15:20:46 --- * end FinishPackage.19.02.2004 15:20:46 --- * begin exit...19.02.2004 15:20:46 --- RC_INST_OK - installation OK!19.02.2004 15:20:46 --- Creating event log entry19.02.2004 15:20:46 --- * end exit. RC = 019.02.2004 15:20:46 --- * CLOSING product.vbs log file for >symantec.nav.7_61.ref.3103<19.02.2004 15:20:48 --- -----------------------------------------------------------19.02.2004 15:20:48 --- FINISHED - product script...19.02.2004 15:20:48 --- ** InstCommand ended with RC: 019.02.2004 15:20:48 --- disconnecting CID drive19.02.2004 15:20:49 --- * CLOSING INSTBOT 3.0 log file for >symantec.nav.7_61.ref.3103<

5.4 Platform Management for Windows Package BuilderThe Platform Management for Windows Setup and Maintenance CD includes an unsupported application named Package Builder. This tool can be used to simplify the tasks associated with the tasks associated in 5.3, “Using the packaging template for application packaging” on page 85. For further instructions on using this tool, please refer to “Using Package Builder to add an application” on page 224.

3aservices.com will use the Package Builder to add WinRAR to the products database. See “Using Package Builder to add an application” on page 224

Attention: Package Builder (packagebuilder3_61.exe) is provided as an unsupported product. However, using this tool can speed up the process of adding an application to the database through the automated creation of the file/directory structures.


5.5 Adding packages to an existing groupTwo applications have now been created as products for 3aservices.com. These packages will be used later in this book.

The following steps will add the applications to the 3aservices.com default group as created in Chapter 2.2, “Starting the Platform Administration Center (PAC)” on page 35.

1. Start the Platform Administration Center from Start -> All Programs -> IBM PMfW -> Platform Administration Center.

2. Click Groups.

3. Click Search.

4. Select Default, as shown in Figure 5-11.

Figure 5-11 Select groups

5. Now click Open.

6. Click the Assigned Products Tab

7. Click Add

8. In the Search Products windows shown in Figure 5-12 on page 94, click Search.

9. Select the two products we want to distribute:

– rarlab.winrar.3_30.ref.3103– symantec.nav.7_61.ref.3103


Figure 5-12 Selecting products

10.Now click OK.

11.Finally, click Close.

Both applications are now part of the default group and ready to be distributed.

5.6 SummaryIn this chapter, we have shown how software packages can be created using a template and an automated process. To add additional software products to the Platform Management for Windows database, follow the same steps used to create the Norton Antivirus package or the WinRAR package.


Chapter 6. Offline installation

This chapter describes the procedures used in Platform Management for Windows for creating offline installation media, which can be used for installing workstations in situations where:

� The network bandwidth is very low.

– Transferring the operating system image takes too long.

� The unavailability of drivers or hardware conflicts.

– A network connection can be established under Windows but not under DOS.

Platform Management for Windows supports the use of removable devices and media to aid the installation at low bandwidth sites.

6


6.1 Offline installation (operating system only)In order to install Phase 0 of Platform Management for Windows from removable media, a reduced image of the CID tree (originally located on a server) has to be copied to the media. Due to the size of the operating system images and the additional drivers, the final size frequently exceeds 750 Mb. In order to bypass this problem when using CD-ROMs, the over-burning option that several CD recording tools offer, and special CD recording media can be used. This CD-ROM can include a boot diskette image, which enables the user to run the entire Phase 0 from the CD. The majority of current CD recording tools include a feature that enables the user to create a bootable CD-ROM.

The CD-ROM has to contain an image of the operating system to be installed, the entire filepack folder and a 0index.txt file. The image of the final CD can be prepared in a temporary folder on a hard disk, as shown in Figure 6-1.

Figure 6-1 Offline installation directory structure

The 0index.txt file, which is a copy of the A:\config\release.db Platform Management for Windows BootDisk file, has to be edited before being burned to the CD. This file contains the paths to the various operating systems that can be installed by a client during Phase 0 from the removable media. If the 0index.txt file is not located on the root of the CID tree, the Platform Management for Windows boot diskette will refer to its local copy located at A:\config\release.db. The 0index.txt located in the root of the media will always have priority over the local file.

BBCID is a null file that should be located in the root of the installation media containing the Phase 2 packages. This file is used as a offline installation identifier for Phase 2 package installation.

6.1.1 Boot imagesA pre configured Platform Management for Windows BootDisk can be transferred to a CD-ROMs boot sector on either an empty CD or a fully configured installation CD. 1.44 floppy

Note: You can also use a DVD-ROM as possible media.

Note: Do not reference server operating systems in 0index.txt as the use of this file is only valid for workstations.

Note: Do not forget to create the BBCID file.


emulation should be configured from within the CD recorder software. Usually, this option is configured by default.

6.2 Offline installation for 3AServices.comIn the following example, we will describe the steps needed to create an offline installation media for both Phase 0 and Phase 2 application installation used in 3AServices.com.

We will install the following applications from a DVD:

� Microsoft Windows XP Professional Service Pack 1� RarLabs WinRAR� Symantec Norton Antivirus� IBM cleanup package� IBM shutdown package

To install Phase 2 applications, an offline copy of the Platform Management for Windows database is needed. We also describe the steps for exporting the Platform Management for Windows database.

6.2.1 Exporting the Platform Management for Windows databaseThese are the steps:

1. Create the temporary directory on your harddisk like C:\Off_Line.

2. Start and log in to the Platform Administration Center from Start -> All Programs -> IBM PMfW -> Platform Administration Center, as shown in Figure 6-2.

Note: DOS and ANSI character sets

When burning the CD, either with or without the Platform Management for Windows BootDisk image, always use the DOS character set defined in the recording software’s ISO definition. Without this setting, the “.” (dot) symbols used in the folder names will be replaced by other characters, which in turn will make the CD unusable during Phase 0.

2\MS.XP\XPPRO.SP0 will become 2\MS_XP\XPPRO_SP0 or possibly 2\MSXP\XPPROSP0

Chapter 6. Offline installation 97


3. On the left hand side, click Utilities. This will bring you to a screen with three options as shown in Figure 6-3.


Figure 6-3 Platform Administration Center - Utilities

4. Click Copy Database to open up the Copy Database Wizard screen as shown in Figure 6-4.

Figure 6-4 Copy Database Wizard - Specify How to Copy and Log-File Path


5. Enter C:\Off_Line in the Directory for Log-File text box.

6. Click Next and you will see a screen like Figure 6-5.

Figure 6-5 Copy Database Wizard - Specify Target Database

7. Select New MS Access Database.

8. Click Next to open up the Create MS Access Database screen as shown in Figure 6-6.

Figure 6-6 Create MS Access Database

9. Enter Passw0rd in the Password text box.

10.Enter C:\Off_Line\ in the Directory for Database text box.

11.Now click OK to enter the Copy Database Wizard as shown in Figure 6-7, and to specify the global copy attributes.


Figure 6-7 Copy Database Wizard - Specify Global Copy Attributes

12.Select Overwrite Objects that exist already in the Target Database.

13.Select Copy Referenced Objects.

14.Click Next.

15.On the select objects screen of the Copy Database Wizard as shown in Figure 6-8, select all the options.

Figure 6-8 Copy Database Wizard - Select Objects

16.Click Next to enter the select groups screen on Figure 6-9 of the Copy Database Wizard.


Figure 6-9 Copy Database Wizard - Select Groups

17.Select Copy Referenced Targets.

18.Select Replace Products (Group, Target).

19.Select the Default and Final groups, and add them to the Selected Groups box as shown in Figure 6-10.

Figure 6-10 Copy Database Wizard - Select Groups

20.Click Next to reach the select targets screen of the Copy Database Wizard seen in Figure 6-11.


Figure 6-11 Copy Database Wizard - Select Targets

21.Select Copy Products Referenced in Target Configurations.

22.Select WKS10 and add this to the Selected Targets box, as shown in Figure 6-12.

Figure 6-12 Copy Database Wizard - Select Targets

23.Click Next to show the select products screen of the Copy Database Wizard; see Figure 6-13.


Figure 6-13 Copy Database Wizard - Select Products

24.Select Copy Product configurations.

25.Select the following products and add them to the Selected Products box; see Figure 6-14:

– ibm.cleanup.1_0.ref.3101– ibm.shutdown.1_102.ref.3100– rarlab.winrar.3_30.ref.3103– symantec.nav.7_61.ref.3103

Figure 6-14 Copy Database Wizard - Products


26.Click Next to enter the select Web-packs screen of the Copy Database Wizard, as shown in Figure 6-15.

Figure 6-15 Copy Database Wizard - Select Web-Packs

27.Accept the Select Web-Packs window’s defaults and click Next to reach the summary screen of the Copy Database Wizard as shown in Figure 6-16.

Figure 6-16 Copy Database Wizard - Summary

Note: There is no need to select the operating system as the database reference will not be used during Phase 0 (operating system).


28.To proceed, click Go. This will start the export process.

29.Once the export is complete, you will see Figure 6-17. Click Finish.

Figure 6-17 Copy Database Wizard - Complete

Figure 6-18 Platform Administration Center - Target database

6.2.2 Preparing the media with the source filesOnce the Platform Management for Windows database has been exported, follow these steps to populate the media with the source files:

Note: The database has now been exported to C:\Off_Line\BBOffl.mdb, and can be modified by opening it through the Platform Administration Center, and changing the default target database. See Figure 6-18.


1. Create a Platform Management for Windows BootDisk as in 3.2, “Creating a BootDisk” on page 51.

2. Create the null identifier file named BBCID and place it in the root of the C:\Off_Line directory.

3. Copy the following files and directories as shown in Table 6-1 from the Platform Management for Windows BootDisk and CID server to the directory that we prepared as source for the boot media.

Table 6-1 Source preperation

4. Delete the C:\Off_Line\CopyDB_<date>_<time>.log.

5. The source files and database files can now be recorded on to a CD.

Figure 6-19 and Figure 6-20 show the correct directory structure after the temporary directory has been prepared.

Source Destination

A:\config\release.db C:\Off_Line\0index.txt

D:\CID\3\ibm.cleanup.1_0 C:\Off_Line\3\ibm.cleanup.1_0

D:\CID\3\ibm.shutdown.1_102 C:\Off_Line\3\ibm.shutdown.1_102

D:\CID\3\ms.wxp C:\Off_Line\3\ms.wxp

D:\CID\3\rarlab.winrar.3_30 C:\Off_Line\3\rarlab.winrar.3_30

D:\CID\3\symantec.nav.7_61 C:\Off_Line\3\symantec.nav.7_61

D:\FilePack\ibm.cleanup.1_0.ref.3101 C:\Off_Line\FilePack\ibm.cleanup.1_0.ref.3101

D:\FilePack\ibm.shutdown.1_102.ref.3100 C:\Off_Line\FilePack\ibm.shutdown.1_102.ref.3100

D:\FilePack\rarlab.winrar.3_30.ref.3103 C:\Off_Line\FilePack\rarlab.winrar.3_30.ref.3103

D:\FilePack\symantec.nav.7_61.ref.3103 C:\Off_Line\FilePack\symantec.nav.7_61.ref.3103


Figure 6-19 OffLine directory structure


Figure 6-20 OffLine directory structure expanded

6. For the complete workstation installation, refer to Chapter 3, “Workstation installation using Platform Management for Windows” on page 49

7. When booting the system for a Phase 0 installation, there are three options when choosing the boot devices, as shown Figure 6-21.


Figure 6-21 Boot devices

8. Select Cd/DvdRom for the installation:

– Network

• Install the system from a CID share on the network.

– Cd/DvdRom

• Install the system from a CD-Rom or DVD-Rom.

– Zdevices

• Install the system from a compatible USB device.

6.3 SummaryIn this chapter, a CD/DVD-Rom was created for an offline installation of a workstation. For instance, where there is a constrained network environment or network drivers are not available, the CD/DVD-Rom provides an alternative for installing the workstations at 3AServices.com.


Chapter 7. CID synchronization

This chapter provides a short introduction into the features of CID tree synchronization and how Platform Management for Windows has implemented it.

CID synchronization is a highly configurable feature as you will see in this chapter.

Its most important attributes are:

� Directed replication

Every server can be configured to receive updates from specific CID master servers only. This allows to create a hierarchy of CID servers.

� Package filters

Package filters allow restricting the type of packages that can be replicated to a CID server. For instance, the user wants to set up a master server containing all packages and slave servers receiving packages of a specific language only. CID synchronization allows to define arbitrary package filters for each package and each CID server. A CID server will only receive packages automatically when the filters of the package and the server match.

� Timed replication

Transfer and maintenance times for every server can be specified separately. For instance, in order to reduce network traffic and increase package availability during normal working hours, it can be useful to replicate packages during night time only.

� Secure connections

Every server can be configured separately to either use SSL secured connections, or non-SSL (unencrypted) but faster connections.

7

Tip: If using CID synchronization, you may use an existing CID tree structure on a master server.


7.1 Master CID installation for srv01.3aservices.comThis section outlines the steps for installing the master CID on srv01.3aservices.com:

1. To start the PMfW configuration and maintenance utility, click Start -> All Programs -> IBM PMfW -> PMfW Configuration and Maintenance. You will see the screen shown in Figure 7-1.

Figure 7-1 Platform Management for Windows configuration and maintenance utility

2. Click Next.

3. Select CID Tree and mark Synchronized as shown in Figure 7-2.


Figure 7-2 PMfW options

4. Click Next.

5. On the CID Setup screen (shown in Figure 7-3) enter Passw0rd for swddsk in the CID UserID box, and re-enter the password again in the Confirm Password box. Repeat this for the IBMPMfWCIDAmin user.

Chapter 7. CID synchronization 113

Figure 7-3 Configure synchronized CID tree

6. Click 1. Check Precond to check if all dependencies are met.

7. Click Yes to create the D:\CIDAREAS as shown in Figure 7-4.

Figure 7-4 Create Directory

8. Click Configure.

9. Click Yes (as shown in Figure 7-5) when asked to assign permissions and check the password validity. This may take several minutes depending on the size of the existing CID tree as permissions are assigned.

Note: If asked to create D:\CID, click Yes.


Figure 7-5 Please Confirm screen

10.The IBM PMfW CID Synchronization - Install Shield wizard will begin. Follow the on-screen instructions using the default values provided; add your license key when prompted.

11.Once complete, the CID Tree Synchronization - Setup screen will be shown as in Figure 7-6 and the setup will begin.

Figure 7-6 CID Tree Synchronization - Setup

12.Select the CID Controller tab.

13.Check the Use Local CID Network Controller field; see Figure 7-7.

Note: If installing the slave server from 7.3, “Slave CID Installation for srv02.3aservices.com” on page 123, stop here and return to “Select the CID Controller tab as in Figure 7-21, and enter srv01 in the Controller Server Name text box.” on page 123.



14.Select the Automatic Updates tab and de-select Accept automatic updates from other servers, as shown in Figure 7-8.


15.Now click Start Configuration and the configuration will start.

16.During configuration the Configuration Progress window will appear with information on the current configuration progress. When this is complete (see Figure 7-9) click Exit.


Figure 7-9 Configuration Progress

17.Click Exit to leave the CID setup, as shown in Figure 7-9.

Figure 7-10 CID setup

18.Click Yes to confirm the exit.

Note: Log information for the configuration process can be found in:

C:\Program Files\IBM\PMfW\cidsync\we\logs\server1\SystemOut.log


7.2 Master CID configuration for srv01.3aservices.comThese are the steps:

1. To start the Platform Administration Center, click Start -> All Programs -> IBM PMfW -> Platform Administration Center.

2. Select Tools -> Options from the menu bar in the Platform Administration Center.

Figure 7-11 Platform Administration Center - Options

3. Select the CID Synchronization tab.

4. Mark CID Synchronization is enabled.

5. Enter http://srv01:15700 in the baseURL text box.

6. Click Add; see Figure 7-7.

Note: To make the Add button available after entering http://srv01:15700, tab to the next field.


Figure 7-12 Platform Administration Options

7. Click Apply.

8. Click OK.

9. Re-start the Platform Administration Center.

10.Click the CID Synchronization plug-in; see Figure 7-13.

Figure 7-13 CID Synchronization plug-in

11.Click the Synchronized CID Severs icon; see Figure 7-14.

Figure 7-14 Synchronized CID Servers

12.Log in with the IBMPMFWCIDAdmin account and the password created earlier (see step 5 on page 113).

Note: The Platform Administration Center must be restarted for the changes to be applied.


Figure 7-15 CID Network Controller Login

13.Click and expand the http://srv01:15700 -> srv01 -> Production Area, as shown in Figure 7-16.

Figure 7-16 Platform Administration Center [Synchronized CID Servers]

14.For each package that exists in the Production Area, right-click and select copy files to edit area; see Figure 7-17.


Figure 7-17 Platform Administration Center [Synchronized CID Servers] copying files

15.Select All Files, as shown in Figure 7-18.

16.Click OK.

Figure 7-18 Enter what files to copy


17.Right-click srv01 and select Refresh; see Figure 7-19.

Figure 7-19 Refreshing the CID synchronization servers

18.Expand the Edit Area as shown in (Figure 7-20) and check to see if the packages now exist.

Note: This will take some time as both the Windows XP Professional and the Windows 2003 server standard files must be copied. It is also possible to do this with a normal copy and paste action:

Copy from D:\CID\3 to D:\CIDAREAS\editarea\3

Copy from D:\CID\FilePack to D:\CIDAREAS\editarea\filepack



19.Exit the Platform Administration Center.

7.3 Slave CID Installation for srv02.3aservices.comIn this section we outline the steps for installing the slave CID on srv01.3aservices.com:

1. Install the PMfW Configuration and Maintenance utility; see Chapter 2.1.5, “Platform Management for Windows: Setup and maintenance” on page 17.

2. Follow steps 1 through step 11 from 7.1, “Master CID installation for srv01.3aservices.com” on page 112.

3. Select the CID Controller tab as in Figure 7-21, and enter srv01 in the Controller Server Name text box.


Figure 7-21 CID Synchronization - Setup

4. Select the Automatic Updates tab.

5. Enter srv01 in the text box.

6. Click Add; see Figure 7-22.

Figure 7-22 CID Synchronization - Setup

7. Click Start Configuration.

8. During configuration the Configuration Progress window will appear with information on the current configuration progress. When this is complete (see Figure 7-23) click Exit.


Figure 7-23 Configuration Progress

9. Click Exit to exit the CID Setup - Configure synchronized CID Tree, as shown in Figure 7-24.

Figure 7-24 CID Setup - Configure synchronized CID Tree

10.Click Yes on the Cancel the PMfW wizard.


7.4 Verifying master/slave relationshipThis section will outline the steps for verifying the synchronization between the master CID server, srv01, and the slave server srv02:

1. Return to server SRV01.

2. Start the Platform Administration Center: click Start -> All Programs -> IBM PMfW -> Platform Administration Center.

3. Click the Synchronized CID Servers icon.

4. Log in as in steps 12 on page 119, and note that srv02 has now appeared; see Figure 7-25.


5. Expand both servers and check if the packages have been transferred.

Note: Depending on the amount of data to be synchronized, it can take quite some time before all servers are updated.


7.5 SummaryIn this chapter we installed and configured a master server and its partner slave server for synchronization. The CID tree structure will now be available to all targets from two different servers: SRV01 and SRV02.

Any changes made to products on these servers can be published and then made available from these servers.



Chapter 8. Hardware integration

This chapter discusses how to integrate new hardware devices for Platform Management for Windows.

Hardware integration can be complex. The scope of this chapter is not to describe hardware integration in detail (refer to Microsoft for detailed instructions on how to integrate mass storage drivers; see 8.2.3, “Add support for third-party mass storage drivers” on page 148). Rather, this chapter will take the user through the process of integrating a new client and server into Platform Management for Windows

The major topics covered in this chapter are:

� Client hardware integration� Server hardware integration

8

Note: In this chapter when referring to directory paths we use the CID synchronization path such as D:\CIDAREAS\editarea\.... Refer to Chapter 7, “CID synchronization” on page 111 for details on CID synchronization. If CID synchronization is not set up, the path is D:\CID\....


8.1 Client hardware integrationThis section describes how to perform client hardware integration. To demonstrate, we have used an IBM Thinkpad T30.

The steps to perform hardware integration on a client are:

1. Add network support to the BootDisk2. Create a new response file3. Build client and identify missing drivers4. Add drivers to the CID server5. Build client with OEM-supplied drivers

8.1.1 Add network support to the BootDisk

The Platform Management for Windows BootDisk configurator is used to add network support to the BootDisk. Many different network cards are supported by the BootDisk configurator. However, sometimes it is necessary to update or add a new network driver to the BootDisk.

The network drivers can be found on the machine running the Platform Management for Windows BootDisk configurator. The default locations for the network drivers are:

Basic C:\programs\IBM\PMfW\BC20\BASIC\

Extend C:\programs\IBM\PMfW\BC20\EXTEND\

The basic directory contains drivers that are added to the BootDisk by default. The extend directory contains drivers that are not automatically added to the BootDisk.

Each network driver is kept in a CAB file (a CAB file is a compressed file). The CAB file contains at least four files:

<driver>.dos The DOS driver that is delivered by the card manufacturer

<driver>.ini Contains the protocol.ini specific part for the hardware

ndis.txt Contains a driver description that will appear in dialogs

ndis.pci Contains the PCI ids for the supported devices

In the following example we add network support for the IBM Thinkpad T30.


1. Obtain the DOS network driver from the vendor of the network card. The IBM Thinkpad T30 uses a Intel® PRO/100 VE Network card. In this case the DOS driver is E100B.dos.

2. Insert a BootDisk created by the BootDisk configurator. Refer to 3.2, “Creating a BootDisk” on page 51.

3. Power on the client.

4. If required, press the space bar to boot from the BootDisk.

Note: This step is only required if the network card is not supported by the BootDisk.

Note: The BootDisk configurator already supports the network card in the IBM Thinkpad T30 (E100B). This example is for demonstration purposes only.


5. At the Welcome to Platform Management for Windows BootDisk screen, select Exit to DOS as shown in Figure 8-1.

Figure 8-1 Exit to DOS

6. Type a: and press Enter.

7. Type cd\bin and press Enter.

8. Type ibmpci -d and press Enter. A listing of PCI information of the Thinkpad will be displayed.

Example 8-1 VENDOR-ID and DEVICE-ID

CLASS SUBCLASS VENDOR-ID DEVICE-ID BUS DEV FCT ----------------------------------------------------------------------------- BRIDGE CPU-PCI 8086 1A30 0 0 0 BRIDGE PCI-PCI 8086 1A31 0 1 0 SERIAL BUS USB 8086 2482 0 1D 0 SERIAL BUS USB 8086 2484 0 1D 1 BRIDGE PCI-PCI 8086 2448 0 1E 0 BRIDGE PCI-ISA 8086 248C 0 1F 0 DISK IDE 8086 248A 0 1F 1 DISPLAY VGA 1002 4C57 1 0 0 BRIDGE PCI-CARDBUS 104C AC55 2 0 0 BRIDGE PCI-CARDBUS 104C AC55 2 0 1 NETWORK ETHERNET 8086 1031 2 8 0 -----------------------------------------------------------------------------

9. Note down the VENDOR-ID and DEVICE-ID for each NETWORK class. In Example 8-1, the VENDOR-ID=8086 and the DEVICE-ID=1031.

10.From the BootDisk Configurator machine, create the following directory C:\programs\IBM\PMfW\BC20\BASIC\NDIS\SOURCE\E100B.

11.Copy the E100B.DOS file (obtained from the vendor) to the C:\programs\IBM\PMfW\BC20\BASIC\NDIS\SOURCE\E100B directory.

Note: IBMPCI.EXE is a utility that lists PCI information.

Chapter 8. Hardware integration 131

12.Create and edit the following files E100B.INI, NDIS.PCI, and NDIS.TXT in the C:\programs\IBM\PMfW\BC20\BASIC\NDIS\SOURCE\E100B directory as the examples Example 8-2, Example 8-3, and Example 8-4 show.

Example 8-2 E100B.INI

DriverName=e100b$

Example 8-3 NDIS.PCI

ret="E100B"ven=8086 "Intel"dev=1031 "PRO/100 VE Network Connection"

Example 8-4 NDIS.TXT

E100B Intel(R) PRO PCI Driver v4.47 030503

13.The directory now contains E100B.DOS, E100B.INI, NDIS.PCI, and NDIS.TXT; see Figure 8-2.

Figure 8-2 BootDisk network support files

14.It is now possible to make a new BootDisk with the new network card support. Refer to 3.2, “Creating a BootDisk” on page 51 for details.

Tip: You do not have to create a new disk to add support for network cards. The BootDisk configurator gives the user the option to add or remove network support from an already configured BootDisk. Refer to the BootDisk configurator help file for more information.


8.1.2 Create a new response file


1. Make a copy of a existing client response file. The Windows XP SP1 response files for Packaging Standard V3.0 can be found in D:\CIDAREAS\editarea\3\ms.wxp\pro.sp1\200\rsp.

2. Rename the file to something that describes the hardware you are installing. The file should be in 8.3 format such as ibmx2366.txt.

3. Update the pc-model line in this file, see Example 8-5. This will be displayed during the BootDisk phase.

Example 8-5 Update pc-model

; pc-model=IBM Thinkpad T30 (2366)

4. Update the pc-crole line in this file; see Example 8-6. Valid values are desktop or mobile.

Example 8-6 Update pc-crole

; pc-crole=mobile

5. Update oempnpdriverspath. We will make the oempnpdriverspath empty; see Example 8-7. This allows us to install the PC without any additional third-party drivers. That way we can identify components that are not supported by the operating system.

Example 8-7 Set oempnpdriverspath to empty

oempreinstall=yesoempnpdriverspath = ""driversigningpolicy = ignore

6. Save the response file.

8.1.3 Build client and identify missing driversThis section takes us through the process of how to identify what third-party drivers are required:

1. Start the workstation build. Refer to Chapter 3., “Workstation installation using Platform Management for Windows” on page 49 for details on installing a workstation.

2. Once the workstation build is complete. Start Computer Management (right-click My Computer and select Manage) and check Device Manager for Other devices; see Figure 8-3.

Note: The response file is an answer file used to automate the installation of the operating system.

Note: The oempnpdriverspath specifies the path to one or more folders that contain OEM supplied drivers. The operating system uses this path to install the drivers automatically.


Figure 8-3 Other devices

3. In Figure 8-3, two devices are listed in the Other devices section. This means the operating system could not find a suitable match. New original equipment manufacturer (OEM) supplied drivers must be installed. Obtain the drivers from the vendors Web site. The IBM ThinkPad® T30 drivers were obtained from the IBM Web site:

http://www.ibm.com/support/us/

4. Update all devices found in Computer Management/Device Manager/Other Devices with the drivers obtained from the vendor. Make a note of the drivers you have used. For example, to update the Video Controller (VGA Compatible) device:

a. Extract the driver locally to c:\video.

b. In Device Manager, find the video contoller (VGA compatible), right-click the device and select Update Driver as shown in Figure 8-4.


http://www.ibm.com/support/us/

Figure 8-4 Update driver

c. Select Install from a list or specific location (Advanced) as shown in Figure 8-5.

Figure 8-5 Welcome to the Hardware Update Wizard

d. Click Next.

e. Select Don’t search. I will choose the driver to install on the Please choose your search and installation options screen; see Figure 8-6.


Figure 8-6 Choose your search and installation options

f. Click Next.

g. On the Hardware Type screen, highlight Display adapters as shown in Figure 8-7.

Figure 8-7 Hardware Type

h. Click Next.

i. Select Have Disk. As shown in the Select the device driver screen, you want to install for this hardware screen as shown in Figure 8-8.


Figure 8-8 Select the device driver you want to install for this hardware

j. Type c:\video. This is the location of OEM video driver; see Figure 8-9.

Figure 8-9 Install from disk

k. Click OK.

l. On the Select the device driver screen, you want to install for this hardware screen. Highlight ATI MOBILITY RADEON 7500 as shown in Figure 8-10.


Figure 8-10 Select the device driver you want to install for this hardware

m. Click Next.

n. The driver for the ATI MOBILITY RADEON 7500 will be installed.

o. Click Finish as shown in Figure 8-11.

Figure 8-11 Finish

p. Notice that the ATI MOBILITY RADEON 7500 has successfully installed in Device Manager as shown in Figure 8-12.


Figure 8-12 Successfully installed driver

5. Add drivers for any other devices that are not supported by the operating system, when finished Device Manager should not have any unknown devices, as shown in Figure 8-13.


Figure 8-13 Successful install of devices

6. Now that we know which OEM-supplied device drivers are required, we can make them available to Platform Management for Windows.

8.1.4 Add drivers to the CID serverThese are the steps:

1. Open \CIDAREAS\editarea\3\ms.wxp\pro.sp1\200\i386\$OEM$\$1\hwdrv on the CID server. This is where all the OEM-supplied drivers are kept.

2. Copy the drivers to a subdirectory. For example, the IBM Thinkpad T30 requires two additional drivers: A video driver and a power management driver. These drivers were copied to the following directories:

Video

D:\CIDAREAS\editarea\3\ms.wxp\pro.sp1\200\i386\$OEM$\$1\hwdrv\video\atirad

Power Mgmt

D:\CIDAREAS\editarea\3\ms.wxp\pro.sp1\200\i386\$OEM$\$1\hwdrv\misc\power.120

3. Once you have identified which OEM-supplied drivers are required, and they have been placed on the CID server, the next step is to update the response file.

4. Open the response file created in 8.1.2, “Create a new response file” on page 133.

5. Edit the file.

6. Update oempnpdriverspath with the location of the OEM-supplied drivers, as shown in Example 8-8.


Example 8-8 Update oempnpdriverspath with location of OEM-supplied drivers

oempreinstall=yesoempnpdriverspath = "hwdrv\video\atirad;hwdrv\misc\power.120"driversigningpolicy = ignore

7. Save the response file.

8.1.5 Build client with OEM-supplied driversThese are the steps:

1. Start the workstation build. Refer to Chapter 3., “Workstation installation using Platform Management for Windows” on page 49 for details on installing a workstation.

2. Open Computer Management and check that all devices have installed successfully through Device Manager; see Figure 8-14.

Figure 8-14 Successful install of devices

8.2 Server hardware integrationThis section describes how to perform server hardware integration. It contains an explanation of the files used to perform hardware integration to demonstrate we have used a IBM e-server xSeries 330.

The steps to perform hardware integration on a server are:

1. Update Phoenix tool with new server.2. Add support for third-party mass storage drivers.3. Build server with newly added hardware.


8.2.1 Explanation of hardware200x.ini and adapter200x.ini

Hardware200x.iniThe hardware200x.ini file holds information about supported server hardware; see Example 8-9. For each server, you will require a set of PCI definitions. These are necessary to install network adapters. The PCI information needed is PCI bus number, device number, and function number (in this order). In addition, you can specify the OemPnPDriversPath if needed.

Example 8-9 hardware2003.ini

; Supported Servers on top; For each Server: MaxLocations specifies possible Locations; For each PCI locations Bus,Device,Function; If OnBoard Ethernet than OnBoard = True

[SERVERS]Server01 = IBM Netfinity 3000...Server15 = e-Server xSeries 232Server16 = e-Server xSeries 235Server17 = e-Server xSeries 255...[SERVER16];e-Server xSeries 235MAXLocations = 6OnBoard = TrueLocation1 = 0,1,0Location2 = 2,1,0Location3 = 2,2,0Location4 = 5,3,0Location5 = 7,5,0Location6 = 9,6,0OnBoardEthernet = 2,8,0Key01_A = Unattended\OemPnPDriversPath ="hwdrv\misc\actpci;hwdrv\misc\smb"...

Each server section holds information about the PCI hardware, on-board ethernet controllers, and the OemPnPDriversPath.

The key MAXLocations specifies the number of hardware (PCI-) slots available for network adapters.

Location1, Location2, Location3, and OnBoardEthernet contain values for the PCI Bus Number, Device Number, and Function Number.

The are two options for gathering the PCI bus number, device number, and function number for each network adapter. The first option is through the server BootDisk. The second option is through Microsoft Windows.

How to gather PCI bus number, device number, and function number using the server BootDisk

1. Insert a server build BootDisk. Refer to 4.2, “Creating a server installation BootDisk” on page 69 for details on creating a server build BootDisk.

Note: The key location stands for the PCI slot where the network adapter can reside.


2. Power on the server.

3. When prompted, press any key to boot from the server build BootDisk.

4. At the Welcome to Platform Management for Windows BootDisk screen, select Exit to DOS.

5. Type a: and press Enter.

6. Type cd\bin and press Enter.

7. Type ibmpci -d and press Enter. A listing of PCI information will be displayed; see Example 8-10.

Example 8-10 Information from IBMPCI.EXE

CLASS SUBCLASS VENDOR-ID DEVICE-ID BUS DEV FCT ----------------------------------------------------------------------------- BRIDGE CPU-PCI 1166 0009 0 0 0 BRIDGE CPU-PCI 1166 0009 0 0 1 DISPLAY VGA 5333 8A22 0 1 0 NETWORK ETHERNET 8086 1229 0 2 0 NETWORK ETHERNET 8086 1229 0 A 0 BRIDGE PCI-ISA 1166 0200 0 F 0 DISK IDE 1166 0211 0 F 1 SERIAL BUS USB 1166 0220 0 F 2 DISK SCSI 9005 008F 1 3 0 -----------------------------------------------------------------------------

8. Note down the PCI bus, device, and function values (such as BUS, DEV, FCT) for each NETWORK class. In Example 8-10, the first NETWORK class values are:bus=0, device=2, function=0. The second NETWORK class values are:bus=0, device=10, function=0.

How to gather PCI bus number, device number, and function number using Microsoft Windows

You must have a Windows 2000 or Windows 2003 operating system up and running.

To obtain the PCI bus number, device number, and function number for all network cards, perform the following steps:

1. Click Start -> Settings -> Control Panel.

2. Double click Network Connections, as shown in Figure 8-15.

Note: IBMPCI.EXE returns BUS, DEV, and FCT values in Hex. Use a Hex converter to get the decimal values such as BUS=0 DEV=A FCT=0 converted to decimal equals BUS=0 DEV=10 FCT=0.


Figure 8-15 Network connections

3. Right-click a LAN adapter as shown in Figure 8-16.

Figure 8-16 Network adapter properties


4. Click Properties.

5. The connection properties will be displayed; see Figure 8-17.

Figure 8-17 Connection properties

6. Click Configure.

7. The adapter properties will be displayed; see Figure 8-18.


Figure 8-18 Adapter properties

8. Note down the PCI bus, device, and function values from the location field. As highlighted in Figure 8-18, the values are: bus=0, device=2, function=0.

9. Click OK.

10.Repeat the steps for each network adapter.

Adapter200x.iniNot all mass storage drivers are included in the operating system. The Adapter200x.ini file facilitates adding new mass storage drivers into the Platform Management for Windows environment; see Example 8-11.

Example 8-11 Adapter2003.ini

[Adapters]Adapt01 = "No Raid Adapter"Adapt02 = "IBM ServeRAID 6.1 - 2x/3x/4H Controller (ipsraid)"...[Adapt01]Key01_A = Unattended\OemPnPDriversPath=""

[Adapt02]Key01_A = Unattended\OemPnPDriversPath="hwdrv\raid\IBMIPS61"...

The section [Adapters] describes which adapters are supported and the text that should be displayed in the Phoenix GUI.

Note: Using IBM ̂xSeries technology enables you to hot-plug each network adapter card.


The [AdaptXX] section describes the necessary unattended.txt keys for the adapter. For each Section-Key-Value pair, you need one KEYxx entry.

8.2.2 Update Phoenix tool with new serverThese are the steps:

1. Edit the hardware2003.ini file. This is found at C:\Program Files\IBM\PMfW\Phoenix if the Phoenix tool was installed in the default location.

2. Add the new server to [Servers] section of the hardware2003.ini file. See Example 8-12 on how to add an IBM ̂xSeries 330 to the file.

Example 8-12 Adding a server to hardware2003.ini

; Supported Servers on top; For each Server: MaxLocations specifies possible Locations; For each PCI locations Bus,Device,Function; If OnBoard Ethernet than OnBoard = True

[SERVERS]Server01 = IBM Netfinity 3000...Server17 = e-Server xSeries 255Server18 = e-Server xSeries 300Server19 = e-Server xSeries 330...

3. Add a section for the new server. See Example 8-13 on how to add an IBM ̂xSeries 330 to the file.

Example 8-13 Adding a server to hardware2003.ini

...[SERVER18];e-Server xSeries 300MAXLocations = 3;OnBoardEthernet = OnBoard 1 !!!!;Location 3 = OnBoard 2 !!!!OnBoard = TrueLocation1 = 0,9,0Location2 = 0,10,0Location3 = 0,14,0OnBoardEthernet = 0,13,0Key01_A = Unattended\OemPnPDriversPath =""

[SERVER19];e-Server xSeries 330MAXLocations = 3OnBoard = TrueLocation1 = 1,5,0Location2 = 1,6,0Location3 = 0,10,0OnBoardEthernet = 0,2,0Key01_A = Unattended\OemPnPDriversPath =""...

4. Save the hardware2003.ini file.


8.2.3 Add support for third-party mass storage driversRefer to the Microsoft Knowledge Base Article 816299 for details on adding third-party mass storage drivers in Windows 2003:

http://support.microsoft.com/?kbid=816299

Refer to the Microsoft Knowledge Base Article 288344 for details on adding third-party mass storage drivers in Windows 2000:


In this example we add support for an IBM ServeRAID™ adapter:

1. Obtain the Windows 2003 IBM ServeRAID adapter third-party mass storage driver from IBM.

2. Copy the driver files to the D:\CIDAREAS\editarea\3\ms.w52\srvstd.sp0\200\i386\$OEM$\textmode directory; see Figure 8-19.

Figure 8-19 Copy mass storage driver

3. Update the D:\CIDAREAS\editarea\3\ms.w52\srvstd.sp0\200\i386\$OEM$\textmode\txtsetup.oem file as shown in Example 8-14.

Note: If the driver contains a DLL file, then you have to place the DLL file in a folder named oemdir located under D:\CIDAREAS\editarea\3\ms.w52\srvstd.sp0\200\i386\$OEM$\$$\.

Note: Microsoft does not allow you to create subfolders in the textmode folder. If different mass storage drivers have files with the same name, you must rename them and edit the references in the inf, ini, and oem files where these files are listed.




Example 8-14 txtsetup.oem

[Disks]d1 = "IBM ServeRAID Device Driver Diskette", w23dsk1, \

[Defaults]scsi = NFRDWin2k32

[scsi]NFRDWin2k32 = "IBM ServeRAID 4M/4Mx/4L/4Lx/5i/6M/6i Device Driver"

[Files.scsi.NFRDWin2k32]driver = d1, nfrd960.sys, NFRD960catalog = d1, ibmnfrd3.catinf = d1, oemsetup.inf

[Config.NFRD960]value = parameters\PnpInterface,5,REG_DWORD,1value = parameters\Device,NumberOfRequests,REG_DWORD,128

[Config.IPSRAIDN]value = parameters\PnpInterface,5,REG_DWORD,1value = parameters\Device,NumberOfRequests,REG_DWORD,128

[HardwareIDs.scsi.NFRDWin2k32]id = "PCI\VEN_1014&DEV_01BD", "nfrd960"id = "PCI\VEN_9005&DEV_0250", "nfrd960"

4. Save the file.

5. Edit the adapter2003.ini file. This will be found at C:\Program Files\IBM\PMfW\Phoenix if the Phoenix tool was installed in the default location.

6. Add a new adapter to the [Adapters] section of the adapter2003.ini file. See Example 8-15 on how to add an IBM ServeRAID 6.1 - “4M/4Mx/4L/4Lx/5i/6M/6i Controller” (changes in bold).

Example 8-15 Add a new adapter

[Adapters]Adapt01 = "No Raid Adapter"Adapt02 = "IBM ServeRAID 6.1 - 2x/3x/4H Controller (ipsraid)"Adapt03 = "IBM ServeRAID 6.1 - 4M/4Mx/4L/4Lx/5i/6M/6i Controller"...

7. Add a section for the new adapter. See Example 8-16 on how to add settings for the “IBM ServeRAID 6.1 - 4M/4Mx/4L/4Lx/5i/6M/6i Controller” (changes in bold).

Example 8-16 Adapter settings

...

[Adapt01]Key01_A = Unattended\OemPnPDriversPath=""

[Adapt02]Key01_A = Unattended\OemPnPDriversPath="hwdrv\raid\IBMIPS61"

[Adapt03]Key01 = OEMBootFiles\=NFRD960.SYSKey02 = OEMBootFiles\=TXTSETUP.OEM


Key03 = MassStorageDrivers\="IBM ServeRAID 4M/4Mx/4L/4Lx/5i/6M/6i Device Driver" = "OEM"

8. Save the file.

8.2.4 Build server with newly added hardwareThese are the steps:

1. Create a server build disk with the Phoenix tool. Refer to 4.2, “Creating a server installation BootDisk” on page 69 for details.

2. Start the server build. Refer to 4.3, “Server installation” on page 78 for details on installing the server.

8.3 SummaryIn this chapter we have added new DOS network drivers to the preconfigured BootDisk, created a workstation hardware profile for the IBM T30 model by adding the OEM drivers that were not supported by the default Microsoft Windows XP Professional installation.

Though complicated, we have shown the user how to integrate and configure new server hardware by adding the required drivers and configuration file entries to the CID tree structure.

Note: The MassStorageDrivers\ value must match the [scsi] section value from the txtsetup.oem. See section-Adapt03, Key-Key03 in Example 8-16.


Chapter 9. Platform Management for Windows Web interface

This chapter provides an introduction into the Platform Management for Windows Web interface and the functions it provides. We also describe the installation and configuration for 3AServices.com.

The Platform Management for Windows Web interface provides an easy to use interface for managing the Platform Management for Windows environment. It gives administrators the possibility to add, remove, and configure all the options available through the Platform Administration Console, as well as providing the user with a central point for installing software.

By applying the target and group concept to the software available in the Platform Management for Windows database, it is possible to control the availability of this software to the users.

9


9.1 Installing and configuring the Web interface for 3aservices.com

To complete this chapter the following server configuration needs to be available.

Table 9-1 Server configuration srv03.3aservices.com

The installation process for the Platform Management for Windows Web interface is split into five parts:

� Configuring Micrsoft’s Active Directory� Installing the Web interface components� Configuring Microsoft’s Internet Information server� Configuring the Web interface’s look and feel� Configuring Web-Packs

9.1.1 Configuring Microsoft’s Active DirectoryBefore installing the Web components, a few small changes must be made to the Organization Unit structure and security pricipals within 3AServices.com. Perform the following steps on srv01.3aservices.com:

1. Start the Active Directory Users and Computers from Start -> All Programs -> Administrative Tools -> Active Directory Users and Computers, as shown in Figure 9-1.

Server Name Role IP address Hardware

srv03.3aservices.com Member serverIISPlatform Management for Windows Web interface



Figure 9-1 Active Directory Users and Computers

2. Select the Organization Unit IBMBB.

3. Right-click IBMBB and select New -> Organization Unit, as shown in Figure 9-2.

Chapter 9. Platform Management for Windows Web interface 153

Figure 9-2 Creating a new Organization Unit

4. Enter BlueWEB in the Name text box; see Figure 9-3.

Figure 9-3 New Object - Organization Unit

5. Click OK.


6. Right-click BlueWEB and select New -> Group; see Figure 9-4.


7. Enter WebAdmins in the Group name text box as shown in Figure 9-5.

Figure 9-5 New Object - Group


8. Click OK.

9. Now right-click BlueWEB and select New -> User; see Figure 9-6.


10.Enter WebAdmin in the First name and User logon name text boxes as shown in Figure 9-7.

Figure 9-7 New Object - User


11.Click Next.

12.In the New Object -User screen shown in Figure 9-8, enter a password in the Password and Confirm password fields.

13.Deselect User must change password at next logon.

14.Select both User cannot change password and Password never expires.

Figure 9-8 New Object - User

15.Click Next.

16.Click Finish.

17.Open the properties page of the newly created user WebAdmin; see Figure 9-9.


Figure 9-9 WebAdmin Properties

18.Select the Member of tab as shown in Figure 9-10.

Figure 9-10 WebAdmin Properties


19.Click Add, and the Select Groups screen (as shown in Figure 9-11) will be presented.

Figure 9-11 Select Groups

20.Add the WebAdmins group.

21.Click OK.

22.Click OK.

23.Click View -> Advanced Features from the mmc; see Figure 9-12.

Note: To configure the security settings for the organization group, IBMBB, the default view for the Active Directory Users and Groups snap-in must be changed.



24.Open the properties page of the organization unit IBMBB.

25.Select the Security tab.

26.Click Add to enter the Select Users, Computers, or Groups screen as shown in Figure 9-13.

Figure 9-13 Select Users, Computers or Groups

27.Add the WebAdmins group.

28.Click OK.

29.Select Full Control for the WebAdmins group as shown in Figure 9-16.


Figure 9-14 IBMBB properties

30.Click Advanced.

31.Select WebAdmins; see Figure 9-15.

Figure 9-15 Select WebAdmins


32.Click Edit.

33.In the Permissions Entry for IBMBB screen, change the drop down box Apply onto to This object and all child objects; see Figure 9-16.

Figure 9-16 Permission Entry for IBMBB

34.From the Permission Entry for IBMBB window, click OK.

35.From the Advanced Security Settings for IBMBB window, click OK.

36.From the IBMBB Properties windows, click OK.

Microsoft’s Active Directory is now configured for the Platform Management for Windows Web interface.

9.1.2 Installing the Web interface componentsBefore starting this part of the installation, php-4.3.4-win32.zip needs to be downloaded from:

http://www.php.net/downloads.php

Perform the following steps on SRV03.3aservices.com:

1. Insert the PMfW Configuration and Maintenance CD.

2. Install the PMfW Configuration and Maintenance utility (see “Platform Management for Windows: Setup and maintenance” on page 17).

3. Start the PMfW Configuration and Maintenance from Start -> All Programs -> IBM PMfW -> PMfW Configuration and Maintenance.

4. Click Next.

5. Select PMfW Tools and click Next.

6. Click BlueWEB as shown in Figure 9-17.


http://www.php.net/downloads.php

Figure 9-17 PMfW Tools

7. Enter C:\ in the Unzip to folder text box; see Figure 9-18.

Figure 9-18 WinZip Self-Extractor - BlueWEB.exe

8. Click Unzip.

9. Extract the contents of the previously downloaded php-4.3.4-win32.zip to C:\Program Files\Php. The extracted files should look like Figure 9-19.

Note: This will unzip the contents of the zip file to the c:\Blueweb directory.


Figure 9-19 C:\Program Files\php listing

10.Copy the files shown in Table 9-2 to their corresponding directory.

Table 9-2 Web Interface file copying

*In our example WINNT is the system directory.

File Name Source Destination*

php.ini C:\BlueWEB\html C:\WINNT

ixed.win.4.3.2.pxp C:\BlueWEB\ixed.zip\ixed C:\Program Files\Php\extensions

libeay32.dll C:\Program Files\Php\dlls C:\WINNT\System32

ssleay32.dll C:\Program Files\Php\dlls C:\WINNT\System32


9.1.3 Configuring Microsoft’s Internet Information ServerThese are the steps:

1. Start the Internet Information Services (IIS) Manager from Start -> All Programs -> Administrative Tools -> Internet Information Services (IIS) Manager; see Figure 9-20.

Figure 9-20 Internet Information Services (IIS) Manager

2. Open the properties page for the default Web site.

3. Select the Home Directory tab and enter C:\BlueWEB\html in the Local path text box as shown in Figure 9-21.

Note:

ixed.zip is a compressed folder, only one file needs to extracted.

If you have installed the system to another directory other than WINNT, you need to update the php.ini file:

session.save_path = "C:\WINNT\Temp"

If you install the Php files to another directory other than C:\Program Files\PHP, you need to update the php.ini file:

extension_dir = "C:\Program Files\PHP\extensions"


Figure 9-21 Default Web Site Properties

4. Click Configuration to enter the Application Configuration screen; see Figure 9-22.

Figure 9-22 Application Configuration

5. Click Add...


6. In the Add/Edit Application Extension Mapping screen, enter the path “C:\Program Files\Php\php.exe” in the Executable text box.

7. Enter .php in the Extension text box; see Figure 9-23.

Figure 9-23 Add/Edit Application Extension Mapping

8. Click OK to move to the Application Configuration screen, as shown in Figure 9-24.

Figure 9-24 Application Configuration

9. Click OK.

10.Select the Documents tab on the Default Web Site Properties dialogue box; see Figure 9-25.

Note: If there is a space anywhere in the path, then the path must be surrounded by quotation marks.



11.Click Add.

12.Add the content pages Index.html and index.php; see Figure 9-26 and Figure 9-27.

Figure 9-26 Add Content Page - index.html

Figure 9-27 Add Content Page - index.php

Note: Index.php must be the first entry in the list; see Figure 9-28 on page 169.



13.Click OK.

Configuring Internet Information Services to run .php extensions


1. Right-click on the Web Services Extensions and select Add new Web service extension...; see Figure 9-29.

Note: Due to changes made to Microsoft’s Windows 2003 Server Standard Edition, a new Web service extension must be created to allow the server to run the .php extension.


Figure 9-29 Internet Information Services (IIS) Manager

2. Enter .php in the Extension name text box as shown in Figure 9-30.

Figure 9-30 New Web Service Extension

3. Click Add.

4. Enter C:\Program files\Php\php.exe in the path to file text box; see Figure 9-31.


Figure 9-31 Add file

5. Click OK.

6. Select Set extension status to Allowed in the New Web Service Extension screen as shown in Figure 9-32.

Figure 9-32 New Web Service Extension

7. Click OK.

8. Close Internet Information Services (IIS) Manager.

9. Start C:\BlueWEB\config.exe to get the BlueWEB Setup and Maintenance screen presented, as shown in Figure 9-33.

10.Select ADS Integrated.

11.Click Lookup to resolve the LDAP path.

12.Click Apply.


Figure 9-33 Web Interface - Setup and Maintenance

13.Click OK to acknowledge that the settings have been saved.

14.To verify the setup, start Internet Explorer and type the URL http://localhost in the address box; see Figure 9-34.


Figure 9-34 IBM BlueWEB

9.1.4 Configuring the look and feel of the Web interfaceWith the release of BlueWEB Series 3, the option for the user to configure the look and feel of the Web interface has been added.

The Web interface provides the user with several configuration options such as:

� Changing the interface theme� Changing the interface language� Setting the default date format


1. Start the Web interface.2. Click the logon link; see Figure 9-35.3. Enter the user name WebAdmin and the corresponding password.


Figure 9-35 Web Interface - Logon

4. Click Logon.

Figure 9-36 shows the default administrative settings and icons for the Web interface. From here you are able to perform the same tasks that are available through the Platform Administration Center.

– Manage Targets (default view)

• Add, edit, and configure Platform Management for Windows targets.


Figure 9-36 Web Interface - standard administrative settings

– The Manage Groups screen looks like Figure 9-37.

• Add, edit, and configure Platform Management for Windows groups.


Figure 9-37 Web Interface - Managing Groups

– The Manage Products screen looks like Figure 9-38.

• Add, edit, and Platform Management for Windows products.


Figure 9-38 Web Interface - Managing Products

– The Manage WEBpacks screen looks like Figure 9-37.

• Add Platform Management for Windows WEBpacks


Figure 9-39 Web Interface - WEBpacks

– Advanced Settings

• Configure the Web interface default look and feel.

5. Click Advanced Settings to see Figure 9-40.


Figure 9-40 Web Interface - Advanced administrative settings

The icons on the left side of the browser window shown in Figure 9-40 represent the different advanced tasks that can be performed from the Web interface.

– Reports (default view)

• Here it is possible to generate Web-based reports on the status of objects in the database.

– Edit News Bulletin as shown in Figure 9-41.

• Add or edit information to be presented on the default Platform Management for Windows Web site.


Figure 9-41 Web Interface - Edit News Bulletin

– Edit Links as shown in Figure 9-42.

• Add or edit the links available on the default Platform Management for Windows Web site.


Figure 9-42 Web Interface - Edit Links

– BlueWEB defaults as shown in Figure 9-43.

• Configure the look and feel of the Platform Management for Windows Web interface.


Figure 9-43 Web Interface - BlueWEB Defaults

All of the above settings can be achieved by editing the relevant .ini files located in the BlueWEB directory. The following tables show these files and an explanation of the different keys available.

Sever connection settingsFile Name: C:\BlueWEB\blueweb.ini

Table 9-3 Server connection settings

Common BlueWEB settingsFile Name: C:\BlueWEB\html\common\settings.ini

Table 9-4 Common BlueWEB settings

Section Value

BlueWEB Configuration File <description>;<database tree>;<database server>

Key Value

Options Contains the data regarding theme, language, and date format

tivoli Enables or disables Tivoli support as well as the legacy client option within BlueWEB


Version information (reference information only)File name: C:\BlueWEB\html\common\version.ini

Table 9-5 Version Information

Theme settingsFile Name: C:\BlueWEB\html\images\<theme name>\theme.ini

Table 9-6 Theme settings

News text valuesFile Name: C.\BlueWEB\html\user\news.ini

Table 9-7 News text values

printer Enables or disables the printer page and contains the corresponding connection data

maxlist Maximum number of items to display in the administration module lists

username Sets the last modified user name (references to the corresponding Web page)

timestamp Sets the last modified date (references to the corresponding Web page)

Key Value

author name of author

edition Platform Management for Windows version

version BlueWEB version

release BlueWEB release

build BlueWEB build

year year

status application status

Key Value

Name Name that will be shown on the “BlueWEB Options” popup window describing the theme

Opacity Transparency level of inactive menu buttons and links within the main frame

Note: By adding a new theme directory containing your own .gif files, it is also possible to customize the Web interface further to meet your needs.

Key Value

BlueWEB News Bullentin Contains the “News Bulletin” message of the start page which can be modified using the administration module of BlueWEB (“Edit News Bulletin”) as well as the user name and timestamp of its last modification.

Key Value


Link lists valuesFile name: C:\BlueWEB\html\user\links.ini

Table 9-8 Link lists values

9.1.5 Web-PacksWeb-Packs are self-installing Platform Management for Windows products that are made available for user download through the Web interface. All products that are available in the database are eligible to be Web-Packs.

Platform Management for Windows targets or groups are given authorization per Web-Pack through the Platform Administration Center or Web Interface. This in turn enables administrative control over product distribution.

Perform the following steps on SRV01.3aservices.com:

1. Start the Platform Administration Center from Start -> All Programs -> IBM PMfW -> Platform Administration Center.

2. Enter Administrator in the Userid text box.

3. Enter the password in the Password text box to enter the Platform Administration Center, as shown in Figure 9-44.

Key Value

BlueWEB Shortcut List Contains the “Useful Links” list of the start page which can be modified using the administration module of BlueWEB as well as the user name and timestamp of its last modification. Each of the seven possible lines contains the following data separated by semicolon (“;”): “<link text>;<linkURL>;<link description>”



4. Click Web-Packs on the left hand side.

Figure 9-45 Platform Administration Center - Web-Packs

5. Click New.

6. Enter rarlab.winrar.3_30.ref.3103 (the full length package name) in the name text box.

7. Enter WinRar (a descriptive name) in the description text box as shown in Figure 9-46.


Figure 9-46 Platform Administration Center - New Web-Pack

8. Click Create.

9. Select the Assign Products tab on the same screen.

10.Click Add.


Note: If the Web-Pack is not created in the database before you assign the products, you will receive a PAC - Information Message asking you to save the Web-Pack.


Figure 9-47 Platform Administration Center - Search Products

12.Select rarlab.winrar.3_30.ref.3103.

13.Click OK to return to the Assigned Products tab; see Figure 9-48.

Figure 9-48 Platform Administration Center - Assigned Products

14.Select the Authorized Groups tab.


15.Click Add.


17.Select the Default group.

Figure 9-49 Platform Administration Center - Search Groups

18.Click OK to return to the Authorized Groups tab; see Figure 9-50.


Figure 9-50 Platform Administration Center - Authorized Groups

19.Click Close.

Winrar has now been made available to all targets who are members of the default group.

9.1.6 Installing applications from the Web interface

To install the new application from the Web interface, these are the steps:

1. Start the Web browser from a target that is a member of the Default group.

2. Click Add New Software as shown in Figure 9-51.

3. Select rarlab.winrar.3_30.ref.3103.

Tip: The BlueWEB client must be installed on the target. Deploying this with a Phase 2 package is recommended.

Note: rarlab.winrar.3.3.... is now available in the Latest Additions & Changes section.


Figure 9-51 Web Interface -Add New Software

4. Click Continue to confirm your selection, and move on to Figure 9-52.


Figure 9-52 Web Interface -Add New Software

5. Click Start Installation and the BlueWEB Software On Demand installation screen will be shown as in Figure 9-53.

Figure 9-53 Web Interface - Software On Demand


6. Once the installation is complete, a message will appear asking to reboot the computer.

7. Click Yes as shown in Figure 9-54.

Figure 9-54 Web Interface - Installation Complete

9.2 SummaryThis chapter has configured the Platform Management for Windows Web interface for 3AServices.com.

The Platform Management for Windows Web interface can be used to administer the Platform Management for Windows environment. It also gives the user the ability to install software packages once the Web client is installed.


Chapter 10. Technology integration preview: Integrating IBM ImageUltra Builder

Platform Management for Windows can interface with other technologies including IBM ImageUltra Builder version 2.2. This will help optimize desktop builds by allowing support for IBM ImageUltra Builder technology.

10

Note: IBM ImageUltra Builder v2.2 was under development during the creation of this publication. This chapter outlines how IBM ImageUltra Builder v2.2 can be integrated into the Platform Management for the Windows installation process. The steps outlined in the following sections will provide instructions on using IBM ImageUltra Builder v2.2 once the final product is generally available.


10.1 IBM ImageUltra BuilderIBM ImageUltra Builder assists IT departments by providing the tools required to develop, deploy, and maintain images efficiently. Through this process, IBM ImageUltra Builder modularized the image build process to allow for reuse between different machines. Integration with Platform Management for Windows enhances Platform Management for Windows functionality.

IBM ImageUltra Builder includes functions for the following:

� Platform Management for Windows supports optional integration with IBM ImageUltra Builder version 2.2. The initial client installation can be done through IBM ImageUltra Builder. This gives Platform Management for Windows environments the benefit of using IBM ImageUltra Builder technology.

� A predefined, extendable repository will enable the use of the latest IBM drivers for the newest IBM hardware through a simple import process using IBM recovery CDs.

� The Platform Management for Windows implementation of IBM ImageUltra Builder includes some preconfigured modules that can be adapted to include your organization’s operating systems and customizations. Importing these pre-configured modules makes it easy to use IBM ImageUltra Builder “out of the box” with provisions for integration into your Platform Management for Windows environment.

� Adding your own operating system, device driver, and application modules

� Creation of customized menus to allow for quick system deployment

� Managing the library of operating system, device driver, and application modules

This section will cover the installation of IBM ImageUltra Builder version 2.2 for Platform Management for Windows.

10.1.1 Requirements for IBM ImageUltra Builder v2.2These are the requirements:

� IBM ImageUltra Builder v2.2 is designed to function with Platform Management for Windows v4.0. The implementation as covered in the earlier chapters of this redbook provide this information.

� IBM ImageUltra Builder Installation CD. The installation CD includes the source to install IBM ImageUltra Builder. It will also provide some preconfigured templates for use with Platform Management for Windows. In addition, there is a pre-configured IBM ImageUltra Repository.

� To use the existing templates that are provided for Platform Management for Windows, you will need to have a Select/Volume License version of Windows 2000 Professional English/ Microsoft Windows XP Professional English.

10.1.2 Installing IBM ImageUltra Builder v2.2

Note: IBM ImageUltra Builder will be installed on a workstation in 3aservices.com (WKS01). The repository will reside on SRV01 where the workstations will access the information for the workstation build process. This will be explained in the sections to follow.


1. Insert the IBM ImageUltra Builder CD into CD-ROM of the machine you plan to be using the builder. The CD will autorun with the IBM ImageUltra Builder Installation. If it does not, run the installation.EXE from the root of the CD-ROM.

2. Click Next as shown on Figure 10-1.

Figure 10-1 Install Shield Wizard for IBM ImageUltra Builder

3. From the welcome screen, click Next.

4. Read and accept the license agreement, click Yes.

5. Choose Destination Location and click Next; see Figure 10-2.

Figure 10-2 Choose Destination Location

6. From the Setup Complete window, click Finish to restart your computer.

Chapter 10. Technology integration preview: Integrating IBM ImageUltra Builder 195

10.1.3 Common ImageUltra terminologyThe IBM ImageUltra Builder Programs allows you to store a variety of image-related files as reusable modules in a repository. Typically, there is a module for each operating system, application, and device driver. These modules are organized by maps to meet the needs of specific users, groups, or an entire organization. A single base map can contain multiple operating systems and applications. Platform Management for Windows and IBM ImageUltra Builder includes support for Windows 2000 Professional and Windows XP Professional.

For more information, see the following IBM Redbook: Using ThinkVantage Technologies: Volume 1 Creating and Deploying Client Systems Configuring ImageUltra Builder, SG247045.

10.1.4 Configuring IBM ImageUltra BuilderSome of the modules within the Platform Management for Windows IBM ImageUltra Builder CD include only the templates required for building the required modules. Due to legal reasons, it is necessary for you to add your own code into the repository accompanied by your organization’s license keys.

When building a module, the source code required for its creation are stored into a single set of files. Thus, when defining the source files and commands required for a module, ensure that the required files, settings, etc. are all in the appropriate areas before the module is built.

The following steps will outline the process for configuring IBM ImageUltra Builder with the 3aservices.com Platform Management for Windows environment.

1. Insert the Platform Management for Windows IBM ImageUltra Builder CD.

2. Map a network drive to SRV01:

net use x: \\srv01\d$ /user:administrator

3. Copy the REPOSITORY directory from the CD to X:\

4. Check the attributes on the files in X:\REPOSITORY. If there is a read-only attribute on the files, you will have to run the following command:

x:\repository>attrib -r *.* /s

5. Start IBM ImageUltra Builder through the desktop icon; see Figure 10-3.

Figure 10-3 IBM ImageUltra Builder icon

Note: Every client that will be set up with Platform Management for Windows must be defined in the configuration database before the installation. This will avoid errors when the client is searching the database for applications to be installed through the Platform Management for Windows environment.

Important: Install IBM ImageUltra Builder as shown in 10.1.2, “Installing IBM ImageUltra Builder v2.2” on page 194.


6. From the Create Repository window, click Cancel. 3sservices.com will be using the templates provided by the Platform Management for Windows IBM ImageUltra Builder CD; see Figure 10-4.

Figure 10-4 Create Repository

7. From IBM ImageUltra Builder, click File -> Open Repository as shown in Figure 10-5.

8. From the Open ImageUltra repository window, click Browse.

Figure 10-5 Open ImageUltra repository

9. Highlight repository on SRV01 and click OK; see Figure 10-6.


Figure 10-6 Browse for repository

10.The following information shown in Figure 10-7 will appear in the console.

Figure 10-7 IBM ImageUltra Builder

11.Click Tools -> Options to start Repository Options.

12.Select the Network Install tab; see Figure 10-8.


Figure 10-8 Repository Options

13.Enter the following information and click OK:

– Location: \\SRV01\repository– Server IP Address: 10.1.0.10

Creating an operating system moduleThis section covers the steps required to add your own operating system source code to the repository:

1. Click the Platform Management for Windows folder, as shown in Figure 10-9.


Figure 10-9 Platform Management for Windows folder

2. Click Insert -> Operating System... from the file menu.

3. From the Create module window, click Next.

4. Select Operating System and click Next; see Figure 10-10.


Figure 10-10 Create Module

5. Enter the name of the module as listed below and click Next; see Figure 10-11:

3aservices.com Microsoft Windows XP Professional i386

Figure 10-11 Name the module


6. We will be using the settings from the existing Platform Management for Windows Template. Select PMfW Template Microsoft Windows XP Professional i386 and click Next as shown in Figure 10-12.

Figure 10-12 Select the PMfW template

7. Uncheck Open the new module for editing after this wizard closes and click Finish.

You will see 3aservices.com Microsoft Windows XP Professional i386 in Figure 10-13.

Figure 10-13 Viewing the newly created module

8. Copy the \i386 folder contents from the Microsoft Windows XP Professional CD to x:\repository\source\pmfw\i386\wxp_pro_en\i386.


This puts the i386 source files into the location where the build process will be using it to create the module.

9. Delete x:\repository\source\pmfw\i386\wxp_pro_en\i386\unattend.txt.

10.Right-click 3aservices.com Microsoft Windows XP Professional i386 and click BUILD; see Figure 10-14.

This step takes the i386 code you have copied and builds it into a IBM ImageUltra Builder module.

Figure 10-14 Building a module

11.Click Finish.

Tip: To ensure installation files for \i386 are up to date, make sure you slipstream the source files with the service pack you plan to deploy within your organization.

Microsoft Windows XP Professional Service Pack 1 has been tested with this template.

Update .exe command-line switches for Windows 2000 Service Packs:


See the the article, How to Slipstream Hotfixes That Replace Pre-Existing Driver Files:





Figure 10-15 Review the scripts

Building a module with a custom unattend.txtThese are the steps:

1. Click the Platform Management for Windows folder.

2. Click Insert -> Operating System from the file menu.

3. From the Create Module window, click Next.

4. Select Operating System and click Next.

Figure 10-16 Create Module


5. Enter the name of the module as follows and click Next:

3aservices.com Microsoft Windows XP Professional Unattend.txt

Figure 10-17 Naming the module

6. We will be using the settings from the existing Platform Management for Windows Template. Select PMfW Template Microsoft Windows XP Professional unattend.txt and click Next.


Figure 10-18 Unattend.txt template


8. 3aservices.com requires the following customizations to the unattend.txt. The unattend.txt that needs to be modified is located in: x:\repository\source\pmfw\unattend\wxp\ . Make the following changes (no other lines were modified at this time):

Example 10-1 3aervices.com UNATTEND.TXT

[UserData]ProductKey="<enter your product key here>" FullName="3aservices.com"OrgName="3aservices.com"; ### CAUTION 'ComputerName' is a mandatory PMfW setting! Default: "*"ComputerName=*

[identification]joindomain = "3Aservices.com"domainadmin = "[email protected]"domainadminpassword = "Passw0rd"

9. Right-click the new module (3aservices.com Microsoft Windows XP Professional unattend.txt) and select BUILD.


Figure 10-19 Build the custom unattend.txt module

10.From the Review your scripts window, click Finish.

Figure 10-20 Review your scripts

Creating a base mapA base map is needed to define the structure within the image. 3aserivces.com will use the base map templates that are included in the Platform Management for Windows IBM ImageUltra Builder CD:

1. Click Insert -> Base Map... from the file menu.

2. From the Create Map window, click Next.

3. Select BASE MAP and click Next.

4. From the Create Map window, enter the following information and click Next:

Name: 3aservices.com Microsoft Windows XP Professional


Figure 10-21 Creating a Base Map for 3aservices.com

5. Select PMfW Template Microsoft Windows XP Professional and click Next.


Figure 10-22 Using PMfW Template for base map creation


7. Click the Base Map tab and double-click the 3aservices.com Microsoft Windows XP Professional base map.


Figure 10-23 3aservices.com base map

8. Right-click ENGLISH -> INSERT -> Operating System.


Figure 10-24 Add the operating system to the base map

9. Click the Platform Management for Windows folder and select (use CTRL key in conjunction with the mouse click to select multiple items) the following:

– 3aservices.com Microsoft Windows XP Professional i386– 3aservices.com Microsoft Windows XP Professional unattend.txt

Figure 10-25 Adding the operating system and Unattend.txt

10.Click OK.

11.Right-click 3aservices.com Microsoft Windows XP Professional from the base map and select SETTINGS.


Figure 10-26 Base map settings

12.Select the User Information tab.


Figure 10-27 Customizing User Information

13.Double-click ComputerName under Field Name (Figure 10-27).

14.Under Default Value, enter Default: WKS and click OK.


Figure 10-28 Changing the default user name

15.Click OK to close map settings.

16.Click File -> Save to save the changes made to this base map.

17.Click File -> Close to return to the repository.

Creating a deploy disketteThis disk will be used to deploy workstations that will be loading their operating system through IBM ImageUltra Builder:

1. Click TOOLS -> DEPLOY from the file menu.2. Click Next.3. Select Deploy over my network and click Next.


Figure 10-29 Deploy over network

4. Select ImageUltra Deploy Diskette and click Next.

Figure 10-30 ImageUltra Deploy Diskette

5. Click the Repository tab and enter \\srv01\repository.


Figure 10-31 Repository location

6. Click the Network tab; the repository IP address should be 10.1.0.10. The other information is only required if a static IP address is required during deployment.

Figure 10-32 Network information

7. Click the Connect As tab and enter the following information:

– Username: swddsk– Password: Passw0rd– Domain: 3aservices.com


Figure 10-33 “Connect As” information

8. Click Next. (If a windows appears with a warning about multiple connections, click OK and click YES to save the settings.)

9. From the Deploy Smart Image window, click Create Diskette.

Figure 10-34 Create BootDisk

10.From the Create another? window, click NO.

11.Click Finish.


12.Create a folder named PMfW on the IBM ImageUltra boot disk. Copy the contents of the config folder from the root of a Platform Management for Windows BootDisk to this directory. See 3.2, “Creating a BootDisk” on page 51.

Configure the Windows repositoryThe repository folder needs to be shared so other machines can access the information being accessed during the image build process:

� Share the folder \\srv01\repository as repository.

Make sure the swddsk ID has read-write access to the directory as we will be deploying the test machine through the network.

Building the platform preparation module (only for Windows 2000)

1. Click Insert -> Application... from the file menu.

2. Create module: Click Next.

3. Create module: Select Application and click Next.

Figure 10-35 Create application module

Note: If you are installing Microsoft Windows 2000 Professional, you will need to copy sc.exe from the Windows 2000 Resource Kit to source\pmfw\add-on\platform preparation\maint\$$\PMfW_TMP.

This tool is used by some Phase 2 packages to start, stop, disable or delete services, and interact with the desktop, etc.

This module will have to be added to the Windows 2000 base map.


4. Enter the name of the module and click Next.

Name: PMfW Platform Preparation

Figure 10-36 Create Module - PMfW Platform Preparation

5. Select PMfW Template Platform Preparation from the list and click Next.

Figure 10-37 PMfW template platform preparation



Right-click on the newly created module, and click BUILD.

10.1.5 Testing the build process To test the build process, use the IBM ImageUltra boot disk created in this chapter. When prompted, select the appropriate operating system and driver map that is associated with the machine being installed. When prompted for a computer name, enter a workstation name that has been created in the Platform Management for Windows database (such as WKS02).

Tip: To optimize deployment times on mass deployments, the machines can be cloned (using Symantec Ghost or PowerQuest Drive Image) after the service partition information has been loaded to a donor system. On first boot, the machine will ask for the computer name as associated with the Platform Management for Windows database.


Chapter 11. Conclusion

Platform Management for Windows can be used to deploy clients and servers in varied environments. This book has shown how to set up a Platform Management for Windows environment for 3AServices.com. The following topics have been covered:

� Installing Platform Management for Windows� Configuring Platform Management for Windows� Building a workstation� Building a server� Creating software packages for deployment with Platform Management for Windows� Workstation Installation through DVD� CID synchronization� Integration of new hardware� Platform Management for Windows Web interface� Integration with IBM ImageUltra Builder

Following the steps described in this book provides the user with an introduction to Platform Management for Windows as well as a working test environment. This environment can be used to become familiar with the different functions, tools, and procedures that together make Platform Management for Windows.

11



Appendix A. Tools to implement the Platform Management for Windows solution

This appendix discusses the use of additional tools that can help with the implementation of various Platform Management for Windows components.

A


Using Package Builder to add an application

3aservices.com will be using WinRAR in their organization. This example shows how to use Package Builder to add WinRAR as an application within their CID tree. Our WinRAR example is named rarlab.winrar.3_30.ref.3103.

Package Builder creates the necessary file structure that will be used in the CID tree.

A.0.1 Package Builder requirementsTo install WinRAR as an installable application in the 3aservices.com environment, you will need the following before continuing:

� Package Builder (This is located on the Platform Management for Windows setup and maintenance CD.)

� WinRAR installation source is downloaded from:

http://www.rarlab.com/download.htm

A.0.2 Using Package Builder with CID synchronizationThis section will outline the installation process for using Package Builder to create the application in the CID structure:

1. Start the Package Builder (E: is the location of Platform Management for Windows - Setup and Maintenance CD):

E:\Unsupported\PackageBuilde\packagebuilder3_61.exe

2. Click the General tab, and enter the following information as in Figure 11-1:

– Driver letter containing CID directory: D– New Package Name: rarlab.winrar.3_30.ref.3103– Package Description: rarlab.winrar.3_30.ref.3103– Space Requirements in KB: 3800– Package Name: 3aservices Admin

Attention: Package Builder (packagebuilder3_61.exe) is provided as an unsupported product. However, using these tools can speed up the process of adding an application to the database through the automated creation of file and directory structures.

Tip: If CID synchronization is used, it is important to know that Package Builder will put the file structure into the CID tree where it will need to be moved, so that synchronization can take place (\CIDAREAS\EDITAREAS).




Figure 11-1 Package Builder - General Information

3. Click the Installation tab and enter the information as follows; see Figure 11-2:

– Installation method: Standard Wise Setup (Classic)– Setup parameters: -s

Figure 11-2 Package Builder - Installation

4. Click the Source tab as shown in Figure 11-3.

Appendix A. Tools to implement the Platform Management for Windows solution 225

Figure 11-3 Application Source

5. From the Source tab, click Create Directory Structure. This will create the directory structure for this application.

6. From the Source tab, click Copy Source Code, a window similar to Figure 11-4 will appear. This window is the location of where the source files need to be copied into.

Figure 11-4 Copy source code

7. Using Explorer, copy wrar33b5.exe in to D:\CID\3\rarlab.winrar.3_30\ref.3103\img. You will see the files in the directory displayed as in Figure 11-4.

Important: As mentioned earlier in this chapter, this tool will create the file structure in the CID tree. If using CID synchronization, this entire file structure will have to be moved to the edit area so synchronization takes place.


8. From the Source tab, click Select Setup Program, highlight wrar33b5.exe and click Open as shown in Figure 11-5.

Figure 11-5 Select setup program

9. Click Generate Files; see Figure 11-6.

Figure 11-6 Generate files

10.Click OK once the files have been created successfully as shown in Figure 11-7.


Figure 11-7 Successful file creation

11.Click Exit.

12.Click YES to confirm exit.

A.0.3 Registering the application in the databaseThis section explains how the application must be registered in the database so it can be used by Platform Management for Windows:

1. From the Platform Administration Center window, click Configuration Data.

2. Click Products. This will lead you to the screen shown in Figure 11-8.

Figure 11-8 Adding Products using the Platform Administration Center

3. From the Products window, click Search.

4. From the Products window, click New; see Figure 11-9.

5. Enter the following information and click OK:


– Name: rarlab.winrar.3_30.ref.3103– Description: rarlab.winrar.3_30.ref.3103– Select multiple assignments allowed

Figure 11-9 Products

6. This will bring us back to the products screen as shown in Figure 11-9.

Note: Notice that WinRAR appears in the product list.


Figure 11-10 Product listing

A.0.4 Testing the new application Now that the product has been registered in the database, we will test that it will install on a workstation. WKS01 is used in our test. It was created using Platform Management for Windows:

1. Create a file named request.txt. It should include the following line as shown in Example 11-1.

Example 11-1 request.txt

rarlab.winrar.3_30.ref.3103

2. Copy request.txt to C:\MAINT\SWD.

3. Wait 30 seconds. The file should disappear from this directory as it is processed by the WKS01.

4. The silent installation should commence and the application should be visible from:

START -> PROGRAMS ->WinRAR

5. To verify the installation, check C:\MAINT\SWD\LOG. There should be a file named rarlab.winrar.3_30.red.3103.log; see Example 11-2. The following return code shows that the installation completed properly:

17.02.2004 12:10:28 --- * end exit. RC = 0

In addition, take note of the installation command to ensure that it is installing the way we have requested:

17.02.2004 12:10:25 --- **** STARTING INSTALL PROGRAM. ("X:\3\rarlab.winrar.3_30\ref.3103\img\wrar33b5.exe" -s)


Example 11-2 rarlab.winrar.3_30.red.3103.log

17.02.2004 12:10:22 --- * OPENING INSTBOT 3.0 log file for >rarlab.winrar.3_30.ref.3103<17.02.2004 12:10:22 --- Got following argument(s) from commit script: rarlab.winrar.3_30.ref.3103 none17.02.2004 12:10:22 --- connecting >X:< to CID17.02.2004 12:10:22 --- using >[email protected]< to connect To >SRV01<17.02.2004 12:10:22 --- ** InstCommand: C:\WINNT\system32\cscript.exe X:3\rarlab.winrar.3_30\ref.3103\scr\winrar.vbs rarlab.winrar.3_30.ref.310317.02.2004 12:10:22 --- STARTING - product script...17.02.2004 12:10:22 --- -----------------------------------------------------------17.02.2004 12:10:25 --- * OPENING product.vbs log file for >rarlab.winrar.3_30.ref.3103< on WKS0117.02.2004 12:10:25 --- ** begin install procedure17.02.2004 12:10:25 --- Got following argument from commit script: rarlab.winrar.3_30.ref.310317.02.2004 12:10:25 --- **** CREATE RSP FILE for Product: rarlab.winrar.3_30.ref.3103 | RSP file: C:\maint\swd\rsp\rarlab.winrar.3_30.ref.3103.rsp | Original file name: 17.02.2004 12:10:25 --- **** Cheking for: wrar33b5.exe17.02.2004 12:10:25 --- Ok.17.02.2004 12:10:25 --- *** begin switch Terminal Server...17.02.2004 12:10:25 --- This is not a TerminalServer in Application mode. No need to switch user.17.02.2004 12:10:25 --- *** end switch Terminal Server.17.02.2004 12:10:25 --- **** STARTING INSTALL PROGRAM. ("X:\3\rarlab.winrar.3_30\ref.3103\img\wrar33b5.exe" -s)17.02.2004 12:10:28 --- **** FINISHED INSTALL PROGRAM (0).17.02.2004 12:10:28 --- *** begin switch Terminal Server...17.02.2004 12:10:28 --- This is not a TerminalServer in Application mode. No need to switch user.17.02.2004 12:10:28 --- *** end switch Terminal Server.17.02.2004 12:10:28 --- ** end install procedure17.02.2004 12:10:28 --- * begin FinishPackage...17.02.2004 12:10:28 --- Creating version (VER) file.17.02.2004 12:10:28 --- Increasing product install counter in registry.17.02.2004 12:10:28 --- * end FinishPackage.17.02.2004 12:10:28 --- * begin exit...17.02.2004 12:10:28 --- RC_INST_OK - installation OK!17.02.2004 12:10:28 --- Creating event log entry17.02.2004 12:10:28 --- * end exit. RC = 017.02.2004 12:10:28 --- * CLOSING product.vbs log file for >rarlab.winrar.3_30.ref.3103<17.02.2004 12:10:29 --- -----------------------------------------------------------17.02.2004 12:10:29 --- FINISHED - product script...17.02.2004 12:10:29 --- ** InstCommand ended with RC: 017.02.2004 12:10:29 --- disconnecting CID drive17.02.2004 12:10:29 --- * CLOSING INSTBOT 3.0 log file for >rarlab.winrar.3_30.ref.3103<

This package has now been deployed to WKS01.



Appendix B. Using system log files

This appendix provides information regarding log files within the Platform Management for Windows system.

B


System log filesThe Platform Management for Windows environment uses the following log files. These can be useful when troubleshooting errors.

Table B-1 System log files

Log file sequencingThe following list outlines when the log files are created in a Platform Management for Windows environment. It will be useful to know when and where these log files are created for troubleshooting:

� Phase 1

%SystemDrive%\maint\phase1.log

%SystemDrive%\maint\slots\slotsrv\slots.log

%SystemDrive%\maint\slots\apps\xxx\*.log

� Phase 2

%SystemDrive%\maint\sid\*.*

%SystemDrive%\maint\sid\TaskH\TaskHservice.log

%SystemDrive%\maint\sid\UPDATE\update.log

%SystemDrive%\maint\swd\log\*.*

Log file name Description

%SystemDrive%\maint\phase1.log Connecting the first time to the PMfWdatabase. Writing important PMfWinformation to the registry. Installationof the slot service.

%SystemDrive%\maint\slots\slotsrv\slots.log Log of the slot service

%SystemDrive%\maint\slots\apps\xxx\*.log Log of the xxx – slot application

%SystemDrive%\maint\slots\apps\instie\kickph2.log (client)%SystemDrive%\maint\slots\apps\insties\kickph2.log (server)

Start of Phase 2:Querying the database for the list of phase 2 packages to be installed.Generating this list at %SystemDrive%\maint\swd\request.txt

%SystemDrive%\maint\swd\log\*.* Log files of the phase 2 applicationpackages

%SystemDrive%\maint\STARTUP\CIDSyncWizard.vbs.log Will exist after setup on the CID server

%SystemDrive%\maint\STARTUPV4_IDS\*.* Will exist after setup on the database server (IDS). Contains logs and work files

%SystemDrive%\maint\STARTUPV4_ADS\*.* Will exist after setup on the database server (ADS). Contains logs and work files

%SystemDrive%\maint\facade\SetupHistory.log Will exist after facade installation.

%SystemDrive%\maint\sid\*.*%SystemDrive%\maint\sid\TaskH\TaskHservice.log%SystemDrive%\maint\sid\UPDATE\update.log

Log files of Software Installation Dispatcher (SID) and related components.


In addition, these tools are useful for troubleshooting, and can be used in special install stages:

� %SystemDrive%\maint\cust\retry.bat (deleted after phase 1)

Use this tool is to continue installation if your machine hung with the One or more tools (e.g. sc.exe, instsrv.exe...) are missing! error in phase 1. Fix the problem of the missing tools, before using retry.bat.

� %SystemDrive%\maint\slots\apps\insties\4rootDC.bat

4rootDC.bat can be used for triggering again phase 2 on the root domain controller. 4rootDC.bat creates the package list again so SID can install them.

� %SystemDrive%\maint\slots\apps\instie\rePh2.bat

It can be used for triggering again phase 2 on client machines, if they had problems starting phase 2.

Appendix B. Using system log files 235


Glossary

Your glossary term, acronym, or abbreviation. Term definition.

ADS. Active Directory Services.

CID Sync. Replication of CID packages between CID servers.

CID. Configuration, Installation, and Distribution.

DHCP. Dynamic Host Configuration Protocol.

DNS. Domain Name Server.

EULA. End User Licence Agreement.

IUB. IBM ImageUltra Builder.

LAN. Local area network.

LDAP. Light Directory Access Protocol.

PAC. Platform Administration Center.

PMfW. Platform Management for Windows.

SMS. Systems Management Server.

SWD. Software Distribution.

VBS. Visual Basic Script.

WHS. Windows Scripting Host.

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


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 239. Note that some of the documents referenced here may be available in softcopy only.

� An Introduction to Tivoli Enterprise, SG24-5494

� Using ThinkVantage Technologies: Volume 1 Creating and Deploying Client Systems, SG24-7045

Other publicationsThese publications are also relevant as further information sources and delivered on the IBM Platform Management for Windows distribution media:

� PMFW 4.0 - Packaging Standard V3.0� PMFW 4.0 - Software Distribution� PMFW 4.0 - Technical Background� PMFW 4.0 - Tools and Utilities� PMFW 4.0 - User Guide� PMFW 4.0 - What’s New

Online resourcesThese Web sites and URLs are also relevant as further information sources:

� IBM Tivoli Directory Server Version 5.1 Installation and Configuration Guide

http://www-1.ibm.com/support/docview.wss?rs=0&context=SWI20&q1=ibm+directory+server&uid=swg27002425&loc=en_US&cs=utf-8&cc=us&lang=en

� Microsoft Active Directory


� Windows Scripting Host

http://msdn.microsoft.com/archive/default.asp?url=/archive/en-us/dnarwsh/html/msdn_wsh_wp.asp

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


http://www.ibm.com/support/

http://www.ibm.com/support/

http://www.ibm.com/services/

http://www.ibm.com/services/

Index

Numerics3AServices.com 9, 633aservices.com Base Map 2103AServices.com environment 13

AActive Directory Users and Computers 153Adapter Properties 146Add Content Page - index.html 168Add Content Page - index.php 168Add the operating system to the base map 211Add/Edit Application Extension Mapping 167Adding an Alias for bbcdb 17Adding Packages to an Existing Group 93Adding Products using the Platform Administration Center 89, 228Application packages (operating systems) 34Applying packages on target 64

BBase map settings 212Boot Devices 110BootDisk Configurator Information 29BootDisk network support files 132Browse for repository 198Build the custom unattend.txt module 207Building a module 203

CChanging the default user name 214Choose Destination Location 195Choose your search and installation options 136CID Access 38CID configuration completed successfull 23CID Configuration Progress 125CID Network Controller Login 120CID Setup 117CID Setup - Configure synchronized CID Tree 125CID Synchronization - Setup 124CID Synchronization plug-in 119CID Tree 22CID Tree Synchronization - Setup 116Client Hardware Integration 130configurator info 29Configure synchronized CID Tree 114Configure the BootDisk 52Configuring Active Directory 21Configuring standalone CID Server 23Connection Properties 145Copy Database Wizard - Complete 106Copy Database Wizard - Products 104Copy Database Wizard - Select Groups 102

© Copyright IBM Corp. 2004. All rights reserved.

Copy Database Wizard - Select Objects 101Copy Database Wizard - Select Products 104Copy Database Wizard - Select Targets 103Copy Database Wizard - Select Web-Packs 105Copy Database Wizard - Specify Global Copy Attributes 101Copy Database Wizard - Specify Target Database 100Copy mass storage driver 148copying files 121Create a new target 78Create Application Module 218Create BootDisk 217Create Module 204Create Module - PMfW Platform Preparation 219Create MS Access Database. 100Create Repository 197Creating a Base Map for 3Aservices.com 208Creating a BootDisk 51Creating a Default group 40Creating a directory structure for Norton Antivirus 86Creating a Master CID Server 39Creating a new organization Unit 154Creating a server installation BootDisk 69Creating a target. 42Creating Multiple Targets 47Creating the Disk 52Customer Information 28Customizing User Information 213

DDatabase Logon 33Default Web Site Properties 166Deploy over network 215Diskman Configuration 74

EEditing BBdomain.db 54Editing CCserver.db 54Enter a computer name for the Target 64Exit to DOS 131

FFile Structure for CID 89Files for symantec.nav.7_61 88Final Reboot 82Formatting Server hard disk 79Formatting Workstation hard disk 61Full Mode View 72

GGenerating an original PMfW v4.0 / v4.02 BootDisk 51Groups 41

241

Groups and Products 45Groups and products 45

HHardware Type 136Hardware Update Wizard 135

IIBM ImageUltra Builder 194IBMBB properties 161Identify all files with ibm.packagetemplate 87ImageUltra Deploy Diskette 215Install from disk 137Installation directory 30Installation process 14Installing and configuring the Web interface for 3AServices.com 152Installing Phase 2 Applications 32Installing the “Phoenix” Tool 27Installing the BootDisk Configurator 29Installing the Platform Administration Center 25Installing the Workstation 60InstallShield Wizard for IBM ImageUltra Builder 195Internet Information Services (IIS) Manager 170

LList of created targets 48Log file sequencing 234

MMaster CID configuration for srv01.3aservices.com 118Master CID installation for srv01.3aservices.com 112Modifying Default Domain Controller Settings 16

NNetwork adapter properties 144Network connections 144Network settings 59New server ticket 71New Target 43New Web Service Extension 171

OObjectives 3Offline directory structure 108Offline directory structure expanded 109Offline Installation (operating system only) 96Offline Installation directory structure 96Offline Installation for 3AServices.com 97Open ImageUltra repository 197Operating systems 57Other Devices 134

PPackage Builder - General Information 225Package Builder - Installation 225

Packaging Template Directory Structure 85Permission Entry for IBMBB 162Phase 2 Application Packaging Template 84Platform Administration Center 37, 98, 185Platform Administration Center - Assigned Products 187Platform Administration Center - Authorized Groups 189Platform Administration Center - Child Forms 36Platform Administration Center - Login 35Platform Administration Center - New Web-Pack 186Platform Administration Center - Options 118Platform Administration Center - Search Groups 188Platform Administration Center - Search Products 187Platform Administration Center - Target Database. 106Platform Administration Center - Utilities 99Platform Administration Center - Web-Packs 185Platform Management for Windows Architecture 5Platform Management for Windows Bootstrap Loader 81Platform Management for Windows Configuration and Maintenance 19, 112Platform Management for Windows Configuration Data-base 7Platform Management for Windows End to End flow 8Platform Management for Windows Package Builder 92Platform Management for Windows Package Wrapper 84Platform Management for Windows Setup and Mainte-nance 18Platform Management for Windows Software Packages 84PMfW Conditions Check 20PMfW Database Active Directory 20PMfW Options Database 19PMfW Template Platform Preparation 219

RRedbooks Web site 239

Contact us xxiReference Material 4Refreshing the CID Synchronization servers 122Repository Location 216Repository Options 199Run in Real Mode 60, 79

SSearch and Replace with new package information 87Search for CID Server 44Select a Detected Network driver 61, 80Select Groups 93, 159Select Hardware in the list 63Select the device driver you want to install for this hard-ware 138Select the PMfW Template 202Select Users, Computers or Groups 160Select WebAdmins 161Selecting Default Group 46Selecting Installation Type 27Selecting Phase 2 Applications 32Selecting Products 42, 94Selecting the Platform Management for Windows tools

242 Installation, Configuration, and Packaging Using Platform Management for Windows

24Selecting the PMfW tools 24Server Hardware Integration 141Server installation 78Setup - PMfW BootDisk Configurator v2.0 / v2.02 31Slave CID Installation for srv02.3aservices.com 123Slot Applications 73Slots.lst 58Start Menu Folder 30Starting the Platform Administration Center (PAC) 35Successful Account Creation 21Successful Connection to Z

62Successfully installed driver 139Sucessful install of devices 140Summary 48Platform Administration Center 121, 123

TTarget environment 9Target name mask 55TCP/IP Parameters in BootDisk 62The Phoenix tool 28, 68The Phoenix tool setup type 28

UUnattend.txt template 206Update driver 135Using Facade and Platform Administration Center 26Using PMfW Template for Base Map Creation 209Using the Packaging Template for application packaging 85

VVerify Applications are Registered 33Verifying Master / Slave relationship 126

WWeb Interface - Advanced administrative settings 179Web Interface - Defaults 182Web Interface - Edit Links 181Web Interface - Edit News Bulletin 180Web Interface - Installation Complete 192Web Interface - Logon 174Web Interface - Managing Groups 176Web Interface - Managing Products 177Web Interface - Setup and Maintenance 172Web Interface - Software On Demand 191Web Interface - standard administrative settings 175Web Interface - WEBpacks 178Web Interface -Add New Software 191WebAdmin Properties 158Welcome Platform Management for Windows 24Welcome to Platform Management for Windows 31What is covered in this book? 3What is out of scope? 4Windows 2003 Server Setup 80Windows 2003 Server Ticket 70

Windows XP Professional 65Write Ticket 77

Index 243

244 Installation, Configuration, and Packaging Using Platform Management for Windows

(0.5” spine)0.475”<

->0.873”

250 <->

459 pages

IBM Platform

Managem

ent for Window

s

Platform M

anagement for W

indows

Platform M

anagement for W

indows

Platform M

anagement for W

indows

Platform M

anagement for W

indows

Platform M

anagement for W

indows

®

SG24-7050-00 ISBN 0738490377

INTERNATIONAL TECHNICALSUPPORTORGANIZATION

BUILDING TECHNICAL INFORMATION BASED ON PRACTICAL 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

IBM Platform Management for Windows

Installation of the Platform Management for Windows solution

Configuration of the Windows client and server provisioning

Packaging software applications for distribution

IBM Platform Management for Windows is a common Windows platform for large-scale rollout of Windows 2000 and XP to clients, and Windows 2000 and 2003 to servers. Platform Management for Windows can either be used stand-alone or tightly integrated with Systems Management frameworks such as Tivoli or Microsoft SMS. It is targeted towards customers having anything between 100 and 100,000 clients, and 5 to 500 servers.

IBM Platform Management for Windows is integrated with the IBM ThinkVantage Tools such as IBM ImageUltra Builder and contains a set of additional automated deployment tools and procedures for roll out of clients, servers, and platform infrastructure components. It also includes and LDAP, or Active Directory-based data repository for customer platform parameters, and tools for Windows 2000/XP administration.

Platform Management for Windows is based on innovative and truly dynamic software distribution technology (which is totally hardware-independent contrary to usual “imaging-based” methods), and inherently supports many different server, desktop, and notebook models from a wide variety of manufacturers.

Back cover


