Use this page to specify options for remote installation.

Figure 2-19 Options page

Compress package data

Specify whether or not the software package is to be compressed. A compressed package is decompressed automatically during remote installation. The default is that this option is not selected.

Compressing a package increases the transfer speed and reduces the cabinet space needed for storing the package. However, compression and decompression require more time for packaging and remote installation.

When you opt to compress package data, you can also select between Higher level compression and Old-version-compatible compression. The default is Higher level compression.

Higher level compression

Compresses the package more efficiently than is the case with the old-version-compatible compression method.

Use this method when you distribute a package to a version 05-23 or later client. Version 05-22 or earlier clients and UNIX clients do not support packages compressed using this method.

Old-version-compatible compression

Compresses a file using the old-version-compatible compression method. The compressed data can also be distributed to a UNIX client or a version 05-22 or earlier client.

The following table compares the compression rates of high-level compression and old-version-compatible compression. Although the actual compression rate depends on the package data, the values shown here can be used as guidelines. These values indicate the compressed data size as a percentage of the uncompressed data size (100%).

Compression method	100 MB of text data	145 MB of program data (Microsoft Office 95)
Higher level compression	Approx. 1%	Approx. 47%
Old-version-compatible compression	Approx. 45%	Approx. 71%

You should note the following about using the higher-level compression method:

• You can use a version 05-22 or earlier managing server or a UNIX managing server to create a package and then distribute it. However, you cannot check the contents of the package with these managing servers. If you attempt to do so, Remote Installation Manager terminates for Windows, and operation cannot be guaranteed for UNIX.
• You can distribute a package via a version 05-22 or earlier relay system.

Restore old version when upgrade failed

This item is available only when the package type is User programs and data. When you select this option, a backup copy of the previous version is created at the remote installation target during software-version upgrading. In the event of a remote installation error, the previous version of the software is restored from the backup copy. The default is that this option is not selected.

If external programs are specified, the backup is created after startup of the external program that is set to start immediately before package installation. Restoration is executed after startup of the external program that is set to start when an installation error occurs.

A backup retention period is set in software that is packaged from the UNIX version of Packager. Even when remote installation fails and restoration also fails, the backup copy of the previous version is saved for a specified period, so the restoration process can be tried again from the client. For details about how to check the backup file and re-execute a restoration process, see 11.10 Managing backup files.

This item is equivalent to Restoring the previous version when installation fails in the Change Installation Conditions dialog box.

Restart computer after installation

Use this option to specify whether or not you wish to restart the client computer after package installation. The default is that this item is not selected. When this item is selected, a restart confirmation dialog box is displayed at the client once installation is completed. After a predetermined amount of time elapses, the computer is restarted. The duration for displaying the confirmation dialog box is set in the Job Options page during setup on the client.

If Unlimited is specified for the confirmation dialog box's display time, the computer will not be restarted until a user responds.

Only clients can be restarted automatically. Even if a package specifying restart is installed, neither a relay manager nor a relay system will be restarted. In order for such a computer to be restarted automatically, If requested by the administrator, shut down or restart the computer must have been selected during client setup on the Job Options page.

You should note the following about restarting the computer:

• If you are remotely installing JP1/Software Distribution Client, do not specify Restart computer after installation. Otherwise, remote installation may not terminate normally.
• Automatic restart of a Windows NT client may not work in some cases. This may be because the hardware or Windows environment does not support automatic restart. In this case, make sure the hardware does support automatic restart. Also, execute the latest updating program provided by the hardware supplier to establish compatibility between the hardware specification and Windows. If the problem persists even though the hardware supports automatic restart and the updating program has been executed, refer to the information provided by the hardware supplier and Microsoft Corporation.
• If restart is specified in multiple packages which are being installed, the computer will be restarted only after all packages have been installed.
• If a client-controlled computer shutdown is specified in a job for distributing a package that specifies a restart, the computer will be shut down after the job is finished.
• If multiple jobs execute consecutively on the client, including a job for distributing a package that specifies a restart or a job that specifies a client-controlled computer shutdown, the computer will be shut down after all the jobs have finished.
• If a package that specifies a restart is installed from the client's package setup manager, Unlimited will be assumed even if a display time is specified in the confirmation dialog box during client setup, and the computer will not be restarted until it receives a user input.
• UNIX clients of version 07-00 or earlier or Windows clients of version 06-71 or earlier cannot be restarted automatically.
• If a screen saver starts in a Windows NT client and password protection is in force, the computer cannot be restarted automatically.
• If a file is being edited during installation of a package that specifies restart, the computer will not be restarted automatically.

When a package that specifies restart is installed from a remote higher system, the computer will not respond in accordance with what you specified if the logon status is one of the following:

• No one has logged on.
• The logon was as a user who has Administrator permissions, and not as the user who installed the Software Distribution Client.
• The logon was as a general user and Run the client with non-Administrator user permissions was not selected in the setup.

In these statuses, the computer will be restarted without the confirmation dialog box being displayed, even if a display time was specified for the confirmation dialog box in the client's setup. If Unlimited is specified for the display time, the computer will not be restarted.

The foregoing (remote installation of a package from a higher system) applies to all cases except installation of a package using Package Setup Manager or the Execute Job Backlog icon from the client side.

Display processing message

Use this option to specify whether or not the processing message is to be displayed at the client during package installation. Appropriate messages can be displayed during downloading and installation. You can select from the following options:

According to the client settings

Whether or not to show or hide the processing message during downloading and installation is to be determined on the basis of what was specified on the Processing message page of the Client Setup. Whether or not the processing message displayed is to be the standard message or a message created from a user program is also to be determined on the basis of what was specified on the Processing message page.

Show

Display a downloading message or installation message regardless of the setting on the Processing message page.

Whether or not the standard message or a user-created message is to be displayed as the processing message is to be determined on the basis of the specification (or lack of specification) on the Processing message page in the client's setup.

Hide

Hides the downloading message or installation message regardless of the setting on the Processing message page.

The following table shows whether a processing message is displayed depending on the settings in Display processing message in the package and the specification on the Processing message page in the client's setup:

Setting for Processing message page in client setup	Setting in the package
	According to the client settings	Show	Hide
Show	Y	Y	N
Hide	N	Y	N

Legend:

Y: Message is displayed.

N: Message is not displayed.

You should note the following about displaying the processing message:

• When Show is specified in the package for a Windows client of version 06-71 or earlier, it is ignored.
• When Show is specified in the package, whether or not the message indicating the installation progress is shown on top of all other windows will depend on the specification (including lack of specification) in the client setup.

Message displayed at the target client before starting installation

Use one of the following methods to enter the message to be included with the package:

• Enter a message in the Message text field.
  You can enter a maximum of 30,000 characters.
  
• Specify a message to be included with the package. You can enter the message directly into the Message text field or load a text file by choosing Copy from File. The maximum message size is 30,000 characters.
  The maximum file size is 30,000 bytes.
  

This message is valid for distributing a package using a Send package, allow client to choose job. The specified message can be viewed when a package is selected for installation with the Package Setup Manager from the client. You should provide in the message any information that is important for the client before installation, such as an explanation of the package's contents and the installation method. If the package type is Differing-components package, providing information about the previous version is recommended.