Migration from Novell GroupWise to Exchange 2003 Server

Preparing the Novell GroupWise Migration Environment

Prerequisites

Ensure that the connector server meets the following requirements:

•	Is running Microsoft Windows Server 2003 • Has network connectivity to the server running Novell GroupWise • Can resolve the name of the server running Novell NetWare

Ensure that the server running Novell NetWare and Novell GroupWise has the following software installed:

•	Novell NetWare 3.x or later
•	Novell NetWare Administrator
•	Novell GroupWise 4.1 or later

To install Novell NetWare Client for Windows

1.	On your Novell NetWare Client CD, open the \Winnt\i386 directory and double-click the SetupNW.exe file.
2.	In the Software License Agreement dialog box, read the license agreement carefully, and if you agree with the terms of the license agreement, click Yes.
3.	In the Novell Client Installation dialog box, click Typical Installation, and then click Install.
4.	When the installation is complete, click Reboot to restart your server.   Figure B.1   Installing Novell NetWare Client for Windows

To test Novell NetWare Client for Windows

1.	After the server restarts, press CTRL+ALT+DEL. When the Novell Login dialog box appears, enter the name of your Novell NetWare administrator account in User Name and the corresponding password in Password, and then click Advanced.
2.	On the NDS tab, click Trees, select your Novell Directory Service (NDS) tree from the Tree dialog box, and then click OK. Click Contexts, and then select the appropriate context for your NetWare administrator account. Click Servers, and then select the Novell NetWare server that you want to use to authenticate your Novell NetWare account.
3.	Click the Windows tab and, under Local username, type Administrator. In the From list, select the name of your Windows domain. In the following procedures, the Windows domain name is CONTOSO.
4.	Click OK.
5.	If a Windows Workstation dialog box appears, enter the password for your Windows administrator account in Password, and then click OK.
6.	Start Windows Explorer, open My Network Places, open Novell Connections, and verify that your preferred NetWare server is listed as a node.
7.	Open the NetWare server (for example, NWServer01), open the SYS volume, open \PUBLIC, open \Win32, and then start Novell NetWare Administrator by double-clicking NWAdmn32.exe. If a File Download dialog box appears warning you that some files can harm your computer, click Open.
8.	If a Welcome to NetWare Administrator message appears, click Close. Verify that NetWare Administrator starts and displays information from the NDS context of the Novell NetWare server.   Figure B.2   Verifying Novell NetWare connectivity
9.	Close the NetWare Administrator program.

To install Novell GroupWise Windows Client

1.	Start Windows Explorer and start d:\client\Win32\Setup.exe from your Novell GroupWise CD (where d: is the drive letter for your CD drive).
2.	In the GroupWise 5.x message box informing you that the Windows Messaging System must be installed, click Continue.
3.	In the Windows Messaging System dialog box, select Leave Windows Messaging System as it is, and then click Next.
4.	On the Welcome page, click Next.
5.	On the Setup Options page, click Standard Install, and then click Next.
6.	On the Destination Directory page, accept the default path of c:\Novell\GroupWise, and click Next. If you would like to change the installation path, click Browse, and select the target directory in the Choose Directory dialog box.
7.	On the Select Optional Components page, accept the default selections, and click Next.   Figure B.3   Installing Novell GroupWise 5.5 Client
8.	On the Select Program Folder page, accept the default program group, GroupWise 5, and click Next.
9.	On the Select Startup Folder Software page, ensure that no tools are selected, and then click Next.
10.	On the Language Selection page, select English, and click Next.
11.	On the Start Copying Files page, click Next.

To install the Novell GroupWise API Gateway on a Novell NetWare server

1.	At the System Console, type NWConfig, and then press ENTER.
2.	On the Configuration Options page, select Product Options, and press ENTER.
3.	Select Install A Product Not Listed, and press ENTER again.
4.	Ensure that the floppy disk containing the API Gateway files is inserted in drive A: on the NetWare server, and then, in the NetWare Configuration program, press ENTER.
5.	The API Gateway Installation screen appears. Change the Domain Path and the Gateway Directory if required, and then select Install and press ENTER to continue.   Figure B.4   Installing the Novell GroupWise API Gateway
6.	In the NetWare Configuration screen that appears after the installation is complete, press ESC twice, and then press ENTER to exit the NetWare Configuration program.
7.	Insert the floppy disk with the files for Patch 2 for the GroupWise version 4.1 API for Netware Loadable Module (NLM) into drive A, and then, on the NetWare System Console, type load A:\PINSTALL.NLM and press ENTER.
8.	In the API Gateway Installation screen, ensure that the settings Domain Path, Gateway Directory, Gateway NLMs, Shared NLMs, and Load Script match your API Gateway configuration. Select Install and press ENTER. A message box appears notifying you that NGWAPI.PRM already exists and will be moved to the \SAVE directory. Press ENTER to continue and install the gateway files. The installation completes automatically.
9.	At the System Console, type edit and press ENTER, and then, in the NetWare Text Editor, specify the path and file name for the gateway's NGWAPI.PRM file (for example, SYS:\API41\NGWAPI.PRM), and then press ENTER again.
10.	Scroll down to the line beginning with /Home- and ensure that it points to the gateway directory (for example, /Home-SYS:\Public\Grpwise\Domain\Wpgate\API41). In an installation without Patch 2 for API NLM, you must correct the default /Home- line manually.
11.	Find the line beginning with ;/Group and remove the semicolon in front of it to activate the inbound group expansion.
12.	Press ESC. When you are prompted to save the changes, select Yes, and then press ENTER.
13.	Press ESC and ENTER to exit the text editor.

