TOC PREV NEXT INDEX

PCDuo Logo
Enterprise User Manual

Chapter 12

Software Distribution

The Software Distribution facility enables you to remotely distribute and update software packages to Clients and Servers on your organization's networks. Because it can be configured to install software with no user intervention, it can be used to keep your network up to date with a minimum of disruption, and, because it 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 resides on Client PCs.

Software Distribution Roadmap

The procedures required to install software with PC-Duo Enterprise's Software Distribution facility are:

The procedures are described in the rest of this chapter.

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:

Other packages may be configurable 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, it may be possible to install it using a separate tool to provide automated responses to the application's questions. We recommend the WinBatch product from Wilson Windowware for this role, but the development of such a script can be complex.

Preparing Kits for Packages that use InstallShield

You can perform a silent InstallShield installation by creating a response file to record the installation settings you want to use. Repeat this procedure for each different type of installation you want to perform.

To create an InstallShield Response file:
  1. Copy the software package to a location that is accessible to all PCs on which you want to install the software.
  2. On a PC that is typical 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
  3. Complete the installation with the responses you want to use to instal the package. The responses are recorded in a file called SETUP.ISS, which is saved in the PC's WINDOWS directory. This file can then be used to provide the installation responses when you install the software on the other PCs.
  4. When Setup has finished, copy the response file to the directory from which you started SETUP.EXE.
    Some applications, such as the PC-Duo Enterprise Client software, provide an example Response file, which can be edited and used for installations.

You can now configure a Package Definition to define 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:
  1. Run Setup from the CD using the administrative option. For example, to create an administrative kit, type: 
     h:\setup /A
  2. 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 deinstallation of Packages. The service, known as MSIEXEC, is included in Windows XP. 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 Windows Installer.

Using this method to install Windows Installer 2.0 can force the 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 with Windows Installer. 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 PC-Duo Enterprise by referring to examples from the Office 2000 Resource kit. 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.htm

If you already have the Office 2000 Resource Kit, you can update it with latest tools from: 

 http://www.microsoft.com/office/ork/2000/journ/NewORKTools.htm

