TME 10 Software Distribution AutoPack User s Guide. Version 3.6

Transcription

1 TME 10 Software Distribution AutoPack User s Guide Version 3.6 September 1998

2

3 TME 10 Software Distribution AutoPack User s Guide (September 1998) Copyright Notice Copyright 1998 by Tivoli Systems, an IBM Company, including this documentation and all software. All rights reserved. May only be used pursuant to a Tivoli Systems Software License Agreement or Addendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of Tivoli Systems. The document is not intended for production and is furnished as is without warranty of any kind. All warranties on this document are hereby disclaimed including the warranties of merchantability and fitness for a particular purpose. Note to U.S. Government Users Documentation related to restricted rights Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation. Trademarks The following product names are trademarks of Tivoli Systems or IBM Corporation: AIX, IBM, OS/2, RISC System/6000, Tivoli Management Environment, TME 10, TME 10 Framework, TME 10 Inventory, TME 10 Software Installation Service, TME 10 Software Distribution, and TME 10 Software Distribution AutoPack. Microsoft, Windows, and the Windows 95 logo are trademarks or registered trademarks of Microsoft Corporation. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited. Other company, product, and service names mentioned in this document may be trademarks or servicemarks of others. Notice References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended to imply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to Tivoli System s or IBM s valid intellectual property or other legally protectable right, any functionally equivalent product, program, or service can be used instead of the referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, except those expressly designated by Tivoli Systems or IBM, are the responsibility of the user. Tivoli Systems or IBM may have patents or pending patent applications covering subject matter 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 the IBM Director of Licensing, IBM Corporation, 500 Columbus Avenue, Thornwood, New York

4

5 TME 10 Software Distribution AutoPack User s Guide Preface...iii I Using AutoPacks Chapter 1 Overview and Installation The AutoPack Control Center The AutoPack Agent The AutoPack Profile AutoPack Control Center Installation Installing on Windows NT or Windows Installing on Windows AutoPack Agent Installation Chapter 2 AutoPack Control Center Creating the AutoPack File Editing an Existing AutoPack File Managing AutoPack File Distributions Locked-files Support Option Replace Newer Files Option Chapter 3 AutoPack Profile Operations Creating an AutoPack Profile Desktop Command Line Setting AutoPack Profile Properties Calculating the Size of an AutoPack TME 10 Software Distribution AutoPack User s Guide i

6 Distributing an AutoPack Profile Drag and Drop Desktop Command Line Removing an AutoPack The autopack.log File II Reference Appendix A Frequently Asked Questions Software Distribution and Framework Concepts... A-1 AutoPack Files... A-3 AutoPack Profiles... A-9 Distributions... A-12 Configuration Programs... A-13 Troubleshooting and Logging Information... A-14 PCs... A-14 Appendix B Behind the Scenes The Pre-installation Scan...B-1 The Post-installation Scan...B-2 The.CHG File...B-3.CHG File Sections...B-4.CHG File MACROs...B-6 The.DEF File...B-9 The.ERR File...B-10 The.REP File...B-10 The.PAK File...B-11 ii Version 3.6

7 Appendix C Configuration Programs Editing the.def File... C-1 Setting Error Codes... C-6 Example Configuration Programs... C-7 TME 10 Software Distribution AutoPack User s Guide iii

8 iv Version 3.6

9 Preface Preface Tivoli Management Environment 10 (TME 10) Software Distribution provides a means for managing and distributing software across a multi-platform network. Similar to a file package, an AutoPack is a TME 10 Software Distribution profile type that provides a simple, convenient way to create installable images for Windows machines in your TME 10 environment. An AutoPack enables you to distribute software to Windows-based client systems without doing anything outside of its creation process. This guide explains the concepts and procedures necessary for you to use Software Distribution s AutoPack technology. It describes and demonstrates how to create an AutoPack file, and then distribute this file using an AutoPack profile. The steps for customizing and setting properties for AutoPack profiles are also included in this guide. Note: The information contained in this guide is also included in the TME 10 Software Distribution User s Guide. Also, the AutoPack Control Center graphical user interface includes online help information about creating AutoPack files. Who Should Read This Guide The target audience for this guide is system administrators who build and distribute AutoPacks. Users of the guide should have some knowledge of the following: The TME 10 Software Distribution product The TME 10 Framework product Operating systems running on target machines to which software is distributed TME 10 Software Distribution AutoPack User s Guide v

10 Preface Prerequisite and Related Documents You must understand the information in the following manuals before attempting to use this guide: TME 10 Software Distribution User s Guide Provides concepts and procedures for daily file package and AutoPack operations. TME 10 Software Distribution Reference Manual Provides command line syntax and usage as well as information about advanced features used to customize TME 10 Software Distribution for the distribution environment. TME 10 Framework User s Guide, TME 10 Framework Planning and Installation Guide, and TME 10 Framework Reference Manual Provide detailed information and procedures to manage the TME 10 environment from the TME 10 desktop or the command line interface (CLI), including information about configuring, maintaining, and troubleshooting your TME 10 installation. What This Guide Contains The TME 10 Software Distribution AutoPack User s Guide contains the following sections: Part I Using AutoPacks Chapter 1, Overview and Installation Provides conceptual information about AutoPack functionality and features. Also provides procedures for installing the AutoPack Control Center and AutoPack agents. Chapter 2, AutoPack Control Center Describes how to create an AutoPack file using the AutoPack Control Center utility. Chapter 3, AutoPack Profile Operations Describes how to create, calculate the size of, distribute, and remove an AutoPack profile in your environment. vi Version 3.6

11 Preface Part II Reference Appendix A, Frequently Asked Questions Lists common questions about using AutoPacks and provides answers to each. Appendix B, Behind the Scenes Describes the files created by the AutoPack Control Center that comprise an AutoPack file. Appendix C, Configuration Programs Describes the steps to add configuration scripts in order to customize an AutoPack file. Typeface Conventions The guide uses several typeface conventions for special terms and actions. These conventions have the following meaning: Bold Italics Commands, keywords, file names, or other information that you must use literally appear in bold typeface. Names of windows, dialogs, and other controls also appear in bold. Variables and values that you must provide appear in italics. Bold Italics New terms appear in bold italic typeface the first time they are used. Monospace Code examples appear in monospace font. Many procedures in this guide include icons in the left margin. These icons provide context for performing a step within a procedure. For example, if you start a procedure by double-clicking on a policy region icon, that icon appears in the left margin next to the first step. If the fourth step of the procedure instructs you to open another icon, that icon appears in the left margin next to the fourth step. TME 10 Software Distribution AutoPack User s Guide vii

