Action - Create/Delete Directory; Section E.4, "Action - Create/Delete Directory - Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - SOFTWARE DISTRIBUTION REFERENCE 10.3 30-03-2010 Management Manual

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.
E.4 Action - Create/Delete Directory
The Action -Create/Delete dialog box lets you create or delete directory on the managed device.
Action - Create/Delete Directory Dialog Box
Figure E-4
You can access this dialog box by using the following methods:
As part of the process of creating a Directive bundle by using the Actions bundle category. For
more information, see
In ZENworks Control Center, 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 (Install,
Launch, Verify, Uninstall, Terminate, or Preboot), click the Add drop-down list, then select an
available action.
Create Directory: Creates a directory on the managed device when the action is performed.
Delete Directory: Deletes a directory on the managed device when the action is performed.
Directory Name: 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.
Executable Security Level: Click More Options to specify the executable security level options.
On Windows 2000/XP/Vista, the application executable can run in either the "user" space or the
"system" space. 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
Section 2.1, "Creating Directive Bundles," on page 19.
Actions 121