Preparing 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:
  1. Create an Administrative Installation Point (see "Creating an Administrative Installation Point").
  2. Optionally, create a Transform, which customizes the installation of the application (see "Creating a Transform 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.

Because Installation Points need to be accessible for the duration of the software's use, ensure that you create Installation Points in a suitable location.

To create an Administrative Installation Point, install the package with the /a option. For example: 

 setup.exe /a data1.msi

You 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. This file is referenced in the next section.

Administrative Installation Points can use a large amount of disk space because they include all installable Features and Components of the software package.

Creating a Transform 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 only 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 option to create a new Transform.

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 now have the option of changing the Package's default installation folder, Organization name, and the Features and Components that will be installed on your Client PCs. Other configurable options include the ability to:

Having specified these Wizard settings, you are prompted to save them. On doing so, 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 PC-Duo Enterprise's 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 define how a and where software packages can be installed, and include the kit location, SETUP command syntax and other installation information.

PC-Duo 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 PC-Duo Enterprise Console, double-click on the Package Defn. Editor Operation.

Using the Package Definition Editor

All currently available Package Definitions are displayed in the Tree View on the left of the PDEdit window. The Packages are listed in alphabetical order.

To view the settings for a Package Definition, click on the plus symbol, then click on 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.

Creating Package Definitions

To create a Package Definition:
  1. In the PDEdit window, right-click in the Tree View to display the shortcut menu, and choose the Add Package Distribution Definition command.
    You can also create a new Definition using the Package, Add Package Distribution Definition menu command.
  2. 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.
  3. 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.
  4. Click on the plus symbol adjacent to the new definition, then click on 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 optionally enter a size for the file. If the file is found, but does not match the specified size, the installation will proceed.

To Specify the Summary Information:
  1. In the Tree View, expand the Package Definition you want to update, then click Summary. The Summary pane is displayed.
  2. 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.
  3. For each check path you want to specify:
    1. In the Check paths section, click the Add button.
    2. 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.
      You can use wildcard characters (* and ?) 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 also use environment variables in check paths, such as %TEMP% for the local PC's TEMP directory. For more information, see "Using Tokens in Package Distribution Definitions".
    3. If you want to check for a specific version of the file, enter the size of the file in the Value field.
    4. Click the OK button to save the check path and close the dialog.
  4. If you want to amend or remove any check paths, select the path in the list, then click the Edit or Delete buttons.
  5. 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, such as Windows Installer, also 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 installation.

For Package Definitions that use the Windows Installer, you can create multiple Install Types based on different Transforms. For more information, see "Creating a Transform using the Custom Installation Wizard".

PC-Duo Enterprise is supplied with default Install Types for most standard software packages. To display a Package's Install Types in the PDEdit window, expand that 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:
  1. In the Tree View of the Package Definition Editor, right-click on the Package you want to update and choose Add Install Type in the shortcut menu.
  2. In the Add New Install Type dialog, enter a Name for the Install Type and click the OK button.
  3. In the Tree View, click the new Install Type.
  4. Enter a Description for the Install Type.
  5. In the Platforms supported section, select all the operating systems on which you want to use this Install Type.
    When you use a Package Definition to install a package, only the platforms specified here are available for selection.
  6. 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. The path must be entered in the format: 
     \\machine\resource%username:password

    The 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 account details that can be used to access the installation kit.

  7. 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".
  8. Select the installation options you want to use:

    Privilege required Privileged installs are common amongst applications that support Windows NT, 2000 and XP. For non-Admin users, privileged installations can be performed using the Software Distribution Service.

    Package Definitions for Windows Installer installations 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 without mapping a drive letter when it runs SETUP or a software distribution command. Use this for installers that remember where they were installed from.

    You must select the UNC Path option when you install Windows Installer packages.

    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 PC user, such as asking them to enter their name, make sure this check box is selected.

    Applications that use the Microsoft Setup install method often ignore the Visible check box. Use a command option (in the Install command text box) of /Q1 to display the installation process, or /QT to hide it.

    Do not select Visible if you are using a batch file, because Client PC users can easily interrupt it. In privileged installs on Windows NT, 2000 or XP, the users can use this to gain access to a privileged command prompt.

    Reboot allowed Allows the installation to reboot without any prompting when the installation is performed.

    Reboot required If the installation requires a reboot, the Client user is prompted to reboot the PC if the installation does not reboot itself.

  1. If you want to perform a free space check, select a drive from the Free space drive list, then enter the minimum required amount in the Size (MB) field.
    Because many installations fail silently when there is insufficient free disk space, we recommend you always specify the space required for an installation.
  2. In the Start prompt field, type the text that you want the system to display on Client PCs before the installation starts.
    Additionally, if you are using an earlier (pre-2.0) version of Windows Installer, 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 on 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 PC-Duo Enterprise tokens in the command line fields specified in a Package Definition's Install Types and Pre-/Post-Processing areas. The following tokens can be used only with Software Distribution:

Token
Description
$ACCOUNT$
User account picked up from settings entered in the PC-Duo Enterprise Software Distribution Wizard, when the job is distributed, taking the format of username@domain:password, for example administrator@engineering:admin
$USERNAME$
User name part of the account, e.g. administrator
$DOMAIN$
Domain name part of the account, e.g. engineering
$PASSWORD$
Password part of the account, e.g. admin

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 must be executed before and after the installation is run.

To Specify Pre- and Post-Processing commands:
  1. To display a Package's Pre-/Post-Processing category, expand the Package in the PDEdit window's Tree View, then click Pre-/Post-Processing.
  2. 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.
  3. Select the Prefix Client install directory check box, if you want to reference files in the Client's installation directory without having to include the full path. For example, you can omit the path and specify: 
     CLOSEAPP TITLE="Readme.txt - Notepad"
  4. 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.
    Do not select Visible if you are using a batch file, because Client PC users can easily interrupt it. In privileged installs, users can use this to gain access to a privileged command prompt.
  5. When successful execution of the Pre-process command is required before an installation can take place, select the Error fatal check box in the Pre-process section. This causes the main installation to abort if the Pre-process command fails to execute.
    Because it is often difficult to distinguish an error from a command, this option must be used only with commands that exit with reliable status information. This option also traps executable files that are missing.
  6. 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 typically 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. Once the PC is rebooted, it is automatically logged on as the appropriate user, and the installation can complete unattended. The user is unable to use the machine during this phase of the install.

For the next reboot, LULOGON disables the automatic logon for the next reboot. It re-enables the keyboard and mouse, waits for the installation to complete, then triggers the second (final) reboot. LULOGON works around problems which can be caused by a premature reboot, by waiting for a specific application window to appear and disappear, and then waiting for a further configurable period of time. On completion of this phase, LULOGON triggers the reboot and returns normal control of the PC to the user.

Incorporating LULOGON in your Package Definition

The syntax for the LULOGON command is as follows: 

 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]