12 Preface Platform-specific Information The following table identifies the supported platform versions known at the time of publication. For more detailed and up-to-date information, please see the release notes. Platform AIX 4.x AS/400 Digital UNIX DG/UX HP-UX NCR NetWare OS/2 Pyramid Sequent Supported Versions Managed Node, Endpoint: IBM RS/6000 series running AIX, Versions 4.1, 4.2, and 4.3 Endpoint: V3R2, V3R7, V4R1, and V4R2 Managed Node, Endpoint: Versions 4.0a and 4.0d. Endpoint: Versions 4.11 and 4.20 on the ix86 platform Managed Node, Endpoint: HP9000/700 and 800 series running HP-UX, Versions 10.01, 10.10, and Managed Node, Endpoint: NCR 3000 series running NCR UNIX SVR4 MP-RAS and PC Agent, Endpoint: IBM-compatible PCs 486 or higher running Novell NetWare, Versions 3.11, 3.12, 4.01, 4.1, and 4.11 TME 10 Desktop for Windows, PC Agent, Endpoint: IBM-compatible PCs 486 or higher running IBM OS/2, Versions 2.0, 2.1,Warp 3.0, and Warp 4.0 with Win-OS/2 Endpoint: Pyramid MIServer-ES, Version 5.4MN Managed Node, Endpoint: Sequent DYNIX/ptx, Releases and viii Version 3.6

13 Preface Platform SCO SGI Solaris Solaris Intel SunOS Windows Windows NT Supported Versions Managed Node, Endpoint: SCO UnixWare 7, SCO UnixWare Versions and Managed Node, Endpoint: SGI IRIX, Versions 6.2 and 6.4 Managed Node, Endpoint: Sun SPARC series running Solaris, Versions 2.4, 2.5, 2.5.1, and 2.6 Managed Node, Endpoint: Solaris2-ix86, Versions and 2.6 Managed Node, Endpoint: Sun SPARC series running SunOS, Versions and TME 10 Desktop for Windows, PC Agent, Endpoint: IBM-compatible PCs 486 or higher running Microsoft Windows, Versions 3.1, 3.11, and Windows 95 TME 10 Desktop for Windows, PC Agent, Managed Node, Endpoint: IBM-compatible PCs 486 or higher running Microsoft Windows NT, Versions 3.51 SP5, 4.0, and 4.0 SP3. TME 10 Software Distribution AutoPack Icon The following icon represents a TME 10 Software Distribution AutoPack profile resource: The AutoPack profile resource is created in the context of a profile manager and is distributed to subscribing systems managed by TME 10. Subscribers can be profile managers, hosts, or NIS domains. TME 10 Software Distribution AutoPack User s Guide ix

14 Preface Contacting Customer Support If you encounter difficulties with any Tivoli products, you can enter to view the Tivoli Support home page. After you link to and submit the customer registration form, you will be able to access many customer support services on the Web. Use the following phone numbers to contact customer support in the United States: the Tivoli number is (1-800-TIVOLI8) and the IBM number is (press or say 8 after you reach this number). Both of these numbers direct your call to the Tivoli Customer Support Call Center. We are very interested in hearing from you about your experience with Tivoli products and documentation. We welcome your suggestions for improvements. If you have comments or suggestions about this documentation, please send to pubs@tivoli.com. x Version 3.6

15 I Using AutoPacks This aection contains conceptual and instructional information about TME 10 Software Distribution s AutoPack technology. The chapters describe AutoPack concepts and installation procedures, and detail procedures to build and distribute AutoPacks. Chapter 1 Overview and Installation The AutoPack Control Center The AutoPack Agent The AutoPack Profile AutoPack Control Center Installation Installing on Windows NT or Windows Installing on Windows AutoPack Agent Installation Chapter 2 AutoPack Control Center Creating the AutoPack File Editing an Existing AutoPack File Managing AutoPack File Distributions Locked-files Support Option Replace Newer Files Option Chapter 3 AutoPack Profile Operations Creating an AutoPack Profile Desktop Command Line Setting AutoPack Profile Properties Calculating the Size of an AutoPack TME 10 Software Distribution AutoPack User s Guide

16 Using AutoPacks Distributing an AutoPack Profile Drag and Drop Desktop Command Line Removing an AutoPack The autopack.log File Version 3.6

17 1 1Overview and Installation Overview and Installation An AutoPack is a TME 10 Software Distribution profile type that is similar to a file package but provides a simpler, more convenient way to create installable images for Windows, Windows 95, and Windows NT PCs managed by TME 10. An AutoPack enables you to distribute software to client machines without having to write collateral configuration programs or to perform additional installation tasks on the Windows PC. Using the AutoPack feature, you need not create and run configuration programs all scripts necessary to install and run the software are built-in. The AutoPack utility automatically determines the files that need to be distributed to the target machine and handles Windows installation issues such as registry changes, desktop icons, and programs listed on the Start menu. An AutoPack is built and distributed to target machines by Creating an AutoPack file with the AutoPack Control Center. The AutoPack Control Center is installed on a Windows-based PC and enables you to create an AutoPack file, which contains all the files necessary to install a shrinkwrapped application, such as Microsoft Word or Netscape Navigator. These files include scripts that are needed to perform system configuration changes to the client machine. Installing an AutoPack agent on each managed node and PC managed node that will receive AutoPacks. The AutoPack agent is automatically installed on an endpoint when the endpoint is created. In conjunction with other services on the target machine, TME 10 Software Distribution AutoPack User s Guide 1 1

18 The AutoPack Control Center the AutoPack agent is responsible for receiving and unpacking an AutoPack profile. Creating an AutoPack profile within a policy region in the Tivoli Management Region (TMR) policy region to distribute the AutoPack file. The AutoPack profile, which is distributed to clients in the TMR, provides a container for the AutoPack file s application and system configuration information. The AutoPack Control Center The AutoPack Control Center is a TME 10 Software Distribution tool installed on a Windows-based PC that enables you to create an AutoPack file. Based on file package block (fpblock) technology, the AutoPack file contains the files and system configuration changes that are installed on target PCs with an AutoPack profile. The AutoPack Control Center is installed on a preparation (prep) machine, which can be any Windows, Windows 95, or Windows NT machine. Tivoli strongly recommends that this prep machine be pristine, having few or no other applications installed. Since the AutoPack Control Center relies on differencing technology that detects files and system configurations, using a pristine system will avoid file contention. If other applications are installed on the prep machine before creating the AutoPack file, the AutoPack Control Center may include unwanted data and system files in, or exclude vital system files from, the AutoPack file. Also, Tivoli strongly recommends that you create an AutoPack file on the same operating system as the target machine. This avoids file contention that may result between different versions of Windows. For example, if you are installing Netscape Navigator on Windows 95 and Windows NT systems, you should create an AutoPack file on each platform. The AutoPack file is created using the AutoPack Control Center by Creating the pre-installation (baseline) snapshot of the prep machine s drive and system configurations Installing the target application on the prep machine 1 2 Version 3.6

