This item sets the job hold facility. For details about the job hold facility, see 2.13.1(2)(a) Using the job hold and cancellation facility in the Description and Planning Guide. During setup of client facilities for JP1/Software Distribution Manager or JP1/Software Distribution Client (relay system), this item is displayed but cannot be set.

Confirm jobs before execution

Select this check box to use the job hold facility. The default is that this check box is not selected.

The confirmation box stays for

If you will be using the job hold and cancellation facility, set the display duration for the Hold or Cancel Software Distribution Job dialog box. The dialog box displays the number of seconds remaining until execution.

If the user performs no operations on the dialog box within the specified display duration, when the remaining number of seconds reaches 0, the system executes the displayed operation and closes the dialog box.

Specify the value in the range from 0 to 1,800 seconds. The default is 180 seconds. If you specify 0, the dialog box remains displayed until the user performs an operation.

The administrator can specify for a job that the computer is to be shut down by client control after a job is executed. The administrator can also specify for a package that the computer is to be restarted automatically after a package has been installed.

This item specifies whether or not it is to be permitted for the computer to be shut down when shutdown after job execution is specified for the job and whether or not it is to be permitted for the computer to be restarted when restart after package installation is specified. It also specifies the settings for the confirmation dialog box when shutdown or restart is enabled.

Note that you cannot specify this item during setup of client facilities for JP1/Software Distribution Manager or JP1/Software Distribution Client (relay system).

If requested by the administrator, shut down or restart the computer

Specify whether or not it is to be permitted for the client to be shut down or restarted on the basis of an instruction when the administrator specifies shutdown after job execution or restart after package installation. The default is that this check box is selected.

If the administrator uses the client control facility to start the PC to execute jobs when it is unattended, you should select this check box so that the PC can be shut down by an instruction. For a PC that is always running, you do not need to select this check box.

If you want to have the computer restarted automatically after package installation on the basis of an instruction from the administrator, select this check box.

Note that if you select If requested by the administrator, shut down or restart the computer check box, a confirmation dialog box is displayed before shutdown or restart takes place.

The confirmation box stays for

If you select this option, specify how long the confirmation dialog box is to be displayed before shutdown or restart takes place. When the dialog box has been displayed at the client for the specified amount of time, shutdown or restarts begins. Specify the value in the range from 1 to 60 minutes. The default is 3 minutes. If you specify Unlimited, shutdown or restart does not begin until the user makes an entry. If a job is executed from the Package Setup Manager of the client, shutdown or restart does not begin until the user makes an entry even though the specified display time elapses.

For details about shutting down the computer by the client control facility, see 6.3.3 Notes on shutdown in the Description and Planning Guide. For details about automatic restart of the computer, see 2.2.8 Options page in the manual Administrator's Guide Volume 1.

Specify whether or not the client is to report to the higher system information such as the available disk space in the local system (which changes whenever an installation is executed) together with the installation results. When automatic inventory updating is enabled, the communication volume increases by about 500 bytes for each installation instruction. The default is that this check box is not selected.

Among the Get system information from client jobs, Get software information from client jobs, and Transfer user inventory schema to client jobs, jobs that are specified to execute at a client periodically (for example, daily, weekly, or monthly) are referred to as periodic jobs.

A periodic job reports periodically the execution results to the connection destination where the job was executed. Therefore, even if a client cannot communicate with the destination (for example, because the client was moved), the job will still try to report the execution results. In such a case, to stop unnecessary communications, select this check box to suppress execution of periodic jobs when the connection destination of the client has changed.

The default is that this check box is selected.

The following table shows the periodic jobs that are executed without being suppressed even though you select this check box:

Product type and setting conditions			Periodic jobs that are not suppressed
Client	Polling of multiple higher systems	No	Jobs at the connection destination after the client is changed
		Yes	Jobs at the connection destination after the client is changed and that have multiple higher systems
Relay system			Jobs at the connection destination after the client is changed and that belong to the relay system itself
Relay manager			Jobs at the connection destination after the client is changed and that belong to the relay manager itself

You should note the following about using this option:

When you want to execute the same job even when the client connection destination is changed

When Suppress periodic jobs when the connection destination of the client is changed is selected, periodic jobs cannot be executed at the previous connection destination if you change the destination. If you want to execute the same periodic jobs at the new connection destination, do either of the following:

When you use ID group jobs (you change the destination within the same network by using the same ID group):

• When Linkage when system configuration is changed is selected
  The same periodic jobs are executed because the system connects to the ID group even if you change the connection destination of the client.
  
• When Linkage when system configuration is changed is not selected
  After you change the connection destination on the client, register the jobs in the ID group.
  

When you use host groups:

At the new connection destination system, delete or execute periodic jobs periodically.

Using the client on an offline machine

With an offline machine, if you wish to suppress periodic jobs from a system that is not at the connection destination, and execute periodic jobs that are from the connection destination, set the host name and IP address of the connection destination in the hosts file so that the address can be resolved. If the address cannot be resolved, periodic jobs from the connection destination are also suppressed.

If you wish to execute periodic jobs from the connection destination even when the address cannot be resolved, select the check box. In this case, periodic jobs from a system that is not at the connection destination can no longer be suppressed.

