Quest® NDS Migrator

Version 4.3

Release Notes

February, 2008

 


Contents

Welcome to Quest NDS Migrator

New in this Release

Resolved Issues and Enhancements

Known Issues

Upgrade and Compatibility

System Requirements

Global Operations

Getting Started

For More Information

 


Welcome to Quest NDS Migrator

Quest® NDS Migrator offers a project-based step-by-step approach for Novell Directory Services (NDS) systems to Active Directory (AD) migration. The product is designed to facilitate the transition of various object types (and associated files) from the NDS environment to Windows 2000/2003/2008 and Active Directory.

The design of Quest NDS Migrator takes into account that most NDS to AD migrations do not occur as one massive copying of objects. The concept of projects is implemented to allow object migration activities to be broken down into a manageable size of object groupings.

Quest NDS Migrator tracks the groupings of objects that were copied by each project to identify which migrations occurred and when they occurred.

 


New in This Release

 

 

Functionality

Supported On

Installation Installation of Quest NDS Migrator on either Windows 2008 Server or Wndows Vista is not supported.

Migration target

  • Windows 2008 Server

Workstation Updater
  • Windows Vista
Link Updater and Shortcut Updater
  • Windows 2008 Server
  • Windows Vista

 


Resolved Issues and Enhancements

The following is a list of issues addressed and enhancements implemented in this release of Quest NDS Migrator.

 

Feature

Resolved Issue

Defect ID

Attribute Mapping Internet email addresses are no longer mapped by default.

TF#18458

Object name

Size limit for path lengths increased to 450 characters.

TF#35595

Macintosh migrations
Macintosh folders with names that include special characters like \ / * ? " < > | are now migrated correctly.

Note: This issue will still persist for salvaged Macintosh folders with special Macintosh characters. To work around this Netware limitation, one needs to use a Macintosh client to rename the salvaged Macintosh folder and then rename it back again once migration is complete.

CR#192323
Macintosh folder icons and color are now migrated correctly. CR#196788
File and folder migrations During file and folder migration, the wrong file permissions could be applied to the target if the NDS TrusteeID is not unique.

This problem has been corrected.

CR#203373
File synchronization fails to delete read-only files on the target. This has been corrected.

Note: if the logged-in user does not have access to clear the file's read-only attribute then an Access Denied error will be logged.

CR#204414
The "Failed converting SID 0 from ..." error is logged during file migration for each file or folder that has no owner.

Errors are no longer logged against a file or folder that has no owner.

CR#205602
The error "Cannot allocate a temporary directory handle" may be reported when copying files from multiple NDS Servers.

This problem has been corrected.

CR#209574
"NWDSReadObjectDSIInfo failed for [Supervisor]" error is logged during file migration for each file and folder with the [Supervisor] owner.

This problem has been corrected.

CR#210061
Inherited permissions do not get applied from folders above the mapped object.

This problem has been corrected.

CR#224299
User and group migrations Synchronizing group membership may fail unexpectedly while processing large amount of groups.

This problem has been corrected.

CR#212132
CPEGs become unnested after a resync.

This problem has been corrected.

CR#213251
Group synchronization might fail unexpectedly when the Domain Controllers are not in sync.

This problem has been corrected.

CR#226737
Workstation Updater Workstation Updater may fail to get a SID value for an AD object.

This problem has been corrected.

CR#202704
Link Updater and ShortcutUpdater LinkUpdater and ShortcutUpdater limitations (10KB .INI file size and 500 mappings)

The .INI file size limit as been increased to 1MB and the number of mappings to 1000.

CR#205631
LinkUpdater may unexpectedly terminate when running on a multi-processor computer.

This problem has been corrected.

CR#212413
Link Updater crashes or silently exits when it encounters a folder with a path that is 255 characters or longer.

This problem has been corrected.

CR#214274
Link Updater silently exits when processing documents with more than 5000 links.

This problem has been corrected.

CR#218218

Known Issues

The following is a list of issues known to exist at the time of this Quest NDS Migrator release.

 

Feature

Known Issue

Defect ID

Installation

If you install Quest NDS Migrator in a domain that has multiple domain controllers, the group NDSMigratorUsers might be created on the secondary DC. Should this happen, you will receive an error message stating that the NDSMigratorUsers group cannot be found. WORKAROUND: Force replication using native Windows tools and install the database again by running the DBInstaller found in the Quest NDS Migrator install directory.