19 The AutoPack Agent Creating the post-installation snapshot of the prep machine, and building the AutoPack file. The AutoPack file encapsulates the differences between the two snapshots and includes distribution instructions that will eventually be executed on client machines. The AutoPack Agent The AutoPack agent works with the lcfd on endpoints or the PC agent on PC managed nodes to unpack and install AutoPack distributions on the client machine. When an AutoPack profile arrives on the client, the client service and AutoPack agent generally work as follows: The PC agent or the lcfd parses the AutoPack file that was created by the AutoPack Control Center, installs the program files into the directories specified, and loads system files into a temporary staging area. The AutoPack agent then transfers the system files from the staging area, installs the system files into the exact locations specified by the AutoPack file, and applies system changes specified in the.chg file, such as updating.ini files or registry items. If you were to perform this installation using Software Distribution s file package technology, you would have to write configuration programs to configure system files for a target the AutoPack agent seamlessly configures the system for you. Overview and Installation The AutoPack Profile An AutoPack profile is a TME 10 Software Distribution profile that references an AutoPack file. The AutoPack profile serves as a vehicle to distribute the AutoPack file s application and system configurations required to install the application on the target machine. An AutoPack profile is created in the context of a profile manager from the TME 10 desktop and can be distributed to any Windows managed node, endpoint, and PC managed node in a TMR. You must create an AutoPack profile for each AutoPack file that you will distribute. TME 10 Software Distribution AutoPack User s Guide 1 3

20 AutoPack Control Center Installation AutoPack Control Center Installation The AutoPack Control Center is used to create an AutoPack file, which contains the information that the AutoPack profile distributes. You can install the AutoPack Control Center on a pristine, Windows platform-specific machine that will serve as the AutoPack Control Center preparation (prep) machine. For instance, if you plan on sending AutoPacks to a Windows NT system, the AutoPack Control Center on which you will build the AutoPack file for eventual distribution must also be a Windows NT machine. Although not recommended, you can install the prep machine on an NT managed node, endpoint, or PC managed node in your TME 10 environment; note, however, that installing the AutoPack Control Center on a TME 10 client machine may cause AutoPack file.dlls to conflict with.dll files that are installed by Tivoli. Tivoli also recommends that the prep machine have minimal software installed. Note: The prep machine does not require a PC agent or lcfd. Refer to the online help provided with the AutoPack Control Center for instructions, important information, and recommendations about using this product. Note: If you are using the TME 10 Software Installation Service (SIS) to install the AutoPack Control Center on a machine in your TMR, refer to the TME 10 Software Installation Service User s Guide for procedures on how to install and manage products or patches in your TMR through this interface. Installing on Windows NT or Windows 95 Use the following procedure to install the AutoPack Control Center on either Windows NT or Windows 95 systems. 1. From the File Manager or Program Manager window, select Run... from the File menu to display the Run dialog. 1 4 Version 3.6

21 AutoPack Control Center Installation 1. Enter the path to the SETUP.EXE file, which resides in the X:\PC\ACC directory on the CD-ROM, in the Open text field, as follows: Overview and Installation where X is the CD-ROM drive where the TME 10 Software Distribution CD-ROM image is inserted. If you do not have a CD-ROM drive on your PC, see the PC agent chapter in the TME 10 Framework Planning and Installation Guide for instructions on copying the installation media to diskettes. 1. Press the OK button to run the setup program and display the Welcome dialog for the AutoPack Control Center. The setup program leads you through the AutoPack Control Center installation. Use the Back, Next, or Cancel buttons to navigate through these option dialogs. TME 10 Software Distribution AutoPack User s Guide 1 5

22 AutoPack Control Center Installation 1. To start the AutoPack Control Center, double-click on the AutoPack icon or select the AutoPack Control Center option in the AutoPack group on the Start -> Programs menu. Installing on Windows 3.1 Use the following procedure to install the AutoPack Control Center on Windows 3.1 machines. To install and run the AutoPack Control Center on a Windows 3.1 machine, you must first install win32s, Vversion or later. Step 2 applies for Windows 3.1 with EIDE only 1. Ensure that SHARE.EXE is included in the AUTOEXEC.BAT file and is running. 1. Ensure that the Use 32-Bit File Access option is disabled. To do so, complete the following steps: a. Open the Control Panel. a. Open the 386 Enhanced group and press the Virtual Memory... button. The Virtual Memory dialog is displayed. 1 6 Version 3.6

23 AutoPack Control Center Installation a. Press the Change>> button to expand the Virtual Memory dialog. Overview and Installation a. Ensure that the Use 32-Bit File Access check box is not selected. a. Press the OK button to close the Virtual Memory dialog. a. Reboot your Windows machine 1. From the File Manager or Program Manager window, select Run... from the File menu to display the Run dialog. 1. Enter the path to the SETUP.EXE file, which resides in the X:\PC\ACC directory on the CD-ROM, in the Command Line text field as follows: where X is the CD-ROM drive where the TME 10 Software Distribution CD-ROM image is inserted. TME 10 Software Distribution AutoPack User s Guide 1 7

24 AutoPack Agent Installation If you do not have a CD-ROM drive on your PC, see the PC agent chapter in the TME 10 Framework Planning and Installation Guide for instructions on copying the installation media to diskettes. 1. Press the OK button to run the setup program and display the Welcome dialog for the AutoPack Control Center. This program leads you through the AutoPack Control Center installation. Use the Back, Next, or Cancel buttons to navigate through these option dialogs. 1. To start AutoPack Control Center on Windows 3.1 machines, double-click on the AutoPack icon. AutoPack Agent Installation For managed nodes and PC managed nodes only In order to distribute an AutoPack profile, you must first install the AutoPack agent on all managed nodes and PC managed nodes that will receive AutoPack distributions endpoints are automatically configured with the AutoPack agent during installation. In conjunction with the lcfd on endpoints or the PC agent on PC managed nodes, the AutoPack agent is responsible for receiving and unpacking an AutoPack profile. Note that installing the AutoPack agent on a client machine does not actually involve AutoPack functionality. Rather, 1 8 Version 3.6

25 AutoPack Agent Installation installation of the AutoPack agent involves Software Distribution s file package block (fpblock) capability to push the Autopack agent down to the client. Once you have installed the AutoPack agent on a subscriber, you will only need to reinstall it if a new release of the AutoPack Control Center is installed on the preparation machine. Reinstalling the AutoPack agent at this time enables it to interpret new.chg files. See Appendix A, Frequently Asked Questions for more information about the AutoPack agent. Note: Before installing the AutoPack agent on a PC, you must install the PC agent and create a PC managed node for it. See the TME 10 Framework Planning and Installation Guide for instructions on both of these procedures. The following table shows the context and authorization role required to perform this task. Overview and Installation Operation Context Required Role Create, edit, and distribute an AutoPack Profile manager senior or super Use the following steps to install the AutoPack agent on Windows, Windows 95, and Windows NT machines in your environment. Note that the steps include procedures to create, edit, and distribute an AutoPack profile which contains the AutoPack agent. Note: Ensure that you are installing a current version of the AutoPack agent. An older version of the AutoPack agent cannot parse an AutoPack file that is generated by the new AutoPack Control Center. 1. From the TME 10 desktop, double-click on a policy region icon to display the Policy Region window. 1. Add the AutoPack and Profile Manager resources to the policy region s list of managed resources. For instructions on adding resource types to a policy region, see the TME 10 Framework User s Guide. TME 10 Software Distribution AutoPack User s Guide 1 9

