6.12 Action - Install Directory

The Action - Install Directory dialog box lets you specify the directory to be installed, specify a destination path, specify whether the directory is hidden or read-only after being installed on the device (applicable only for Windows), and specify a copy option. You can also specify the requirements that a device must meet for the action to be executed on the device

Copying a file or directory copies the file or directory from one location to another without uploading the files into the content repository. Copying a file or directory is described as copying without using content. When copying a file or directory, the managed device performs the copy operation and must be able to resolve both the source and destination paths. Also, when copying a file or directory, the file or directory is not cached on the managed device.

Installing a file or directory uploads the file or directory to the content repository before it is distributed to assigned devices. Installing a file or directory is described as copying using content. When installing a file or directory, the file or directory is cached on the managed device. If a directory does not have any content, it is not uploaded to the content repository. This causes any successive action depending on this empty directory to fail.

Installing an executable file does not launch or execute the file. To launch or execute the file, you must add a launch executable action (Launch Executable, Launch Java Application, and so forth) to the bundle.

You can access this information by using the following methods:

As part of the process of creating a Windows bundle by using the Install Directory bundle category. For more information, see Section 2.2, Creating Windows Bundles.
In Endpoint Management Console, click the Bundles tab, click the underlined link of a bundle in the Name column of the Bundles list, click the Actions tab, click one of the action set tabs (Distribute, Install, Launch, Repair, Uninstall, Terminate), click the Add drop-down list, then select an available action.

The following sections contains additional information:

6.12.1 General

The General page lets you specify the directory to be installed, specify a destination path, specify whether the directory is hidden or read-only after being installed on the device (applicable for Windows only), and specify a copy option.

Source Directory

Click Browse icon , allow browser to launch Console Helper. In the Select Directory dialog box, browse and select the directory you want to install on the device.

If you have not installed Console Helper on this device, you must do so before you can browse to and upload directories to be installed.

NOTE:You cannot upload an empty directory.

Destination Directory

Specify the destination directory on the device in which you want to install the directory. The destination directory should be the folder where the files are installed from the uploaded source folder. .

Hidden

Applicable for Windows only. Select the Hidden check box to specify that the directory is hidden after installation.

Read-Only

Applicable for Windows only. Select the Read-only check box to specify that the directory is read-only after installation.

Copy Option

Select a copy option from the list:

Copy Always: Copies the contents of the directory regardless of whether the files currently exists on the workstation.
Copy If Exists: Copies the contents of the directory only if the files currently exists on the workstation.
Copy If Does Not Exist: Copies the contents of the directory only if the files does not currently exist on the workstation.
Copy If Newer: Copies the contents of the directory only if the modified date and time of the file is newer than the existing file’s date and time, or if the files does not currently exist on the workstation.
Copy If Newer and Exists: Copies the contents of the directory only if it already exists on the workstation and the date and time of the file is newer than the existing file’s date and time.
Copy if Newer Version: Copies the contents of the directory only if the internal version of the file is newer than the existing file’s version (if version information is present).
Request Confirmation: Prompts the user to confirm that the content of the directory should be copied when the directory already exists on the workstation.
Copy If Different: Copies the contents of the directory if the creation date, creation time, or size is different than the existing file’s date, time, or size.

NOTE:It is recommended that when you copy files to the local disk, you use the Repository to store the files. This ensures that the entire package is available wherever the computer is located. This makes the application portable, since the user’s computer needs to have neither a UNC/SMB connection to a server nor some other means for transferring files to the local hard drive before they can be used by the bundle. The computer will not even need to have an Internet connection for the installation if the configuration is correct.

Executable Security Level

By default, the Run normal option is selected, which causes the application to run in the “user” space and inherit the same workstation security level as the logged-in user.

If the logged-in user's security level does not provide sufficient rights and file access to run the application, you can configure the application to run in the “system” space or as a dynamic administrator, as described below:

Run as logged in user: The action uses the logged-in user’s credentials. For example, the action has the same rights to the registry and the file system as the logged-in user.
Run as secure system user (Don't allow system to interact with desktop): The application is run under the Local System user and inherits Administrator-level credentials. For example, the application has full rights to the registry and the file system. Because the security level is set to Secure, the application's interface is not displayed to the user and the application is only visible in the Task Manager. This option is useful when running applications that require full access to the workstation but require no user intervention. If you use mapped network drives to specify files and directories, the action fails because system users do not have access to user mapped drives.
Run as dynamic administrator: A dynamic administrator is an administrator account that is created on the fly to perform certain procedures, such as installing applications. Using a dynamic administrator is helpful when installing applications (some MSI applications, for example) that cannot be installed in the system space. When you select this action, the dynamic administrator is created, it performs the required tasks, and then the account is deleted.

You cannot use mapped network drives to specify files and directories because dynamic administrators do not have access to mapped drives.

6.12.2 Requirements

The Requirements page lets you define specific requirements that a device must meet for the action to be enforced on it. For information about the requirements, see Requirements.