Table 1-1 Location of Temporary Files for Windows
Utility Used to Create Bundle
Location of Temporary Files
ZENworks Control Center zman (command line utility) ZENworks Migration Utility
zenworks_home\share\tomcat\temp zenworks_home\work\content-repo\tmp zenworks_home\work\collection\datamodel
Table 1-2 Location of Temporary Files for Linux
/opt/novell/zenworks/share/tomcat/temp/ /var/opt/novell/zenworks/content-repo/tmp/ /var/opt/novell/zenworks/collection/datamodel/
If the space on the temporary location is insufficient, you can specify a different disk drive to be the location of temporary files. For more information on changing the location of temporary files on a Windows device, see Changing the Location of the Temporary Location on a Windows Server in the ZENworks 10 Configuration Management System Administration Reference. For more information on changing the location of temporary files on a Linux device, see Changing the Location of the Temporary Location on a Linux Server in the ZENworks 10 Configuration Management System Administration Reference.

1.4 Dependency Bundles

When you create the following actions for a bundle, you create bundle dependencies: Action - Install Bundle Action - Launch Bundle Action - Uninstall Bundle Action - Verify Bundle A bundles Dependency Bundles tree shows the chaining information of that bundle and the action sets that each dependency is in. To view the Dependency Bundles tree in ZENworks Control Center, click the Bundles tab, click a bundle that has dependent bundles, then on the Summary tab, click the Display Bundle Dependencies link in the Dependency Bundles row. If the selected bundle does not have dependent bundles, the link displays None instead of Display Bundle Dependencies. The following sections contain additional information: Section 1.4.1, Primary Applications vs. Dependent Applications, on page 11 Section 1.4.2, Bundle Chains, on page 12 Section 1.4.3, Distributing, Installing, and Launching a Bundle That Has Dependencies, on page 13
1.4.1 Primary Applications vs. Dependent Applications
When working with bundle dependencies, the primary bundle is the bundle for which you are establishing dependencies. The bundles that are defined as dependencies are called the dependent bundles. The following illustration shows this relationship. Application A as the primary bundle with Applications B, C, and D as dependent bundles.

3.3 Assigning Existing Bundles to Users
When you create bundles, the object is created without assigning devices or users to it, or specifying distribution, launch, or availability schedules. Before the bundle can be used on assigned devices, you must complete the steps in this procedure. You can use ZENworks Control Center or the zman command line utility to assign bundles. The following procedure explains how to assign a bundle using ZENworks Control Center. If you prefer the zman command line utility, see the Bundle Commands in ZENworks Command Line Utilities. 1 In ZENworks Control Center, click the Bundles tab. 2 Select the desired bundle in the Bundles list by clicking the box next to its name, click Action, then click Assign to User. or Click the desired bundle, click Relationships. In the Device Assignments panel, click Add.
A bundle must be assigned to devices and users before it can be distributed to them. You can assign the bundle to individual devices, users, folders, or groups. Assigning a bundle to a folder or group is the preferred method of assigning bundles. This allows for easier management of the bundle assignments and can decrease the possibility of high server utilization caused by assigning the bundle to a large number of items (for example, more than 250). 3 In the Select Objects dialog box, browse to and select the objects to which you want to assign the bundle. The Select Objects dialog box opens with the Users folder as the root folder. By default, the user sources that have been defined are displayed, as well as the ZENworks User Groups folder. Browse for and select the users, groups, and folders to which you want to assign the bundle. To do so: 3a Click next to a folder to navigate through the folders until you find the user, group, or folder you want to select. If you are looking for a specific item, such as a User or a User Group, you can use the Items of type list to limit the types of items that are displayed. If you know the name of the item you are looking for, you can also use the Item name box to search for the item.
3b Click the underlined link in the Name column to select the user, group, or folder and display its name in the Selected list box. 3c Click OK to add the selected users, folders, and groups to the Devices list. 4 Specify the bundles shortcut location. You can use the Shortcut Location assignments to specify the locations on the managed device where ZENworks Adaptive Agent displays the bundles icon. The possible locations include the following: Application Window: Places the icon in the Application window. This location is selected by default. Quick Launch: Places the icon on the Quick Launch toolbar area of the Windows taskbar. Desktop: Places the icon on the devices desktop. System Tray: Places the icon in the system tray (notification area) of the Windows taskbar. Start Menu: Places the icon on the Start menu on all Windows devices except for Windows Vista. On Windows Vista, it places the icon in Start > All Programs. On Windows Vista device, if you want to change the look and feel of the Start menu or pin applications to the Start menu, see Appendix G, Best Practices, on page 185. 5 Click Next to display the Schedules page, then select the schedules you want to define: Distribution Schedule: Defines the dates and times when the content of the bundle is distributed from the ZENworks Server to the managed device or user. If you do not establish a schedule, the bundles content is distributed to the device or user when it is first launched. However, the schedule does not define the date and time when the action in the bundle runs. Launch Schedule: Defines the dates and times when the ZENworks Adaptive Agent automatically launches the bundle. If you do not establish a schedule, the bundle is launched only when the user launches it. Before launching the bundle, the ZENworks Adaptive Agent checks if the bundle is distributed and installed. If the bundle is not yet distributed, the agent first distributes the bundle, performs the bundles install actions to install the bundle, then performs the bundles launch actions to launch it. Availability Schedule: Defines the dates and times when the bundle is available to the device or user. The ZENworks Adaptive Agent displays the bundle icon only during the times defined by the schedule. If you do not establish a schedule, the bundle is available at all times. NOTE: If a bundle with an assignment schedule fails to execute on a device, an attempt to execute the bundle on the device is made five times, by default. To change the default value: 1.Open the Registry Editor. 2.Go to HKLM\Software\Novell\ZCM\. 3.Create a STRING called ScheduleRetries, and set its value as desired. For example, if you do not want the failed bundle to be executed again on the device, set the value of ScheduleRetries to 0. 6 (Conditional) If you selected Distribution Schedule in Step 5, click Next to display the Bundle Distribution Schedule page. The distribution schedule defines the dates and times when the bundle is distributed from the ZENworks Server to the managed device. The default schedule (no schedule) causes the bundle to be distributed to the device when it is first launched.

3.9 Managing Bundle Variables
The Bundles Settings page lets you manage the variables that are available for use on bundles. The Inherited Variables panel displays all system variables that are inherited from the ZENworks Management Zone or parent folders. You cannot delete or modify inherited variables. However, if you add the same system variable, but give it a different value, the new variable value overrides the inherited variable value. When specifying the variable in a field, use the following syntax:

${VAR_NAME}