26 AutoPack Agent Installation 1. Create a profile manager in which the AutoPack will reside. See the TME 10 Framework User s Guide for instructions on creating profile managers. 1. Double-click on a profile manager icon to display the Profile Manager window. 1. Select Profile... from the Create menu in the Profile Manager window to display the Create Profile dialog. 1. Enter a unique name for the profile in the Name/Icon Label field that describes the AutoPack and select AutoPack from the Type scrolling list. 1. Press the Create & Close button to create the new profile and return to the Profile Manager window. An icon representing the newly-created AutoPack is displayed in the Profile Manager window Version 3.6

27 AutoPack Agent Installation 1. Double-click on the AutoPack icon to display the Set AutoPack Properties dialog. Overview and Installation 1. In the Managed Node field, type the name of the managed node where the TME 10 Software Distribution installation CD-ROM is mounted. 1. Type the following full path in the Path field: cdrom_path/ap_agent.pak where cdrom_path is the path to the mounted CD-ROM drive. The ap_agent.pak file is an AutoPack file that contains the AutoPack agent files and scripts needed to install it on the target. 1. Press the Save & Close button to save the AutoPack and return to the Profile Manager window. 1. Set all target machines that will receive the AutoPack agent as subscribers in this profile manager. You must set these subscribers (profile managers, endpoints, managed nodes, PC managed nodes, and NetWare managed sites) before you can distribute the AutoPack profile. a. Select Subscribers... from the Profile Manager menu to display the Subscribers dialog. TME 10 Software Distribution AutoPack User s Guide 1 11

28 AutoPack Agent Installation a. Select a subscriber from the Available to become Subscribers scrolling list and press the left arrow button to move the subscriber to the Current Subscribers scrolling list. a. After selecting all subscribers that will receive the AutoPack agent, press the Set Subscriptions & Close button to set the new subscriptions and return to the Profile Manager window. The modified subscriptions are added to the profile manager s list of subscribers. 1. Select Distribute... from the AutoPack icon pop-up menu to display the Distribute AutoPack dialog. 1. Ensure that the Distribute AutoPack To scrolling list accurately displays the subscribers on which you want the AutoPack agent installed Version 3.6

29 AutoPack Agent Installation Perform the following actions using the scrolling lists: To move a subscriber to the Distribute AutoPack To scrolling list, choose one or more subscribers from the Available Subscribers scrolling list and press the left arrow button. By default, all subscribers in the profile manager are displayed in the Available Subscribers scrolling list. To remove a subscriber, choose one or more subscribers from the Distribute AutoPack To scrolling list and press the Remove button. 1. Press the Distribute & Close button to begin distributing the AutoPack to the selected subscribers and dismiss the dialog. Note: The dialog is not dismissed until the distribution is complete. If the distribution fails for any of the subscribers, a pop-up dialog is displayed to inform you which subscribers failed the distribution. Overview and Installation After installing the AutoPack Control Center on a prep machine and installing the AutoPack agent on all client systems that will receive AutoPack profile distributions, you are ready to create and distribute AutoPack files. The following chapters detail how to create an AutoPack file with the AutoPack Control Center and how to distribute it to client systems with an AutoPack profile. TME 10 Software Distribution AutoPack User s Guide 1 13

30 AutoPack Agent Installation 1 14 Version 3.6

31 2 2AutoPack Control Center The AutoPack Control Center enables you to conveniently create installable images of software applications that can be distributed to client machines using an AutoPack profile. This chapter details how to create an AutoPack file using the AutoPack Control Center. It also describes how to set the new keyword options to better manage AutoPack distributions to target machines. All keywords are described in Appendix B, Behind the Scenes and in the TME 10 Software Distribution Reference Manual. You build an AutoPack file with the AutoPack Control Center on the preparation (prep) machine by Scanning a drive on the prep machine where software will be installed in order to create a pre-installation snapshot of drive and system configurations. It is important that the prep machine is pristine and of the same operating system type as the target PC. Installing software on the prep machine the file and system changes that result from this software installation are bundled and eventually distributed to target machines. Taking a post-installation scan of the prep machine drive and identifying the installed files. Setting the AutoPack file s distribution properties, including information about target machines. Building an AutoPack file based on the difference between the pre- and post-installation scans and on user-defined properties. AutoPack Control Center TME 10 Software Distribution AutoPack User s Guide 2 1

32 Creating the AutoPack File After creating the AutoPack file, you can distribute it using an AutoPack profile in a Tivoli Management Region (TMR) policy region. Instructions to create, set properties for, and distribute an AutoPack profile are explained in Chapter 3, AutoPack Profile Operations. Creating the AutoPack File An AutoPack file cannot perform OS upgrades or installations. An AutoPack file contains all the files necessary to install a software application, including any necessary system-configuration changes. The AutoPack file is similar to a file package block. You must create an AutoPack file from the AutoPack Control Center desktop. Use the following steps to create an AutoPack file: 1. Run the AutoPack Control Center on the prep machine. By default, this program (the autopack.exe file) is installed in the \tivoli\autopack\win_type directory, where win_type corresponds to the type of PC. Also, the AutoPack group is created, in which an icon for the AutoPack Control Center resides. Note: If you are running the AutoPack Control Center on an NT machine, you must be logged in as Administrator this ensures that all system files are scanned properly. 2 2 Version 3.6

33 Creating the AutoPack File The AutoPack Control Center cannot scan a network drive. 1. Create a pre-install snapshot by pressing the Create Baseline Snapshot button on the AutoPack window. The baseline snapshot is a preliminary snapshot of the prep machine s drive and system configuration. Before running the scan to create the snapshot, you will specify the drive to scan, the working directory, the files to monitor, and the files to exclude. a. In the Drive field on the General Options property sheet, specify the drive where you will install the software on the prep machine. AutoPack Control Center When the AutoPack Control Center compares the pre- and post-install snapshots, it compares the files found on this drive to create the contents of the AutoPack file. Note: Ensure that you specify file and directory paths using backslashes (\). The AutoPack Control Center will not convert forward slashes (/) to backslashes (\). a. In the Directory field, specify the working directory where the AutoPack Control Center will store the files used to create the AutoPack file. These files will require a little more disk space than recommended by the installed application. This space consideration depends on the actual software you are installing. a. On the Files to Monitor property sheet, enter additional.ini files to monitor. TME 10 Software Distribution AutoPack User s Guide 2 3

34 Creating the AutoPack File The AutoPack Control Center monitors listed.ini files, even if they reside on different drives, by detecting differences in pre- and post-installation.ini files. This differencing allows files to be updated, rather than replaced, with new differencing information. By default, the AutoPack Control Center monitors the files listed in the dialog shown below. Tivoli strongly recommends that you do not change or edit files listed here. You can, however, add additional files to be monitored. For example, you can include My.INI to this list, which prompts the AutoPack Control Center to gather information about sections or items that have been modified inside My.INI. These modifications are then automatically replicated in the target My.INI file. a. On the Files to Exclude property sheet, include any files you want to exclude from the snapshots. Add files and directories to this property sheet if you are not interested in replicating any changes to these files or directories on the target system. For example, you can exclude log files that are created by the application installation but are not an integral 2 4 Version 3.6