To configure the API Gateway for Exchange 2003

1.	Log on to your future Exchange 2003 server, and start the Novell NetWare Administrator program (SYS:\Public\Win32\NWAdmn32.exe). If a File Download dialog box appears warning you that some files can harm your computer, click Open.
2.	If a Welcome to NetWare Administrator dialog box appears, click Close. In NetWare Administrator, on the View menu, click Set Context.
3.	In the Set Context dialog box, under Tree, select your NDS tree (for example, CONTOSO) and under Context, select [Root]. Click OK.
4.	Double-click the GroupWise node and then select the GroupWise domain object where you want to install the gateway (for example, CONTOSO_DOM).
5.	Right-click the domain object (for example, CONTOSO_DOM) and then click Create.
6.	In the New Object dialog box, double-click GroupWise Gateway/Internet Agent.
7.	In the Create GroupWise Gateway/Internet Agent dialog box, specify the following information (leave the remaining settings at their defaults), and then click Create: • Gateway Name - Use a descriptive, unique name within the domain (for example, Exchange Gateway) that identifies the gateway. NetWare Administrator prevents the creation of gateway objects with duplicate names. • Gateway Home Directory - Select the directory that you specified during the installation of the API Gateway (for example, API41). • Gateway Type - API • Version - 4.x (Note that an API Gateway for GroupWise 5 or later does not exist.) • Platform - NetWare Loadable Module (It is recommended that you use the NLM version of the API Gateway with Microsoft Exchange Connector for Novell GroupWise.) • Define Additional Properties - Select the corresponding check box to define further settings.   Figure B.5   Creating the Novell GroupWise API Gateway
8.	The GroupWise Gateway/Internet Agent:Exchange Gateway dialog box appears next. Click Optional Gateway Settings, and then, under Directory Sync/Exchange, select Exchange to enable directory synchronization with Exchange 2003. Connector for Novell GroupWise controls the synchronization process.
9.	To support delivery reports and other status messages, click Yes under Convert Status To Messages.
10.	In the Outbound Status Level list, click Full, and then click Required Parameters to switch to the Required Parameters tab.
11.	Correct the information displayed under Gateway File Paths to match your API Gateway installation. You must specify absolute NetWare paths in the form <Server Name>/<Volume>:\<Path> (for example, NWSERVER01/SYS:\PUBLIC\GRPWISE\DOMAIN\WPGATE\API41).
12.	In the Addressing Format list, click Component, and then click OK to complete the configuration. The Exchange Gateway configuration object should now be listed in the NetWare Administrator view beneath the GroupWise domain object.   Figure B.6   Setting required parameters for the Novell GroupWise API Gateway

Note :

In the gateway properties, under Gateway Time Settings, you can decrease the value for Idle Sleep Duration to one second to avoid delays in manual directory synchronization. The API Gateway checks its API_IN directory for inbound messages in intervals according to the Idle Sleep Duration setting. The default value is 30 seconds.

To create an external foreign domain for Exchange 2003

1.	In NetWare Administrator, open the Tools menu, and then select GroupWise View. Expand the GroupWise domain where the API Gateway for Exchange 2003 is installed (for example, CONTOSO_DOM).
2.	Right-click the gateway object (for example, Exchange Gateway), select Create, and then, in the Create External Object dialog box, select External Domain.   Figure B.7   Creating an external domain for an Exchange 2003 organization
3.	Under External Domain Name, type Exchange. This is the default domain name assigned to Exchange users. You must change the proxy address generation rules if you choose a different name.
4.	Under Domain Type, select External Foreign.
5.	Ensure that Version is set to 4.x (because the API Gateway is version 4.1), and set Time Zone to the time zone of the Exchange 2003 server that runs Connector for Novell GroupWise. Under Link To Domain, list the API Gateway's GroupWise domain (for example, CONTOSO_DOM).
6.	Click Create and then verify that a foreign domain object is created in the GroupWise tree.
7.	Right-click the API Gateway's GroupWise domain (for example, CONTOSO_DOM), and then select Link Configuration.
8.	In the link configuration tool, right-click the newly created external domain (for example, Exchange), and then select Edit.
9.	In the Link Type list, select Gateway.
10.	In the Gateway Link list, ensure that the API Gateway that connects the GroupWise domain to Exchange 2003 is listed (for example, Exchange Gateway), and then click OK.   Figure B.8   Creating a link to the external domain for an Exchange 2003 organization
11.	Close the link configuration tool. In the Links Have Changed dialog box, click Yes to save the link changes for the GroupWise domain.

To set connector permissions in Novell NetWare

