Updated: September 15, 2010
Applies To: Windows Server 2008 R2
When you consider whether to choose migration or synchronization, the size of existing services in your network environment is a major factor. One of the most important large services for most organizations is the mail system. Novell GroupWise mail system and its GroupWare feature (for scheduling, document management, and so on) rely on NDS.
To migrate the mail system from NDS-dependent Novell GroupWise to Microsoft® Exchange Server is a major project that you must implement separately from the MSDSS migration of users, groups, containers, and files. If you want to continue using GroupWise, then long-term directory synchronization is the appropriate strategy.
If you do choose to migrate Novell GroupWise to Microsoft Exchange Server and use directory synchronization during the transition period, you can continue to use GroupWise during the time that NDS is still available. Windows-based client workstations use TCP/IP; therefore, it is easier to migrate if all post office agents (POAs) are set up to use only TCP/IP. Setting up POAs to use only TCP/IP makes it possible for users to retrieve mail as before.
Keep in mind that on a workstation running Windows in a mixed network GroupWise uses the Messaging Application Programming Interface (MAPI), a Microsoft API that supports messaging applications. GroupWise also uses the Windows® Messaging System (WMS), an electronic mail system that makes it possible for you to share information with other people using online services. During a clean install of Windows® 7, you must install MAPI and Windows Messaging on the workstation for GroupWise to work.
GroupWise administration is done from NetWare Administrator 32 (Nwadmin32) and, up to version 5.5, GroupWise does not use DNS directly. GroupWise maintains a separate directory and synchronizes this directory with NDS. Therefore, when you want to remove NetWare from the network, you must also perform a mail system migration.