...
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.
Navigate to Settings > Agents/Plug-ins > Arellia > Application Control > Application Control Rollout under the Configuration tab in the Arellia Console.
Package tab
Configure a package using this tab.
Image Removed
Image Added
Item | Description |
|---|
Name | Package name. |
Description | Package description. |
Publisher | Package Publisher details. |
Language | Language for which the package is designed. |
Version | Version details. |
Package source | Drop-down list with the following options, which are only availablewith Altiris® Software Delivery Solution™ software installed: - Package does not contain source files - A command line is sent to the managed computer. Example: A call to a utility, such as Chkdsk.exe. The package contains no source files.
- Access Package from a local directory in the NS computer - The location of the package exists in a local directory on the Notification Server computer.
- Access package from Existing UNC - To access packages that exist at a UNC path, you must first enter the credentials that the Notification Server will use when connecting to the UNC path. To do this, go to the Advanced Settings page on the Configuration tab and enter the credentials in the Distribution Point Credential (DPC) section. Next, give these credentials Read Access on the UNC source folder. When the Application Control Agent downloads a UNC package from the Notification Server through HTTP, it will connect to IIS on the Server using the Agent Connectivity Credential (ACC), and IIS will authenticate to the UNC source using the DPC. The Application Control Agent uses the ACC when connecting to sources for download. So, if the Application Control Agent is downloading directly from the UNC package source, instead of through HTTP from the Notification Server, the ACC credentials will also need Read Access on the UNC source location.
- Access Package from a URL - This option requires a package location URL. Package Location URL - Application Control Agent will access the package through this anonymous URL.+Note:+We recommend you select the Use Agent Connectivity Credential option when setting the DPC on the Advanced Settings page as this ensures only one credential, the ACC, will need to exist on UNC package source locations. This doesn't apply if the Application Control Agent is downloading from a Package Server because the Package Server will apply anonymous access or the ACC to their downloaded package files, and the DPC won't be used.
|
Package location | Package location on the Notification Server computer. This can be a local directory, a UNC path, or a URL location depending on the package source. |
Package files will be deleted from the client computer if unused for: | Drop-down list to specify time frame for package files to be deleted from the client computer if they have been unused for any length of time. |
Save changes | Click to save changes. |
Cancel | Click to cancel changes. |
Update Distribution Point | Click to update this package information as soon as possible on all enabled Package Servers. |
...