1.	In the NetWare Administrator View, right-click the organizational unit in which you want to create the gateway account, and then select the Create command.
2.	In the New Object dialog box, double-click User. In the Create User dialog box, under Login Name, type Exchange, under Last Name, type Server, and then select the Define Additional Properties check box.
3.	Click Create, and then, in the User : Exchange dialog box, click Password Restrictions.
4.	Clear the Allow User To Change Password check box, select Require A Password, verify that the displayed Minimum Password Length matches your company's security policies, and then click Change Password.
5.	In the Change Password dialog box, under New Password and Retype New Password, type a password, and then click OK.   Figure B.9   Creating a Novell NetWare account for Connector for Novell GroupWise
6.	Click Rights To Files And Directories, and then, under Volumes, click Show. In the Select Object dialog box, select the NetWare volume where you installed the API Gateway (for example, NWSERVER01_SYS)—you might need to navigate through the NDS tree to find the server—and then click OK.
7.	If a NetWare Administrator dialog box appears informing you that there are a large number of directory entries on this volume, click Yes.
8.	Under Files And Directories, click Add, and then navigate through the directories to select the API Gateway's root directory (for example, NWSERVER01/SYS:\mail\gwdom\wpgate\API41). Grant the Exchange account all rights to this directory (except Supervisor and Access Control), and then click OK.
9.	To create the NTGATEWAY group, right-click the organizational unit, and select Create.
10.	In the New Object dialog box, double-click Group. In the Create Group dialog box, type NTGATEWAY.
11.	Select the Define Additional Properties check box, and then click Create.
12.	Click Members, click Add to select the connector account (for example, Exchange) in the Select Object dialog box, and then click OK.   Figure B.10   Creating the NTGATEWAY group for Connector for Novell GroupWise
13.	Click OK to close the Group : NTGATEWAY dialog box. Note : It is a good idea to log on to Novell NetWare manually using the connector's NetWare account to test access to the API Gateway directory. You must be able to create, read, write, and delete files. If Connector for Novell GroupWise cannot connect to NetWare, the Router for Novell GroupWise service reports the following error in the application event log (Event ID 5017): "Error occurred when logging on NetWare server. The system error code is 1317. The specified user does not exist."

To start and test the API Gateway

1.	At the System Console of your NetWare server, type API, and press ENTER to start the API Gateway's NLM. Note : The API.ncf file is written during the installation of Patch 2 for API NLM. Without the patch, you cannot use the API command to start the gateway. If you do not have the patch, start the API's Gateway NLM using the following command: load <Volume:\Path>\NGWAPI.NLM (for example, load SYS:\API41\NGWAPI.NLM).
2.	On your workstation, start the Novell GroupWise client and log on to your Novell GroupWise mailbox. Compose a new message, address it to Exchange.First Administrative Group.Administrator, and then send it. Note : You cannot perform this step directly on the Exchange server because the MAPI subsystem has not been prepared yet. The Novell GroupWise client requires MAPI, and the MAPI subsystem is installed during the installation of Exchange Server 2003. If you are performing these steps in a test environment without a separate workstation, perform the API Gateway test after you install Exchange 2003.
3.	The API Gateway should place the message body in form of a .bdy file in the \ATT_OUT directory, and the message header should be in an .api file in the \API_OUT directory.
4.	Copy the .bdy file into the \ATT_IN directory. (It is important to copy the message body before you copy the header.)
5.	Open the .api file in Notepad and change the mail header information, as shown in the following sample listing (your sender and recipient information might be different): WPC-API= 1.2; Header-Char= T50; Msg-Type= MAIL; From= LN= admin; S= admin; ; To= WPPONUM= 1; WPUNUM= 1; CDBA= 0001:0001; ; All-To= WPPONUM= 1; WPUNUM= 1; ; Msg-Id= 39B424B2.CFE6.0001.000; Subject= API Gateway Test; < further text >
6.	Save the .api file in \API_IN. It is convenient to use the original file name, although the file name and extension actually do not need to be retained.
7.	On the Novell GroupWise client, verify that you have received the test message. For subsequent tests, you must copy the .bdy file into the \ATT_IN directory again before you save the .api file in \API_IN.
8.	After you have finished your tests, delete the .bdy and .api files from the API Gateway directory.   Figure B.11   Testing the Novell GroupWise API Gateway

Installing and Configuring Connector for Novell GroupWise

After you configure your Novell GroupWise environment, you can install and configure Connector for Novell GroupWise on an Exchange 2003 server. This includes installing the connector, which you can do as part of the server setup or afterwards, when you start the Exchange Setup program on a server where Exchange 2003 is already installed. For the purposes of these instructions, it is assumed that you are performing the connector installation during the initial server setup.

Prerequisites

Ensure that your environment meets the following requirements:

•	You already have an existing Microsoft Windows® network, including an Exchange organization, and the Active Directory® directory service is deployed.
•	You have Exchange Administrator permissions to install an Exchange 2003 server in the Exchange organization.
•	In Exchange System Manager, you have selected the Display routing groups and Display administrative groups options on the properties page for the organization object.

Ensure that the server on which you install Exchange 2003:

