What Is Services for Netware
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
Services for NetWare Scenarios
To enhance interoperability with NetWare networks, Services for NetWare 5.03 includes Directory Synchronization Services (MSDSS) and the File Migration Utility (FMU):
Directory Synchronization Services — Enables you to migrate and synchronize directory resources from NetWare servers.
File Migration Utility — Enables you to migrate files from NetWare servers.
Services for NetWare 5.03 also provides Active Directory and NDS interoperability. This functionality enables you to add Active Directory to a Bindery or NDS environment. In addition, Services for NetWare provides tools that enable you to troubleshoot connectivity problems, login scripts, and password synchronization. Services for NetWare also provides utilities for monitoring network traffic.
Services for NetWare 5.03 requires Novell Client for Windows.
- File and Print Services for NetWare (FPNW) has been removed from Services for NetWare 5.03.
Directory Synchronization Services (MSDSS) performs the following functions:
Simplifies the integration of NDS/eDirectory and Active Directory.
Reduces directory management overhead by enabling two-way synchronization.
Speeds the migration of NDS/eDirectory and NetWare bindery information to Windows Server 2003.
To enable these capabilities, MSDSS bi-directionally synchronizes data stored in Active Directory with NDS or eDirectory.
To provide interoperability between Windows Server
For more information about the following synchronization methods used by MSDSS, see “How Services for Netware Works:”
The File Migration Utility (FMU) enables you to migrate files from NetWare servers to Windows Server
FMU is integrated with MSDSS and enables the migration of large amounts of file data from supported versions of NetWare over to Windows Server
Before you use FMU to translate the NDS, eDirectory, or Bindery file system rights and permissions to the equivalent rights and permissions in the NTFS file system, you must run a one-time migration of NDS or Bindery directory objects to Active Directory. After you have performed the one-time migration and selected the option to migrate files, a migration log will be created that can be used later by FMU. This migration log serves as a mapping file that maps user objects in NDS to Active Directory.
For each NDS or Bindery volume, FMU calculates the effective rights, starting at the root, and tracks inheritance and filters as the migration continues through the tree. Like Novell NetWare, Microsoft Windows secures folders and files by controlling group and user access. Windows security is supported through the NTFS file system. To help preserve security on transferred NetWare files, you must transfer the NetWare files to an NTFS volume, where the effective rights of the NetWare files are converted to permissions.
If you want to maintain an environment that contains both Active Directory and Bindery/NDS directory services, you can perform a phased migration and run the two systems in parallel. If you choose to run the two systems in parallel, you will be able to perform additional migration tasks (other than synchronizing the two directory services), such as replacing applications that are dependent on Novell services with applications that are compatible with Active Directory.
The following resources contain additional information that is relevant to this section.