Agent Policy Group (Software Delivery)
The Agent policy group lets you set the following policies for the Software Delivery agent. You can modify policy parameter values by double-clicking a policy to display the Setting Properties dialog.
Indicates whether the job check icon is displayed. If True, the job check icon is not displayed. If False, the job check icon is displayed.
Note: If the administrator of the manager to which the Software Catalog is connected has a large number of catalog clients and finds an overuse of the job check feature, this policy should be set to True for better control of the number of connections initiated by end users.
Default: False
Defines the number of connection attempts an agent will make to the scalability server. The operating system type of the agent determines the parameter entry to be used.
Default: 3
Defines the number of connection retries an agent will make to the scalability server. The operating system type of the agent determines the parameter entry to be used.
Default: 3
Defines the number of connection retries an agent will make to the scalability server. The operating system type of the agent determines the parameter entry to be used.
Default: 3
Determines the maximum length of time in seconds an agent will attempt to contact its scalability server. This setting is used together with the Communication: Maximum number of retries (UNIX) and Communication: Maximum number of retries (Windows) policies.
Default: 1800
If True, the agent does not add quotation marks around macros that are expanded. This policy affects the $ip, $in, $iv, $msi, $pf, $pn, $pp, $rf, and $sl macros.
Note: For more information about SD macros, see the Software Delivery CLI Reference Guide.
Default: False
If True, the agent does not close its window when the X button in the upper-right corner is clicked.
Default: False
Controls whether the Software Job Check dialog is displayed in the context of the CAF Windows Service or whether a second instance of the Software Job Check dialog is started in the context of the logged-on user to display a separated user interface. The separated user interface is identical in appearance to the in-process user interface.
Valid values are as follows:
Disables the separated user interface.
Enables the separated user interface for Windows Vista and later versions of Microsoft operating systems.
Note: This policy applies only to Windows Vista and later versions of Microsoft operating systems.
Enables the separated user interface for operating systems released prior to Windows Vista. Windows Vista behavior would remain the same.
Note: This policy applies only to operating systems prior to Windows Vista.
Default: Display GUI for logged-on user on Vista/Longhorn
Specifies the number of minutes a job can be executing on a target computer. If the timer elapses, the job status is listed as "Error due to job timeout" on the manager.
Note: This policy applies only to Microsoft Windows agents.
Limits: 30–600
Default: 360
Controls which output files are uploaded to the manager. Valid values are as follows:
Output files are always uploaded to the manager.
Only output files for failed jobs are uploaded.
No output files are uploaded.
Default: 0
With the Job Check: Pre-command policy, controls pre- and post-job check processing, which makes it possible to run external executables before and after the actual software delivery jobs are processed. The Job Check: Post-command policy specifies an executable that will run after software delivery jobs or after the last software delivery job in a batch.
Default: empty
With the Job Check: Post-command policy, controls pre- and post-job check processing, which makes it possible to run external executables before and after the actual software delivery jobs are processed. The Job Check: Pre-command policy specifies an executable that will run before software delivery jobs or before the first software delivery job in a batch. An example is switching off an antivirus realtime monitor for the duration of a job container.
Default: empty
Controls the visibility of the agent dialog. If True, the agent UI is not visible unless a prompt needs to be displayed. If set to False, the agent UI is visible unless the flag /BG is specified on the command line or the macro $#BG is set for the job.
Default: False
Controls the uploading of software detection records. If set to 0, software detection records for DSM software are uploaded to the manager every time the job check is run. Any other setting activates the delta mode, causing only changes to be sent except, for every nth job check where the whole list of installed DSM software will be sent.
Default: 10
Controls the behavior of MSI job execution when no user is logged on to the computer. If set to False, MSI jobs are always executed. If True, MSI jobs will be postponed if no user is logged on.
Note: This policy applies only to Windows 95/98/Me agents.
Default: True
Controls whether MSI system components should be detected or not. System components are not displayed in the Windows Add/Remove Programs applet.
Default: True
Controls the updating of the MSI source list when agents change scalability servers. Valid values are as follows:
Do not update the MSI source list for a product.
Add a new source to the list.
Clear the source list and add the new source to the list.
Note: This policy applies only to Microsoft Windows agents.
Default: 1
Specifies what information the agent should use when updating the MSI source list in the agent's registry. If False, CA ITCM compares the package name and version against SDName and SDVersion stored in msilib.dct on the server. If True, CA ITCM compares it against productName and Version instead.
Default: <locally managed>
Indicates whether the internal NOS-less delivery fallback is enabled. If set to True, the delivery automatically changes from NOS to NOS-less, which can cause large jobs to fail if the agent has insufficient disk space.
Default: True
Indicates whether the agent prohibits logging off and rebooting while a job is active. If True, the agent allows logging off and rebooting during job execution. If False, the agent prohibits logging off and rebooting while a job is active.
Default: False
If True, the reboot routine forces programs to shut down. This policy is used by the logoff and reboot routines.
Default: False
Controls what happens when a user or application has attempted to both log off and reboot while a job is running. If True, a logoff is initiated after the job has completed. If False, a reboot is initiated.
Default: False
Specifies the number of times the reboot prompt can be postponed.
Default: 10
This policy is used by the logoff and reboot routines. If set to True, a requested logoff or shutdown is not initiated automatically. Instead, a message is displayed prompting the user to save all work. The message does not have a timer and can be closed only by the user. By closing the message, the shutdown is initiated.
Default: False
Specifies the timeout period in seconds for the reboot dialog. If empty (not set), the initial timeout is 30 minutes and every consecutive postponement is 5 minutes in duration. If set, both the initial timeout and the consecutive postponements use the specified value.
Default: 1800
Controls non-scheduled software scans. If set to ON, the asset management agent starts a non-scheduled software signature scan in order to update detected software records in the MDB. The scan runs after the execution of the last software job known to the agent.
Default: OFF
Specifies the letter to be used when mapping a drive for MS NOS agents.
Default: empty
Indicates whether a drive for MS NOS agents should be mapped to either the scalability server's share or a UNC path. By default, a drive is mapped (True). However, on certain platforms drive mapping may fail, requiring UNC paths to be used. (See the readme file for more information.)
Default: True
If True, each job set up in a batch container with prompt user enabled causes a prompt. If False, a batch container only causes one prompt and that occurs before the first job is executed.
Default: False
Specifies the number of minutes to wait for a user to make a selection in the Job Check dialog preceding a job execution. This policy is relevant if the Prompt user option was selected when defining the job order. If the timer elapses, a new attempt to start the job is initiated by the scalability server; that is, the timer elapse has the same effect as the user's clicking the Later button in the Job Check dialog.
Note: This policy applies only to Microsoft Windows agents.
Limits: 1–60
Default: 5
Controls what happens if the User Prompt: Timeout policy times out. Valid values are as follows:
The default action is 1 (or 2 if the Execute if prompt times out option is set in the Job Setup dialog).
Cancels the job.
Postpones the job.
Runs the job.
Note: This policy applies only to Microsoft Windows agents.
Default: -1
Controls what happens if the User Prompt: Timeout policy times out and no user is logged on to the computer. Valid values are as follows:
The default action is taken from the User Prompt: Timeout action policy.
Cancels the job.
Postpones the job.
Runs the job.
Note: This policy applies only to Microsoft Windows agents.
Default: -1
|
Copyright © 2013 CA.
All rights reserved.
|
|