The LULOGON command options are described below:

/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. This command option should be used 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 disappears (assuming it is found).

/EXPLORER

Checks the Client PC Registry to see if Web browser updates are scheduled. If they are, the relevant Registry key is deleted at the first LULOGON pass and restored after the reboot. This prevents an installation being disturbed by automated Web browser update operations. This option is automatically generated, so you do not have to specify it as a command option.

/HELP

Displays a Help screen for the LULOGON command.

An example LULOGON command line would therefore be as follows: 

 LULOGON /INSTALL "$ACCOUNT$" /MESSAGE /LOCKOUT
You can include Enterprise tokens in your LULOGON command line. Tokens are particularly relevant for the /INSTALL option values.

All command options can be abbreviated to their first letter. Only one letter is checked.

Using LULOGON on Windows 95, 98 and Me

The LULOGON utility 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 typically 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, could occur for the following reasons:

Any of the above problems could cause your Windows Installer installation to fail on a Client PC. If the failure occurs during the keyboard and mouse lockout phase, there is no immediate, simple facility for recovery. However, you can use the following method to restore the PC.

The following procedure does not guarantee recovery in all situations and is provided for illustration only:

  1. On another PC, run the RegEdit utility.
  2. Use the Registry, Connect Network Registry menu command to open the input-locked PC's Registry.
  3. Locate the following Registry Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Kbdclass. Change the Start value to 1 to enable keyboard input.
  4. Locate the following Registry Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Mouclass. Change the Start value to 1 to enable it.
  5. Use the Registry, Disconnect Network Registry menu command to close the remote connection, then exit RegEdit.
  6. The locked PC must now be restarted using a remote shutdown utility, or by manually switching it off and on. On rebooting, the locked PC should be accessible and operational again.

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 on another Package after making changes to the current Package, a message box asks if you want to save the changes you have made.

Printing Package Definitions

To print a hard copy of the currently selected Package Definition, click the Print button in the toolbar or choose the File, Print menu command.

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 on the Package to display the shortcut menu, then choose Delete Package Distribution Definition.

Alternatively, you can use the Package, Delete Package Distribution Definition menu command.

Importing and Exporting Package Definitions

Package Definitions can be transferred between databases as .INI-style text files. These can be imported to and exported from PDEdit. You can import multiple Package Definition files simultaneously.

Any Package Definitions with names over forty characters long are truncated. (A warning message is displayed when this happens.)

To Import Package Definitions:
  1. In the PDEdit window, choose the File, Import menu command.
  2. When the Open dialog appears, navigate to the directory containing the PD files you want to import.
  3. Select the .PD files you want to import.
  4. Click the Open button to import the Package Definitions. The selected Package Definitions are imported into the PDEdit application.
To Export a Package Definition:
  1. In the PDEdit window, choose the File, Export menu command.
  2. When the Save As dialog appears, navigate to the directory in which you want to save the file.
  3. 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 Software Inventory Operation. This enables you to ensure consistency between package names and Package Distribution Definitions.

