Interoperability, Coexistence, and Migration from Non-Exchange Messaging Systems to Exchange Server 2003 (November 8, 2005)
Chat Topic: Interoperability, Coexistence, and Migration from Non-Exchange Messaging Systems to Exchange Server 2003
Date: Tuesday, November 08, 2005
Please note: portions of this chat have been edited for clarity.
Introduction:
MarkL (Moderator):
Welcome to today’s chat on Interoperability, Coexistence, and Migration from Non-Exchange Messaging Systems to Exchange Server 2003. Your questions, comments and feedback are welcome. Feel free to begin asking questions now and be sure to check the "ask the experts" box before sending. Thanks!
Start of chat:
Stephen Gilbert MSFT (Expert):
Q: An excellent resource for migrating from mail systems like Lotus Notes and GroupWise is Interoperability and Migration Guide. You can download white paper from the following location below.
http://www.microsoft.com/technet/prodtechnol/exchange/2003/library/interopmig.mspx
RayFong - MSFT (Expert):
Q: Besides the whitepaper Stephen posted earlier, this is another good KB article for Exchange Connector for Novell Groupwise: How to configure the Microsoft Exchange Connector for Novell GroupWise 6http://support.microsoft.com/?id=899107
RayFong - MSFT (Expert):
Q: A heads up, as of today, IBM's Notes 6 client is not supported under Windows 2003. So in order to use Notes 6, you will need to use Windows 2000 instead. You can install Exchange 2003 on Windows 2000 in order to connect to Notes 6. For more info, please check out this: Support for the Exchange Connector for Lotus Notes in Exchange Server http://support.microsoft.com/?id=839594
Bethfr - MSFT (Expert):
Notes 6 client will run on Windows 2003, but the issue is that IBM will not support the client on Windows 2003
Bethfr - MSFT (Expert):
Q: Quick question...I have a mixed mode lab. When I try to mail-enable an AD user (not mailbox enable), it prompts me to choose an admin group. One option is my pure E2K3 admin group and the other 2 are my mixed 5.5 sites. Why is it required for a mail enabled user.
A: It is prompting you for an Admin Group so that it can build the proper Legacy Distinguished Name. This is because of the mixed mode environment.
Stephen Gilbert MSFT (Expert):
Q: The Lotus Notes connector can be used to synchronize the address book entries between Lotus Notes mail server and Exchange 2000/2003 servers. This will allow you to Exchange mail between Lotus Notes mail servers and Exchange. It can also be use to start a migration from Lotus Notes and to Exchange. For more information check out the coexistence white paper at: http://www.microsoft.com/technet/prodtechnol/exchange/2003/library/interopmig.mspx
Stephen Gilbert MSFT (Expert):
Q: Most of the issues that are encountered with Lotus Notes connector are in the configuration of the connector on the Exchange server and the configuration on the Lotus Notes server. Here are some basic troubleshooting steps Troubleshooting Lotus Notes Connector on Exchange server.
1. Can you exchange mail between Lotus Notes and Exchange?
2. Do you have directory synchronization between Lotus Notes and Exchange?
3. What version of the Lotus Note client is installed on the Exchange server? What version of Lotus Notes server are we communicating with?
4. On the Exchange server is Microsoft Exchange Lotus Notes Connector service and Exchange Connectivity Controller Service Started?
5. Check the configuration of Lotus Notes connector. Is it configured like the example in Coexistence whitepaper?
6. Turn up diagnostic logging on the connector by going to properties on Exchange server in Exchange System Manager. Then click Diagnostic Logging Tab. In the Services tab select LME-
RayFong - MSFT (Expert):
Q: Not many people know about this, but you can create a folder called Logs under Program Files\Exchsrvr\Conndata. This will give you more extensive loggings about the connectors. 295307 How to Enable and Increase Logging for Microsoft Exchange Connectivity http://support.microsoft.com/?id=295307
Stephen Gilbert MSFT (Expert):
Q: The GroupWise connector in Exchange 2000/2003 can be used to synchronize the address books between GroupWise and Exchange. This will allow you send mail between GroupWise and Exchange. The GroupWise connector in Exchange 2003 Service Pack 2 can be use to communicate with a GroupWise 5.x and 6.x servers. For more information check out the coexistence white paper at http://www.microsoft.com/technet/prodtechnol/exchange/2003/library/interopmig.mspx
RayFong - MSFT (Expert):
Q: Sometimes when you troubleshoot mail flow between Exchange and GroupWise, you can archive the message in between, so you know if the message at least reaches the Exchange side or the GroupWise side. You can simply add this registry key to enable the archive - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LME-GWISE\Parameters\Archive (DWORD) = 1269845 XFOR: How to Enable Archiving on the Exchange 2000 GroupWise Connector http://support.microsoft.com/?id=269845
Fbrown MSFT (Expert):
Q: How does the Groupwise connector work?To interact with Groupwise, Exchange connects to Novell Groupwise using a Novell technology called API Gateway.
The Groupwise API Gateway 4.1 is an optional component that can be added by the Groupwise administrator.
This Groupwise technology uses keyword-based text files to provide a communication channel with non-groupwise systems. It uses pre-defined plain text keywords to format a message for delivery to and from the external system.
Exchange Groupwise connector utilizes the keyword-based text files for the purpose of message flow and directory synchronization with Groupwise (through the Groupwise API Gateway).
Fbrown MSFT (Expert):Q: What are the requirements?
The following are the configuration requirements on the Exchange side:
- A working Novell Groupwise environment with API Gateway version 4.1 (or later) that is configured properly
- A working Exchange 2003 connector server
- Your Exchange server must be able to resolve the name and access the Novell Netware server that is running API Gateway
- Your Exchange server must be using either the Gateway services for Netware (GSNW) or Novell Netware Client for Windows. NDS authentication is needed to access Netware Volumes (shares). Please note that GSNW does not ship in Windows Server 2003
- On the Exchange 2003 recipient policy, activate GWise address type
NOTE: Certain ports may need to be open if there are firewalls between Exchange and Groupwise. The following ports should be open between these two servers (only):
- UDP ports 43981 and 43982
- Both UDP and TCP port number 396
- Echo UDP port 7
Bethfr - MSFT (Expert):
This article will help you understand how the mail flow between Notes and Exchange worksExchange Notes Connector Mail Flow http://support.microsoft.com/?id=298414
Fbrown MSFT (Expert):
Q: How does the message flow work from Exchange to Groupwise?
For message flow you need to have three services started on the Exchange server:
Connectivity controller, the Connector for Novell Groupwise, and Router for Novell Groupwise (which is responsible for transferring the text files to and from Groupwise API share).
- Exchange transport examines the message target address. If the address type is GWISE then it sends the message to the Message Transfer Agent (MTA) by placing it in the SMTP mailbox folder called MTS-IN
- MTA picks up the message and delivers it to the Groupwise connector mailbox folder called MTS-OUT
- LXMEXOUT picks up the message from MTA-OUT and delivers it to READYOUT folder
- MEX2GW process converts the message to Groupwise format and writes the results in the Connector Store on ?\Program Files\Exchsrvr\Conndata\GWRouter?
- Exchange Router for Novell Groupwise service (GWRouter) picks it up from there and delivers it to the API Gateway
- GWMTA in turn delivers the
RayFong - MSFT (Expert):
Q: One of the limitation of Exchange Notes Connector is you cannot use the connector to send HTML format. As a workaround, you can use SMTP instead. This article will give you a good start.
FOR: Exchange Notes Connector Does Not Send HTML http://support.microsoft.com/?id=303986
RayFong - MSFT (Expert):
Q: Earlier I indicated you can use SMTP to send mail between Notes and Exchange instead of using the Notes Connector because you want to send HTML mail. If you do that, you may want to also use SMTP to synchronize the directory. This article will give you start.303724 XFOR: Directory Synchronization Between Notes and Exchange with SMTP http://support.microsoft.com/?id=303724
Fbrown MSFT (Expert):
Q: For step by step instructions on configuring the Groupwise connector:Appendix B: Configuration Procedures for Migrating from Novell GroupWise Messaging Functionality http://www.microsoft.com/technet/prodtechnol/exchange/default.mspx
Stephen Gilbert MSFT (Expert):
Q: Like the Lotus Notes connector most issue occur because of misconfiguration of the Connector on the Exchange server or misconfiguration on the GroupWise mail server. Here are some basic troubleshooting steps:
1. Do you have directory synchronization between GroupWise and Exchange?
2. If you have directory synchronization can you send mail messages between GroupWise and Exchange?
3. Have you checked the configuration of GroupWise connector and configuration in GroupWise made sure that it matches the example in the coexistence whitepaper?
4. Are the Exchange Connectivity Controller, Microsoft Exchange GroupWise Connector and GroupWise Routing Engine Services started?
5. What version of the Netware client is installed on the Exchange server?
6. Can you access API gateway on the GroupWise server by going \\server\folder\api 7. If turn up diagnostic logging on the Exchange server by going properties on Exchange server in diagnostic logging. Then select LME-GroupWise and turn up all the categories to maximum. Do you get any error messages in the application log?
8. Turn text based logging on the connectivity controller by creating the logs folder in the program files\exchsrvr\conndata
RayFong - MSFT (Expert):
Q: You can customize the attributes when you synchronize the directory between notes and Exchange. The attributes are not limited to the one defined in the tbl file only. You can create your own. Please see this KB for more information.
FOR: Customizing Directory Synchronization Between Exchange and Notes http://support.microsoft.com/?id=180517
Stephen Gilbert MSFT (Expert):
Q: The calendar connector can be used to share the free busy information between Exchange and Lotus Notes or GroupWise. The calendar connector will not allow you to pull up a Lotus Notes user or GroupWise user calendar. The calendar connector works that it intercepts calls the Schedule Plus free busy folder and forwards those requests to Lotus Notes or GroupWise. It also listens to requests from Lotus Notes and GroupWise for Exchange user free busy information. In order to use the calendar connector for Lotus Notes or GroupWise you must have a working Lotus Notes or GroupWise mail connector that you are passing mail between systems and directory synchronization.
Stephen Gilbert MSFT (Expert):
Q: Continuation....
If you are using SMTP to route mail between Lotus Notes or GroupWise and Exchange you will not be able to use the calendar connector. For more information on how to configure the calendar connector check out the coexistence whitepaper at the link listed below.
http://www.microsoft.com/technet/prodtechnol/exchange/2003/library/interopmig.mspx
RayFong - MSFT (Expert):
Q: The connection between Connector for Novell GroupWise and the Novell GroupWise API Gateway is a critical point in the connector architecture. The Router for Novell GroupWise handles the communication between Connector for Novell GroupWise and the Novell GroupWise API Gateway by transferring keyword-based text files between the connector store and the API gateway directory. If you discover that messages are not being transferred successfully, try starting the router process in console mode to obtain more detailed information about this process
RayFong - MSFT (Expert):
Q: To start the Router for Novell GroupWise service in console mode, perform the following steps:
1.Stop the Microsoft Exchange Router for Novell GroupWise service in the Services tool. In the Stop Other Services dialog box, click Yes to stop the Microsoft Exchange Connector for Novell GroupWise service as well.
2.Start Windows Explorer, open the \Program Files\Exchsrvr\bin directory, and locate the Gwrouter.exe file.
3.Double-click the Gwrouter.exe file to start the GroupWise Router program in console mode. Verify that the router process started successfully and is polling the API Gateway directory (Figure 5.6).
4.To stop the GroupWise Router, press CTRL+BREAK to terminate the program.
Stephen Gilbert MSFT (Expert):
Q: Just like the mail connectors the calendar connector most issues that you encounter will be a misconfiguration. Here are some basic troubleshooting steps to help out troubleshooting calendar connector issues.
1. Check the configuration of the calendar connector. You can compare that against the Exchange coexistence whitepaper.
2. Make sure that we have established mailflow and directory synchronization across mail connector to Lotus Notes/GroupWise and Exchange.
3. Make sure the customer is not using SMTP to route mail between Exchange and GroupWise/Lotus Notes
4. Check to see if we replica of Schedule Plus Free Busy folder on the Exchange server
5. Check to see if default recipient policy has the Lotus Notes Address or GroupWise address enabled. This so the system attendant mailbox will get a Lotus Notes or GroupWise address.
6. On the Lotus Notes server is the excalcon task loaded? You check on Notes console by typing in show task excalcon and pressing enter.
Stephen Gilbert MSFT (Expert):
Q: 7. Turn up logging for the calendar connector you can use the following KB article. 197372 XFOR: How to Run Calendar Connector in Console Mode http://support.microsoft.com/?id=197372
MarkL (Moderator):
Well that wraps things up for our chat this afternoon. Thank you to our guests for stopping by, and thank you to our Experts for being here to answer questions-- have a great afternoon everyone!