This dialog controls and provides procedure inherited options for a job, for example, boot level settings, activation time, user access ability.
Displays the procedure inherited options:
Defines whether the target computer is to be rebooted prior to the job activation, and at what level this should be done. All the options available in this list are supported on the Windows, Linux, and MAC agents.
Levels: None, Restart machine, Logoff user
This option is set to None by default for all job linkage settings (batch job, synchronized or no linkage) on the Job container tab. Select one of the options from the drop-down list.
Note: The option Logoff user does not prevent the user to re-login before the job is executed.
Defines whether to restart the target computer after the job activation, and at what level this must be done. It also defines whether to shut down the target computer after completion of the last SD job. All the options available in this list are supported on the Windows, Linux, and MAC agents.
Levels: None, Restart machine, Logoff user, Restart machine after last job, Logoff user after last job, Shutdown machine after last job
This option is set to None by default for all job linkage settings (batch job, synchronized or no linkage) on the Job container tab. Select one of the options from the drop-down list.
Note: The Shutdown machine after last job option always takes precedence over the Restart machine after last job option. For example, consider a scenario where one job in a job container uses the Shutdown machine after last job option and another job uses the Restart machine after last job option. In this case, the Shutdown machine after last job option takes precedence over the Restart machine after last job option, and the target computer shuts down after completion of the last job.
Note regarding Boot level: The level selected here (booting job driven) should not be confused with the boot level concept used in the Software Management Installer: booting installer driven (if any active dll's, or other active system components, must be changed or deleted during the installation, the Installer introduces a restart, so that the appropriate components can be updated by the operating system during the restart).
Regarding the latter case, just note here that after the Software Management Installer has processed its jobs (installs, uninstalls, and updates), a system start (boot or logoff/logon) will be initiated once a respective boot level (0, 1, 2, 3 or 4) has been set, or when a system start is necessary because of locked files.
This check box defines whether questions should be asked of the users at the target computer(s) before and after the activation.
This option is not checked by default for all job linkage settings (batch job, synchronized or no linkage) on the Job container tab.
Before the job activation is started, the user is asked to confirm that it is to be started, to be run later, or not at all. If "Prompt user" is not checked, the job activation will always start.
After activation: At the conclusion of an item procedure activation, of a 16-bit Windows program in Windows NT/2000/XP environment only, users will be prompted to indicate if the item procedure completed successfully. If it did not complete successfully, the user can specify the reason for the interrupt. Then the installation register will list this installation as an error.
Check this box, if you want to use this feature. "Prompt user" must also be checked.
If Prompt user is selected, the check box for Execute if prompt times out is eligible.
If Execute is checked, the execution of the job, when the timeout elapses, could depend on the settings of the parameters “UserPrompt: Timeout Action” and “UserPrompt: Timeout action when user is logged off” in the common configuration. For example, if “UserPrompt: Timeout Action” is set to 0 on the target, the job will be cancelled at the target if the prompt times out.
If “UserPrompt: Timeout action when user is logged off” is not set on the target, the checking of this box determines the action. If the box is checked, the job will execute and if it not checked, the job will be postponed.
If Prompt user is not selected, the Execute check box is grayed out.
This check box defines whether the Job check program of the target computer should release communication with the server during execution of the job. When the job has finished, the agent reconnects to the server to report job status.
The reason for this check box is that when updating, for example, kernel drivers on a UNIX manager, a reboot is required. Since these kind of managers will be rebooted only occasionally, a mechanism is needed to schedule jobs for execution, while the system is going to shutdown.
This option is not checked by default for all job linkage settings (batch job, synchronized, or no linkage) on the Job container tab.
If this box is checked, the box Job will be triggered by server will automatically be grayed out, since these two options are mutually exclusive.
The box will be set by default, if the box Run at shutdown (UNIX only) is checked on the Options tab of Procedures.
If the UNIX agent lacks the shutdown functionality, the job will never run and hence time out.
The box should not be checked for jobs targeted at non-UNIX systems. In such a case, the job will never run but time out.
Jobs for execution on shutdown must not be combined with standard jobs within the same container, since this will postpone all jobs of the container.
This option (only supported for Windows NT/2000/XP agents) is to be selected, if a user is to be prevented from logging on, while the agent processes a job. When the user is already logged on, the Software Delivery agent will proceed with the scheduled job when the user has been logged off.
This option is not checked by default for all job linkage settings (batch job, synchronized, or no linkage) on the Job container tab.
In order for this function to be activated, it is necessary to execute the Enable per job procedure first, a Logon Shield function. It will prevent the user from disturbing applications that are currently updated or not completely installed. A message is presented during attempts to log in.
When the Logon Shield has been activated, a dialog will inform the user about the current state of the job. If the user hits CTRL+ALT+DEL, the dialogue will appear and continuously display the progress. It will disappear automatically after the job has ended. All progress messages can be configured.
Note: This option PREVENTS the user to re-login before the job is executed.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|