TF#37987

General Issues

The Import mapping functionality fails to detect whether a machine is in Native mode; therefore, it will not allow you to create Universal Security groups.

TF#37988

Issue with re-distributables option in Autorun. SQL Server Desktop Engine fails to open on Windows 2003. This is a known issue with Microsoft. You can apply Service Pack 3 only to the instances of the Desktop Engine installed by Sqlrun01.msi. For more information about this known issue, refer to: http://support.microsoft.com/default.aspx?scid=kb;en-us;
Q315721 Windows 2003 does not support SQL 2000 SP2 or earlier
http://support.microsoft.com/default.aspx?scid=kb;en-us;329329

TF#37989

Object Migrations

Unable to evaluate boolean value of source attribute "Password Allow Change" errors will occur during object migrations to a domain controlled by a non-English domain controller. TF#37829
Quest NDS Migrator will not display NDS objects starting with < or >. TF#19424

Certain extended ASCII characters will map to common characters. This causes name duplications which result in the failure to migrate some objects. For example, the names Mellor and Méllor will be considered the same name by Active Directory. The first object to be migrated will be created but the second object will be treated as a duplicate. Quest NDS Migrator's collision detection does not recognize this issue.

TF#37990

If the Group SAM Account Name truncation option is turned on and there are two Organizational Roles whose names are identical for the first 20 characters, only one of the two Organizational Roles will be migrated. The second Organizational Role will be treated as a duplicate.

TF#37991

File Migrations

Macintosh files and folders that have the Apple symbol in their name are incorrectly migrated. The migrated file or folder does not appear with an icon and disappears when double-clicked. TF#38689
If the password option selected for user migrations does not meet the password policies on the target, migrated users will not be able to log on to the target. WORKAROUND: Reset the password on the target. TF#35123

Quest NDS Migrator is unable to view the Virtual Server Name of a Microsoft Cluster. The Physical Nodes of the cluster are available, but not the Virtual Name.

TF#37992

Folders or files that end up with a path longer than 260 characters (but no more than 4,256 characters) on the target Windows server can be migrated; however, there no known commercial tools that allow users to view these folders and files with long path names. For more information, refer to the following: http://support.microsoft.com/kb/210631/en-us

Folders or files with paths already longer than 260 characters on the source Netware server cannot be accessed by NDS Migrator.

TF#37993

A migration is still scheduled even if the Windows Administrator password is not provided. In the Schedule Migration dialog box, once you click Schedule the migration is scheduled regardless of whether one enters a Windows Administrator password for the target computer or not. However, the migration will not be able to start without the Administrator password. WORKAROUND: Add the password manually using Scheduled Tasks, one of the native system tools provided by Windows. To access this tool, select Start | Programs | Accessories | System Tools | Scheduled Tasks.

TF#37994

Comments on Mac files are not migrated to the target.

TF#37995

Trustees in the Novell trustee list of a file or folder that have no given rights are translated to explicit deny full-control ACEs in NTFS. Other trustees with given rights are translated to the appropriate allow ACEs in NTFS.

TF#37996

If you are scheduling a remote file migration or scan, you must make sure that the Remote Registry Access is set in order to allow your permissions to access the registry of the remote computer. Otherwise, you will not be able to run the task schedule.

TF#37997

When doing more than one migration using the Update DACL instead of the Replace DACL option, a target Windows file or target Windows folder can end up with both a deny and an allow ACE in its DACL for a trustee. This happens when the trustee has some Netware rights before one migration and the trustee's rights are then set to none prior to a subsequent migration. The presence of both deny and allow ACEs for a trustee is harmless. The deny ACE comes first and blocks any rights that may be granted by the allow ACE. Subsequent updates to the DACL update both ACEs appropriately.

TF#37998

The Exclude Folder page of Project Options does not properly accept folders with certain characters in their path. When the path of a folder contains characters that are not in the current Windows ANSI character set, that folder’s path will not be properly recorded in the list of excluded folders. For example, if your computer uses US English Windows, US English ANSI characters such as µ ¶ ¸ ¹ » ¼ ½ ¾ ¿ À Ê Ç ç é will be correctly recorded in the folder path. However, box drawing characters such as ╝ ╬ ║ ╕ ╢ ▓ ┼ ╔ ╠ are not in the English ANSI character set and will not be correctly recorded in the path. You can review the excluded folder list after a folder is added. If the folder name is not displayed correctly in the list, then it will not be excluded correctly.