Replace VAR_NAME with the name of the variable. The System Variables panel lets you define variables that can be used to replace paths, names, and so forth as you enter information. You can define system variables at three levels: Management Zone: The system variables are inherited by the following: device folders, devices, and bundles. Device Folder: The system variables are inherited by all devices contained within the folder or its subfolders. Device or Bundle: The system variables apply only to the device or bundle for which they are configured. The following table lists the tasks you can perform to manage the system variables:

Additional Details

Add a variable
1. If you are configuring system variables for an object (not for the entire Management Zone), click Override settings to activate the System Variables panel. 2. Click Add, provide the name and value for the variable, then click OK. 3. Click Apply.
When configuring system variables for an object, you can override an inherited variable by defining a new variable with the same name but a different value. For example, if Var1=c:\ is inherited, you can override it by defining Var1=d:\. Variable names cannot include spaces and must be unique at the level where they are defined. For example, you cannot have two variables named Var1 defined at the device level (unless one is inherited, in which case the device level variable overrides the inherited variable). Variable values cannot include the characters & and <.

Remove a variable

1. Select the check box next to the variable (or variables). 2. Click Remove. 3. Click Apply.

Edit a variable

6.8 Viewing a Bundles Properties
You can view a bundles properties to see its version number, current installation status, and help contacts. In addition, if the bundle is unavailable, you can see if it is unavailable because of system requirements or schedule restrictions. 1 Access the bundle in one of the following locations: ZENworks Window: From the Start menu, click Programs > Novell ZENworks > ZENworks Window. ZENworks Explorer: Open Windows Explorer and find the ZENworks Adaptive Agent entry. Depending on how your ZENworks administrator configured the bundle, the bundle icon might also be displayed on the desktop, Start menu, Quick Launch toolbar, or notification area. 2 Right-click the bundle icon, then click Properties.
6.9 Uninstalling a Bundle
Uninstall is an administrator-controlled feature. By default, uninstall is not enabled, which means that you can only uninstall bundles if your administrator has enabled the feature. Uninstall is enabled on a per-bundle basis. Depending on what your administrator enables, you might be able to uninstall some bundles but not others. When you uninstall a bundle, the ZENworks Adaptive Agent removes all files from your device and undoes all configuration settings made to your device during the bundle installation. Only files that the Adaptive Agent installs specifically for the bundle are removed. For example, the Adaptive Agent does not remove any shared files (files used by another application) or any user-created files such as word processing documents or spreadsheets. After you uninstall a bundle, the bundles icon remains on your device. This enables you to install the bundle again whenever necessary. To uninstall a bundle: 1 Access the bundle in one of the following locations: ZENworks Window: From the Start menu, click Programs > Novell ZENworks > ZENworks Window.
ZENworks Explorer: Open Windows Explorer and find the ZENworks Adaptive Agent entry. Depending on how your ZENworks administrator configured the bundle, the bundle icon might also be displayed on the desktop, Start menu, Quick Launch toolbar, or notification area. 2 Right-click the bundle icon, then click Uninstall.

Section E.20, Action - Launch URL, on page 149 Section E.21, Action - Launch Executable, on page 150 Section E.22, Action - Launch Windows Thin Client Application, on page 154 Section E.23, Action - Prompt User, on page 157 Section E.24, Action - Reboot/Shutdown, on page 158 Section E.25, Action - Registry Edit, on page 160 Section E.26, Action - Run Script, on page 165 Section E.27, Action - Start/Stop Service, on page 171 Section E.28, Action - Store Personality, on page 172 Section E.29, Action - Terminate Application, on page 173 Section E.30, Action - Terminate Application Prompt, on page 174 Section E.31, Action - Undo Install Actions, on page 175 Section E.32, Action - Uninstall Bundle, on page 175 Section E.33, Action - Verify Bundle, on page 176 Section E.34, Action - Verify Install Actions, on page 177
E.1 Action - Apply Personality
The Apply Personality page lets you specify the personality migration template and the Platform Neutral Package (PNP) file to be used for the migration. For more information on personality migration template, see ZENworks 10 Personality Migration Reference.
Figure E-1 Action - Apply Personality Dialog Box
116 ZENworks 10 Configuration Management Software Distribution Reference
You 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 Section 2.1, Creating Directive Bundles, on page 17. 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 the Add drop-down list, then select the Apply Personality action. Upload a template from this device Select this option and click dialog box. Browse to and select the template to upload. to display the Upload content
Specify a template on the managed device Select this option to specify the path of personality migration template file on the managed device. You can also specify the UNC path of the file. Path from where the PNP file is to be loaded Specify the path of the PNP file containing the migration settings and data on the managed device. You can also specify the UNC path of the file. Password to decrypt the PNP file Select this check box to enter the password to decrypt the PNP file. NOTE: If you spanned the PNP file, be sure to keep the spanned files and the PNP file in the same folder.

118 ZENworks 10 Configuration Management Software Distribution Reference
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 files 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 files 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 files version (if version information is present). Request Confirmation: Prompts the user to verify that the contents of the directory should be copied. Copy If Different: Copies the contents of the directory if the creation date, creation time, or size of the file is different than the existing files date, time, or size. 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 users 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. 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.

120 ZENworks 10 Configuration Management Software Distribution Reference
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. 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.
Figure E-4 Action - Create/Delete Directory Dialog Box
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 Section 2.1, Creating Directive Bundles, on page 17. 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.

E.10 Action - End Process
The Action - End Process dialog box lets you specify the executable name of the process that you want to stop (for example, notepad, mspaint, winword, and so forth). If the process is not running on the device, the End Process task completes.
130 ZENworks 10 Configuration Management Software Distribution Reference
Figure E-10 Action - End Process Dialog Box
You 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 Section 2.1, Creating Directive Bundles, on page 17. 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.
E.11 Action - File Removal
The Action - File Removal dialog box lets you specify files or directories to remove from the device.

Actions 131

Figure E-11 Action File Removal Dialog Box
You 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 Section 2.1, Creating Directive Bundles, on page 17. 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. You can use this action to perform an automated system cleanup. For example, you can specify that the c:\windows\Temp\Temporary Internet Files directory and all files matching c:\windows\Temp\*.log in are removed from the device. You cannot remove read-only files. If you specify a directory that contains several files (including some read-only files), the directory and the read-only files are not removed when the File Removal action runs. The files that are not read-only, however, are removed from the device. Full Path to Source Files/Directories: Specify the full path to the file or directory that you want to remove, then click Add to add the file or directory to the list. You can use wildcard characters. If you use a mapped network drive to specify the path, you must select User from the Run Action As list. Include System Files: Select this option to remove system files. If you specify a directory for removal that includes both system and non-system files, only non-system files are deleted, unless you specify this option. Delete Folder Only if Empty: Select this option if you want to remove the specified folders only if they are empty.

E.25.1 Registry Tree