To Link a Package Definition to a PC-Duo Enterprise Package:
  1. In the Tree View, right-click on the Package Definition you want to link to and choose Link to Enterprise Package in the shortcut menu.
  2. In the Select Package dialog, locate the Enterprise Package in the list.
  3. Select the Use package name for distribution name check box if you want to rename the Package Definition with the Package name used by PC-Duo Enterprise.
  4. Click the OK button to save your changes and return to the PDEdit window. A linked icon is displayed alongside the Package Definition.
    To remove a link to a PC-Duo Enterprise Package, right-click on the Package Definition in the Tree View and choose the Unlink from Enterprise Package menu command. The linked icon alongside the Package Definition changes to an unlinked icon.

    To display the Link Details for a Package Definition, right-click on 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 PC-Duo Enterprise Console. When you have defined your Package Distribution Definitions and have prepared the install kits, you can use the Software Distribution Operation to place the Package Definition information in each Client's Offline Area.

You can perform a Software Distribution as an interactive operation, or submit it as a scheduled Job.

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

Like most other operations, Software Distribution is performed on the currently selected Group or Nodes in the Console window. This enables you to use the powerful Dynamic and Fixed Group features. For example, you can include or exclude Nodes based on department, domain, or operating system.

To Start the Software Distribution Wizard:
  1. In the Console window, select the Group or Nodes on which you want to install the software package.
  2. If you want to distribute the package interactively, double-click on the Software Distribution Operation.

    Alternatively, if you want to distribute the software using a Job Scheduler, right-click the Software Distribution Operation and choose Submit Job from the shortcut menu. When the message appears, click the OK button.

    The Software Distribution Wizard is displayed.

    If you are submitting a Software Distribution Job to a scheduler, the Submit Job dialog is displayed immediately after the Software Distribution Wizard. This enables you to change the Clients to which the software will be distributed, as well as specifying the Host and other Job Schedule settings.

Selecting a Package and Install Type

The first stage of the Software Distribution Wizard is to select the package you want to distribute to the selected Group or Nodes.

To Choose the Package you want to Distribute:
  1. Select the Package you want to install in the list at the top of the dialog. 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".
  2. Click the Next button to advance to the next stage of the Software Distribution Wizard.
  3. 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:
  1. 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.
  2. 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.
  3. Click Next to open the Settings dialog.
    Any changes you make to the Client Filter settings in the Wizard affect only the current operation. They do not affect the Package Definition specified in the Package Definition Editor.

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:
  1. 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.
  2. In the Expiry date field, enter the last date on which the system should attempt to distribute this software. The date must be entered in dd-mmm-yyyy format, such as 14-Feb-2002. If the system has not completed the distribution by this date, the operation is automatically cancelled by the system.
  3. 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 do not want to allow users to postpone the distribution, enter 0.
  4. By default, the system attempts to distribute the software to all the Clients at the first opportunity. If you want the system to stagger the installations over a number of days, select the Enable load control check box, and enter a Target completion date. The date must be entered in dd-mmm-yyyy format.
    When testing, leave the Enable load control check box unselected to allow the Agent to process the job on its next run.
  5. 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. For more information, see "To delete an Install Type".
    Always enter the Windows NT account information details if you are distributing software to any Windows NT, 2000 or XP Clients; these settings are ignored by other Clients.
  6. By default, the progress of the software installation is displayed on Client PCs as it is performed. Select the Silent check box if you want the installation to display only error messages, or select the Totally Silent check box to suppress error messages and make the installation completely invisible to the user.
  7. Click the Next button to open the Logging dialog.

Specifying Log File Locations

Use the Logging dialog to specify where you want to save the files that are used to log the progress of the Software Distribution Operation. All the locations must be specified as full UNC paths, and must include user name and password settings.

To Specify Log File Locations:
  1. 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.
  2. 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.
  3. Click the Finish button to complete the Software Distribution Wizard.
    To run Software Distribution Operations as scheduled jobs, right-click the operation and choosing Submit Job. The Submit Job dialog is displayed after completing the Software Distribution Wizard. This dialog enables you to assign a Host to schedule the distribution job. You can also drag-and-drop additional Clients to which the software will be distributed.

    After specifying the information and choosing the Submit button, you can view the Software Distribution job in the Jobs database.

Customizing the Software Distribution Operation