35 Creating the AutoPack File part of the application. If Tivoli code is installed on the preparation machine, you should exclude the Tivoli directory, which contains the TMEAGENT.CFG file, by completing the following steps: a. Press the Browse Directories button to display the Directories dialog. a. Select the C:\Tivoli directory and press the OK button to return to the Create Baseline Snapshot dialog. This adds the C:\Tivoli directory to the list of files to be excluded from the scans. All other directories listed are excluded by default. AutoPack Control Center a. Press the Run button to create the baseline snapshot and save the baseline snapshot to the directory specified in the Directory field on the General property sheet. TME 10 Software Distribution AutoPack User s Guide 2 5

36 Creating the AutoPack File While the AutoPack Control Center creates the baseline snapshot, the Scan Status dialog is displayed. 1. Install the software package. You can run the installation executable from the Install Software dialog, which is displayed when you press the Install Software button on the AutoPack window. You can also install the software as you would normally, from the File menu of the Program Manager or from the File Manager. Regardless of how you run the executable, be sure to close all applications, including the AutoPack Control Center, if the installation requires that you do so. 2 6 Version 3.6

37 Creating the AutoPack File 1. Create a second snapshot and build the AutoPack file by pressing the Build AutoPack button. The Build AutoPack dialog is displayed. Enter the name of, and full path to, the AutoPack file in the Name field. The.PAK extension is appended to the name automatically when the AutoPack file is built, regardless of any extension that you may add the AutoPack Control Center identifies files with the.pak extension as AutoPack files. Note: Ensure that the AutoPack file name conforms to file naming conventions required by Windows 3.1 systems if you will be distributing the AutoPack file to a Windows 3.1 machine. AutoPack Control Center TME 10 Software Distribution AutoPack User s Guide 2 7

38 Creating the AutoPack File When you press the Run button, the AutoPack Control Center creates the second snapshot and compares it to the baseline. It creates the.def,.chg,.err and.rep files. These files are described in detail in Appendix B, Behind the Scenes. While the AutoPack Control Center creates the baseline snapshot, a dialog similar to the following is displayed. 1. The AutoPack Control Center displays the AutoPack Properties window after the AutoPack file is built. From this window, you can set the AutoPack s distribution properties, including information about the destination machine. This dialog has four 2 8 Version 3.6

39 Creating the AutoPack File property sheets: General, File Mode, Log Info, and Distribution. a. In the Destination Drive on the General property sheet, specify the drive on the target machine onto which files contained in the AutoPack file will be installed. The program files will be installed on the specified drive. All system files in the AutoPack file, however, will be installed on the system directory. Note that an AutoPack profile can only be distributed to one destination drive at a time. If you wish to distribute an AutoPack profile to multiple drives, create a separate AutoPack file and profile for each target drive. a. In the Staging Directory field, specify the working directory on the target machine that TME 10 Software Distribution will use when distributing the AutoPack profile. In general, the staging directory on the target machine should have enough space to hold the required system files, not the entire software package. Note: Ensure that you specify file and directory paths using backslashes (\). The AutoPack Control Center will not convert forward slashes (/) to backslashes. AutoPack Control Center TME 10 Software Distribution AutoPack User s Guide 2 9

40 Creating the AutoPack File 1. Set the options on the File Mode property sheet. This dialog enables you to set the defaults for the AutoPack Properties window, which lets you set options for distributing the AutoPack file on the target. Select the Preserve mode of source files radio button to set the permissions of the files distributed by the AutoPack profile to those of the source files contained in the AutoPack file. Select the Change mode of destination files to radio button to change the permissions of the files distributed by the AutoPack profile to those specified in the Read and Write check boxes Version 3.6

41 1. Set options on the Log Info property sheet. Creating the AutoPack File Check the Send to Distribution notice group check box to have TME 10 Software Distribution send a notice to its notice group when the AutoPack profile is distributed. The notice includes an indication of success or failure for each target. Check the Send to check box to have TME 10 Software Distribution send to the specified address when the AutoPack profile is distributed. You can specify multiple addresses by separating each domain name with a comma. The includes an indication of success or failure for each target. Check the Send to log file on check box to have TME 10 Software Distribution post a notice to the AutoPack log file, specified in the Host and Path fields. The log file includes an indication of success or failure for each target. It also includes information about problems encountered during the distribution and targets that were down. This log file is the best source of information about an AutoPack profile distribution and Tivoli recommends that you select this check box and fill in the Host and Path fields. If you choose to post a notice to the AutoPack log file in this manner, check the Append log file check box to append the log file to an existing log file rather than overwriting it. AutoPack Control Center TME 10 Software Distribution AutoPack User s Guide 2 11

42 Creating the AutoPack File 1. Set options on the Distribution property sheet. This property sheet enables you to set the defaults for the AutoPack Properties window, which lets you set options for distributing the AutoPack file. Not supported on Windows NT Check the Stop distribution on error check box to immediately stop the AutoPack profile distribution if an error occurs on a target. Note that the distribution to only that target will stop if an error occurs, but will continue normally for all other targets. If you do not select this box, errors are logged as specified on the Log Info property sheet and the distribution continues, if possible. Check the Perform compression on distribution check box to compress the data in the AutoPack profile before distributing it. The AutoPack file is compressed on the PC before it is copied to the managed node and then distributed. The data in the AutoPack profile is uncompressed once it reaches the target. Select the Mandatory radio button to have TME 10 Software Distribution distribute the AutoPack profile without giving the targets users the option to cancel the distribution. Select the Optional radio button to have TME 10 Software Distribution distribute the AutoPack profile, giving the targets users the option to cancel the distribution. An optional distribution displays a pop-up dialog on the target at distribution 2 12 Version 3.6

43 Creating the AutoPack File time. The user can then choose to accept the distribution or not. If the user does not choose in the amount of time specified in the seconds field, the AutoPack profile is distributed. Specify a time (in seconds) that is between 1 and 6000 seconds, inclusive. The default value is 120 seconds. Check the Timeout check box to specify a timeout value (in seconds) to terminate a distribution if scripts running on the client system do not complete in the allotted time. The default is no timeout. The timeout value applies to all configuration programs that run on the client system, including the AutoPack agent and any customized scripts that you include in the.def file. Tivoli recommends that you set the timeout value to at least 30 minutes for an average size installation or longer if you are installing a very large software product, such as Lotus SmartSuite After setting all of the options, press the Build button. The AutoPack Control Center creates the AutoPack file by bundling all files, options, and system configuration changes necessary to install the application on the target machines. 1. Prior to pressing the Build button, you can press the Contents button to list all files that will be distributed with the AutoPack profile and the system changes that will be performed. AutoPack Control Center TME 10 Software Distribution AutoPack User s Guide 2 13

44 Editing an Existing AutoPack File This list, which is displayed in the Contents dialog, is the result of the pre- and post-install snapshot differences. Tivoli recommends that you select the Contents button to track files that will be installed as well as system changes that will be made on target machines. Editing an Existing AutoPack File Using the Edit AutoPack feature on the AutoPack Control Center, you can edit an existing AutoPack file. This feature enables you to modify the contents of the.def file, which lists all properties of the AutoPack file. The files listed in the definition file are those that are listed on the AutoPack Contents dialog. When you edit an existing AutoPack file, you must ensure that all software files exist in the same location as when the AutoPack was originally created. For example, if you previously created an AutoPack file for Microsoft Office 97 whose files were located in C:\temp, you must ensure that all files for Office 97 still exist in the C:\temp directory Version 3.6