•	Is running Windows Server 2003.
•	Has network connectivity to the Novell NetWare server running the Novell GroupWise API Gateway.
•	Can resolve the name of the Novell NetWare server.
•	Has Novell NetWare Client for Windows installed.
•	Lists you as a member of the Administrators group on the server on which you install Exchange 2003.

To install Exchange 2003 with Connector for Novell GroupWise

1.	Insert the Exchange 2003 CD into the CD-ROM drive of a computer running Windows Server 2003.
2.	At a command prompt, type cd e:\setup\i386, where e is the drive letter for the CD-ROM drive.
3.	Type setup.exe and press ENTER.
4.	On the Microsoft Exchange Installation Wizard Welcome page, click Next.
5.	On the License Agreement page, if you agree with the terms of the license agreement, click I agree, and then click Next.
6.	On the Product Identification page, enter your CD key and then click Next.
7.	On the Component Selection page, in the Action drop-down list next to Exchange 2003, click Custom.
8.	In the Microsoft Connector for Novell GroupWise drop-down list, click Install, and then click Next.   Figure B.12   Installing Connector for Novell GroupWise
9.	If you are installing your first Exchange 2003 server, an Installation Type page appears. Ensure that Create a new Exchange Organization is selected, and click Next.
10.	If you are creating a new Exchange organization, on the Organization Name page, enter an organization name, such as Contoso, and click Next.
11.	On the Licensing Agreement page, if you agree, click I agree that I have read and will be bound by the license agreements for this product, and then click Next.
12.	On the Component Summary page, ensure that Connector for Novell GroupWise is selected, and then click Next.
13.	If a Microsoft Exchange Installation Wizard message box appears informing you that your domain has been identified as an insecure domain for mail-enabled groups with hidden distribution list membership, click OK.
14.	After Setup completes successfully, click Finish.

To enable and customize Novell GroupWise proxy addresses

1.	Start Exchange System Manager: On the Start menu, point to All Programs, point to Microsoft Exchange, and then click System Manager.
2.	Expand Recipients, and then click Recipient Policies.
3.	In the details pane, right-click Default Policy, and then click Properties. You can also create a new recipient policy.
4.	On the policy's E-Mail Addresses (Policy) tab, select the GWISE check box (this enables the address), ensure that the GWISE address entry is selected, and then click Edit.
5.	In the Address box, modify the address format. For example, you can set the address format to Exchange.First Administrative Group.&d. A user whose display name is Birgit Seidl receives a Novell GroupWise address of: Exchange.First Administrative Group.Birgit Seidl. For more information about placeholders in GWISE address generation rules, see Chapter 3, "Interoperating with and Migrating from Novell GroupWise Messaging Infrastructures."
6.	After you configure the address formula, click OK.   Figure B.13   Customizing GWISE proxy address generation
7.	In the Default Policy Properties dialog box, click OK.
8.	A message box appears asking whether you want to update all corresponding recipient e-mail addresses to match the new addresses. To run the Recipient Update Service immediately, click Yes. To update the addresses the next time the Recipient Update Service runs, click No. Non-Exchange addresses are always updated, even if you made manual changes to specific addresses.
9.	Wait for the Recipient Update Service to populate the Exchange address lists. The time required to populate the lists varies depending on the update interval set on the service.

To configure Connector for Novell GroupWise

1.	In Exchange System Manager, expand Administrative Groups, expand Routing Groups, and expand the First Routing Group. Expand the Connectors container, right-click Connector for Novell GroupWise, and then click Properties.
2.	On the General tab: 1. In the API Gateway Path box, type the full path to your Novell GroupWise API Gateway directory in Universal Naming Convention (UNC), including the server name. For example: \NWSERVER01\SYS\Mail\GWDom\WPGate\API41. 2. Under Netware Account, click Modify. Type the account name in the NetWare Account box (for example, Exchange). Under Password and Confirm Password, enter the password that was defined in NetWare Administrator. 3. Under Message Size specify a maximum size for messages that are allowed to pass this Connector for Novell GroupWise instance, or accept the default setting of No Limit. 4. In the Delivery Order list, choose the order in which messages are to be delivered from Exchange 2003 to Novell GroupWise. The order you specify controls the sequence in which Exchange messages are placed in the MTS-OUT queue by the Exchange message transfer agent (MTA), and hence the sequence in which messages are delivered to the API Gateway. The options are:  - Priority   High priority messages, such as urgent messages, are delivered to the outbound queue first. This is the default setting.  - FIFO   Messages are delivered to the outbound queue on a first in, first out (FIFO) basis.  - Size   Smaller messages are delivered to the outbound queue before larger messages.   Figure B.14   Connector for Novell GroupWise General tab settings
3.	On the Address Space tab: 1. Click Add to add the address space for Novell GroupWise. 2. On the Add Address Space tab, click GWISE, and then click OK. 3. On the Novell GroupWise Address Space Properties tab, in the Address box, type * to allow all users to connect to Novell GroupWise using Connector for Novell GroupWise, and then click OK.   Figure B.15   Configuring the GWISE address space
4.	Click OK to close the Connector for Novell GroupWise Properties dialog box and apply the settings.

To start Connector for Novell GroupWise

