The Action - Create/Delete Directory dialog box lets you create or delete a directory on the managed device and define the specific requirements that a device must meet for the action to be executed on the device.
Theaction deletes the entire folder along with its inner files and folders; it also deletes the folders that are in the hidden mode.
You can access this information by using the following methods:
As part of the process of creating a Windows bundle by using the Section 2.5, Creating Windows Bundles.bundle category. For more information, see
In ZENworks Control Center, click thetab, click the underlined link of a bundle in the column of the list, click the tab, click one of the action set tabs (Distribute, Install, Launch, Repair, Uninstall, Terminate, or Preboot), click the drop-down list, then select an available action.
The following sections contains additional information:
The General page 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.
Deletes read-only 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, Windows XP, Windows Vista, or Windows 7 device, 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.
You cannot use mapped network drives to specify files and directories because dynamic administrators do not have access to mapped drives.
Select credential for network access: If the file or directory specified in the action are a part of the UNC path or network share that can be accessed only through credentials, then browse through the credential vault to select a credential that has access to the network.
For more information on Credential Vault and adding credential to the Credential Vault, see Using the Credential Vault in the ZENworks Control Center Reference.
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 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.