Blog Entry

Finally, after a last push by our development team (who have been working all hours on this) we have been able to get the new Exchange Gateway out of the door.  I just released it to Beta status and it should appear on filefinder soon.

Here are the main bits from the TID:

NOVELL TECHNICAL INFORMATION DOCUMENT

TITLE:  Beta: GroupWise 7 Gateway for MS Exchange
TID #:  2973664
README FOR:  fgwexch700.exe

NOVELL PRODUCTS and VERSIONS:
GroupWise Gateway

ABSTRACT:

This is a public beta of the upcoming GroupWise 7 Gateway for Microsoft
Exchange.  It supports connectivity between GroupWise 6.5 and 7.0 and Microsoft
Exchange 5.5, 2000 and 2003.  It will run on Windows NT 5.5, 2000 and 2003.

-----------------------------------------------------------------
DISCLAIMER
THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO
NOVELL.  NOVELL MAKES ALL REASONABLE EFFORTS TO VERIFY THIS
INFORMATION.  HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT
IS FOR YOUR INFORMATION ONLY.  NOVELL MAKES NO EXPLICIT OR IMPLIED
CLAIMS TO THE VALIDITY OF THIS INFORMATION.
-----------------------------------------------------------------

INSTALLATION INSTRUCTIONS:

1) Download file fgwexch700.zip to a temporary location on your Exchange server
2) Double click the file to extract the contents
3) IMPORTANT: Modify the Windows PATH Environment Variable and add the path to
your Exchange server BIN dir - eg: c:\Program Files\exchsrvr\bin
4) Browse to the extracted Exchange directory and run install.exe
5) Follow onscreen prompts
6) Repeat steps on any other Exchange Servers and install the addressing
component if required (do not install the gateway)

ISSUE:

Changes in this version:
1) Support for MS Exchange 2003
2) Zero byte files supported
3) Various snapin installation changes
4) Crash fix performing Directory Sync
5) Memory Leak Fix
6) Log path read from domain db
7) Windows version no longer required /appl switch
8) Install now supports /clean switch
9) NetWare client no longer required to install addressing components
10) Display name is included on Sync
11) Crash Fix on object open
12) Crash Fix on contect cleanup
13) Release MAPI table to prevent failure after 255 messages

If you encounter any problems be sure to let us know, preferrably not as a comment on here but as a support request, so we can track it properly.