45 Editing an Existing AutoPack File The following steps describe how to edit an AutoPack file: 1. Press the Edit AutoPack button on the AutoPack Control Center window. The Open dialog is displayed. All available.def files are listed in the File name scrolling list. 1. Select the.def file you wish to edit and press the OK button. The AutoPack Properties window is displayed for the.def file that you are editing. This window is the same as the one that is displayed when you initially create an AutoPack file, as illustrated in Step 1 on page 2-8. AutoPack Control Center TME 10 Software Distribution AutoPack User s Guide 2 15

46 Managing AutoPack File Distributions In the Staging Directory field, enter the name of the working directory on the target machine to which the AutoPack profile is distributed. You can specify the same staging directory as the one you specified when creating the AutoPack file. 1. Once you have entered the path to the staging directory, you can reset the AutoPack s distribution properties, including information about the destination machine, the file mode, and any logging information. Follow steps 6 to 11 in the Creating the AutoPack File section for instructions about resetting these properties and rebuilding the AutoPack file. Managing AutoPack File Distributions In building the AutoPack file, the AutoPack Control Center sets several keywords in the.chg file, which specify all system changes that must take place on a target machine. The following two new keywords provide flexibility in handling how locked files and newer versions of files that are present on the target will be managed during an AutoPack file distribution. All keywords are described in Appendix B, Behind the Scenes as well as in the TME 10 Software Distribution Reference Manual. Locked-files Support Option Supported on Windows 95 and Windows NT only AutoPack provides locked-files support, which enables the AutoPack agent to install system files on a client machine even if these files are locked by a running application at distribution time. The AutoPack agent keeps track of locked file entries and prompts the PC agent to reboot the workstation after the installation is complete. As the AutoPack agent moves files from the staging directory to the Windows system directory (and its subdirectories), the following steps are taken if a file in the destination directory is locked by a running application: A warning message is logged in the AutoPack log file indicating that the file will be moved at the next reboot. A return code is added to the error.tiv file if at least one file is to be moved at the next reboot Version 3.6

47 Managing AutoPack File Distributions The PC agent interprets the return code and initiates a reboot. By default, the reboot is not automatic the AutoPack agent only prompts for a system reboot if it encounters the reboot_if_necessary keyword in the.chg file argument list. You must set the client machine to automatically reboot when locked files are detected by editing this keyword in the.chg file: reboot_if_necessary=n Does not perform a reboot even if there are locked files to replace. Files are replaced when the user manually reboots the client machine. This is the default setting. reboot_if_necessary=y Performs a reboot if there are locked files to be replaced. To set the reboot_if_necessary keyword, you must first build an AutoPack file in order to generate the.chg file. Close the AutoPack Control Center graphical user interface and edit the.chg file to set the keyword. And then rebuild the AutoPack file from the GUI to implement these changes. The reboot_if_necessary keyword functions only with the or higher version of the PC agent. If you are using release (or earlier) of the PC agent, you must manually reboot the machine if the following message appears in the AutoPack log file: AutoPack Control Center Execution completed successfully - Reboot is required Additionally,.CHG files generated by previous versions of the AutoPack Control Center do not contain the reboot_if_necessary keyword. For these files, the AutoPack agent behaves as if the keyword exists and is set to n. Replace Newer Files Option The option to replace newer versions of files enables you to control whether a file will be installed on the client if a newer version of this file already resides on the client machine. By setting the replace_newer_files keyword in the argument list of the.chg file, you can prompt the AutoPack agent to replace existing newer versions of files with distributed files in an AutoPack installation as follows: TME 10 Software Distribution AutoPack User s Guide 2 17

48 Managing AutoPack File Distributions replace_newer_files=n Prompts the AutoPack agent to not replace newer files that currently exist on the client during an AutoPack installation. This is the default setting. replace_newer_files=y Newer files that currently exist on the client are replaced during a AutoPack installation. To set the replace_newer_files keyword, you must first build an AutoPack file in order to create the.chg file. Close the AutoPack Control Center GUI and edit the.chg file to set the keyword. And then rebuild the AutoPack file from the GUI to implement these changes Version 3.6

49 3 3AutoPack Profile Operations An AutoPack profile is used to distribute the AutoPack file that you have created using the AutoPack Control Center. After creating and editing the properties of this profile, you can distribute the AutoPack to its subscribers endpoints, NT managed nodes, PC managed nodes, NetWare managed site clients, and other profile managers. When you distribute an AutoPack profile, the application and system files contained in the file are distributed to the target machines. This chapter discusses the following topics: Creating an AutoPack profile in the context of a profile manager in the TME 10 desktop Setting AutoPack profile properties, such as AutoPack profile name and AutoPack file path Calculating the size of an AutoPack profile to determine the total size of its included application files Distributing an AutoPack profile to subscribers Removing an AutoPack profile, which removes all distributed files and directories on those machines, and reverses any system changes performed by the AutoPack Using the autopack.log file to track the status of AutoPack distributions and removals AutoPack Profile Operations TME 10 Software Distribution AutoPack User s Guide 3 1

50 Creating an AutoPack Profile Creating an AutoPack Profile After creating an AutoPack file on the AutoPack Control Center, you can distribute it to client machines with an AutoPack profile. You must create this profile within a profile manager in a Tivoli Management Region (TMR) policy region. The following table shows the context and authorization role required to perform this task. Operation Context Required Role Create an AutoPack profile Profile manager senior or super Desktop You can perform this task from the TME 10 desktop or from the command line. Use the following steps to create an AutoPack profile from the desktop: 1. Add the AutoPack and ProfileManager resources to the policy region s list of managed resources. Create a profile manager in which the profile will reside. Note that for the purposes of this procedure, the Dataless Endpoint Mode radio button is enabled when creating the profile manager. The dataless mode enables a profile manager to distribute to any TME 10 client managed nodes, endpoints, PC managed nodes, and Netware managed sites but not to other profile manager. For instructions on adding resource types to a policy manager and creating a profile manager in either the database mode or the dataless mode, see the TME 10 Framework User s Guide. 3 2 Version 3.6

51 Creating an AutoPack Profile 1. From a policy region, double-click on a profile manager icon to display the Profile Manager window. AutoPack Profile Operations TME 10 Software Distribution AutoPack User s Guide 3 3

52 Creating an AutoPack Profile 1. Select Profile... from the Create menu in the Profile Manager window to display the Create Profile dialog. 1. Enter a unique name for the profile in the Name/Icon Label field that describes the AutoPack. Tivoli recommends that you avoid using characters other than alphanumeric characters, a dash (-), an underscore (_), and the caret symbol (^). Also, the profile name must not exceed 32 characters. If you intend to create AutoPacks for different versions of a software package, Tivoli recommends that you include the name and version of the AutoPack, separated by a caret (^), in the profile name. For example, you could create profiles with the following names to represent different versions of the Startup AutoPack: Startup^C Startup^D Using this format enables UserLink for TME 10 Software Distribution to distinguish between multiple versions of the same AutoPack. 1. Select AutoPack from the Type scrolling list. 3 4 Version 3.6