The Registry Tree page lets you select hives in the tree to which you want to add values and keys, rename or remove sections, or import a registry file.
Figure E-27 Action - Registry Edit Dialog Box: Registry Tree Page
The following table lists the tasks you can perform to manage registry tree changes.

Actions 161

Add a registry key
1. Select a registry hive, click New, then click Key. 2. Specify the keys name. For example, Software. You can also specify multiple levels of keys by separating them with a backslash (\). For example, Novell\ZENworks\Zfd. Do not use the forward slash (/) as a separator. 3. Select one of the following registry operations: Create Always: Creates the key regardless of whether the key currently exists in the workstations registry. Create If Does Not Exist: Creates the key only if the key does not currently exist in the workstations registry. Rename: Renames the key if it currently exists in the workstations registry. Delete: Deletes the key if it currently exists in the workstations registry. Delete and Recreate: Deletes the key if it currently exists in the workstations registry, then re-creates the key. Delete if Empty: Deletes the key if it currently exists in the workstations registry and the key is empty. None: Does not perform any registry operation.
162 ZENworks 10 Configuration Management Software Distribution Reference

Add a registry value

1. Select the check box next to the desired item, then click Value to display the Add Value To dialog box. 2. Select one of the following options from the Value Type list: Default: Adds a default string value to the selected key. String: Adds a string value to the selected key. Binary: Adds a binary value to the selected key. Most hardware component information is stored as binary data and is displayed in hexadecimal format. Dword: Adds a DWORD value to the selected key. DWORD values are represented by a number that is 4 bytes long. Many parameters for device drivers and services are this type and are displayed in binary, hexadecimal, or decimal format. Expandable String: Adds an expandable-string value to the selected key. An expandable string is a variable-length data string. This data type includes variables that are resolved when a program or service uses the data. Multiple String: Adds a multi-value string to the selected key. Multiple string values contain lists or multiple values in a form that people can read. Entries are separated by spaces, commas, or other marks. Qword: Adds a Qword string to the selected key. A Qword value is data represented by a number that is a 64-bit integer. This data is displayed in the Registry Editor as a binary value. Link: Adds a link string value to the selected key. A link string value is a Unicode string naming a symbolic link. None: Does not perform any registry operation. Full Resource Descriptor: Adds a full resource descriptor value to the selected key. A full resource descriptor is a series of nested arrays designed to store a resource list for a hardware component or driver. Resource List: Adds a resource list to the selected key. A resource list is a series of nested arrays that is designed to store a resource list that is used by a hardware device driver or one of the physical devices it controls. Resource Requirement List: Adds a resource requirements list to the selected key. A resource requirements list is a series of nested arrays designed to store a device driver's list of possible hardware resources that the driver or one of the physical devices it controls can use. 3. Specify the data. Depending on which value type you selected in the previous step, the type of data varies. 4. Select one of the following registry operations: Create Always: The setting is always created in the registry, even if it already exists. If it exists, the setting's current values are overwritten. For example, if PATH=C:\ already exists, PATH=C:\TEMP replaces it. Create If Exists: The setting is created only if it already exists. The setting's current values are overwritten. For example, if PATH=C:\ already exists, PATH=C:\TEMP replaces it. Create If Does Not Exist: The setting is created only if it does not already exist. Delete: The setting is deleted. If the registry setting has subordinate settings, the subordinate settings are also deleted. Append If Exists, Otherwise Create: Appends the registry value if the value currently exists in the workstations registry. If the registry value does not exist, it is created. Prepend If Exists, Otherwise Create: Prepends the registry value if the value currently exists in the workstations registry. If the registry value does not exist, it is created.

E.26.1 Specify a File on a Managed Device
Select this option to run a script that exists on the managed device.

Actions 165

Figure E-29 Action - Run Script Dialog Box
Script Filename: Specify the path to the script file on the target device, for example, C:\scripts\xyz.pl. Script Parameters: Specify any additional parameters you want to place on the command line after the script filename is specified. This results in parameters being passed to your executable script. Path to Script Engine: Specify the interpreter that launches to run your script. For example, C:\Program Files\Perl\bin\Perl.exe. For Windows scripts other than batch scripts (for example, VBScript), the Path to Script Engine field should specify the path to the Windows Based Script Host, such as (C:\Windows\System32\wscript.exe) Script Engine Parameters: Specify any parameters you want included on the command line when the script engine launches. Wait Before Proceeding to Next Action: Specify what happens after the script is run: No wait: The next action in the list is immediately performed. When launch action is complete: The next action in the list is performed after the launch action completes. Wait for _ seconds: Wait the specified number of seconds before proceeding to the next action. Terminate action if wait period exceeded: If you select the Wait for _ seconds option, this option is enabled. If the specified number of seconds is exceeded and the action is not successfully performed, the action is terminated. Success Return Codes: Specify the non-zero success codes that the script returns. You can specify multiple success codes separated by commas.
166 ZENworks 10 Configuration Management Software Distribution Reference
If a script returns non-zero success codes, you should specify these non-zero success codes while launching the action. For example, explorer.exe in Windows returns a success code of 1. To successfully launch the Explorer application, you should add 1 as the success code while launching the action. Working Directory: Click More Options to specify the scripts working directory. Specify the initial working directory for the script. Priority: Click More Options to specify the scripts priority. Specify the priority of the process that runs the script. This option lets you configure how much of the CPU usage the script process consumes. Select from the following priorities: Real Time, High, Above Normal, Normal, Below Normal, and Low. Run As: Click More Options to specify the scripts run as setting. Specify an option: System: Runs the script as the system account (as a service). Administrator: Runs the script as a dynamic administrator user. A dynamic administrator is an administrator account that is created on the fly to perform certain procedures, such as installing applications or running scripts. 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. User: The script runs, using the logged-in users credentials. For example, the script has the same rights to the registry and the file system as the logged-in user.

E.26.3 Select From This Device
Select this option to specify a script file that is already on the device on which you are running ZENworks Control Center.

Actions 169

Figure E-31 Action - Run Script Dialog Box
Select From This Device: Browse to and select the script file. Script Parameters: Specify any additional parameters you want to place on the command line after the script filename is specified. This results in parameters being passed to your executable script. Path to Script Engine: Specify the interpreter that launches to run your script. Script Engine Parameters: Specify any parameters you want included on the command line when the script engine launches. Wait Before Proceeding to Next Action: Specify what happens after the script is run: No wait: The next action in the list is immediately performed. When launch action is complete: The next action in the list is performed after the launch action completes. Wait for _ seconds: Wait the specified number of seconds before proceeding to the next action. Terminate action if wait period exceeded: If you select the Wait for _ seconds option, this option is enabled. If the specified number of seconds is exceeded and the action is not successfully performed, the action is terminated. Working Directory: Click More Options to specify the scripts working directory. Specify the initial working directory for the script. Priority: Click More Options to specify the scripts priority. Specify the priority of the process that runs the script. This option lets you configure how much of the CPU usage the script process consumes. Select from the following priorities: Real Time, High, Above Normal, Normal, Below Normal, and Low.
170 ZENworks 10 Configuration Management Software Distribution Reference
Run As: Click More Options to specify the scripts run as setting. Specify an option: System: Runs the script as the system account (as a service). Administrator: Runs the script as a dynamic administrator user. A dynamic administrator is an administrator account that is created on the fly to perform certain procedures, such as installing applications or running scripts. 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. User: The script runs, using the logged-in users credentials. For example, the script has the same rights to the registry and the file system as the logged-in user.

