Migrate Policy Packages

Policy packages have been reorganized in ZENworks^® Desktop Management. This included creating new policy packages and reorganizing the legacy policies into the new packages. However, you can migrate legacy policy packages from a previous version of ZENworks, such as ZENworks 2, to ZENworks Desktop Management.

If you are upgrading from ZENworks for Desktops 3.x or newer, you do not need to migrate policy packages.

The current policy packages in Desktop Management are:

Container
Server
Service Location
User
Workstation

Migrate From
Select the legacy policy packages to be migrated. You cannot select the new policy packages where the legacy policies will be placed. This is predetermined by Desktop Management.

Include Subcontainers
Include any legacy policy packages that were created in subcontainers.

Preview Only
Displays what the migration will do. This option is selected by default. If you are satisfied with the results, click OK to perform the actual migration. We strongly recommend using this option. It allows you to see exactly which policies are being migrated and how they are being migrated.

Select Policy Package Naming Convention for the New Packages
When you migrate legacy policy packages, you can create new package names or you can retain the old package names. Depending on which option you select, click the appropriate drop-down list to further specify the naming conventions that you want to use.

Create New Package Name
Select Create New Package Name to create a new name. Click the drop-down list to specify how you want to name the new package. The following options are available:

Use the Default Naming Convention
Lets you use the default naming conventions for any new package names. If you choose this option, specify the default names that you want to use for User packages, Workstation packages, and Container packages.

Prompt for User Input
Lets you prompt the user to supply the new package name. If you choose this option, the migration cannot run unattended.

Retain Old Package Name
Select Retain Old Package Name if you want Desktop Management to use the legacy package names for the new package names. If an old package name cannot be retained because you are combining packages, you can specify how the new package should be named. The following options are available:

Use the Default Naming Convention
Lets you use default naming conventions if your package name cannot be retained. If you choose this option, specify the default names that you want to use for User packages, Workstation packages, and Container packages.

Prompt for User Input
Lets you prompt the user to supply the new package name. If you choose this option, the migration cannot run unattended.

Use the Old 9x Package Name
Lets you use the existing 9x package name.

Use the Old NT Package Name
Lets you use the existing NT package name.

Enter a Default Name to Be Used in Naming the Migrated Packages
If you specified Use the Default Naming Convention from either the Create New Package Name or the Retain Old Package Name drop-down list, specify the default names that you want to use for each type of package.

A trademark symbol (^®, ^TM, etc.) denotes a Novell trademark. An asterisk denotes a third-party trademark. For information on trademarks, see Legal Notices.