C.0 Troubleshooting

The following sections explains the scenarios that you might encounter while migrating your traditional ZENworks software to Novell ZENworks 11 Configuration Management SP3.

The schedule of an application is not correctly migrated

Explanation: If an application with an availability schedule configured during daylight saving time is migrated, the schedule is not migrated correctly. For example, if you specify the Start Date as 2/11/08 and the End Date as 10/11/08, the application is migrated with the Start Date as 1/11/08 and the End Date as 9/11/08.
Action: After the migration is completed, use ZENworks Control Center to manually edit the schedule.

Application icons might not be available after migration

Explanation: If an application object is migrated as an MSI bundle to ZENworks Configuration Management, some of the application icons might not be available and the following error is displayed in the logs:
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.
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:

      uninstfl.exe -u

    • If a file with a name matching *FlashUtil.exe, such as NPFSW32_FlashUtil.exe, is available, execute the following command:

      *FlashUtil.exe -uninstallUnlock -u

  4. Deploy the bundle on the managed device.

A manually created user is unable to perform migration

Possible Cause: The user is not configured in eDirectory as a Trustee of the container containing the migration objects.
Action: In addition to providing administrator rights, the user must also be configured as a Trustee of the container containing the objects to migrate. For more information on adding trustees, see the ConsoleOne User Guide.

Unable to view the user associations in the Migration Utility

Explanation: If an application is associated to a user container, the Migration Utility lists the the association at the container level. However, the association applies to the individual users within the container. If you migrate the association, the association for all the individual users within the container is migrated.
Action: None.

How do I enable debug logs

Action: To enable the logs, see TID 3418069 in the Novell Support Knowledgebase..

Unable to use the migrated add-on images

Explanation: Add-on images that are created by exporting applications in traditional ZENworks are not valid in ZENworks Configuration Management. If these add-on images are migrated in combination with a base image or otherwise, they should be deleted.
Action: Manually delete the add-on image from ZENworks Configuration Management.

Migration of applications is slow on a Windows Vista device

Explanation: Migration of AOT or AXT applications to MSI applications is comparatively slower on a Windows Vista device.
Action: None.

Migration of the PXE Menu settings configured in the traditional ZENworks Imaging Server Policy fails

Action: After migrating the traditional ZENworks Imaging Server policy to ZENworks 10 Configuration Management, manually configure the PXE Menu settings:
  1. In ZENworks Control Center, click the Configuration tab.

  2. In the Management Zone Settings panel, click Device Management > Preboot Services.

  3. Configure the desired PXE options.

  4. Click OK.

Unable to migrate an AOT application

Explanation: If the Migration Utility is installed on a device that already has AdminStudio installed, the migration of an AOT application fails with the following error:
Could not locate Admin Studio's AOTAXT Converter. The converter is required to covert an AOT/AXT file to an MSI package.
Action: You must install the Migration Utility on a device that does not have AdminStudio previously installed.

Unable to migrate iPrint policy that does not have the policy setup file associated with it

Explanation: If you choose to migrate an iPrint policy without its setup file, the migration fails with the following error:
No iPrint setup file was found cannot continue.
Action: Perform the following steps on the device from which you want to migrate the iPrint policy without its setup file:
  1. Open the Registry Editor.

  2. Go to HKLM\Software\Novell\ZCM\Migration.

  3. (Conditional) If a String called SkipIPrintClientValidation already exists, ensure that the value of this string is set to false.


    Create a String called SkipIPrintClientValidation and set its value to false.

ZENworks Migration Tool fails during migration of an object that is deleted in the destination zone and throws Internal Server Exception

Explanation: If you migrate an Application, Policy or Device using the ZENworks Migration Utility and delete it, and immediately try to migrate it again, ZENworks Migration tool fails and throws Internal Server Exception.
Possible Cause: Previously deleted object cleanup is still pending on the server.
Action: Try after sometime.