TF#37999

In the file migration logs, the number of read-only files and the number of successfully updated files can be reported incorrectly when there are zero-sized files on the source. When a file on the target is successfully overwritten with a zero-length source file, the number of read-only files is incorrectly incremented instead of the number of successfully updated files.

TF#38000

The "Update DACL" file migration option will causes an error in NTDLL.DLL if a target file or folder does not have a DACL. Files and folders with no DACL will not occur if NDS Migrator is used to copy the contents of the files and folders. However, files and folders with no DACL can occur if another file copying tool is used instead. WORKAROUND: The "Replace DACL" option should be used the first time NDS Migrator is used to migrate Netware rights to the files on the target Windows server.

TF#38001

Workstation Updater

If a shortcut path name contains spaces, the shortcut will not be updated as NDS Migrator does not recognize the full path name. TF#37085
If a shortcut path name contains characters from the ANSII extended character set, the shortcut will not be updated. TF#11519
Updating workgroups from the network takes a noticeable amount of time. TF#38003

Workstation Updater does not reliably join workstations to child domains.

TF#38004

Once users have confirmed that drive mappings have been updated, they must manually delete the c:\QuestDriveMap folder. TF#38005
Server Link Updater When a link update job is run, the Server Link Updater will close all instances of .doc, .xls, and .pps files on a server regardless of what shares and folders were targeted for the link update. TF#38006

Link updater fails to update links when Microsoft® PowerPoint is not installed. WORKAROUND: Install Microsoft® Word, Excel, and PowerPoint.

TF#38007

Access Based Enumeration

In order to have ABE functioning as expected, you must set the security in the target root share or the root subfolder under the target share to AUTHENTICATED USERS. In the advanced options for the inheritance you must set AUTHENTICATED USERS to “This Folder only” on that ACL list.

TF#38008

Password Synchronization Utility

If you are running IIS 6.0 you must enable the Web Extensions Active Server Pages in order to run the Password Synchronization Utility. To do this, open the IIS Manager and select the Web Services Extensions folder in the left panel. From the list of extensions that appear in the right panel, select Active Server Pages and change its status by clicking the Allow button.

TF#38009

The Password Synchronization Utility fails to install on a non-English server.

TF#38010


Upgrade and Compatibility

The following should be considered when upgrading Quest NDS Migrator:

General

Application upgrades are not supported. However, database upgrades from older versions of NDS Migrator to Release 4.3 are supported.

Registration

The 4.3 release of Quest NDS Migrator uses a 4.x license key in order to run. If you are upgrading from a 4.x version of NDS Migrator, you do not need to obtain a new key before starting the upgrade process. If you have a version lower than 4.x, you will require a new license key prior to upgrading. Please contact License@quest.com for more information. For updated license information, please see

https://support.quest.com/SUPPORT/index?page=licenseKey

Database Upgrade

It is necessary to update your database. Select the Update option in the DBInstaller dialog box.

Licensing

The 4.3 release of Quest NDS Migrator uses a 4.x license key in order to run. If you are upgrading from a 4.x version of NDS Migrator, you do not need to obtain a new key before starting the upgrade process. If you have a version lower than 4.x, you will require a new license key prior to upgrading. Please contact License@quest.com for more information.

 


System Requirements

Before installing NDS Migrator, ensure your system meets the following minimum hardware and software requirements:

Note: If the NDS Migrator database resides on the same machine as NDS Migrator, SQL Server or MSDE system requirements must be met in addition to the following requirements.

Hardware
  • A 1GHz processor (Recommended 1.5 GHz)
  • 512 megabytes of RAM (Recommended 1.0 GB RAM)
  • 500 megabytes of free disk space for the application. This should exist on a local disk drive rather than a network drive. (Recommended 1 GB free space where Quest NDS Migrator is installed)
  • Monitor - Minimum resolution 1024 x 768, High Color
Network Clients
  • Novell NetWare® Client for Windows 2000 version 4.83 or later. It must be installed and running on the computer where you run Quest NDS Migrator.