53 Creating an AutoPack Profile Note: If AutoPack is not available, you must add it as a managed resource of your policy region. For more information on this procedure, see the TME 10 Framework User s Guide. 1. Press the Create & Close button to create the new profile and return to the Profile Manager window. An icon representing the newly-created AutoPack (Office97) is displayed in the Profile Manager window. AutoPack Profile Operations TME 10 Software Distribution AutoPack User s Guide 3 5

54 Setting AutoPack Profile Properties Command Line Because profiles must reside in a profile manager, you must create a policy region and profile manager in which to create the AutoPack. To create policy regions and profile managers, see the TME 10 Framework Reference Manual for information on the wcrtpr and wcrtprfmgr commands. To create the Office97 AutoPack profile in the Source profile manager, enter the following command: AutoPack Office97 Creates the AutoPack in the Source profile manager. AutoPack Creates an AutoPack profile. Office97 Specifies Office97 as the name of the AutoPack. Note: AutoPack profile properties must be set from the TME 10 desktop as described in Setting AutoPack Profile Properties even if you create the profile from the command line. For information about the wcrtprf command, see the TME 10 Framework Reference Manual. Setting AutoPack Profile Properties Before an AutoPack profile is used to distribute an AutoPack file to your targets, you must set the AutoPack profile s properties. These properties include the name that you assign to the AutoPack profile and, more importantly, the path of the AutoPack file that you are referencing. 3 6 Version 3.6

55 Setting AutoPack Profile Properties As with file packages, the source host for distributing AutoPacks must be located on any managed node in your TME 10 environment. This is necessary because Software Distribution cannot initiate a profile distribution from a PC managed node or an endpoint. Therefore, to set AutoPack profile properties, complete the following steps: Manually copy the AutoPack file to a managed node if the prep machine on which it was created is not part of the TME 10 environment. Specify the AutoPack file s host and path in the managed node in the Set AutoPack Properties window if the AutoPack file was created on or copied to a managed node. Copy the AutoPack file from an endpoint, managed node, or PC managed node location in the TME 10 environment. Note: You cannot access an AutoPack file from a PC that is not managed by your TMR, such as from a NetWare managed site s client or from a prep machine that is not a managed node, endpoint, or PC managed node. In these cases, you must manually copy the AutoPack file from the client to a managed node and then complete the steps defined below. The table below shows the context and authorization role required for this task: Operation Context Required Role Set or edit AutoPack properties AutoPack senior or super You can perform this operation only from the TME 10 desktop. AutoPack Profile Operations Use the steps on the following pages to set or edit the properties of an AutoPack. TME 10 Software Distribution AutoPack User s Guide 3 7

56 Setting AutoPack Profile Properties 1. From the profile manager, double-click on an AutoPack icon to display the Set AutoPack Properties window. 1. In the Managed Node text field, type the name of the managed node where the AutoPack file resides. Type the full path to the file in the Path field. You can specify an AutoPack file that exists on a managed node, or you can specify a file to which the AutoPack file will be copied from an NT managed node, endpoint, or PC managed node. OR 3 8 Version 3.6

57 Setting AutoPack Profile Properties Press the ellipsis button (...) button to display the Set AutoPack File Location dialog. This dialog provides a view of the available managed nodes and their directory structures. Use this browser dialog to select a managed node and AutoPack file. To select a file from the Set AutoPack File Location dialog, follow these steps: a. Select one of the listed managed nodes in the Hosts scrolling list. a. Double-click on the directory name in the Directories scrolling list to list the files and directories contained in that directory. Repeat this step until you find the desired file. a. Select a file from the Files scrolling list. a. Press the Set File & Close button to add the file to the Source File field, and close this dialog. AutoPack Profile Operations TME 10 Software Distribution AutoPack User s Guide 3 9

58 Setting AutoPack Profile Properties 1. If you are copying an AutoPack file from a PC that is part of your TMR, you must specify the TME 10 machine from which the file will be copied as follows: a. Select the Copy file from PC managed node radio button to sensitize the Copy From section of the window. Type the name of PC managed node where the AutoPack file resides in the PC Managed Node field. OR Press the ellipsis button (...) to open the Select AutoPack File browser dialog, which enables you to navigate through the directory tree to select a file. a. Select the Copy file from managed node radio button to sensitize the Copy From section of the window. Type the name of managed node where the AutoPack file resides in the Managed Node field. OR Press the ellipsis button (...) to open the Select AutoPack File browser dialog, which enables you to navigate through the directory tree to select a file Version 3.6

59 Setting AutoPack Profile Properties a. Select the Copy file from Endpoint radio button to sensitize the Copy From section of the window. Type the name of the endpoint where the AutoPack file resides in the Endpoint Name field. OR Press the ellipsis button (...) button in the AutoPack File section to display the Select AutoPack File dialog. This dialog provides a view of the available NT managed nodes or PC managed nodes and their directory structures. Use this dialog to select an AutoPack file to copy to the managed node selected in the AutoPack File section of the dialog. To select a file from the Select AutoPack File dialog, complete the following steps: a. Select one of the listed NT managed nodes or PC managed nodes in the Hosts scrolling list. a. Double-click on the directory name in the Directories scrolling list to list the files and directories contained in that directory. Repeat this step until you find the desired file. AutoPack Profile Operations TME 10 Software Distribution AutoPack User s Guide 3 11

60 Setting AutoPack Profile Properties Note: If you need to access directories on another drive, enter N:\ in the Path Name field, where N is the desired drive letter, and press the Return key. a. Select a file from the Files scrolling list. a. Press the Set File & Close button to add the file to the Source File field, and close this dialog. The selected machine and file are displayed in their respective fields. 1. Select the Save & Close button to save the AutoPack and return to the profile manager window. If you specified a file in the Copy From section of the window, it is copied to the specified AutoPack file location when you save the AutoPack profile s properties. If a file exists in the specified AutoPack file location, it is overwritten with the file copied from the NT managed node, endpoint, or PC managed node Version 3.6

61 Calculating the Size of an AutoPack Calculating the Size of an AutoPack Calculate the size of an AutoPack to determine the total size (in bytes) of its included application files. Note that the calculated size may be larger than the sum of the AutoPack components due to TME 10 Software Distribution data overhead. It also may not reflect the disk space needed on the targets to install the application. The calculated size is primarily used to gauge network load and distribution time. The table below shows the context and authorization role required for this task: Operation Context Required Role Calculate the size of an AutoPack Profile manager s policy region admin, senior, or super You can perform this task from the TME 10 desktop only. To calculate the size of an AutoPack from the desktop, complete the following steps: 1. Select Calculate size... from the AutoPack icon popup menu. Software Distribution displays the Calculate AutoPack Size dialog: AutoPack Profile Operations 1. Press the Calculate Size button to calculate and display the AutoPack size (in bytes). TME 10 Software Distribution AutoPack User s Guide 3 13