174 ZENworks 10 Configuration Management Software Distribution Reference
To create a message: 1 Click Add to display the Select Locale and Prompt dialog box. 2 Select a language from the Locale drop-down list. The message displays only on devices in the specified locale. You can create different messages, each with its own locale setting. 3 Type the text you want to display on the device. You can include {0} in your text to provide a running counter that counts down the number of seconds to 0, after which the prompt is auto-accepted. For example, you could specify the following text:
E.31 Action - Undo Install Actions
The Action - Undo Install Actions dialog box lets you undo all operations that are performed in the install action set. The list displays the name and type of each operation that is reversed. There are no configuration tasks that you need to perform for this action. You access this dialog box by using the following methods: As part of the process of creating a File bundle by using the Actions bundle category. For more information, see Section 2.2, Creating File Bundles, on page 21. 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.
E.32 Action - Uninstall Bundle
The Action - Uninstall Bundle dialog box lets you select a bundle to remove from the device.
Figure E-36 Action - Uninstall Bundle Dialog Box

Actions 175

You access this dialog box by using the following methods: As part of the process of creating a File bundle by using the Actions bundle category. For more information, see Section 2.2, Creating File Bundles, on page 21. 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. Click to browse to and select the bundle to uninstall from the device.
The Look in list defaults to /Bundles. If you have created subfolders to hold your bundles, use the down-arrow to select the appropriate folder. The Items of type list defaults to All Types so that all types of bundles are displayed (Directive, File, Imaging, and Windows bundles). If you know the name of the bundle you are looking for, you can use the Item name box to search for the bundle. You must not use the Uninstall Bundle action to uninstall Directive bundles. Creating this action creates a bundle dependency. For more information, see Section 1.4, Dependency Bundles, on page 11.

The following sections contain information on the best practices to follow while using the Bundles component of Novell ZENworks 10 Configuration Management: Section G.1, Changing the Look and Feel of the Start Menu on a Windows Vista Device, on page 185 Section G.2, Pinning Applications to the Start Menu on a Windows Vista Device, on page 185 Section G.3, Assigning Bundles to a Device or User, on page 185 Section G.4, ZENworks Explorer Folder Naming Convention, on page 186
G.1 Changing the Look and Feel of the Start Menu on a Windows Vista Device
On a Windows Vista device, the folders on the Start menu have a cascading effect. To have the same look and feel as the Windows XP Start menu: 1. Right-click Start. 2. Click Properties. 3. Select Classic Start Menu. 4. Click OK.
G.2 Pinning Applications to the Start Menu on a Windows Vista Device
On a Windows Vista device, you can choose to have the folders pinned to the Start menu to have the same look and feel as the pinned folders on the Windows XP Start menu. 1. Right-click Start. 2. Click Properties. 3. Select Classic Start Menu. 4. Click OK. 5. Restart the system.
G.3 Assigning Bundles to a Device or User
Do not assign more than two bundles that has the same name to a Windows managed device because only the first two bundles that are assigned to the device are displayed on the device. Sample Scenario: Assume that bundles named test, Test, TEST are assigned to a Windows managed device. The first bundle that is assigned to the device has the specified name. The second bundle that is assigned to the device has the management zone name appended to the specified name. However, the third bundle is not displayed on the device.

Best Practices 185

G.4 ZENworks Explorer Folder Naming Convention
If the ZENworks Explorer Folder name for two or more bundles is the same but has a different case, then only one folder and containing all the bundle's shortcuts is displayed in the start menu and the ZENworks Explorer window.
186 ZENworks 10 Configuration Management Software Distribution Reference

Macros

The following sections contain information on the macros supported in Novell ZENworks Configuration Management: Section H.1, Windows Macros, on page 187 Section H.2, Login Script Macros, on page 192 Section H.3, Novell eDirectory Attribute Macros, on page 193

H.1 Windows Macros

A Windows macro is one that defines the Windows directories. The typical paths listed below are based on default installations and might not match your specific setup. Suppose that you have installed Windows to drive D: (for example, D:\WINDOWS). However, an application installation expects Windows to be on drive C: (for example, C:\WINDOWS). You can use the WinDisk macro to substitute drive D: for the files that require it.

AUTHORIZED DOCUMENTATION

ZENworks Migration Guide

Novell

March 09, 2011
ZENworks 10 Configuration Management SP3

www.novell.com

Legal Notices
Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc., makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes. Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the Novell International Trade Services Web page (http://www.novell.com/info/exports/) for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals. Copyright 2007 - 2011 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher. Novell, Inc. 404 Wyman Street, Suite 500 Waltham, MA 02451 U.S.A. www.novell.com Online Documentation: To access the latest online documentation for this and other Novell products, see the Novell Documentation Web page (http://www.novell.com/documentation).

Novell Trademarks

For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/ trademarks/tmlist.html).

Third-Party Materials

All third-party trademarks are the property of their respective owners.

Contents

About This Guide 1 Migration Process 7 9
2 Differences between ZENworks 10 Configuration Management and Traditional ZENworks 11
2.1 Architecture. 2.1.1 Traditional ZENworks Architecture. 2.1.2 The Next Generation ZENworks Architecture. 2.1.3 More Detail on the Architectural Changes. System Management. Workstations. Inventory. Imaging. Remote Management. Application Management. Additional Features. 22
2.2 2.3 2.4 2.5 2.6 2.7 2.8
3 Planning Your Migration to ZENworks Configuration Management
3.1 3.2 3.3 Migration Candidates. Installing the ZENworks Migration Utility. What the ZENworks Migration Utility Does. 3.3.1 Migrated. 3.3.2 Not Migrated. 3.3.3 Other Software. Planning Your Migration. 3.4.1 Coexistence of the ZENworks Systems. 3.4.2 LDAP Authentication. 3.4.3 PXE Devices and Server Referral Lists. 3.4.4 Incremental Migration. 3.4.5 Migration Order. 3.4.6 Management Zone Settings. 3.4.7 Migrating Workstations. 3.4.8 Identifying Users. 3.4.9 Folder Usage in Configuration Management. 3.4.10 Migration Modeling. 3.4.11 Whats Next?.