Software
  • Source
    The source computer requires Novell Netware 4.x, 5.x, or 6.x, with Novell NDS 4.x, 5.x, or 8.x.
  • Target
    For object migrations, the target computer must be a Windows 2000/2003/2008 Domain Controller (DC) with Microsoft Active Directory (mixed or native mode).
    For data migrations, the target computer must be Windows 2000/2003/2008 running NT file system (NTFS), or the target computer must emulate the windows environment, such as a NETAPP(c) Filer.
  • Console
    The computer where Quest NDS Migrator is installed requires one of the following:
    > Microsoft Windows 2000 (any version) Service Pack 4
    > Windows 2003 Service Pack 2
    > Windows XP Service Pack 2
    > Windows 2003 R2
    In addition:

    > Windows Internet Explorer is required for accessing the Password Synchronization utility.
    > A minimum of Windows 2003 Server Service Pack 1 is needed for ABDE functionality.

  • Remote Computer (Proxy)
    Novell NetWare® Client for Windows 2000 version 4.83 or later must be installed and running on the computer where you run Quest NDS Migrator.
Resource Updating
Database
  • Microsoft® SQL Server 2000 (Service Pack 3)
  • Microsoft® Data Access Components (MDAC) version 2.7
  • Microsoft® Data Engine (MSDE) 2000 (Service Pack 3)
  • Microsoft® SQL Server 2005 (Service Pack 2)
  • Microsoft® SQL Server 2005 Express Edition

 


Global Operations

This section contains information about installing and operating this product in non-English or non-ASCII configurations. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.

This release can be used on systems in different time zones, which are in different languages, and use different regional options. All components of this product must be configured to use the same default system code page. This product limits support to the Western European code page 1252. Other configurations and single-byte encodings may work appropriately, but have not been extensively tested. Multi-byte character data is not supported.

 


Getting Started

Contents of the Release Package

The NDS Migrator release package contains the following products:

  1. Quest NDS Migrator version 4.3
  2. Microsoft® Data Access Components (MDAC) version 2.7
  3. Microsoft® Data Engine (MSDE) 2000 (Service Pack 3)
  4. Product Documentation, including:

Installation Instructions

How to install the product from this CD:

Before you start the installation, it is recommended that you close all the previously open applications.

 


For More Information

Other Document Sources

The complete NDS Migrator documentation suite includes the following:

You can display the online help by selecting an option from the Help menu or by pressing F1.

Contacting Quest Software:

Email info@quest.com
Mail Quest Software, Inc.
World Headquarters
5 Polaris Way
Aliso Viejo, CA 92656
USA
Web

http://www.quest.com

Refer to our Web site for regional and international office information.

Contacting Quest Support:

Quest Support is available to customers who have a trial version of a Quest product or who have purchased a commercial version and have a valid maintenance contract.
Quest Support provides around the clock coverage with SupportLink, our web self-service. Visit SupportLink at http://support.quest.com.

From SupportLink, you can do the following:

View the Global Support Guide for a detailed explanation of support programs, online services, contact information, and policy and procedures.
The guide is available at: http://support.quest.com/pdfs/Global Support Guide.pdf.

 


© 2008 Quest Software, Inc.

ALL RIGHTS RESERVED.

 

This document contains proprietary information protected by copyright. The software described in this document is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software, Inc.

 

If you have any questions regarding your potential use of this material, contact:

Quest Software World Headquarters
LEGAL Dept
5 Polaris Way
Aliso Viejo, CA 92656

 

www.quest.com

Email: legal@quest.com

Refer to our website for regional and international office information.

 

Trademarks

Quest, Quest Software, the Quest Software logo, Aelita, AppAssure, Benchmark Factory, Big Brother, DataFactory, DeployDirector, ERDisk,   Foglight, Funnel Web, I/Watch, Imceda, InLook, IntelliProfile, Internet Weather Report, InTrust, IT Dad, JClass, Jint, JProbe, LeccoTech, LiteSpeed, LiveReorg, NBSpool, NetBase, Npulse, PerformaSure, PL/Vision, Quest Central, RAPS, SharePlex, Sitraka, SmartAlarm, Spotlight, SQL LiteSpeed, SQL Navigator, SQLab, SQL Watch, Stat, Stat!, StealthCollect, Tag and Follow, Toad, T.O.A.D., Toad World, Vintela, Virtual DBA, Xaffire, and XRT are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks used in this guide are property of their respective owners.

 

Disclaimer

The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.