1.	Start the Services tool: Click Start, point to All Programs, point to Administrative Tools, and then click Services.
2.	Right-click Microsoft Exchange Connector for Novell GroupWise, and then click Start.
3.	Verify that Connector for Novell GroupWise starts successfully, and then close the Services tool.   Figure B.16   Starting Connector for Novell GroupWise

Configuring Directory Synchronization

After you configure Connector for Novell GroupWise, you can synchronize directories between Novell GroupWise and Exchange 2003 (Active Directory). It is recommended that you test the directory synchronization process manually to ensure that everything works as expected.

Prerequisites

Ensure that your environment meets the following requirements:

•	You have Exchange Administrator permissions.
•	You have network connectivity to the Novell NetWare server running Novell GroupWise.
•	You can resolve the name of the Novell NetWare server running Novell GroupWise.
•	You have installed and configured the Novell GroupWise client software.
•	You have installed and configured Connector for Novell GroupWise.

To configure directory synchronization with Novell GroupWise

1.	In Exchange System Manager, right-click Connector for Novell GroupWise, and then click Properties.
2.	On the Import Container tab: 1. To specify the Active Directory container (or organizational unit) to which Novell GroupWise users are imported, click Modify. It is recommended that you create a special organizational unit for all of your Novell GroupWise users and select that organizational unit here. 2. On the Choose a container tab, browse to the container to which you want to import Novell GroupWise users. Click the container, and then click OK. Note : You might receive an error message that reads, "The machine account must be granted permission to create and modify recipients in the selected import container. Continue?" If you receive this error message, click Yes. This is necessary for directory synchronization from Novell GroupWise to Exchange 2003 to work. When you click Yes, you add the computer account with the permissions required to manipulate objects in the selected container. 3. In the When replicating a mailbox whose primary Windows account does not exist in the domain list, choose one of the following options for Active Directory to use when new users are imported:  - Create a disabled Windows user account  - Create a new Windows user account  - Create a Windows contact This setting applies only to new users. If you change this setting later, it does not affect Novell GroupWise users who are already replicated to Active Directory. If you are not sure which option to choose, click Create a disabled Windows user account or Create a Windows contact. Click Create a new Windows user account only if Novell GroupWise users are logging on to the Windows domain. 4. Under Filtering, choose one of the following options to determine which GroupWise directory entries to replicate to Active Directory:  - Import all directory entries  - Only import directory entries of these formats  - Do not import directory entries of these formats The default setting, Import all directory entries, imports all GroupWise directory objects with a visibility set to System in GroupWise without applying any filters. The remaining two options allow you to define a filter when you click the New button to display the Import Filter dialog box. In the Import Filter dialog box, you can use wildcard characters (asterisk (*) and question mark (?)) to create your filter, where an asterisk denotes any number of characters of any value, and a question mark denotes one character of any value. For example, the following filter affects only the recipients at CONTOSO_PO in the CONTOSO_DOM domain: CONTOSO_DOM.CONTOSO_PO.*   Figure B.17   Configuring inbound directory synchronization
3.	On the Export Containers tab: 1. To specify which groups or organizational units to export from Active Directory to the Novell GroupWise directory, click Add. 2. On the Choose a container tab, click the organizational unit that you want to export to the Novell GroupWise directory, and then click OK. Note : You might receive an error message that reads, "The machine account must be granted permission to read the deleted recipients in the selected domain. Continue?" If you receive this error message, click Yes. This is necessary for directory synchronization from Novell GroupWise to Exchange 2003 to work. When you click Yes, you add the computer account with the permissions required to manipulate objects in the selected container. 3. Repeat the preceding two steps for each organizational unit that you want to export. Nested organizational units are not selected for export if you select the parent organizational unit. You must select each organizational unit individually.   Figure B.18   Selecting organizational units to export
4.	On the Dirsync Schedule tab: 1. In the Exchange-GroupWise directory update schedule list, select the schedule for directory synchronization. Connector for Novell GroupWise performs the directory synchronization. Do not schedule synchronization during peak traffic hours, because it can slow message throughput. If your directory information changes infrequently, schedule synchronization for once a day. If your directory information changes frequently, schedule synchronization for two or more times a day. 2. Click Customize to schedule synchronization for a period other than those provided by default in the Exchange-GroupWise directory update schedule list.   Figure B.19   Selecting a synchronization schedule
5.	Click OK to close each dialog box.

To test directory synchronization manually

1.

In Exchange System Manager, right-click Connector for Novell GroupWise, and then click Properties.

2.

On the Dirsync Schedule tab: 1. Under Exchange to GroupWise directory synchronization, click Immediate full reload. In the Exchange System Manager message box informing you that a process has been started to synchronize the directories, click OK. This process synchronizes directory objects from Active Directory to the Novell GroupWise directory. 2. Under GroupWise to Exchange directory synchronization, click Immediate full reload. Again, a message box appears informing you that directory synchronization has begun. This process synchronizes directory objects from the Novell GroupWise directory to Active Directory. Click OK.

Installing and Configuring Calendar Connector in a Novell GroupWise Environment

Use the following procedures to configure Microsoft Exchange Calendar Connector so that users using either Exchange or Novell GroupWise can access each other's free/busy information. You install Calendar Connector on a server running Exchange. The most straightforward option is to install Calendar Connector on the server running Connector for Novell GroupWise.

