Cool Solutions

Finally….Exchange Gateway is released to Beta



By:

May 2, 2006 9:48 am

Reads: 2933

Comments:5

Score:0

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.

VN:F [1.9.22_1171]
Rating: 0.0/5 (0 votes cast)

Categories: Uncategorized

Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

5 Comments

  1. By:Heiko Talarek

    Hello,

    install.exe runs up to the selection “Install Gateway and Addressing components”.
    If i press “next” windows displays an error from install.exe!!!

    (Windows 2000 Server SP4 – german installation, Exchange 5.5 sp4)

    Thanks

    Heiko

    VA:F [1.9.22_1171]
    Rating: 0.0/5 (0 votes cast)
  2. By:Alex Evans

    Did you add to the PATH Environment Variable? You need to add the path to the BIN dir of the Exchange Server – c:\program files\exchsrvr\bin by default (at least on 2003 it is). This is a new requirement

    VA:F [1.9.22_1171]
    Rating: 0.0/5 (0 votes cast)
  3. By:Dean Engmann

    All options to install the gateway are greyed out for me. The only option I can see is Install Gateway Snap-Ins for ConsoleOne only. (Windows 2003 SP1 / Exchange 2003 SP2) Any suggestions?

    Thanks!

    VA:F [1.9.22_1171]
    Rating: 0.0/5 (0 votes cast)
  4. By:Alex Evans

    Absolutely – you need to add the path to your Exchange server’s BIN directory to the PATH environment variable – the default path is listed in my previous reply on this thread :)

    VA:F [1.9.22_1171]
    Rating: 0.0/5 (0 votes cast)
  5. By:Richard

    Ok, some weirdness here w2k3sp1 with msx2k3sp2 and also tested on w2k3 no sp and msx2k3 no sp. Install reports it cannot find Exchange server sites. Which of course there are none in msx2k3. So we cannot install the gateway.

    Also old sp1 gateway does not install on msx2k3 either.. Needs dirsync connector.. I think there is an sp2 2.0 around so Ill try that.

    Any ideas on an updated beta, we have a GW7 client needing to coexist with a w2k3 AD and msx2k3 Org.

    VA:F [1.9.22_1171]
    Rating: 0.0/5 (0 votes cast)

Comment

RSS