7.3.5 Notes on performing remote installation

(1) Notes on split distribution

Notes on split distribution are shown below.

When executing multiple jobs specifying split distribution

Even if you execute multiple jobs specifying split distribution at the same time, the packages for each job are not simultaneously transferred between the transfer source and the transfer destination. Each job is executed sequentially one at a time. This means that any jobs other than the job that is currently transferring packages are in a package download waiting state (job running rate: 20%).

Notes on specifying destinations

• If you execute the Install package job specifying split distribution on a relay system, in system configuration, you must specify the destination as the icon of a managed computer under the relay system. (If you specify the destination as the icon of the relay system, normal distribution is performed instead of split distribution.)

• For the Install package job destined for a relay system, you must specify the destination as the icon of a managed computer under the relay system in the system configuration. (In this case, split distribution is not performed between the relay system and the managed computer.)

• If you execute multiple jobs specifying split distribution at the same time, normally, these jobs are executed sequentially on each transfer source node and transfer destination node. However, if jobs for which destinations are specified manually during job registration coexist with jobs for which destinations are specified according to the system configuration or destination information, multiple jobs might transfer packages in parallel.

Circumstances under which package installation sequence cannot be guaranteed

If multiple packages are specified for the Install package job, these packages are installed on the distribution destination system in the following priority order: cabinet ID, package ID, version, and generation number of the package specified for the job. Note, however, that jobs specifying split distribution might be unable to guarantee proper installation sequence under the following circumstance:

• When a job specifying split distribution is forcibly terminated during execution

Download progress display during split distribution

If the package size of split distribution is too small, the download progress dialog box on the managed computer might indicate 0%. If you perform split distribution jobs successively, the download progress dialog box on the managed computer might indicate 0% for jobs awaiting split distribution.

Forcibly enabling the split distribution settings specified during job registration

If you set the package split distribution settings in the agent settings to the default values, you can forcibly transfer packages to the distribution destination system by using the split distribution settings specified during job registration. The default values in the agent settings are as follows:

• Split package and then distribute check box: Selected

• Split size: 2,097,151 kilobytes

• Distribution interval: 1 hour

Relationship between package split distribution and Client Control

If you execute the Install package job with both package split distribution and Client Control specified, the system behaves as below.

If you select Start the target computer if it is not running and Shut down the client after the job execution:

1. The computer turns on.

2. The first split package is transferred.

3. The computer turns off.

4. Steps 1, 2, and 3 are repeated.

If you select Start the target computer if it is not running:

1. The computer turns on.

2. The first split package is transferred.

3. Package transfer continues, and the computer remains on.

Notes on JP1/IT Desktop Management 2 - Agent (relay system)

The split size and distribution interval specified during job creation are compared with the specified values in the agent settings on the subordinate system, and split distribution is performed by using the smaller values. However, the split size and distribution interval (displayed by selecting Display Job Detailed Information from the View menu of the Job Status window) might be displayed as the values specified during job creation, depending on the timing of display. This behavior is normal and does not indicate any operational problems.

To Page Top

(2) Notes on suspending and restarting jobs

When suspending and restarting jobs, note the following:

• If you select Suspend/Resume File Transfer and then Resume from the Execute menu of the Remote Installation Manager (to instruct the manager itself to restart transferring files), the execution status display might change. For example, if a suspended distribution job from the Packager enters a running state, the execution status display changes back to a lower running rate (for example, from 50% to 20%).

To Page Top

(3) Notes on distribution during job suspension

It is not effective if you execute a job with the Distribute option selected in an environment where job suspension functions are not used. Because a job with the Distribute option selected behaves in the same way as a job with the Distribute option unselected, the distribution order does not change.

To Page Top