Prerequisites

Ensure that the server on which you install Calendar Connector meets the following requirements:

•	The server is running Exchange Server 2003.
•	The server running Exchange 2003 has a local replica of the SCHEDULE+ FREE BUSY public folder.
•	The server is part of the same routing group as the server running Connector for Novell GroupWise.
•	You have Exchange Administrator permissions, and you are a member of the Administrators group on the computer on which you install Calendar Connector.
•	You have network connectivity to the Novell NetWare server running the Novell GroupWise API Gateway.

To install Calendar Connector

1.	Insert the Exchange Server 2003 CD into the CD-ROM drive of the server running Exchange 2003.
2.	At a command prompt, type cd e:\setup\i386, where e is the drive letter for the CD-ROM drive.
3.	Type setup.exe, and then press ENTER.
4.	On the Microsoft Exchange 2003 Installation Wizard Welcome page, click Next.
5.	On the Component Selection page, in the Action list next to Microsoft Exchange, click Change.
6.	In the Action list next to Microsoft Exchange Messaging and Collaboration Services, click Change.
7.	In the Microsoft Exchange Calendar Connector list, click Install, and then click Next.   Figure B.20   Installing Calendar Connector
8.	On the Installation Summary page, verify your installation choices, and then click Next.
9.	After the installation is complete, click Finish.

To add a local replica of the SCHEDULE+ FREE BUSY public folder

1.	In Exchange System Manager, expand Administrative Groups, expand the administrative group that contains the server running Exchange with Calendar Connector (for example, First Administrative Group), and then expand Folders.
2.	Expand Public Folders. If you do not see the SCHEDULE+ FREE BUSY public folder, right-click Public Folders, and then click View System Folders.
3.	Expand Public Folders, expand SCHEDULE+ FREE BUSY, right-click the public folder that refers to your administrative group that contains the Exchange server running Calendar Connector (for example, EX:/o=Contoso/ou=First Administrative Group), and then click Properties.
4.	On the Replication tab, click Add.
5.	On the Select a Public Store page, select the server running Exchange 2003 with Calendar Connector, and then click OK.
6.	In the Public folder replication interval list, click Always Run. This causes replication to occur whenever there is a change in free/busy information. Click OK.   Figure B.21   Configuring free/busy information replication

To configure Calendar Connector

1.	In Exchange System Manager, expand Administrative Groups, expand the administrative group that contains the server running Exchange with Calendar Connector (for example, First Administrative Group), expand Routing Groups, expand the routing group in which you installed Calendar Connector (for example, First Routing Group), expand Connectors, right-click Calendar Connector, and then click Properties.
2.	On the General tab: 1. Next to the Connector used to import users into Active Directory box, click Modify. 2. In the Select Exchange Notes or Groupwise Connector dialog box, select the Connector for Novell GroupWise instance that is used to connect to the Novell GroupWise API Gateway, and then click OK. 3. In the Number of days of free/busy information to request from foreign calendars box, enter the number of days that users are able to see free/busy information for users on the foreign messaging server. Free/busy information beyond the number of days specified is not retrieved by Calendar Connector and appears as free, even if meetings are scheduled during this time. Remember that the maximum value for GroupWise is 389 days. 4. In the Maximum age in minutes of foreign free/busy data in Exchange that can be used without querying the foreign calendar box, enter the age limit for free/busy information in minutes. If the free/busy information is beyond the specified number of minutes and a user requests the information, Calendar Connector queries the non-Exchange messaging system for updated data. If the free/busy information is within the specified number of minutes, Calendar Connector uses the current free/busy information. 5. In the Maximum number of seconds to wait for response from foreign calendars box, enter the number of seconds that you want Calendar Connector to wait for a response after it requests an individual user's free/busy information. Set this to a low number, because each recipient on a meeting request is handled in turn, and a long response interval can cause the mail client to stop responding as it proceeds down the list of recipients.   Figure B.22   Setting the General tab Calendar Connector options
3.	On the Calendar Connections tab: 1. Click New. 2. In the Calendar Type dialog box, click Novell GroupWise, and then click OK. 3. In the GroupWise Calendar Connection dialog box, in the GroupWise API Gateway box, type the domain and gateway name of the Connector for Novell GroupWise that interfaces with the API Gateway. Do not include the certifier information. For example, if your Novell GroupWise domain name is CONTOSO_DOM, and the API gateway name is Exchange Gateway, then type CONTOSO_DOM.Exchange Gateway. 4. Click OK.   Figure B.23   Configuring the calendar connection to Novell GroupWise
4.	On the Schedule tab, click Always. This causes Calendar Connector to create a free/busy record for Novell GroupWise recipients in the Exchange public folder. This happens every 15 minutes for new recipients. Alternatively, click Selected times to specify a custom time for the connector to create new records in the server's public folder. Click OK.

To start the Calendar Connector service

