![]() |
![]() |
![]() |
![]() |
Enterprise User Manual
Chapter 14
Software Distribution
Software Distribution enables you to remotely distribute and update software packages to Clients and Servers on your organization's networks. Because you can configure the Distribute Software Operation to install software with no user intervention, it can be used to keep your network up-to-date with a minimum of disruption. In addition, because the Operation uses the standard installers that are supplied with new third-party software, it can be used to install software safely with a minimum of preparation.
Three main components are used to distribute software packages to PCs: the Package Definition Editor, which stores Package Definitions; the Software Distribution Wizard, which is used to organize distribution Operations; and the Software Distribution Agent, which runs on Client PCs.
The Software Distribution Process
Enterprise uses a four stage process to distribute software to Client PCs:
- Prepare the installation kits. This section describes how to use three common installation kits: InstallShield, Microsoft Setup and Windows Installer.
- Configure a Package Definition using the Package Definition Editor (see page 114). Package Definitions are profiles that define how a software package must be installed, and include the kit location, SETUP command syntax and other relevant information.
- Distribute the Package Definitions to the Offline Area using the Software Distribution Wizard (see page 123). The Wizard helps you specify how a Package is to be distributed.
- The Software Distribution Agent reads the Package Definition and installs the Package (see page 126). The Software Distribution Agent forms part of the Enterprise Client kit.
After performing a software distribution, you can monitor the progress of installations on individual PCs using the Software Distribution Jobs Viewer (see page 127), or by checking the error and progress logs.
Preparing Installation Kits
To minimize disruption, most installers enable you to configure installation kits to install their software without user intervention. This section describes how to create these silent installation kits using the following tools:
- InstallShield
- Microsoft Setup, for older software packages, such as Office 97
- Windows Installer (MSI), for applications that have the Certified for Microsoft Windows logo.
It may be possible to configure other packages to support silent installation methods. For more information, refer to the documentation supplied with the software package. If an application does not support a silent install, automated responses can be specified using a separate tool. We recommend using WinBatch from Wilson Windowware.
Preparing Kits for InstallShield Packages
You can perform a silent InstallShield installation by creating a response file to record the installation settings you want the installation to use. Repeat this procedure for each different type of installation you want to perform.
To create an InstallShield response file:
- Copy the software package to a location that is accessible to all PCs on which you want to install the software.
- On a PC that is representative of the target group, run the SETUP.EXE of the package with the -R (Record) option. For example, if the package is in the RCP32 directory of the PC's U: drive, type:
u:\rcp32\setup -r- Complete the installation with the responses you want to use to install the package. The responses are recorded in a file called SETUP.ISS, which is saved in the PC's WINDOWS directory. This file provides the installation responses when you install the software on the other PCs.
- When Setup has finished, copy the response file to the directory from which you started SETUP.EXE.
You can now configure a Package Definition to specify how the application must be installed. For more information, see "Configuring Package Definitions".
Preparing Kits for Microsoft Setup Packages
This section describes how to prepare installation kits for Microsoft Setup applications, such as Office 97.
To create a Microsoft Setup Installation kit:
- Run Setup from the CD using the administrative option. For example, to create an administrative kit, type:
h:\setup /A- Follow the Setup instructions to copy the software package to a location that is accessible to all PCs on which you want to install the software, and to configure the kit.
Distributing Packages with Windows Installer (MSI)
Windows Installer is a Microsoft service designed to improve the installation, maintenance and removal of software packages. The service, called MSIEXEC, is included in Windows XP and 2003. It is also available in redistributable packages for Windows 95, 98, Me, NT4 and 2000.
Each installation that attempts to use the Windows Installer first checks whether it is present on the Client. If it is not installed, the installation checks which operating system is running, then attempts to install the appropriate version of the Installer.
- This method can force target PCs to reboot before the package installation begins. We recommend you install Windows Installer 2.0 on all Clients before installing any software packages. For more information, see "Distributing Windows Installer 2.0". More information about Windows Installer is available in the Microsoft Windows and Office Resource Kits
In PC-Duo Enterprise, you can use the Software Distribution module in conjunction with the Windows Installer. This combination offers reliable and efficient deployment of applications that feature the Certified for Microsoft Windows logo.
The following sections describe how to configure and distribute Windows Installer packages with Enterprise using the Office 2000 Resource kit as an example. You can use a similar method to install other Windows Installer packages.
For detailed information on preparing Office installation kits, refer to the Office Resource Kit documentation. You can obtain the Resource Kit information from the Microsoft Web site, using the following links.
Microsoft's Office resource kit Web page:
http://www.microsoft.com/office/ork/xp/default.htmIf you already have the Office 2000 Resource Kit, you can update it from:
http://www.microsoft.com/office/ork/2000/journ/NewORKTools.htmPreparing Windows Installer Kits
This section provides an overview of the steps required to prepare an application for distribution using Windows Installer. More detailed information is supplied in the following sections.
To prepare an application for distribution with Windows Installer:
- Create an Administrative Installation Point (see "Creating an Administrative Installation Point").
- Optionally, create a Transform, which customizes the installation of the application (see "Creating Transforms using the Custom Installation Wizard").
Creating an Administrative Installation Point
An Administrative Installation Point is a source image of the software package that is located on a server, or a network-accessible drive.
- Installation Points must be created in a location that is accessible for the duration of the software's use.
To create an Administrative Installation Point, install the package with the /a option. For example:
setup.exe /a data1.msiYou are then prompted to specify the default organization name and the location for the Administrative Installation Point. An .MSI file is created in this location.
- Administrative Installation Points can use a large amount of disk space because they include all installable features and components of the software package.
Creating Transforms using the Custom Installation Wizard
By default, Windows Installer performs a standard software package installation. For example, if you use Windows Installer to install Office 2000, all the Office components are installed on the target PC. However, if you want to customize the installation to include specific features, or to install specific components, you must create a Transform that identifies the options and components you want to use. For example, if you want to install only Excel, you must create a Transform to restrict the installation to that component.
Transforms have an extension of .MST. They are created by customizing the Package with, for example, the Custom Installation Wizard supplied with the Office Resource kit. You can create multiple Transforms, which offer different installable features and components. These Transforms can be used as the base for your Package Definition's multiple Install Types.
The Custom Installation Wizard prompts you for the location of the MSI file created in the previous stage. Choose the Create new Transform option.
Following this, you are prompted for the name of the new .MST file. This file must be located in the root directory of your Administrative Installation Point (the location of the kit you created earlier), alongside the .MSI file.
You can now change the Package's default installation folder, Organization name, and the Features and Components that will be installed on Client PCs. Other options include:
- Adding files to the installation.
- Adding registry entries by importing .REG files.
- Customizing the default list of program folder shortcuts.
- Providing alternative locations for the Administrative Installation Point, if you have multiple kit sources.
- Running additional command lines, such as when you want to install or remove other packages.
- Including application profile settings for users (created separately using a Profile Wizard).
Having specified these Wizard settings, you are prompted to save them. The name of the saved Transform is presented, along with an example silent install command line, such as:
setup.exe TRANSFORMS="G:\OFFICE2K\Custom Outlook Setup File.MST" /wait /qn+Make a note of this suggested SETUP command, as it is used later in the Package's Definition, using the Package Definition Editor.
You can modify the Transform you have created by re-opening it in the Custom Installation Wizard.
Configuring Package Definitions
Package Definitions are profiles that specify how and where software packages can be installed. They include the kit location, SETUP command syntax and other installation information.
Enterprise is supplied with a large number of Package Definitions that can be used without modification to install most common third-party applications. However, you can use the Package Definition Editor to customize these Definitions to suit the needs of your network, or to create Definitions that enable you to control the installation of new and custom software applications.
- Package Definitions are stored centrally in the Global Site. When you add or edit Package Definitions using the editor, these modifications are made to the data in the Global Site Database's SWDISTDB Table.
To start the editor from the Console, click the Edit Distribution Definitions Operation.
Using the Package Definition Editor
The Package Definition Editor lists all available Package Definitions in the Tree View in alphabetical order. To view the settings for a Package Definition, expand the definition, then click a category. The settings are displayed on the right of the window. Each Package Definition contains the following categories:
Summary
Stores basic information such as the package name, check paths and any notes about the Package Definition.
Install Types
Specify the operating systems on which the software package can be installed, and what installation options are to be used. Many packages support different types of installation for different operating systems, different levels of use, or for installing optional components. Different install types usually have different commands and command options. You can create a different install type for each of these options as part of a single Package Definition.
Pre-/Post-Processing
Specifies any commands that you want the system to execute before and after the main installation command runs.
To create a package definition:
- In the Package Definition Editor, right-click the Tree View, and choose Add Package Distribution Definition from the shortcut menu.
- A message is displayed asking if you want to link the new definition to a Software Inventory Package. If you are creating a Package Definition for a standard software package, click Yes and select the application from the Select Package dialog. Otherwise, click No.
- In the Add New Package Definition dialog, enter a Name for the new Package Definition and click OK. The new definition is added to the Tree View.
- Click the plus symbol adjacent to the new definition, then click the Summary, Install Types and Pre/Post Processing sections to enter the details of the definition.
Package Definition Summary Information
Use the Summary category of a Package Definition to record general information about the package that this definition is used to install, and to enter the check paths that the system uses to determine whether the Package is installed.
Check paths are tested before the Agent attempts to install an application on a Client. If any of the specified files are present, the Agent assumes the package is already installed, and continues on to the next Client install. You can specify multiple check paths to check for different locations and multinational versions of an application. The check paths are also tested following an installation, to ensure the installation was successful.
When you enter a check path, you can enter a size for the file. If the file is found, but does not match the specified size, the installation will proceed.
To specify summary information:
- In the Tree View, expand the Package Definition you want to update, then click Summary. The Summary pane is displayed.
- If you want to change the name of the Package Definition, type a new name in the Package name field. The change is displayed in the Tree View when you close the definition.
- For each check path you want to specify:
- In the Check paths section, click the Add button.
- In the Check Path Details dialog, enter the location and name of a file you want to use to check for the presence of this software package.
- Use * and ? as wildcard characters to detect multiple files in a single check path. If any matching files are present, the package will not be installed.
Check paths are treated as local paths on each PC. You can use environment variables in check paths, such as %TEMP% to specify the PC's local TEMP directory. For more information, see "Using Tokens in Package Distribution Definitions".- If you want to check for a specific version of the file, enter the size of the file in the Value field.
- Click the OK button to save the check path and close the dialog.
- If you want to amend or remove any check paths, select the path in the list, then click the Edit or Delete buttons.
- If you want to enter any extra information about this Package Definition, type it in the Package notes field.
Package Definition Install Types
Many software packages support different types of installation. As well as supporting different operating systems, some installers, such as Windows Installer, enable you to select which optional components you want to install, and what level of functionality is available to users. Install Types enable you to control how and where a package can be installed and any special installation requirements.
All Package Definitions must include at least one Install Type. If your organization uses several different installations of the same package, you can define an Install Type to support each one.
- You can create multiple Install Types based on different Transforms for Package Definitions that use the Windows Installer. For more information, see "Creating Transforms using the Custom Installation Wizard".
Enterprise is supplied with default Install Types for many software packages. To display a Package's Install Types in the Package Definition Editor, expand the package in the Tree View, and expand the Install Types. You can then select the Install Type to view its settings.
To create a new Install Type:
- In the Tree View of the Package Definition Editor, right-click the Package you want to update and choose Add Install Type from the shortcut menu.
- In the Add New Install Type dialog, enter a Name for the Install Type and click the OK button.
- In the Tree View, click the new Install Type, and enter a Description.
- In the Platforms supported section, select all the operating systems on which you want to use this Install Type.
- In the Kit path field, type the location of the program (such as SETUP.EXE) that is used to start the installation of the package (see "Preparing Installation Kits"), or click the Browse button to select the kit location. Enter the path in the form:
\\machine\resource%username:passwordThe path must be accessible from all Client PCs on which the software will be installed. Also, because the path is interpreted by the Clients, it must not include host-specific information. The %username and password parameters are optional. Use them to specify any account details required to access the installation kit.- In the Install command field, enter the name of the package's installation command and the parameters you want to use. For example:
setup.exe /wait TRANSFORMS="Office Setup.MST" /qn+
- If you are creating an Install Type for Windows Installer, SETUP.EXE, must be followed by the command options suggested by the Custom Installation Wizard.
For more information on the parameters that can be used with installers, see Appendix B, "Installation Commands."
- Select the installation options you want to use:
Privilege required Privileged installs are common amongst applications that support Windows NT, 2000, XP and 2003. Non-Admin users, can perform privileged installations using the Software Distribution Service.
- Package Definitions for Windows Installer must select the Privilege required, Reboot allowed and Reboot required options.
Login required Specifies whether the user must be logged on before installation starts.
Use UNC Path Causes the Client to make a UNC (Universal Naming Convention) network connection when it runs SETUP or a software distribution command. Use this for installers that remember where they were installed from.
User input required Enables the user to interact with the installation process.
Visible Determines whether the installation can be viewed by the user. If an installation requires responses from the Client user, ensure this check box is selected.
- Applications that use the Microsoft Setup install method may ignore the Visible check box. Use the /Q1 option (in the Install command field) to display the installation process, or /QT to hide it.
Do not select Visible if you are using a batch file. Client PC users can easily interrupt it and gain access to a privileged command prompt in Windows NT, 2000, XP and 2003.Reboot allowed Allows the installation to reboot without user intervention.
Reboot required If the installation requires a reboot, the Client user is prompted to reboot the PC if the installation does not reboot itself.
- Select the target drive from the Free space drive list, and enter the minimum space required for the installation in the Size (MB) field.
- In the Start prompt field, type the text you want the system to display to Client users before the installation starts.
- If you are using an early version of Windows Installer (pre-2.0), or an installation kit that requires multiple reboots, you must specify LULOGON.EXE as a Pre-process command. For more information, see "Pre- and Post-Processing Information".
To delete an Install Type:
Right-click the Install type you want to delete in the Tree View, then choose Remove Install Type.
Using Tokens in Package Distribution Definitions
You can use the following Enterprise tokens in the command line fields of a Package Definition's Install Types and Pre-/Post-Processing areas:
$ACCOUNT$
The user account specified in the Software Distribution Wizard when the Job is distributed. The account is supplied in the form: username@domain:password.
$USERNAME$
$DOMAIN$
The Domain name of the account.
$PASSWORD$
$KITDIR$
The path that the installer is being run from, with a trailing backslash. The format of the path is specified as a UNC or a mapped drive, depending on the Kit path settings.
You can also use the standard Enterprise tokens (for more information, see "Using Tokens in Command Launch Operations") to create distribution Jobs that only run commands specified in the Pre- and Post-Processing areas.
Pre- and Post-Processing Information
The Pre-/Post-Processing category of a Package Definition enables you to specify commands that you want Enterprise to execute before and after the installer runs.
To specify pre- and post-processing commands:
- To display a Package's Pre-/Post-Processing category, expand the Package in the Editor's Tree View, then click Pre-/Post-Processing.
- If you want the system to perform a command before the installation commences, enter it in the User command field of the Pre-process area. You can include any tokens in this command line, and specify a UNC path or reference any file held locally on the PC.
- If you are editing a Package Definition for a software package that uses an earlier (pre-2.0) version of Windows Installer, or an installation kit that requires multiple reboots, you must specify the LULOGON as a pre-processing command, and select the Prefix Client install directory and Error fatal check boxes.
LULOGON.EXE is part of the Enterprise Client kit. It configures an Admin-level automatic login that enables the installer to reboot the Client when required.- Select the Prefix Client install directory check box to reference files in the Client's installation directory without including the full path. For example, if you choose this option, you can omit the path and specify:
CLOSEAPP TITLE="Readme.txt - Notepad"- Select the Visible check box if the process requires responses from the user (such as their name), or if you want the command to be displayed on the Client PC.
- If the Pre-process command must complete successfully before the installation can be performed, select the Error fatal check box in the Pre-process section. This causes the installation to abort if the Pre-process command fails.
- To perform a command after the installation, repeat steps 1 through 3 in the Post-process area.
Specifying the LULOGON Pre-Process Command for Windows Installer (MSI) Packages
LULOGON.EXE enables the installation of Packages kit that requires multiple reboots, such as Internet Explorer 5, and early versions of Windows Installer (before version 2). It does this by running as a Pre-Process command in a Software Distribution Job, facilitating reboots during the installation process.
The first phase of an installation is completed by triggering a reboot. LULOGON has configured an automatic privileged login for when the reboot happens and it has inserted itself to run again on the reboot.
LULOGON also disables the keyboard and mouse after the reboot, removing the dangers of having an open PC with a privileged logon. When the PC is rebooted, it automatically logs on with the specified user account, and the installation is completed. The user is unable to use the PC during this phase of the install.
For the next reboot, LULOGON disables the automatic logon. It re-enables the keyboard and mouse, waits for the installation to complete, then triggers the second (final) reboot. To avoid problems caused by a premature reboot, LULOGON waits for a specific application window to close, and then waits for a further specified period of time. When this phase is completed, LULOGON triggers a reboot and returns control of the PC to the user.
LULOGON command has the following syntax:
LULOGON [/DEBUG] [/INSTALL "AdminUser@Domain:Password" [/LOCKOUT]] [/UNINSTALL]
[/TIMEOUT nn (secs)] [/NTFSLOCKDOWN] [/EXPLORER] [/CAPTION "MessageBox Caption/Title"]
[/MESSAGE ["MessageBox Text"]] [/WINDOW "Target Synchronize Window Caption"] [/HELP]/INSTALL
Adds the details of the specified account to the registry.
/LOCKOUT
Causes the keyboard and mouse to be disabled on the reboot after the /INSTALL phase. Use this command option during a formal deployment to avoid leaving an open Admin login.
- Always test the distribution before implementing it with the /LOCKOUT option.
/NTFSLOCKDOWN
This is determined automatically during execution. It indicates that the system is a locked-down NTFS machine. This must be released on /INSTALL and restored on /UNINSTALL.
/CAPTION and /MESSAGE
Enable you to control the message displayed when counting down before the final reboot is triggered. Similarly, the /TIMEOUT option is passed through in the /INSTALL phase and is acted upon as the reboot delay in the /UNINSTALL phase.
/WINDOW
Enables you to customize the title of the "Personalized Settings" window. This window is used to perform the per-user setup following the first reboot. The final reboot is triggered after the target window closes (assuming it is found).
/EXPLORER
This option protects an installation from interruption by these Web browser updates, and is automatically generated by the system. It checks the Client PC Registry for scheduled browser updates. If it finds any, the installation deletes the Registry key at the first LULOGON pass and restores it after the reboot.
/HELP
Displays a Help screen for the LULOGON command.
- All command options can be abbreviated to their first letter. Only one letter is checked.
You can include Enterprise tokens in the LULOGON command line. For example, the following command line specifies the access details for Client PCs:
LULOGON /INSTALL "$ACCOUNT$" /MESSAGE /LOCKOUTUsing LULOGON on Windows 95, 98 and Me
LULOGON operates without problems on Windows 95, 98 and Me Clients, enabling you to distribute MSI packages to these platforms using the same Package Definitions. (However, you should always test such distributions before deployment.)
Troubleshooting Windows Installer Installations
During a Windows Installer installation, the Client is normally rebooted twice. The LULOGON command disables the Client's keyboard and mouse following the first reboot, while the Windows Installer installation is carried out using a privileged user login. When the Client PC is automatically rebooted again, keyboard and mouse input is restored.
Problems with a Windows Installer installation, particularly during the input-lockout session, can occur for the following reasons:
- The Windows Installer installation has tried to use an incorrect or out-of-date password. Always check the user name and password used to connect to the Administrative Installation Point kit before performing an installation.
- The appearance of unexpected dialogs that require user input, such as other application's notice messages regarding software licenses.
- Unexpected prompt messages that require a response, such as anti-virus software notices.
- Persistent drive mappings that attempt to access an unavailable server or that require a changed password.
Any of these problems can cause an installation failure. If the failure occurs when the Client's keyboard and mouse are locked, use the following method to restore the PC.
- On another PC, run RegEdit.
- Choose Connect Network Registry in the Registry menu to open the input-locked PC's Registry.
- Locate the following Registry Key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Kbdclass.- Locate the following Registry Key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Mouclass.- Choose Disconnect Network Registry in the Registry menu to close the remote connection, then exit RegEdit.
- Reboot the locked PC using a remote shutdown utility, or by manually switching it off and on. The PC should now be unlocked.
Saving Package Definitions
After creating or modifying a Package Definition, click the Save button in the toolbar to save your changes. Alternatively, if you click another Package after making changes to the current Package, a message asks if you want to save your changes.
Printing Package Definitions
To print a hard copy of the currently selected Package Definition, click the Print button in the toolbar or choose Print in the File menu.
The format of the printed information is the same as an exported Package Definition.
Deleting Package Definitions
To delete an existing Package Definition, right-click the Package and choose Delete Package Distribution Definition from the shortcut menu.
Alternatively, choose Delete Package Distribution Definition in the Package menu.
Importing and Exporting Package Definitions
You can transfer Package Definitions between databases as .INI-style text files. These can be imported to and exported from the Package Definition Editor. You can import multiple Package Definition files simultaneously.
Any Package Definitions with names over forty characters long are truncated. (A warning message is displayed.)
To import package definitions:
- In the Package Definition Editor, choose Import from the File menu.
- In the Open dialog, navigate to the directory containing the PD files you want to import.
- Select the .PD files you want to import.
- Click the Open button to import the Package Definitions. The selected Package Definitions are imported into the Package Definition Editor.
To export a Package Definition:
- In the Package Definition Editor, choose Export from the File menu.
- In the Save As dialog, navigate to the directory in which you want to save the file.
- Enter a name for the file, then click the Save button to export the Package Definition.
Linking Package Definitions to Packages
You can link Package Definitions created in the Package Definition Editor with the software packages that can be identified by the Update Software Inventory Operations. This enables you to ensure consistency between package names and Package Distribution Definitions.
To link a package definition to a Package Recognition Rule:
- In the Tree View, right-click the Package Definition you want to link to and choose Link to Enterprise Package in the shortcut menu.
- In the Select Package dialog, locate the Enterprise Package in the list.
- Select the Use package name for distribution name check box if you want to rename the Package Definition with the Package name used by Enterprise.
- Click the OK button to save your changes and return to the Package Definition Editor. A linked icon is displayed alongside the Package Definition.
To remove a link to a Package, right-click the Package Definition in the Tree View and choose Unlink from Enterprise Package from the shortcut menu. The linked icon alongside the Package Definition changes to an unlinked icon.
- To display the Link Details for a Package Definition, right-click the Package and choose Show Enterprise Package Link Details.
Using the Software Distribution Wizard
Use the Software Distribution Wizard to set up and organize the distribution of software packages across your Site. Software Distribution tasks are organized from the Console. When you have defined your Package Distribution Definitions and have prepared the install kits, you can use the Distribute Software Operation to place the Package Definition information in each Client's Offline Area.
- Packages are installed when the Software Distribution Agent next checks the target PC. You can change the period between checks using the SnapshotMinutesInterval parameter in the Client's LUCLIENT.INI file. For more information, see "Controlling Client Behavior".
To start the Software Distribution Wizard:
- If you want to distribute the package interactively, click the Distribute Software Operation.
If you want to schedule the distribution, right-click the Distribute Software Operation and choose Submit Job from the shortcut menu. In the message, click the OK button.
- In the Select Clients window, select the Group or Clients on which you want to install the software package. The Software Distribution Wizard is displayed.
Selecting a Package and Install Type
The first stage of the Software Distribution Wizard is to select the package you want to distribute.
To choose the package you want to distribute:
- Select the Package you want to install in the dialog list. The Package description is displayed.
- If the Package you want to distribute is not displayed in the Select Package dialog, click Cancel to exit the Wizard, and use the Package Definition Editor to create or import the definition. For more information, see "Configuring Package Definitions".
- Click the Next button to advance to the next stage of the Software Distribution Wizard.
- If the Package Definition you have selected for Distribution contains multiple Install Types, the Select Install Type dialog is displayed. Select the Install Type you want to use, then click Next. The Client Filter dialog is displayed.
Filtering Clients
Use the Client Filter dialog to identify which Clients the software package must not be distributed to. The two types of filter you can apply are based on the Platform supported (by the Package Installation) and a free disk-space check.
The Platform filter gives you control of PCs that have a multi-boot configuration. Any Clients that do not match the specified Platform are ignored when the Agent processes the Job.
To filter clients:
- By default, the Client Filter selects all the platforms where the associated Package Definition allows you to distribute the software. Deselect any platforms that you do not want to distribute the software package to.
- If you want to change the Free space check specified in the Package Definition, select the Drive you want this install to check and enter a new value in the Space field. Enter 0 in the Space field if you do not want the system to perform a space check.
- Click Next to open the Settings dialog.
Specifying the Kit Settings
Use the Settings dialog to specify the location of the Installation kit from which you want to install the software package, and to control how and when the package is distributed.
To specify the Kit settings:
- In the Kit location field, enter the location of the kit you want to use to install the software package, or click the Browse button to select the directory. This location is usually a UNC Path and must include any necessary user name and password information.
- In the Expiry date field, enter the last date on which the system should attempt to distribute this software. The date must be in
dd-mmm-yyyy format, such as 14-Feb-2003. If the system has not completed the distribution by this date, the Operation is cancelled by the system.- If you want to allow users to postpone the installation of this software package, type the maximum number of postponements they can make in the Refusal limit field. If you want to prevent postponements, enter 0.
- By default, the system attempts to distribute the software to all the Clients at the first opportunity. If you want to stagger the installations over a period of days, select the Enable load control check box, and enter the last day of the period in the Target completion date field. The system automatically spreads the installations over the specified period.
- If you are distributing software to Clients that are members of a domain, or that have restricted access, use the Windows NT account information fields to enter the details of an account that can be used to define a user context and privilege level for Agent Service Jobs. $ACCOUNT$ and related tokens allow access to these settings in the Pre-/Post-Processing and SETUP commands.
- By default, the progress of the software installation is displayed on Client PCs. Select the Silent check box if you want the installation to display only error messages. Select the Totally Silent check box to suppress error messages and completely hide the installation the user.
- Click the Next button to open the Monitoring and Logging dialog.
Specifying Log File Locations
Use the Monitoring and Logging dialog to specify whether you want to log the progress and error information for a distribution Operation, and to specify where you want to save the progress logs of the Distribute Software Operation. You must specify all locations as full UNC paths, and include any required user name and password settings.
To specify log file locations:
- In the Package specific section, enter a location and name for the files in which you want to record error and progress for each software installation on each Client PC.
- By default, the first available Scheduler in the Site database monitors distribution jobs. If you want to nominate a specific Scheduler to monitor this Job, select the Scheduler's name in the Monitoring Host list.
- In the Agent specific section, enter a location and name for the files in which you want to record error and progress for the software distribution Agent.
- Click the Finish button to complete the Software Distribution Wizard and start the Operation.
If you submitted the Operation as a Job, the Submit Job dialog is displayed. Specify the details of the Job and click Submit to schedule it. For more information, see "Scheduling Operations".
Customizing the Distribute Software Operation
By customizing the Distribute Software Operation, you can define default values for distribution kit paths, kit expiry dates and log file locations in the Software Distribution wizard.
To customize the Distribute Software Operation:
- Right-click the Distribute Software Operation and choose Customize from the shortcut menu.
- In the Customize Software Distribution dialog, select the Software Distribution tab.
- Enter the default values you want to use for Distribute Software Operations, then click OK to save your settings and close the dialog. The settings are automatically used the next time you perform a Distribute Software Operation.
Distributing Windows Installer 2.0
Windows Installer version 2.0 is an improved version of the Microsoft installation and maintenance service that enables you to install software packages without the need to reboot PCs during the course of an installation. It is included with Windows XP, but it can also be installed on older operating systems.
This section describes how to install Windows Installer 2.0 across your network using the Distribute Software Operation. To provide a consistent and up-to-date method of installation across your network, we recommend you install the kit on all Clients before installing any software packages with Windows Installer.
You can obtain Windows Installer 2.0 upgrade kits for Windows NT4 and 2000 (INSTMSIW.EXE), and Windows 95, 98 and Me (INSTMSIA.EXE) from Microsoft at www.microsoft.com/downloads.
- Windows NT 3.5.1, Windows 3, and Windows for Workgroups are not supported by Windows Installer 2.0.
To distribute Windows Installer version 2.0:
- Save the Windows Installer kits in a location that can be accessed across your network.
- In the Console, click the Distribute Software Operation. In the Select Clients dialog, select the Clients or Group to which you want to distribute the kit, then click the OK button.
- In the Select Package dialog, select Windows Installer 2.0 (MSI) in the package list and click the Next button to continue.
- In the Select Install Type dialog, select Typical to install the kit on Windows 95, 98 and Me, or select Admin to install MSI on Windows NT and 2000. Click the Next button to continue.
- In the Client Filter dialog, click the Next button to continue.
- In the Settings dialog, enter the Kit location, target dates and any account information necessary to access the target PCs, then click Next.
- In the Monitoring and Logging dialog, enter a Job name for the installation, then click Finish to start the installation.
The Software Distribution Agent
Software Distribution is performed by an Agent that runs on each Client PC. The Agent can also run as a Service on Windows NT, 2000, XP and 2003. This is normally set to Autostart on system reboot.
The Agent loads its settings from files held locally on each Client PC. If necessary, it looks at files held on the Offline Area to collect updated instructions. This Agent is started as part of the Client startup procedure and runs following a Client PC reboot. When an application is queued for installation, the Agent makes a connection to the server that holds the installable kit and runs the command line at the scheduled time.
Network Load Control
If a Target completion date was specified when the Distribute Software Job was specified, installation is staggered across the target Clients to prevent excessive network load. After the Target completion date is reached, all Agents become eligible to execute the Job on Clients where the installation is still outstanding.
- You can change the frequency at which Clients connect to the Offline Area (for more information, see "Reconfiguring Clients after Installation"). However, this can affect the responsiveness of the Distribution Agent running on those PCs.
Agent Logging Activity
When an installation is completed, the Agent adds entries to the centralized log files, so that you can see how the Job is progressing. Any errors are also logged.
The location of these log files is specified in the Software Distribution Wizard.
Monitoring Distribution Jobs
When software packages are distributed using the Software Distribution Wizard, Enterprise automatically starts a system Job to monitor the progress of the package installation on each target Client. This Job collects the installation events and records them in the Site database where you can track the installation on individual Clients using the Software Distribution Jobs window.
To view your distribution Jobs, click the Monitor Software Distribution Operation in the Console.
Using the Distribution Jobs Viewer
The Distribution Jobs window contains two panes. Use the top pane to choose how you want to organize the display of distribution feedback; use the bottom pane to display the details of installations on each Client:
- To display the data for individual Jobs, click the Distribution Jobs tab. This view contains the status of each Job, the Scheduler responsible for monitoring each installations, and the software package being installed.
- To display the feedback for each software package distributed by software distribution Jobs, click the Package Items tab.
- To display information on the current status of the installation on each associated Client, plus the time and date when the installation started, and the last task completed by each Client, click an entry in the Distribution Jobs list or Package Items list.
You can use the Distribution Job Viewer to perform the following tasks:
- To list all the currently completed events for a Client, double-click its entry in the Client list.
- To display the progress of a selected distribution Job in a chart, right-click the Job and choose Show Summary in the shortcut menu.
- To create a new Fixed Group, select the Clients in the Clients list, right-click your selections and choose Make a Fixed Group in the shortcut menu.
- To change the Scheduler that is currently responsible for monitoring the progress of the selected distribution Job, right-click the Job, and choose Change Monitoring Host.
- To update the database with the latest feedback from the Clients, choose Start Feedback Collector in the View menu. This option can take some time to complete because it forces the immediate collection of feedback from all Clients assigned to the selected Job.
- To update the Viewer with the latest information from the database, choose Refresh All in the View menu, or press the F5 key.
- To delete distribution feedback from the database, select one or more entries in the Jobs list, right-click your selections and choose Purge Job Data in the shortcut menu.
Configuring the Distribution Monitor
By default, Enterprise automatically monitors all software distributions, and stores the installation feedback from each Client indefinitely. If you don't want to monitor the distribution of software packages, or you want to delete the feedback data you can use the Software Distribution Monitoring Settings dialog to change the Monitor's settings.
To open the dialog, click Monitor Software Distribution in the Software Distribution folder.
Disabling the Distribution Monitor
To disable monitoring of new Distribute Software Jobs, deselect the Enable software distribution monitoring check box. To re-enable distribution monitoring, select the check box.
- Each distribution Job checks whether feedback monitoring is enabled only when it starts. If you start a distribution Job while monitoring is disabled, monitoring cannot be re-enabled for that Job.
Purging Feedback Data
Collection of software installation feedback is performed by two processes. The Client is responsible for collecting feedback from the installation process and saving the data in the Offline Area. The Distribution Monitor (DISTMON.EXE) is responsible for collecting the data from the Offline Area and saving it to the Site database. By default, this feedback data is stored indefinitely. However, you can use the Software Distribution Monitoring Settings dialog to remove old feedback data using the purge options:
- To automate the deletion of feedback from the Offline Area, type a non-zero value in the Purge feedback from clients field. The system will automatically delete all data that is older than the specified number of days.
- To delete feedback data from all distribution Jobs in which all Client installations are successfully completed (or halted due to failure), type a non-zero value in the Purge database of completed jobs field, and click the Purge completed jobs now button. The system deletes any completed Jobs that are older than the specified number of days.
- To delete feedback data from all distribution Jobs regardless of whether the Client installations are complete, type a non-zero value in the Purge database of all jobs field, and click the Purge all jobs now button. The system deletes all feedback data that is older than the specified number of days.
- The Purge all option cancels the collection of further installation feedback from all currently active distribution Jobs, although the software installations themselves will continue. Use these options only when the database contains Jobs that can never be completed, such as installations that have been assigned to Clients that are no longer attached to your network.
Logging Options
Each Scheduler that is responsible for collecting and saving the installation feedback can record the activities of DISTMON.EXE, the program that is responsible for collecting and saving the installation feedback. This enables you to monitor the activity of each Scheduler, and to identify problems that occur during monitoring. You can select one of the following logging options:
No logging
To record no logging data for all Schedulers.
Log errors
To record all errors encountered during the monitoring of distribution Jobs.
Log errors and additional information
to record all monitoring errors plus status reports, the Clients and Jobs processed, information on the number and type of events found, and the actions taken.
Each Scheduler that is responsible for monitoring distribution Jobs maintains its own distribution log, called SWDISTMONITOR.LOG, in its own PC-Duo Enterprise directory.
Software Distribution Logs
In addition to using the Distribution Job Viewer, you can monitor the progress of distribution Jobs using the centralized Error and Progress logs specified in the Software Distribution Wizard. These logs can be created for both the Packages and Client PCs, and are updated at the same time as the Distribution Job Viewer.
Each log entry contains the Client name and the event. The progress logs record details from each Client Agent as it processes a package. For example, the progress log identifies PCs that have skipped a package due to filters or load control. It also records when an installation is refused by the user and when the installation process starts and finishes. Progress logs also store error log entries.
- For a detailed list of progress and error log entries, see "Error Messages".
Viewing Software Distribution Progress in Event Logs
The error logs record errors encountered during the execution of each Agent. They enable you to check for problems during package installations.
For Windows NT, 2000, XP and 2003, the progress log entries are also displayed in the Client's Operating System Event Log, which can be viewed using the Event Viewer dialog:
- To display the Event Viewer in Windows NT, choose Programs, Administrative Tools, Event Viewer in the Windows Start menu.
- To display the Event Viewer in Windows 2000, XP and 2003, double-click the Windows Control Panel's Administrative Tools icon, then double-click the Event Viewer icon.
In the Event Viewer dialog, choose Select Computer, in the Log menu to display the Select Computer dialog, then enter the Client PC name whose Events you want to view.
![]() Vector Networks http://www.vector-networks.com Voice: +44 (0) 1827 67333 Fax: +44 (0) 1827 67068 info@vector-networks.co.uk |
![]() |
![]() |
![]() |
![]() |