Job Management Partner 1/Software Distribution Administrator's Guide Volume 1
This section explains the preparations necessary at the client for when the software installation time is specified as Install when system starts.
When a job is executed from the managing server, the client executes the required processing on the basis of instructions provided by the managing server. However, sometimes instructions from the higher system do not arrive, because of a communications error or a failure of the client PC to start properly. For such cases, the client uses a process called polling to connect to the higher system and check to see whether jobs addressed to the client system have arrived.
Whether or not polling is to be conducted and, if so, the interval at which polling is to be conducted, are specified on the Default Running Status/Polling page.
Figure 11-4 Default Running Status/Polling page
If jobs will be received with the Install when system starts option specified, you should select the Client will poll the managing server check box and the Start polling when the client program starts check box.
The timing of software installation on the client can vary as follows, depending on whether The first polling is executed is specified as Before the client starts or After the client starts.
For example, the following figure shows three installation timings that can occur when a job, scheduled for installation at 05/21/03 05:00 is executed at 01:00 on 05/21/03.
Figure 11-5 Differences in installation timing due to polling settings
Specifying Before the client starts offers the benefit of completing the installation process all at once at one system startup. However, if programs are registered in the Software Distribution Client Setup folder, these programs will not be started until after packages downloaded through polling have been installed, resulting in an installation delay of dozens of seconds. To speed up the startup of programs that are registered in the Software Distribution Client Setup folder, specify After the client starts. In this case, these programs are started without waiting for polling. For details about how to register programs into the Software Distribution Client Setup folder, see (2) Moving startup programs below.
Programs that are registered in the Startup group of the Start menu start automatically when Windows starts. However, because the time at which Install when system starts jobs execute is virtually the same as the time at which Windows starts, an attempt to remotely install programs while startup programs are being started causes the installation process to fail. To prevent such failures when there are programs registered in the Startup group, you can create a Software Distribution Client Setup folder at each client and move the startup programs into this folder. Then, the client will manage the programs registered in the Software Distribution Client Setup folder so that they do not start until after system startup installation processing is completed. As a result, the timing for automatic program startup does not overlap remote installation timing.
The default is that a Software Distribution Client Setup folder is not created. You can create it by taking one of the following actions:
You can move the Software Distribution Client Setup folder to the Startup group either automatically or manually. These methods are explained below.
You can automatically move the shortcuts for programs in the Startup group to the Software Distribution Client Startup group according to setup specifications. To specify the automatic move option, select the check box Move programs in the Startup group to the Software Distribution Client Startup group on the Startup page.
In addition, you can specify for each program individually whether or not it is to be moved to the Software Distribution Client Startup group. To do this, select the check box Move programs in the Startup group to the Software Distribution Client Startup group, and choose the Browse button.
To move a program, you must first select the check box that is located above the list of programs in the Select the shortcuts to move menu. If this check box is not selected, programs cannot be moved to the Software Distribution Client Startup group.
Figure 11-6 Startup page
If customization of the Startup icon move option results in a program being excluded from the list of programs to be moved and as a result it is left in the Startup group, installation during system startup may fail.
If the Create Software Distribution Client Startup folder check box is selected but the check box Move programs in the Startup group to the Software Distribution Client Startup folder is not selected on the Startup page during setup, the startup programs will not be moved automatically. In such a case, you can use a manual procedure to move to the Software Distribution Client Startup folder the shortcuts for the programs registered in the Startup group. In addition, when you register new startup programs, you must register them into the Software Distribution Client Startup folder.
If you exclude shortcuts in the Windows Startup group from the list of shortcuts to be moved, installation of the programs that use those shortcuts may fail during system startup. Therefore, it is best theoretically if all shortcuts are included in the shortcuts to be moved. However, moving some programs' shortcuts to the Software Distribution Client Startup folder can produce problems with version-upgrade installations or uninstallations. For example, for the Microsoft Office shortcut bar, uninstallation of the program is likely to fail if the associated shortcut is moved to the Software Distribution Client Startup folder. For this program, the associated shortcut should not be moved to the Software Distribution Client Startup folder.
In the case of a version-upgrade installation for a program whose shortcut has been excluded from being moved, you must shut down the program so that the installation processing can be executed while the system is active.
All Rights Reserved. Copyright (C) 2009, 2013, Hitachi, Ltd.
Copyright, patent, trademark, and other intellectual property rights related to the "TMEng.dll" file are owned exclusively by Trend Micro Incorporated.