4 Migrating to ZENworks Configuration Management
4.1 4.2 4.3 4.4 4.5 4.6 4.7 Prerequisites. Starting the ZENworks Migration Utility. Selecting the Migration Source. Selecting the Migration Destination. Migrating Applications. Migrating Images. Migrating Policies.
4.8 4.9 4.10 4.11 4.12 4.13 4.14
Migrating Management Zone Settings. Migrating Workstations. Migrating Associations. Migrating Applications That Have the Same Application GUID. Setting Up Migrated Workstations to be Managed. Make an Image of the Migrated Workstations. Managing Your Traditional ZENworks Installation.

A Migration Data

A.1 A.2 A.3 A.4 A.5 A.6 Applications. Images. Policies. Management Zone Settings. Workstations. Associations.

B Migration Options

B.1 Using the Migration Utility to Configure Migration Options. B.1.1 General. B.1.2 Applications. B.1.3 Associations. B.1.4 Imaging. B.1.5 Policies. B.1.6 Zone Settings. B.1.7 Workstations. B.1.8 Web Client Configuration. Using the Registry Editor to Configure Additional Options for Migrating MSI Applications.
C Understanding the Migration Utility
C.1 C.2 C.3 C.4 C.5 C.6 Migration Tasks. Migration Source/Destination. Migrate Now Button. Cancel Button. Exit. Select Tab. C.6.1 Source eDir Tree. C.6.2 Destination Zone. C.7 Items to Migrate Tab. C.8 Migration History Tab. C.9 Whats New Icon. C.10 Options Icon. C.11 Overall Progress.
D Troubleshooting E Best Practices

E.1 E.2 E.3

Running the Migration Utility on a Windows Vista device. 95 Selecting a Migration Option. 95 Uploading Objects to the Content Server. 95
ZENworks 10 Configuration Management ZENworks Migration Guide

E.4 E.5 E.6 E.7 E.8

Migrating Applications as Actions or MSI. 96 Using Network Files. 96 Listing the Associations in the Migration Utility. 96 Listing Application Objects with the AppFsRights attribute in the Migration Utility. 97 Specifying the File Upload HTTP Port and Web Service Port to Log In to the Migration Destination Management Zone. 97 E.9 Migrating Group Policies. 97 E.10 Migrating Applications with a Large Number of INI or Registry Operations as Individual Actions 97

F Documentation Updates

F.1 F.2 F.3 F.4
March 8, 2011. 99 January 17, 2011: Update for ZENworks 10 Configuration Management SP3 (10.3.2). 99 July 27, 2010: Update for ZENworks 10 Configuration Management SP3 (10.3.1). 100 March 30, 2010: SP3 (10.3). 100

About This Guide