1.	Open the Services Microsoft Management Console (MMC) snap-in: Click Start, point to All Programs, point to Administrative Tools, and then click Services.
2.	In the details pane, right-click Microsoft Exchange Calendar Connector, and then click Start.
3.	The default startup type for Calendar Connector is manual. You should change the startup type to Automatic. To do this, right-click Microsoft Exchange Calendar Connector, and then click Properties. In the Startup type list, click Automatic, and then click OK. The next time the server starts, the Calendar Connector service starts automatically.   Figure B.24   Starting Calendar Connector

Migrating from Novell GroupWise to Exchange Server 2003

The following procedures explain how to migrate a group of users from Novell GroupWise to Exchange 2003. The guidelines are recommended for most migrations, and consist of extracting data from the server running Novell GroupWise and immediately importing it into Exchange 2003. To migrate data from Novell GroupWise to Exchange 2003, the Exchange Migration Wizard requires access to the mailbox for each user who is to be migrated. Your users must grant full proxy access to their mailboxes using the Novell GroupWise client.

Prerequisites

Ensure that the server on which you run the Exchange Migration Wizard meets the following requirements:

•	The server is running Exchange Server 2003.
•	If you have configured Connector for Novell GroupWise and directory synchronization, stop the Connector for Novell GroupWise service. This is necessary to prevent directory synchronization from propagating address list changes before you verify that the migration is successful.
•	You have installed and configured the Novell GroupWise client software. It is recommended that you install Novell GroupWise 5.2.5 on the migration server.
•	You have network connectivity to the Novell NetWare server running Novell GroupWise. It is recommended that you install Novell NetWare 4.8 on the migration server.
•	You have administrative permissions in Exchange 2003, Novell NetWare, and Novell GroupWise.

To grant full proxy access to a user mailbox using the Novell GroupWise client

1.	Start Novell GroupWise: Click Start, point to All Programs, point to GroupWise 5, and then click Novell GroupWise.
2.	On the Tools menu, click Options, and then double-click Security.
3.	On the Proxy Access tab, add the account that is being used to migrate the mailbox into the Access list. For example, in Name, type admin and then click Add User.
4.	Highlight the account that you added, and select all of the Access Rights listed below. Click OK.   Figure B.25   Setting full proxy access to a GroupWise mailbox
5.	Ask each Novell GroupWise user who is being migrated to perform these same steps.

To migrate users and mailboxes from Novell GroupWise to Exchange