62 Distributing an AutoPack Profile 1. Select the Close button to close this dialog. OR Press the Calculate Size & Close button to determine and display the AutoPack size and close the dialog. Distributing an AutoPack Profile After you create an AutoPack profile and edit its properties, you can distribute it to the subscribers. Distributing an AutoPack installs the software and makes the necessary system configuration changes on the target machine. Consider the following distribution requirements: If the target is an NT managed node, Software Distribution must be installed either on the target TMR server or on an interconnected TMR server, and the AutoPack agent must be installed on the target. If the target is an endpoint, Software Distribution must be installed either on the target TMR server or on an interconnected TMR server, and the Software Distribution Gateway must be installed on the endpoint gateway. The AutoPack agent is automatically installed on the endpoint when the endpoint is installed. If the target is a PC managed node, Software Distribution must be installed either on the target TMR server or on an interconnected TMR server. Both the PC agent and AutoPack agent must be installed on the target. If the target is a NetWare managed site, Software Distribution must be installed either on the target TMR server or on an interconnected TMR server. Both the Tivoli NetWare repeater (TNWR) and PC agent must be installed on the NetWare server. And both the PC agent and AutoPack agent must be installed on the NetWare managed site s clients. See Chapter 1, Overview and Installation, for instructions about installing the AutoPack Control Center and the AutoPack agent. See the TME 10 Framework Planning and Installation Guide for information about installing the Tivoli Netware Repeater (TNWR) and PC agent. Refer to Chapter 2, AutoPack Control Center, for 3 14 Version 3.6

63 Distributing an AutoPack Profile information about problems you may encounter as the result of how you created the AutoPack file. Note: Older versions of the AutoPack agent cannot parse an AutoPack file that is generated by the new AutoPack Control Center. If the following error appears in the PC agent error log after distribution, install a new version of the AutoPack agent on the client system and redistribute the AutoPack profile: 12/15/97 10:43:09 [E] Expecting target_dir = at \ line 3, but found target_dir=c: The table below shows the context and authorization role required for this task: Operation Context Required Role Distribute an AutoPack TME 10 Software Distribution profile admin, senior, or super You can perform this task from the TME 10 desktop, from the command line, or by using drag and drop,. Drag and Drop To distribute an AutoPack using drag and drop, drag the AutoPack icon and drop it onto a subscriber icon: a subscriber can be an NT managed node, endpoint, PC managed node, NetWare managed site, or profile manager. The resource must subscribe to the profile manager containing the AutoPack. AutoPack Profile Operations TME 10 Software Distribution AutoPack User s Guide 3 15

64 Distributing an AutoPack Profile Desktop Use the following steps to distribute an AutoPack: 1. Select Distribute... from the AutoPack icon pop-up menu to display the Distribute AutoPack dialog. Ensure that the Distribute AutoPack To scrolling list accurately displays the subscribers to which to distribute the AutoPack Version 3.6

65 Distributing an AutoPack Profile 1. Perform the following actions using the scrolling lists: To move a subscriber to the Distribute AutoPack To scrolling list, choose one or more subscribers from the Available Subscribers scrolling list and press the left arrow button. By default, all subscribers in the profile manager are displayed in the Available Subscribers scrolling list. To remove a subscriber, choose one or more subscribers from the Distribute AutoPack To scrolling list and press the Remove button. If the Available Subscribers scrolling list contains a profile manager, a plus sign (+) appears in front of its name. By double-clicking on the profile manager name, you can expand the list to view all subscribers to this profile manager. Note that the managed resource type for each subscribing machine is listed next to the machine name. You can then add any of its subscribers to the Distribute AutoPack To scrolling list. AutoPack Profile Operations TME 10 Software Distribution AutoPack User s Guide 3 17

66 Distributing an AutoPack Profile Note: If you select a profile manager name in the Available Subscribers scrolling list, you must deselect it before double-clicking on it. The name of an expanded profile manager has a dash (-) in front of it in the Available Subscribers scrolling list. To compress an expanded profile manager entry, double-click on the profile manager name. Use the Expand All or Compress All buttons to expand or compress all profile managers in the Available Subscribers scrolling list. If you have TME 10 Inventory installed, you can select subscribers by scanning the available endpoints, NT managed nodes, and PC managed nodes for certain criteria defined by a query in a query library. To run a query, press the Query button to display the Execute a Query dialog. This dialog lists the available query libraries that were created using Inventory. Select a query library from the Query Libraries scrolling list then press the Execute button to run the query on the TME 10 configuration repository and return the names of the endpoints, NT managed nodes, and PC managed nodes that meet the criteria. This list automatically populates the Distribute AutoPack To scrolling list. See the TME 10 Inventory User s Guide for more information on creating and using queries Version 3.6

67 Distributing an AutoPack Profile 1. Press the Schedule... button to schedule operations at a future time or to automatically retry the distribution to any target for which the distribution might fail. Software Distribution displays the Add Scheduled Job dialog. AutoPack Profile Operations See the TME 10 Framework User s Guide for more information about creating tasks and jobs, and about using drag and drop to schedule a job. TME 10 Software Distribution AutoPack User s Guide 3 19

68 Removing an AutoPack Command Line 1. Press the Distribute & Close button to begin distributing the AutoPack to the selected subscribers and dismiss the Distribute AutoPack dialog. Note: The dialog is not dismissed until the distribution is complete and the operation stops. If the distribution fails for any of the subscribers, a pop-up dialog is displayed to inform you which subscribers failed during the distribution. This status is also displayed on the TME 10 desktop. To use the wdistrib command to distribute the Office97 AutoPack to the NTMachs profile manager, enter the following Specifies to distribute the Office97 Distributes the AutoPack to the subscribers of the NTMachs profile manager. For more information about distributing from the command line, see the wdistrib command in the TME 10 Framework Reference Manual. Removing an AutoPack You can remove AutoPacks that you have distributed to targets. You might remove an AutoPack, for example, if the software does not perform as you expected. You can easily remove an old version of a software package before distributing the new version, rather than writing over the old version. Removing an AutoPack from a client does not remove the original AutoPack from the source host or the original AutoPack s profile from the TME 10 database. You can also delete an AutoPack profile from a profile manager. Deleting an AutoPack profile does not delete the AutoPack source file or the distributed files on the targets. This operation simply removes 3 20 Version 3.6

69 Removing an AutoPack the AutoPack profile from the TME 10 database and deletes its icon from the desktop. The following table shows the context and role required to remove an AutoPack from a subscriber: Operation Context Required Role Remove an AutoPack Profile admin, senior, or super You can perform this task only from the TME 10 desktop. Use the following steps to remove an AutoPack from one or more subscribers using the desktop: 1. Select Remove from hosts... from the AutoPack icon pop-up menu to display the Remove AutoPack dialog. AutoPack Profile Operations All subscribers of the AutoPack s profile manager are displayed in the Available Subscribers scrolling list. 1. Ensure that the Remove From Hosts scrolling list accurately displays the subscribers from which to remove the AutoPack. To add a subscriber to the Remove From Hosts scrolling list, select one or more subscribers from the Available TME 10 Software Distribution AutoPack User s Guide 3 21