Application Control Agent Package Page
This page lets you create a package used by Application Control Agent installation policies as needed when performing an agent rollout or uninstallation. Generally, we recommend not changing any settings to this package.
...
This tab is used to specify Package Servers associated with a package.Page Items
...
Description |
Package Destination Location on Package Servers | Enter the desired package destination location on the Package Servers if you do not want the default. The default package delivery location on Package Servers is install path\altiris\Application Control agent\package delivery{package guid}\cache). |
Assign package to | Select the destination Package Server from one of the following: |
...
- All Package Servers - Assign the package to all Package
|
...
...
- Package Servers Individually - Assign the package to selected Package Servers.
|
...
- Package Servers by site - Manually assign sites to packages from a list of sites configured in the Site Maintenance page. When a site is assigned to a package, all Package Servers within the selected site will host the package.
|
...
- Package Servers automatically with manual prestaging - Sites are automatically assigned to packages according to the clients and Package Servers requirement for that package.
Example: An administrator creates a task, associates it with a package assigned to Package Servers automatically with manual prestaging, and also assigns a collection to the task. Now, all members of this collection require the package and need to download it. The next time Package Refresh runs, or the Update Distribution Points button is clicked, the package is assigned to sites according to the collection members. So, if ClientA is a member of the collection assigned to the task, and ClientA is a member of SiteA, then SiteA will get assigned to the package. When SiteA is assigned to the package all Package Servers in SiteA will host the package. So, when ClientA needs to download the package, all the Package Servers within its own site will have already downloaded and prepared the package, or be in the process of doing it. This option also lets you manually assign packages to sites as desired. So, if a site has not been automatically assigned to the package, the user can potentially assign it to a number of other sites manually.
|
Apply | Click to save changes. |
...
...
Click to discard changes. |
Update Distribution |
...
Points | Click to update this package information as soon as possible on all enabled Package Servers. |
Advanced tab
This tab is used to specify advanced settings with a package.Page Items
...
Agent display description
...
Description |
---|
Agent display name | The name of the package that will be displayed on the Application Control Agent. This can be different than the package name you specified on the Package tab. |
...
The purpose of this field is to supply package names to the end user that makes sense to users and to have package names that make sense to you on an administrative level.
|
Agent display description | The description of the package that will be displayed on the Application Control Agent. This can be different than the package description you specified on the Package tab. We recommend you enter a description here that will let the end user know what the package will do to the managed computer. |
Enable Verbose Reporting of Package Status Events. | Controls whether the Application Control Agent sends package status events for this package to the Notification Server. Select the check box to enable sending package status events to the Notification Server. Disabling events for this package prevents Application Control Agents from sending AeX SWD Package events to the Notification Server. The following types of AeX SWD Package events are not sent if package events are disabled: - New Package
- Package Updated
- Package To Be Removed
- Package Removed
- Unable To Check Package
- Insufficient Disk To Download Package
- Download Complete
- Package Download Blocked
For information on capturing events in large environments, see "Scalability" in the Altiris Notification Server Reference.
|
Use Alternate Download Destination on Client | Use an alternate package download destination to the managed computer besides the default. This option makes it possible to deliver package files to computers at alternate destinations. When the task executes, the package files will be copied from the internal cache location to the location specified. Copied package files will never be deleted by the Application Control Agent. They will be recopied every time the task is run; so if the task is on a recurring schedule, the files will be copied repeatedly. This can be useful to ensure the user does not delete a required file. Info |
---|
| The default of the internal cache location is install path\Altiris\Altiris Agent\Software Delivery{0CC5DF0E-BA6C-4AB3-8471-D6F0377F44D6}\cache. |
|
...
|
Apply | Click to save changes. |
Cancel | Click to discard changes. |
Update Distribution Points | Click to update this package information as soon as possible on all enabled Package Servers. |