1.	On the server running Exchange 2003 with Connector for Novell GroupWise, stop the Connector for Novell GroupWise service. 1. Click Start, point to All Programs, point to Administrative Tools, and then click Services. 2. In the details pane, right-click Microsoft Exchange Connector for Novell GroupWise, and then click Stop.
2.	Start the Exchange Migration Wizard: Click Start, point to All Programs, point to Microsoft Exchange, point to Deployment, and then click Migration Wizard. Note : It is assumed that you are using the Exchange server that you configured as described in the procedures earlier in this appendix. If so, this Exchange server is already configured to access Novell GroupWise. It is running the Novell GroupWise client and has network access to the Novell NetWare server running Novell GroupWise.
3.	On the Exchange Server Migration Wizard Welcome page, click Next.
4.	On the Migration page, click Migrate from Novell GroupWise 5.x, and then click Next.   Figure B.26   Specifying the migration type
5.	On the Novell GroupWise 5.x Migration page, click Next.
6.	On the Migration Procedure page: 1. Under Select the migration method, click One step migration (recommended). 2. In the Path to migration files box, type the path to which the migration files are to be temporarily copied. Ensure that the hard disk drive has sufficient space to copy the mailboxes for all of the users you plan to migrate. You must specify a valid folder path. Click Next.   Figure B.27   Selecting the migration procedure
7.	On the Migration Destination page, click Migrate to a computer running Exchange Server. The Server list should now show the name of the Exchange 2003 server. In the Information store list, select the information store (now known as the Exchange store) to which to migrate the Novell GroupWise data, and then click Next.   Figure B.28   Selecting the migration destination
8.	On the GroupWise Domain page: 1. In the Path box, type the UNC path to the Novell GroupWise domain on the Novell NetWare server. Typically, this is \NWSERVER01\SYS\Mail\GWDom, where NWSERVER01 is the Novell NetWare server on which Novell GroupWise is installed. 2. In the Account Name box, type the name of the account that the Exchange Migration Wizard uses to access the Novell NetWare server that runs Novell GroupWise. The account you specify must have access to each user's Novell GroupWise mailbox. It is recommended that you use the account that is already used by Connector for Novell GroupWise or a Novell NetWare admin account. 3. In the Password box, type a Novell GroupWise password (if there is one) for the account used by Connector for Novell GroupWise. Click Next. Note : You must specify a password only if the migration account has a GroupWise password. This is not the same password as the password for Novell NDS. To verify whether a GroupWise password must be specified, start the Novell GroupWise client for this account, and determine whether this user is being prompted for a password.   Figure B.29   Specifying Novell GroupWise domain information
9.	On the GroupWise Postoffice page, click the name of the Novell GroupWise post office from which you to migrate users. For example, if your post office is named CONTOSO_PO, click this entry, and then click Next.   Figure B.30   Selecting the Novell GroupWise post office from which to migrate users
10.	It is recommended that you accept the defaults on the Migration Information page. To do so, click Next. If you do not want to accept the defaults, you can change the following options: 1. The Information to create mailboxes check box. When selected, this creates a new mailbox for users whom you migrated from Novell GroupWise to Exchange. 2. The Mail and Phone Messages check boxes in the Message Types section. When these check boxes are selected, the user's mail and phone messages that are stored on the Novell GroupWise post office are migrated to Exchange. You can click either All to migrate all of the user's data, or Dated from to specify a date range of messages to migrate. 3. The Appointments, Notes, and Tasks check boxes in the Calendar Items section. When these check boxes are selected, the user's calendar information is migrated to Exchange. You can select either All to migrate all of the user's calendar information, or Dated from to specify a date range of calendar information to migrate. Note : Any meeting requests in users' inboxes that have not been accepted are migrated as text messages. Users must add these meetings to their calendars manually. Before you complete the migration, ensure that users accept any outstanding meeting requests.   Figure B.31   Specifying the migration information
11.	On the Account Migration page, select the Novell GroupWise users whom you want to migrate to Exchange 2003. The user ID that the Exchange Migration Wizard uses must have full proxy access to the mailbox of each user that you select. You can click Select All to select all users, or hold down the CTRL key and select users individually. Click Next.   Figure B.32   Selecting users to migrate to Exchange 2003
12.	On the Container for New Windows Accounts page, click the Active Directory container or organizational unit to which users will be migrated. The Exchange Migration Wizard creates a new Active Directory account for each user in the specified container. Click Options.   Figure B.33   Selecting the container to which to migrate accounts
13.	On the Account Options page, click Generate random password, and then select the User must change password at next logon check box. This generates a random strong password for each user, which is stored in the Accounts.Password file in the \Program Files\Exchsrvr\Bin directory on the Exchange 2003 server. Alternatively, you can select other advanced options on this page, such as whether to create disabled user accounts that point to actual accounts in a different domain. For the purposes of this procedure, it is assumed that you are not selecting these advanced options. Click OK, and then click Next.   Figure B.34   Setting the account password options for the new user accounts
14.	On the Windows Account Creation and Association page, you see a list of all the user accounts that will be created. In some instances, these are new accounts, but they might also be updates to existing accounts. For example, when you configured interoperability with Novell GroupWise, you might have decided to create disabled Windows accounts for each Novell GroupWise user. These disabled accounts appear for each corresponding user migrating from Novell GroupWise. Novell GroupWise users are matched with Exchange accounts based on their e-mail addresses. Verify that the accounts are matched correctly. If they are not, you can find the correct account using the Find Existing Account option. You can also choose to create a new account, using the Create New Account option, if the Exchange Migration Wizard matched an account incorrectly. After you finalize the account list, click Next.   Figure B.35   Matching Novell GroupWise accounts to new or existing Windows accounts   Note : This figure shows an example of Novell GroupWise users with disabled Windows accounts resulting from Exchange 2003 and Novell GroupWise directory synchronization. When these users are migrated, the accounts are matched to the users' e-mail addresses, and then the users' Novell GroupWise messaging data is imported to the users' mailboxes. You must enable the user accounts in Active Directory Users and Computers after migration, so that your users can log on to the Windows domain.
15.	The Exchange Migration Wizard extracts the data from the server running Novell GroupWise and then imports it into Exchange and Active Directory. Migration can take some time, depending on the number of users and messages that are migrated, the speed of the server, network latency, and other factors. On the Migration Process page, verify that the migration process proceeds normally, and when the process completes, click Finish.   Figure B.36   Finishing the Novell GroupWise migration
16.	In the Exchange Server Migration Wizard message box informing you that the migration is complete, click OK.

To check the application event log for migration information

1.	On the Exchange 2003 server that performed the migration, click Start, point to All Programs, point to Administrative Tools, and then click Event Viewer.
2.	Click Application.
3.	Look for event log messages for which the source is MSExchangeMig. Double-click the message to view it. Then use the up and down arrows to scroll through the message.

To migrate Novell GroupWise Contacts, Appointments, and Tasks items

1.	Verify that you have received the Migrated Calendar Information import file with an .sc2 file attachment, which the Exchange Migration Wizard generates and sends to each individual user.
2.	In Microsoft Office Outlook®, on the File menu, click Save Attachments.
3.	Type the location and file name for the attached file, and then click Save.
4.	On the File menu, click Import and Export.
5.	Click Import from another program or file, and then click Next.
6.	Click Schedule Plus Interchange and then type the path and file name of the file that you want to import.
7.	Under Options, click Do not import duplicate items to ensure that any previously imported items are not duplicated, and then click Next.
8.	On the next tab, verify the import actions that will be performed. You can click Map Custom Fields to customize the mapping of information from the import file to Outlook contacts, appointments, or tasks, and you can click Change Destination, to specify a destination folder. By default, Outlook imports the information into the standard Contacts, Calendar, and Tasks folders.   Figure B.37   Importing Novell GroupWise Contacts, Appointments, and Tasks items into Outlook
9.	Click Finish to complete the calendar migration.
10.	In the Microsoft Office Outlook message box informing you that you have Schedule+ data stored on the server, click Yes to delete the server copy of this data.