Package Source | Drop-down list with the following options, which are only available
with 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.
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.
Access Package from a URL 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.
|