A.3 Policies

Policies that cannot be migrated are filtered so that they are not displayed for migration. The following policies are migrated:

The following are not migrated:

Table A-2 Policy Features Not Migrated to Configuration Management

Feature

Comment

Computer Extensible Policies

Extensible policies do not exist in Configuration Management.

Group Policy

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.

User Extensible Policies

Extensible policies do not exist in Configuration Management.

Workstation Inventory

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.

zendmSearchPolicy

Similar to applications, policies are now assigned to folders, users, and devices, thus eliminating the need for a Search policy.

zenimgWorkstationPolicy

A per-workstation Management Zone setting is not available in Configuration Management for this policy.

zeninvDictionaryUpdatePolicy

The new ZENworks Asset Management inventory system has no equivalent 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 Zone’s Primary Servers.

zenlocDatabaseLocationPolicy

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.

zenlocSMTPHostPolicy

Configuration Management has no equivalent policy.

zenlocXMLTargetPolicy

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.

zenwmWorkstationImport

Although it is technically possible to migrate a workstation import policy to a Management Zone setting, it is simply easier to set the few global zone settings manually in ZENworks Control Center to migrate them. In Configuration Management, you can set a registration rule on any folder level hierarchically, but in ZENworks 7.x you had to set a Workstation Import policy on a Server Package that was associated to one or more servers. There is not a simple one-to-one mapping for these relationships. It is easier for the administrator to define these rules manually.

zenwmWorkstationRemoval

There is no policy for workstation removal in Configuration Management.

zenwmZENConfigPolicy

This policy applies to the previous ZENworks agent. The new ZENworks Adaptive Agent is controlled by new Management Zone settings and behave differently.

Dynamic Local User Policy

The Volatile User Cache setting is not migrated. You can edit the migrated policy in ZENworks Control Center to do the following:

  1. Select the Enable Volatile User Cache option.

  2. In the Cache Volatile User for Time Period option, specify the number of days to cache the volatile user account on the device.

For more information on editing the policy, see Editing Policies in the ZENworks 11 SP2 Configuration Policies Reference.