This Novell ZENworks 10 Configuration Management ZENworks Migration Guide contains the information, steps, and processes that you need to move from traditional Novell ZENworks to Novell ZENworks 10 Configuration Management SP3, the next generation of ZENworks. The information in this guide is organized as follows: Chapter 1, Migration Process, on page 9 Chapter 2, Differences between ZENworks 10 Configuration Management and Traditional ZENworks, on page 11 Chapter 3, Planning Your Migration to ZENworks Configuration Management, on page 23 Chapter 4, Migrating to ZENworks Configuration Management, on page 33 Appendix A, Migration Data, on page 67 Appendix B, Migration Options, on page 77 Appendix C, Understanding the Migration Utility, on page 83 Appendix D, Troubleshooting, on page 89 Appendix E, Best Practices, on page 95 Appendix F, Documentation Updates, on page 99 Audience This guide is intended for ZENworks Configuration Management administrators. Feedback We want to hear your comments and suggestions about this manual and the other documentation included with this product. Please use the User Comments feature at the bottom of each page of the online documentation, or go to the Novell Documentation Feedback site (http://www.novell.com/ documentation/feedback.html) and enter your comments there. Additional Documentation ZENworks 10 Configuration Management is supported by other documentation (in both PDF and HTML formats) that you can use to learn about and implement the product. For additional documentation, see the ZENworks 10 Configuration Management SP3 documentation (http:// www.novell.com/documentation/zcm10/) When a single pathname can be written with a backslash for some platforms or a forward slash for other platforms, the pathname is presented with a backslash. Users of platforms that require a forward slash, such as Linux, should use forward slashes as required by your software.

ZENworks Servers Managed Devices

LDAP Directory

Distribution Point

Primary Server

The new Novell ZENworks 10 Configuration Management architecture includes the following important characteristics: Installation of the ZENworks Adaptive Agent on every managed device Three-tier SOA Additional Primary Servers for computing tasks, which removes the workload from the managed device No more specific requirement for Novell eDirectory No more requirement for Novell Client32 to be installed on either the managed device or the server A new Web-based administrative console (ZENworks Control Center) to manage all ZENworks objects, configurations, and functions Native support for both Novell eDirectory and Microsoft Active Directory Based on industry-standard protocols Direct, one-time server installation, then managed devices are deployed from the server through ZENworks Control Center Installation of Primary Server software on either Windows Server 2003, Windows Server 2008, or SUSE Linux Enterprise Server
2.1.3 More Detail on the Architectural Changes
The following sections provide further detail on the architectural differences: Management Console on page 16 Software Repository on page 16
Novell eDirectory on page 16 Object Management on page 17 User Management on page 17 Client Agents on page 18 Middle Tier Server on page 18 Management Console ZENworks Control Center, a Web-based management console is used as a graphical management interface for Configuration Management and it replaces ConsoleOne that is used in tradional ZENworks: Administrator Roles: ZENworks Control Center provides robust administrator roles unique to its new architectural design. For more information, see Administrators in the ZENworks 10 Configuration Management System Administration Reference. Watch Lists: ZENworks Control Center provides watch lists on a Home page where you can see the current status of selected devices and bundles, as well as overall Management Zone statistics. For more information, see Creating a Watch List in the ZENworks 10 Configuration Management Administration Quick Start. iManager: If you already use Novell iManager to manage other Novell products, you can configure the ZENworks Control Center to be launched from iManager. For more information, see Accessing ZENworks Control Center through Novell iManager in the ZENworks 10 Configuration Management System Administration Reference. Software Repository Every Primary Server in the Management Zone contains the same content, providing redundancy for all managed devices in the zone. For more information, see Content Repository in the ZENworks 10 Configuration Management System Administration Reference. In Configuration Management, content replication and closest server rules replace the traditional load balancing techniques for fault tolerance. For more information, see both Content Replication and Closest Server Rules in the ZENworks 10 Configuration Management System Administration Reference. Novell eDirectory Novell eDirectory is no longer required for data storage. Instead, the ZENworks Configuration Management database is used. This is different from traditional ZENworks in several ways: ZENworks Database: A new ZENworks database replaces the old ZENworks database and all eDirectory tree object information stores. Instead of eDirectory containers and contexts, Configuration Management uses database folders and the inheritance functionality relevant to folder/object hierarchy. The new database is the content repository for all Configuration Management data. For more information on which databases can be used with Configuration Management, see Database Requirements in the ZENworks 10 Configuration Management Installation Guide. For more information on maintaining your selected database, seeDatabase Management in the ZENworks 10 Configuration Management System Administration Reference.

No Schema Extensions: Because Configuration Management stores all the data in the ZENworks database, it does not impact your Novell eDirectory schema. Any access to eDirectory is read-only for the purpose of referencing user information. User Sources: You can use eDirectory and Active Directory as the source for users. To do this, you define a read-only LDAP link to a directory and specify the contexts where users reside. ZENworks creates references to the users in its own database that allow for ZENworks management activities to occur completely within the ZENworks database rather than in the directory. If you only plan to manage devices through device assignments rather than user assignments, user sources are not needed. For more information, see User Management on page 17. Management Zone: Primary Servers and managed devices are organized into a Management Zone, replacing the organization provided by the eDirectory tree. Object Management Configuration Management uses ZENworks Control Center objects instead of eDirectory objects. The following describes some of the differences: Dynamic Groups: This is a new feature in Configuration Management. Both groups and dynamic groups are available. From the perspective of software and policy assignments, groups and dynamic groups have the same function. The only difference between the two types of groups is the way that devices are added to the group. With a group, you must manually add devices. With a dynamic group, you define criteria that a device must meet to be a member of the group, and then devices that meet the criteria are automatically added. Several dynamic groups are predefined, but you can define your own. For more information, see Groups in the ZENworks 10 Configuration Management Administration Quick Start. Inheritance: You can set configurations in several ways: Globally for all ZENworks Control Center objects (devices or bundles) in the Management Zone For all objects in a folder and its subfolders For a group of objects (predefined, user-defined, and dynamic groups are available) For an individual object For more information, see Organizing Devices: Folders and Groups in the ZENworks 10 Configuration Management Administration Quick Start. Associations: In Configuration Management, ZENworks Control Center objects are assigned to each other (such as bundles to devices), instead of being associated with eDirectory objects. The differences between assignments and associations should be considered when migrating to Configuration Management. For more information, see Section 4.10, Migrating Associations, on page 59. User Management Configuration Management references existing LDAP user sources, in either eDirectory or Active Directory. Users are not migrated to Configuration Management. This way, ZENworks knows immediately of any changes done natively to user objects. For more information, see User Sources in the ZENworks 10 Configuration Management System Administration Reference.

Client Agents The ZENworks Adaptive Agent replaces the ZENworks Desktop Management Agent. The differences include the following: Deployment: You can use the ZENworks Control Center to deploy the Adaptive Agent to any workstation whose IP address or LDAP directory context you know (or have discovered using the network discovery of LDAP directory discovery technologies included in ZENworks). Functionality: All functionality (software distribution, imaging, remote management, policies) is automatically included with the installation of the Adaptive Agent. The only functionality you can choose to remove from the agent installation is remote management. No Network Client: The Adaptive Agent does not require network clients (Novell Client or Microsoft Client) to retrieve content (applications, etc.) from Primary Servers. The Adaptive Agent uses HTTP and Web services requests to retrieve the content. NOTE: The latest version of the Novell client must be installed on the managed device before a Dynamic Local User policy or a Roaming Profile Policy that has Store User Profile in Users Home Directory enabled is enforced on the device. To obtain the latest version of Novell Client, see the Novell Download Web site (http://download.novell.com/index.jsp). Integrated Interface: The separate client programs (Workstation Manager, Remote Control, etc.) have been replaced with a common interface called the ZENworks Icon. The ZENworks Icon is displayed in the notification area at the bottom of the desktop. The NAL Window and NAL Explorer views are still available. Configuration Settings The Adaptive Agent behavior is now controlled through a combination of configuration settings and policy settings (ZENworks Explorer Configuration policy) rather than through the Launcher Configuration settings only. This allows for greater flexibility in determining which devices receive specific settings. Inventory-Only Module: If you have workstations that dont meet the requirements for installing the Adaptive Agent (see Managed Device Requirements in the ZENworks 10 Configuration Management Installation Guide), you can still receive inventory information from these workstations by installing the Inventory-only module. For more information, see Deploying the Inventory-Only Module in the ZENworks 10 Configuration Management Discovery and Deployment Reference. For more information, see ZENworks Adaptive Agent Deployment in the ZENworks 10 Configuration Management Discovery and Deployment Reference. Middle Tier Server The Middle Tier Server does not exist in Configuration Management. Instead, the ZENworks Adaptive Agent communicates directly with the Primary Server through Web services and HTTP requests.

2.2 System Management

Configuration Management provides several methods for managing ZENworks: ZENworks Control Center: This is the main Configuration Management administration interface. For more information, see ZENworks Control Center in the ZENworks 10 Configuration Management System Administration Reference.

Configuration Management uses its own database, not eDirectory. The Adaptive Agent replaces the traditional ZENworks Agent on managed devices. Because of these things, the Configuration Management and traditional ZENworks systems can run concurrently in your environment without conflicts. The Configuration Management and traditional ZENworks systems do coexist but are not interoperable. They remain as separate management software for the devices where their respective agents are running.
3.4.2 LDAP Authentication
The ZENworks Migration Utility authenticates to both the source eDirectory tree by using LDAP and the destination ZENworks Management Zone by using Web services, and both rely on SSL for security over TCP/IP. LDAP must be enabled, which is the default for eDirectory trees. For eDirectory login, you must provide a fully distinguished user name that has sufficient rights to read eDirectory. Writing to eDirectory is not required because the migration process only reads eDirectory. If you are migrating images, the migration user must also have rights to read.zmg imaging files. For reading information from eDirectory, the default port for LDAP SSL is 636. The default nonLDAP SSL port is 389. Although you can migrate without Novell Client32 running on the device where you are running the migration utility, Client32 might be necessary to access files on NetWare volumes. Authentication to the ZENworks Management Zone is done using the administrator login name and password that you established when installing Configuration Management. If you added other administrator logins in ZENworks Control Center after installation, these are also valid, provided they have the necessary Read rights to eDirectory and Write rights to the ZENworks Configuration Management database. For writing to the zones database, the default port for SSL is 443.
3.4.3 PXE Devices and Server Referral Lists
If you have both Configuration Management and ZENworks Linux Management systems running concurrently, the following information might apply: PXE Devices: When a PXE device boots, it makes a broadcast request on the network for PXE services. The ZENworks Proxy DHCP server (the novell-proxydhcp daemon) responds to this request with information that includes the IP address of an imaging server where the device can send requests for assigned preboot work. Because PXE devices can exist in an environment with both newer and traditional ZENworks systems running concurrently, the device can fail to determine its assigned preboot work if it cannot find the imaging server for its own ZENworks version. In ZENworks Configuration Management, devices can exist in multiple Management Zones. It is essential that the PXE device contact PXE services associated with its home zone so that it can correctly determine if there is any preboot work assigned to it. When there is only a single Management Zone, this is easy to do because all Proxy DHCP servers provide addresses to services that belong to the same zone. Any device can request preboot work from any imaging server in the same zone and get the same response.

To migrate, you simply use the migration screen to queue what you want migrated, resolving any issues that the utility might identify as you queue them, then click a button to migrate your eDirectory data to the ZENworks database. Therefore, in addition to planning your migration on paper, you can use this modeling capability of the migration screen to visualize your migration before actually performing it. The migration screen works by migration task. The tasks described in Section 3.4.5, Migration Order, on page 28 are each a migration session. A selected task is migrated when you click the Migrate Now button. Therefore, at a minimum, you must plan to migrate your eDirectory data in several separate clicks of the Migrate Now button. However, you can model an incremental migration consisting of many sessions per migration task.

3.4.11 Whats Next?

In addition to planning your migration on paper, you can use the migration screen to model your migration. To get started with using the migration screen, continue with Chapter 4, Migrating to ZENworks Configuration Management, on page 33.
Migrating to ZENworks Configuration Management
Do the following tasks in the order listed to migrate your traditional ZENworks software to Configuration Management: Section 4.1, Prerequisites, on page 33 Section 4.2, Starting the ZENworks Migration Utility, on page 35 Section 4.3, Selecting the Migration Source, on page 37 Section 4.4, Selecting the Migration Destination, on page 38 Section 4.5, Migrating Applications, on page 40 Section 4.6, Migrating Images, on page 47 Section 4.7, Migrating Policies, on page 50 Section 4.8, Migrating Management Zone Settings, on page 53 Section 4.9, Migrating Workstations, on page 55 Section 4.10, Migrating Associations, on page 59 Section 4.11, Migrating Applications That Have the Same Application GUID, on page 64 Section 4.12, Setting Up Migrated Workstations to be Managed, on page 65 Section 4.13, Make an Image of the Migrated Workstations, on page 66 Section 4.14, Managing Your Traditional ZENworks Installation, on page 66

4.1 Prerequisites

To fulfill the prerequisites for migrating to Configuration Management: 1 Make sure that the version of ZENworks you are migrating from is one of the following: ZENworks for Desktops 4.0.1 ZENworks Desktop Management 6.5 ZENworks 7.x Desktop Management IMPORTANT: For your current installation of a traditional ZENworks system, you must have a Novell eDirectory tree with the ZENworks schema installed and have ZENworks eDirectory objects listed in the tree. The ZENworks Migration Utility cannot be used to create new objects or attributes in Configuration Management that do not exist in your traditional version of ZENworks, but you can use the utility to create new folders in Configuration Management. 2 Install the Configuration Management software to at least one Primary Server with the ZENworks Configuration Management database in order to establish the Management Zone and to provide the target ZENworks database for migrating the eDirectory data. For more information, see the ZENworks 10 Configuration Management Installation Guide.

3 Use ZENworks Control Center to configure the user source for your users so that the eDirectory items that they are associated with allows for a successful migration. For more information on configuring the user source, see User Sources in ZENworks 10 Configuration Management System Administration Reference. If you want to continue using eDirectory as the user source in ZENworks Configuration Management, you must update the version of eDirectory to meet the minimum requirements. For more information on the minimum eDirectory requirements in ZENworks Configuration Management, see Authoritative user source in the ZENworks 10 Configuration Management Installation Guide. However, a user source is not required if you do not have any user associations with traditional ZENworks objects in eDirectory. 4 If you are running a version of eDirectory that is 8.7 or lower, or you have upgraded from Starter Pack 1.0, you should make sure that the LDAP attributes listed in Step 4b are properly mapped because LDAP is used to read existing application attributes during migration. Newer versions of eDirectory automatically map spaces and colons to the newer attribute names. If you have multiple versions of an attribute in your version of eDirectory (one using the colon, and another using a space), it is possible that the automatic mapping functionality will provide the Migration Utility with the version that uses only spaces. However, attributes using colons are the preferred versions for migration. To configure attribute mapping for migrating applications to Configuration Management: 4a In ConsoleOne, select your LDAP Group object, then click the Attribute Mapping tab. 4b Locate the following attributes and map them to the correct name:
Old Attribute Name New Attribute Name
App:Path App:Icon App:Contacts App:Working Directory App:Drive Mappings App:Printer Ports App:Parameters App:Flags App:Startup Script App:Shutdown Script
appPath appIcon appContacts appWorkingDirectory appDriveMappings appPrinterPorts appParameters appFlags appStartupScript appShutdownScript

The Skip saving/loading history option allows you to dramatically improve performance on large migrations by not storing the local history. There are currently no global migration options specific to Management Zone settings. 2 Click Step 4: Zone Settings in the Migration Tasks field. 3 To model the migration, go to the Source eDir Tree panel, then navigate the eDirectory contexts to locate the information to be migrated. To stop listing of the objects in the Source eDir Tree, click. IMPORTANT: The individual components of the Novell Application Launcher settings or Imaging policies are displayed so that you can selectively migrate them, instead of migrating all of the settings or policy information. 4 Repeat Step 3 as necessary to locate and queue all of the information to zone settings that you want to migrate at this time. IMPORTANT: Every item that you queue in the Destination Zone panel is migrated when you click the Migrate Now button. 5 Review your selections in the Destination Zone panel. 6 To delete items from the migration queue, select the items and click the icon. You can use the Ctrl and the arrow keys or Shift and the arrow keys to select multiple items for deletion. Items queued for migration have their icons and texts dimmed. If you select dimmed items for deletion, they are only deleted from the queue. WARNING: If you select colored items (with teal or black text), they are deleted from the ZENworks database and are no longer available in ZENworks Control Center. 7 To migrate all of the dimmed items displayed in the Destination Zone panel, click the Migrate Now button. The following information applies to the Migration Utility during or after the migration process: Focus is immediately moved to the Items to Migrate tab, where you can view the sequential progress of the migration. The Step column displays a progress bar for each item being migrated. The overall progress bar is at the bottom of the screen. The Migration History tab displays all of the items that were migrated. This list is updated dynamically as the items are migrated. You can click back and forth between the Items to Migrate and Migration History tabs during the migration process. You can also right-click anywhere in the tabs panel and select Refresh to refresh the view with items that might not yet be displayed, but are migrated. The Select tab displays all of the migrated objects, with their texts in teal color after being migrated, in both the Source eDir Tree and Destination Zone panels. The teal color persists, so the next time you open the Migration Utility and navigate the Source eDir Tree contexts and Destination Zone folders, you can see what you have previously migrated. Objects that failed migration continue to be displayed with their icons dimmed. Instructions for handling failed migration items are covered in Step 8.

Computer Extensible Policies Group Policy
Extensible policies do not exist in Configuration Management. The following settings are not migrated: Cache User Configuration: Does not exist in Configuration Management. Group Policies Remain in Effect on User Logout: Does not exist in Configuration Management. Group Policy Loopback Support: This is a policy infrastructure option that is now defined for any Group policy when it is assigned to a device. Persist Workstation Settings: Does not exist in Configuration Management.

Scheduled Action Policy

These policies contain scheduled launches of an executable. This functionality is duplicated by using simple applications to perform the same functionality. Therefore, no equivalent policy is created in Configuration Management. Instead, you can create a Directive bundle in ZENworks Control Center to duplicate this functionality. Extensible policies do not exist in Configuration Management. All ZENworks Asset Management inventory data migration is handled by the ZENworks Asset Management migration tool. The traditional pre-ZENworks Asset Management Workstation Inventory data is not migrated because of major differences in database schema. Similar to applications, policies are now assigned to folders, users, and devices, thus eliminating the need for a Search policy.
User Extensible Policies Workstation Inventory

zendmSearchPolicy

zenimgWorkstationPolicy A per-workstation Management Zone setting is not available in Configuration Management for this policy. zeninvDictionaryUpdateP The new ZENworks Asset Management inventory system has no equivalent olicy policy in Configuration Management. zeninvRollUpPolicy The new ZENworks Asset Management inventory system has no equivalent policy in Configuration Management. Roll-up is configurable in ZENworks Control Center for the Management Zones Primary Servers. This policy deals with locating the database for reporting and inventory to write to it. Configuration Management uses a different database for both reporting and inventory, so this policy is not migrated. Configuration Management has no equivalent policy. This policy dealt with reporting in ZENworks 6.5 and ZENworks 7.x. There is no equivalent policy or setting in Configuration Management because reporting is not sent through XML.

ISDEV : error -1024: message string.
This error does not impact the functionality of the bundle in the managed device and the migration is still successful. Action: Ignore the error. Migration Utility hangs during migration Explanation: While migrating AOT applications with more than 500 INI sections to ZENworks Configuration Management, the Migration Utility tool hangs. Action: None. Unable to migrate the iPrint policy Explanation: The iPrint policy configured with the nipp.exe client installer is not migrated to ZENworks Configuration Management because nipp.exe does not support silent installation. Action: In traditional ZENworks, configure the iPrint policy to use the nipp-s.exe or nipp.zip client installer and then migrate. Unable to migrate a Group policy Explanation: If you configure a Group policy in traditional ZENworks by providing the UNC path of the shared folder that requires authentication, then migrate the policy to ZENworks Configuration Management by using the Migration Utility installed on a Windows Vista SP1 device, the migration fails because the Vista device is unable to access the network folder. Action: Do the following: 1. Click Start > Run. Specify system32, then click OK. 2. Right-click cmd.exe, then select Run as administrator. 3. Enter explorer at the command prompt to launch the Explorer window. 4. In the Explorer window, click Tools > Map Network Drive to map the network location. 5. Provide the user credentials, then migrate the policy or application configured with that path. A registry action migrated with certain options fails on the managed device Explanation: If an application with only registry and INI changes and with options such as Create if exists, Delete, Append if existing otherwise create, or Prepend if existing otherwise create configured under the distribution options is migrated as an MSI, the options fail on the managed device.
Action: Perform the following steps to migrate the application as an individual action instead of an MSI: 1. Launch the Migration Utility. 2. Click the Migration Tool Settings icon, then click Application. 3. Select the Migrate distributions options as individual actions option. 4. Migrate the application that has the registry changes to the destination zone. The application is migrated as a Windows Bundle with a Regedit action. Unable to migrate objects that should be uploaded to the content server Explanation: While migrating objects that should be uploaded to the content server, the Migration Utility might encounter an error resulting in the failure of migration. Possible Cause: The Proxy enabled on the device that is hosting the Migration Utility might not be configured to send data in chunks or establish a persistent connection with the server while uploading files to the content server. Action: Use the Web Client Configuration option to configure the settings for uploading files to the content server and try migrating again. For more information, see the Section B.1.8, Web Client Configuration, on page 80. Possible Cause: The connection to the remote server might have failed. Action: Ensure that the File Upload Http Port specified while logging in to the migration destination zone is the same as the port configured on the ZENworks Configuration Management server. Unable to install the migrated Adobe MSI Possible Cause: The Adobe Flash Player plug-in is installed on the device. Action: Perform the following steps on the managed device before deploying the bundle to the device: 1 Open the command prompt. 2 Navigate to the Flash Player plug-in installation directory. The default installation directory is C:\WINDOWS\system32\Macromed\Flash. 3 Do the following to unlock the registry entries of the existing Flash files: If the uninstfl.exe file is available, execute the following command:

E.3 Uploading Objects to the Content Server
While migrating applications that require the content to be uploaded to the content server, the migration might fail. Ensure that the port specified in the File Upload Http Port option while logging in to the migration destination zone matches the port configured while installing the ZENworks Configuration Management server. For information on configuring the port while installing the ZENworks Configuration Management server, see Performing the Installation.
While migrating large applications that should be uploaded to the content server, the connection to the server might be lost, resulting in failure of the migration. Ensure that Get response timeout in the Web Client Configuration is set to None in order to establish a persistent connection with the server. For more information, see Section B.1.8, Web Client Configuration, on page 80. While migrating applications, deselect the Upload to content server option if you do not want to upload the applications to the content server. Deselecting the option migrates the MSI applications as bundles with an Install Network MSI action, which installs the MSI from a network path. By default, the Upload to content server option is enabled. For more information on the option, see Section B.1.2, Applications, on page 78
E.4 Migrating Applications as Actions or MSI
If you use tools such as Snapshot Manager in traditional ZENworks to create complex application objects with multiple changes such as Registry, INI, and File Copy, you should migrate the applications as MSI by disabling the Migrate distribution options as individual actions option. For more information on the migration options, see Section B.1.2, Applications, on page 78. If you use tools such as Snapshot Manager in traditional ZENworks to create application objects with single changes such as Registry, INI, or File Copy, or if the application object must be edited at a later point of time, then you should migrate the application as actions by enabling the Migrate distribution options as individual actions option. If an application is dependent on other applications, review the applications on which the dependency exists and migrate them as MSI or actions based on the requirement, then migrate the dependent applications.