When uncompleted jobs are generated

Depending on the timing for suppressing periodic jobs, periodic jobs may be suppressed without being executed at all. In such a case, the execution status of jobs on the managing server stays at 70% and their execution is not completed.

When a job is distributed to a client, the higher system may be notified that the job is in the Waiting for installing/collecting status. After this notification, the execution status of this job in the Job Status window of the higher system is placed in the Waiting for installing/collecting status. Normally, after a job is distributed, it takes some time before completion (or failure) of installation or collection is reported to the higher system. Therefore, the contents of the Job Status window change each time the report is made.

However, the higher system may receive the job results (completion or failure) report immediately after receiving the Waiting for installing/collecting status report. If you select this check box for such cases, the Waiting for installing/collecting report is suppressed. Every time this report is suppressed, 170 bytes (340 bytes for an ID group job) of network traffic is eliminated. Also, the load on the higher system for updating the job execution status is reduced. In the initial settings, this check box is not selected.

You can suppress the Waiting for installing/collecting status report for the following jobs:

• Install package job
• Collect files from client job
• Collect files from client to relay system job
• Get system information from client job
• Get software information from client job
• Get user inventory information job

When any of these jobs is executed with the following settings specified, and all the conditions for suppression are satisfied, the Waiting for installing/collecting status report is suppressed. The conditions for suppression depend on the combination of the job settings.

Job settings			Conditions for suppression
Installation date/time	Install when system starts	GUI installation mode
Y#1	N	N	The specified date/time has been reached when the job distribution is completed.
N	Y	N	At the client, The first polling is executed: Before the client starts is set. The job was distributed at the first polling.
Y	Y	N	At the client, The first polling is executed: Before the client starts is set. The job was distributed at the first polling. The specified date/time has been reached when the job distribution is completed.
N	N	Y#2	The client has logged on when the job distribution is completed.
Y	N	Y#2	The specified date/time has been reached when the job distribution is completed. The client has logged on when the job distribution is completed.
N	Y	Y#2	At the client, The first polling is executed: Before the client starts is set. The job was distributed at the first polling. The client has logged on when the job distribution is completed.
Y	Y	Y#2	At the client, The first polling is executed: Before the client starts is set. The job was distributed at the first polling. The specified date/time has been reached when the job distribution is completed. The client has logged on when the job distribution is completed.

Legend:

Y: Specified. N: Not specified

#1

Suppression is not performed for Collect files from client jobs and Collect files from client to relay system jobs.

#2

Suppression is performed for Install package jobs only.

Software information about Hitachi program products is reported to the higher system as installed packages under the type Hitachi program products. Therefore, when a Get software information from client job is received in which the option Search software listed in "Add/Remove Programs" is specified, information about the Hitachi program products will not be reported.

When this check box is selected, information about Hitachi program products that have been registered in Add/Remove Programs on the Control Panel is reported as installed packages in Add/Remove Programs. As a result, software information including Hitachi program products that have been registered in Add/Remove Programs can be acquired in the batch mode. The default is that this check box is not selected.

If you select this check box, you should not execute the operations listed below. If they are executed, information about Hitachi program products will also be reported as Hitachi program products, resulting in a duplication of software information that is managed in the higher system.

• Acquiring software information with Search all software specified from the managing server
• Choosing Collect Software Information and Update from Package Setup Manager's Execute menu at the client

If JP1/Asset Information Manager is linked, and installed package information is duplicated, information may no longer be managed correctly by JP1/Asset Information Manager.

Package IDs may be repeated for the following software information, preventing accurate collection of information.

• Software listed under Add or Remove Programs or Add/Remove Programs in the Windows Control Panel.
• Patches applied to the computer
• Patches not applied to the computer

The programs for which software information cannot be accurately collected are generally updates after Microsoft Office 2007.

When this check box is selected, software information can be collected accurately for these programs.

When clients for which the Do not repeat package IDs when collecting software information check box is selected are mixed with clients for which it is not selected, note the following:

When clients on which the check box is selected are mixed with clients on which it is not selected

• Different package IDs may be set for the same software. For that reason, software cannot always be reliably identified by the package ID.

Also, when the Do not repeat package IDs when collecting software information check box is selected and Asset Information Manager Subset or JP1/Asset Information Manager is set in Server Setup to acquire package IDs, note the following:

Sharing between Asset Information Manager Subset and JP1/Asset Information Manager

• When a package ID is updated, first the software information for the previous package ID is deleted, then the software information for the updated package ID is added. Therefore, it may take some time to collect software information.
• In the update history for installed software, this appears as deleting the software information for the previous package ID and adding the software information of the updated package ID.
• Note that you can delete update histories of this type.
  For information about deleting update histories with Asset Information Manager Subset, see 10.7.3 Specifying the types of history information to be deleted and the deletion timing. For information about deleting update histories with JP1/Asset Information Manager, see the manual JP1/Asset Information Manager Administrator's Guide.
  

Note on JP1/Asset Information Manager

• If the installed software name is used to automatically registered software names, software names may be repeated. If this happens, unify the software names. For details, see the manual JP1/Asset Information Manager Administrator's Guide.