The General page of the Create/Delete Directory action lets you specify the name of the directory to create or delete from the managed device and the executable security level.
Creates a directory on the managed device when the action is performed.
Deletes a directory on the managed device when the action is performed.
Specify the complete path of the directory you want to create or delete on the managed device. This path must be resolved by the device on which the bundle is run.
On Windows 2000/XP/Vista, the application executable can run in either the “user” space or the “system” space. By default, theoption 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, 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.
NOTE:Performing this action as dynamic administrator on a Windows domain controller fails because Microsoft does not allow the use of local administrator accounts on domain controllers.
The following options are available for Linux:
Run as logged in user: The action is executed as the user logged in to the display :0 (zero). For example, if you select this option while creating a directory, the directory created is owned by the user logged in to display :0 at the time when the action is executed.
Run as root: The action is executed as the root user.
For trademark and copyright information, see Legal Notices.