By customizing the Software Distribution 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 Software Distribution Operation:
  1. Right-click on the Software Distribution Operation and choose Customize from the shortcut menu.
  2. In the Customize Software Distribution dialog, select the Software Distribution tab.
  3. Enter the default values you want to use for each Software Distribution Operation, then click OK to save your settings and close the dialog. The settings are automatically used the next time you perform a Software Distribution Operation.
    To avoid repeatedly customizing and resetting an operation, create a new operation variant that includes your specific preferences.

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 can also be installed on older operating systems.

This section describes how to install Windows Installer 2.0 across your network using the Software Distribution 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 Windows 2000 (INSTMSIW.EXE) and Windows 95, 98 and Me (INSTMSIA.EXE) and from the Microsoft Web site at www.microsoft.com/downloads.

Windows NT 3.5.1, Windows 3, or Windows for Workgroups are not supported by Windows Installer 2.0.
To distribute Windows Installer version 2.0:
  1. Save the Windows Installer kits in a location that can be accessed across your network.
  2. In the Console's Operations View, select the nodes or group that you want to distribute the kit to, then select the Software Distribution tab and double-click the Software Distribution Operation.
  3. In the Select Package dialog, select Windows Installer 2.0 (MSI) in the package list and click Next to continue.
  4. 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 Next.
  5. In the Client Filter dialog, click Next to continue.
  6. In the Settings dialog, enter the Kit location, target dates and any account information necessary to access the target PCs, then click Next.
  7. In the Monitoring and Logging dialog, enter a Job name for the installation, then click Finish to start the installation.
    Do not schedule any Windows Installer installations until the kit has been installed on all target Clients.

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 and XP. 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 PC-Duo Enterprise 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 appropriate command line at the scheduled time.

Network Load Control

If a Target completion date was specified when the Software Distribution 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. 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 similarly logged.

The location of these log files are 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 that monitors 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 Distribution Job Viewer.

Distribution Jobs Viewer

To open the Distribution Jobs Viewer, double-click the Distribution Jobs Operation in the Console's Operations View.

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:

You can use the Distribution Job Viewer to perform the following tasks:

Configuring Distribution Monitoring

When PC-Duo Enterprise is first installed, it 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 open the dialog, choose Monitor Software Distribution in the Console's Site menu.

Software Distribution Monitoring Setting Dialog

Enabling and Disabling Distribution Monitoring

To disable monitoring of new Software Distribution jobs, clear the Enable software distribution monitoring check box. To re-enable distribution monitoring, reselect 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:

Logging Options

Software Distribution Monitoring includes a facility to record the activities of DISTMON.EXE, the program that is responsible for collecting and saving the installation feedback. You can use this logging facility to check on the activity of each Scheduler that is responsible for distribution monitoring, and to identify problems that occur during monitoring. Choose:

No logging

To record no logging data for all Schedulers.

Log errors

To record all errors encountered during the monitoring of Software Distribution jobs.

Log errors and additional information

to record all monitoring errors plus status reports, the nodes 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 the Distribution Job Viewer, you can monitor the progress of Software 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 is a single line which identifies the Node name and the event that is being logged. The progress logs record relatively fine detail as the Agent running on each Client PC processes each package. They record the PCs which have skipped a package due to filters or due to load control, and they also record when an installation is refused by the user and when the installation process starts and finishes. Progress logs also store error log entries.

Typically, Agents do not execute a job immediately after the Job is queued.

For a detailed list of progress and error log entries, see "Error Messages".

Viewing Software Distribution Progress in Event Logs

The error logs only record errors encountered during the execution of each Agent. The error logs serve as a location which you can check for problems during package installations.

For Windows NT, 2000 and XP, the progress log entries are also displayed in the Client's Operating System Event Log, which is viewed using the Event Viewer dialog:

In the Event Viewer dialog, use the Log, Select Computer menu command to display the Select Computer dialog, then enter the Client PC name whose Events you want to view.

Vector Logo
Vector Networks
http://www.vector-networks.com
Voice: +44 (0) 1827 67333
Fax: +44 (0) 1827 67068
info@vector-networks.co.uk
TOC PREV NEXT INDEX