GroupWise 7 Exchange Gateway "Bad GroupWise proxy"

I am testing the GW7 Gateway on a GW702(NW) and Exchange 2003SP2 installation. I have it basically running, but there are 2 issues that I cannot seem to fix.
as part of my learning, I have determined that I must run the Gateway as an Application, due to the windows Service being unable to run from a NetWare UNC, and I also determined that the Gateway name must be 8 chars. This all works.
At this point, if I initiate a Directory Synchronization, it creates contacts for every GroupWise user in the AD import container, and contacts in GroupWise for any existing Exchange users.
My first issue is that it ONLY creates contacts. It does not seem to be able to "mail enable" existing AD accounts event though they match. It is ignoring the settings in the properties of the gateway-> Import Container "When replicating a mailbox whose primary account does not exist in the domain" if I set it to create a Windows Account. Is this normal?
Second issue is: if I migrate a user from GroupWise to Exchange using the Microsoft Exchange 2003 sp2 Migration wizard, it correctly removes the Contact, and mail enables the AD User account, but the new Exchange account will not synchronize.
The problem is that the directory sync gives errors on every user account that was migrated, and does not create a new contact in GroupWise. Any new user created manually in Exchange does sync and is ok. The verbose log in the Gateway says "DXIN: Ignored: Adding User GW701DO.GW701PO.Bob Brown: Reason-Bad GroupWise proxy".
Taking this message at it's word, I have ensured that the account running the Gateway has full AD and NDS rights, and is explicitly assigned full GroupWise proxy rights.
What does this error message really mean?

There is something else going on with the migrated user account. I have deleted the NDS account, leaving only the AD/Exchange user, but it still does not populate the gateway domain with a contact. It still says "Bad GroupWise Proxy".
I will test if I can export, delete, and then import this user so that I can reproduce the content of the AD account. Perhaps there is something in the attributes that is causing the gateway to fail to do it's creation.
Originally Posted by durrand
I've previously tried (and failed) to get the gateway to create windows user accounts - maybe a call to NTS is require to get newer code(?)
On the second issue, are you trying to import/export to/from the same conatner in AD and DOMAIN in GroupWise? Is it possible that the create fails because it clashes with the old account?
If you're only testing the gateway my suggestion would be to create a separate External Domain and use this in the Exchange GWISE addressing scheme (which, in turn, will ensure that any sync'd accounts are created in the new domain).

Similar Messages

Groupwise 7 Gateway for Exchange

I am testing the Novell Groupwise Gateway for Exchange SP2. I have already tested the API Gateway but wanted to try the newer version because it will be supported for awhile. I downloaded the install and went through all the instructions. I am using Groupwise 7.0.1 and Exchange 2003. The install went fine and the configurations are correct but I must be missing something. When I go to start the Gateway Application it starts then stops. I checked on the GW MTA and it says the link is Closed. The reason the link it closed it says can't create directories. I checked the Gateway application and it shows Groupwise link closed and other link Open. I logged into a ws as the same user to check the rights and I was able to create a new directory in the domain directory. I changed the logging to verbose on the Exchange Gateway to see if I can see an error and it says trying to re-establish GW link.
03-11-08 10:17:53 0 Begin Configuration Information
03-11-08 10:17:53 0 Platform= Windows 2003 (TM) Version 5.2 (Build 3790) Serv
ice Pack 2
03-11-08 10:17:53 0 Domain and gateway= VMDomain.Exchange_Gateway1
03-11-08 10:17:53 0 Foreign Name= <none specified>
03-11-08 10:17:53 0 Description= <none specified>
03-11-08 10:17:53 0 Alias Type= Exchange
03-11-08 10:17:53 0 Root Directory= \\VMNW65\data\VMDOMAIN\wpgate\Exchange_Ga
teway1
03-11-08 10:17:53 0 Work Directory= \\VMNW65\data\VMDOMAIN\wpgate\Exchange_Ga
teway1\000.prc\gwwork
03-11-08 10:17:53 0 Log File= \\VMNW65\data\VMDOMAIN\wpgate\Exchange_Gateway1
\000.prc\0311log.001
03-11-08 10:17:53 0 Directory ID= exc367d
03-11-08 10:17:53 0 Directory Synchronization= NO
03-11-08 10:17:53 0 Directory Exchange= NO
03-11-08 10:17:53 0 Accounting= YES
03-11-08 10:17:53 0 Access Control= NO
03-11-08 10:17:53 0 Convert GroupWise Status to Messages= NO
03-11-08 10:17:53 0 Outbound Status Level= OPEN
03-11-08 10:17:53 0 Log Level= Verbose
03-11-08 10:17:53 0 Log Max Age= 7 days
03-11-08 10:17:53 0 Log Max Space= 1024 kb
03-11-08 10:17:53 0 Enable Recovery= YES
03-11-08 10:17:53 0 Retry Count= 10
03-11-08 10:17:53 0 Retry Interval= 60 seconds
03-11-08 10:17:53 0 Failed Recovery Wait= 3600 seconds
03-11-08 10:17:53 0 Network Reattach Command= <none specified>
03-11-08 10:17:53 0 Correlation DB Enabled= YES
03-11-08 10:17:53 0 Correlation DB Age= 14 days
03-11-08 10:17:53 0 Correlation DB Directory= \\VMNW65\data\VMDOMAIN\wpgate\E
xchange_Gateway1
03-11-08 10:17:53 0 Send/Receive Cycle= 2 minutes
03-11-08 10:17:53 0 Minimum Run= 0 minutes
03-11-08 10:17:53 0 Idle Sleep Duration= 30 seconds
03-11-08 10:17:53 0 Snap Shot Interval= 10 minutes
03-11-08 10:17:53 0 Time Zone= PST
03-11-08 10:17:53 0 GMT Offset= -8 hours, 0 minutes
03-11-08 10:17:53 0 Hemisphere= NORTH
03-11-08 10:17:53 0 Daylight Saving Change= 1 hours, 0 minutes
03-11-08 10:17:53 0 Daylight Saving Begin= 4/6 (month/day)
03-11-08 10:17:53 0 Daylight Saving End= 10/26 (month/day)
03-11-08 10:17:53 0 Procedure ID= 000
03-11-08 10:17:53 0 SNMP On
03-11-08 10:17:53 0 Gateway Build Timestamp: Wednesday, April 25, 2007 15:30:38
03-11-08 10:17:53 0 GWIN.DLL Build Timestamp: Wednesday, April 25, 2007 15:32:2
4
03-11-08 10:17:53 0 GWOUT.DLL Build Timestamp: Wednesday, April 25, 2007 15:33:
50
03-11-08 10:17:53 0 Startup Switches= /Home-\\VMNW65\data\VMDOMAIN\wpgate\Exc
hange_Ga
03-11-08 10:17:53 0 teway1 /rt-1 /st-1 /group /Custom /appl
03-11-08 10:17:53 0 End Configuration Information
03-11-08 10:17:54 0 Checking the correlation DB
03-11-08 10:17:54 0 Correlation DB check complete
03-11-08 10:17:54 0 The gateway is attempting to reestablish the GroupWise link

The gateway directory has to be in less that 8 chars, or at least 8.3...
On Netware the agents have this restriction.
Morris
cnakagaw wrote:
> I am testing the Novell Groupwise Gateway for Exchange SP2. I have
> already tested the API Gateway but wanted to try the newer version
> because it will be supported for awhile. I downloaded the install and
> went through all the instructions. I am using Groupwise 7.0.1 and
> Exchange 2003. The install went fine and the configurations are correct
> but I must be missing something. When I go to start the Gateway
> Application it starts then stops. I checked on the GW MTA and it says
> the link is Closed. The reason the link it closed it says can't create
> directories. I checked the Gateway application and it shows Groupwise
> link closed and other link Open. I logged into a ws as the same user to
> check the rights and I was able to create a new directory in the domain
> directory. I changed the logging to verbose on the Exchange Gateway to
> see if I can see an error and it says trying to re-establish GW link.
>
>
> 03-11-08 10:17:53 0 Begin Configuration Information
> 03-11-08 10:17:53 0 Platform= Windows 2003 (TM) Version 5.2 (Build
> 3790) Serv
> ice Pack 2
> 03-11-08 10:17:53 0 Domain and gateway= VMDomain.Exchange_Gateway1
> 03-11-08 10:17:53 0 Foreign Name= <none specified>
> 03-11-08 10:17:53 0 Description= <none specified>
> 03-11-08 10:17:53 0 Alias Type= Exchange
> 03-11-08 10:17:53 0 Root Directory=
> \\VMNW65\data\VMDOMAIN\wpgate\Exchange_Ga
> teway1
> 03-11-08 10:17:53 0 Work Directory=
> \\VMNW65\data\VMDOMAIN\wpgate\Exchange_Ga
> teway1\000.prc\gwwork
> 03-11-08 10:17:53 0 Log File=
> \\VMNW65\data\VMDOMAIN\wpgate\Exchange_Gateway1
> \000.prc\0311log.001
> 03-11-08 10:17:53 0 Directory ID= exc367d
> 03-11-08 10:17:53 0 Directory Synchronization= NO
> 03-11-08 10:17:53 0 Directory Exchange= NO
> 03-11-08 10:17:53 0 Accounting= YES
> 03-11-08 10:17:53 0 Access Control= NO
> 03-11-08 10:17:53 0 Convert GroupWise Status to Messages= NO
> 03-11-08 10:17:53 0 Outbound Status Level= OPEN
> 03-11-08 10:17:53 0 Log Level= Verbose
> 03-11-08 10:17:53 0 Log Max Age= 7 days
> 03-11-08 10:17:53 0 Log Max Space= 1024 kb
> 03-11-08 10:17:53 0 Enable Recovery= YES
> 03-11-08 10:17:53 0 Retry Count= 10
> 03-11-08 10:17:53 0 Retry Interval= 60 seconds
> 03-11-08 10:17:53 0 Failed Recovery Wait= 3600 seconds
> 03-11-08 10:17:53 0 Network Reattach Command= <none specified>
> 03-11-08 10:17:53 0 Correlation DB Enabled= YES
> 03-11-08 10:17:53 0 Correlation DB Age= 14 days
> 03-11-08 10:17:53 0 Correlation DB Directory=
> \\VMNW65\data\VMDOMAIN\wpgate\E
> xchange_Gateway1
> 03-11-08 10:17:53 0 Send/Receive Cycle= 2 minutes
> 03-11-08 10:17:53 0 Minimum Run= 0 minutes
> 03-11-08 10:17:53 0 Idle Sleep Duration= 30 seconds
> 03-11-08 10:17:53 0 Snap Shot Interval= 10 minutes
> 03-11-08 10:17:53 0 Time Zone= PST
> 03-11-08 10:17:53 0 GMT Offset= -8 hours, 0 minutes
> 03-11-08 10:17:53 0 Hemisphere= NORTH
> 03-11-08 10:17:53 0 Daylight Saving Change= 1 hours, 0 minutes
> 03-11-08 10:17:53 0 Daylight Saving Begin= 4/6 (month/day)
> 03-11-08 10:17:53 0 Daylight Saving End= 10/26 (month/day)
> 03-11-08 10:17:53 0 Procedure ID= 000
> 03-11-08 10:17:53 0 SNMP On
> 03-11-08 10:17:53 0 Gateway Build Timestamp: Wednesday, April 25, 2007
> 15:30:38
> 03-11-08 10:17:53 0 GWIN.DLL Build Timestamp: Wednesday, April 25,
> 2007 15:32:2
> 4
> 03-11-08 10:17:53 0 GWOUT.DLL Build Timestamp: Wednesday, April 25,
> 2007 15:33:
> 50
> 03-11-08 10:17:53 0 Startup Switches=
> /Home-\\VMNW65\data\VMDOMAIN\wpgate\Exc
> hange_Ga
> 03-11-08 10:17:53 0 teway1 /rt-1 /st-1 /group /Custom /appl
> 03-11-08 10:17:53 0 End Configuration Information
> 03-11-08 10:17:54 0 Checking the correlation DB
> 03-11-08 10:17:54 0 Correlation DB check complete
> 03-11-08 10:17:54 0 The gateway is attempting to reestablish the
> GroupWise link
>
>

Groupwise 7 Exchange Gateway

I have and exchange system with 130K users and GW system with 50K users connected together via Exchange Gateway 7 SP2.
Is there a maximum in the number of contacts in either direction?
What is the maximum number of Post Offices on GW side supported by the gateway? There is a error stating maximum open POs but no number is given.
Is there any way to cause a full sync only on the weekends while allowing delta exchange at all times? I was considering a script file to delete the flag files in the DX directories. I think this is an ungraceful method to a simple problem.
I was told about GW7 SP3 coming out before GW8. How can I get a beta copy of the newer exchange gateway.

I have and exchange system with 130K users and GW system
with 50K users connected together via Exchange Gateway 7 SP2.
Q.- Is there a maximum in the number of contacts in either direction?
A.- None that I'm aware of. As long as your HW is fast enough for all them it should be fine.
Q.- What is the maximum number of Post Offices on GW side supported by the gateway?
A.- Same as before.
Q.- There is a error stating maximum open POs but no number is given.
A.- Could you provide more details about it?
Q.- Is there any way to cause a full sync only on the weekends while allowing delta exchange at all times? I was considering a script file to delete the flag files in the DX directories. I think this is an ungraceful method to a simple problem.
A.- I don't think it's supported by the product but you can always try.
Q.- I was told about GW7 SP3 coming out before GW8.
A.- GW 7.0.3 is expected between the second and third week of March. Of course this is not fixed and subject to change.
Bonsai is expected for 10/2008, again, not fixed and subject to change.
Q.- How can I get a beta copy of the newer exchange gateway.
A.- You need to subscribe to the beta program to have access to it or wait for the beta public release.
Hope it helps.
Roberto Helering.

Exchange 2003 to GroupWise 7

We are not able to successfully complete a migration of all users from
Exchange 2003 to GroupWise 7 on Netware. Issues below:
** NOT Necessarily in exact order of sequence **
System config:
Netware OES fully service packed, new server, 4GB RAM, 4 Processors.
GroupWise 7.0.1 IR1 Post Office installed. Domain located on an older,
existing server.
Microsoft Windows Server 2003, Exchange 2003 single server. Nothing
special or unusual about this setup for Exchange, pretty generic.
1. Issue attempting to install Migration utility. Utility unable to run
after installation on any workstation. Various errors from "unable to
create GroupWise account" to "unable to login to Exchange mailbox" and a
few others. We also got "fatal errors when trying to extract .csv file".
This was resolved later by running fixmapi.
2. After nearly 18 hours attempting to get the utility to work, we were
able to successfully load it onto 2 workstations. It appeared that it
would work on both.
3. We tried many things to install and run the utility on 15 additional
workstations with no success.
4. Found that the only 2 workstations that appeared to run the utility
were fairly new, less than 2 months old. We then tried fresh installations
of WINXP and WIN2000 on 2 workstations with no success. One of the 2
workstations that did work, later no longer would run the utility. After
running fixmapi.exe on that workstation, it did again work.
5. A suggestion from Novell NTS was to run fixmapi.exe. This appeared to
have corrected 4 of the 10 workstations on which we tried it.
6. Found on 2 workstations that if ZEN DLU (Dynamic Local User) was used,
the migration utility did not work. We found this by logging in as
"Workstation Only" which connected the workstation to the domain, then a
login to eDirectory. The utility did work. So, again we tried to login on
startup to eDirectory and again were not able to run the utility. So, the
fact that some workstations here use DLU may be an issue for this utility.
7. Found that on other workstations, the utility would run ONLY if
"Workstation Only" was selected, then login to eDirectory. We were able to
repeat this sequence multiple times. This is on a workstation not running
ZEN DLU.
8. Of the 6 workstations we were able to run the utility, 1 failed in the
first 5 minutes and would no longer work. So, we split the .csv file from
the Exchange server into 5 parts and started the migration on the 5
available operating workstations. Of the 5, only 2 completed the utility.
Of those 2, only 7 of the 45 users to be migrated completed on 1
workstation and 15 of 45 completed on another.
9. On the 2 workstations that completed, all user accounts were created
but the utility was unable to access the GroupWise account. Login to
GroupWise account failed.
10. Migration utility rules creation issue. There are 2 issues here.
10a. The utility suggests to create a rule using a sub-domain and a
forward rule in Exchange to the new GroupWise system. We are migrating
from: royalmouldings.com to ggc.com. So, the sub-domain is
marexch.ggc.com. The rule would read "forward all mail to
[email protected]. However, Exchange cannot forward to an external
domain at the client level. The only means to do so is to create a contact
in AD with an SMTP email address of the domain to be forwarded to. Then,
in the users account a rule may be created to forward to that newly
created contact. The fact that we are forwarding to an external internet
domain, as in NOT the same one currently used in Exchange, is not
indicated in the documentation. Additionally, if anyone is to do this, a
lot of manual work must be done to accomplish this task. Not too practical
to do for hundreds or thousands of users. This has been a big problem as a
result of the large amount of users in the system and the time it takes to
create each of these contacts.
10b. The second issue is the fact that the rule was created for 1 user,
then no other users had the rule created. So, even if the rule were to
work or we were migrating from and to the same domain name, we'd still
have the rule issue as it was never again created by the utility after the
first user was migrated.
Any help would be greatly appreciated.
Thanks

Bill, you're understandably frustrated. I have a couple of comments.
1. The network authentication system used by Microsoft Exchange requires that you log in to your workstation with the same user ID and password as your account on Exchange. If they don't match, Exchange returns errors that are not always understandable. That might explain why Zen DLU has problems.
2. It seems that every application that deals with e-mail has its own version of MAPI, and they're not always compatible with each other. Outlook, GroupWise, and the migration utility all use MAPI. The fixmapi utility will restore the MAPI DLLs that Outlook expects, which is usually the version that works best.
3. The migration utility should be improved to detect potential errors like these.
>>> Bill Long<[email protected]> 5/19/07 11:59 AM >>>
We are not able to successfully complete a migration of all users from
Exchange 2003 to GroupWise 7 on Netware. Issues below:
** NOT Necessarily in exact order of sequence **
System config:
Netware OES fully service packed, new server, 4GB RAM, 4 Processors.
GroupWise 7.0.1 IR1 Post Office installed. Domain located on an older,
existing server.
Microsoft Windows Server 2003, Exchange 2003 single server. Nothing
special or unusual about this setup for Exchange, pretty generic.
1. Issue attempting to install Migration utility. Utility unable to run
after installation on any workstation. Various errors from "unable to
create GroupWise account" to "unable to login to Exchange mailbox" and a
few others. We also got "fatal errors when trying to extract .csv file".
This was resolved later by running fixmapi.
2. After nearly 18 hours attempting to get the utility to work, we were
able to successfully load it onto 2 workstations. It appeared that it
would work on both.
3. We tried many things to install and run the utility on 15 additional
workstations with no success.
4. Found that the only 2 workstations that appeared to run the utility
were fairly new, less than 2 months old. We then tried fresh installations
of WINXP and WIN2000 on 2 workstations with no success. One of the 2
workstations that did work, later no longer would run the utility. After
running fixmapi.exe on that workstation, it did again work.
5. A suggestion from Novell NTS was to run fixmapi.exe. This appeared to
have corrected 4 of the 10 workstations on which we tried it.
6. Found on 2 workstations that if ZEN DLU (Dynamic Local User) was used,
the migration utility did not work. We found this by logging in as
"Workstation Only" which connected the workstation to the domain, then a
login to eDirectory. The utility did work. So, again we tried to login on
startup to eDirectory and again were not able to run the utility. So, the
fact that some workstations here use DLU may be an issue for this utility.
7. Found that on other workstations, the utility would run ONLY if
"Workstation Only" was selected, then login to eDirectory. We were able to
repeat this sequence multiple times. This is on a workstation not running
ZEN DLU.
8. Of the 6 workstations we were able to run the utility, 1 failed in the
first 5 minutes and would no longer work. So, we split the .csv file from
the Exchange server into 5 parts and started the migration on the 5
available operating workstations. Of the 5, only 2 completed the utility.
Of those 2, only 7 of the 45 users to be migrated completed on 1
workstation and 15 of 45 completed on another.
9. On the 2 workstations that completed, all user accounts were created
but the utility was unable to access the GroupWise account. Login to
GroupWise account failed.
10. Migration utility rules creation issue. There are 2 issues here.
10a. The utility suggests to create a rule using a sub-domain and a
forward rule in Exchange to the new GroupWise system. We are migrating
from: royalmouldings.com to ggc.com. So, the sub-domain is
marexch.ggc.com. The rule would read "forward all mail to
[email protected]. However, Exchange cannot forward to an external
domain at the client level. The only means to do so is to create a contact
in AD with an SMTP email address of the domain to be forwarded to. Then,
in the users account a rule may be created to forward to that newly
created contact. The fact that we are forwarding to an external internet
domain, as in NOT the same one currently used in Exchange, is not
indicated in the documentation. Additionally, if anyone is to do this, a
lot of manual work must be done to accomplish this task. Not too practical
to do for hundreds or thousands of users. This has been a big problem as a
result of the large amount of users in the system and the time it takes to
create each of these contacts.
10b. The second issue is the fact that the rule was created for 1 user,
then no other users had the rule created. So, even if the rule were to
work or we were migrating from and to the same domain name, we'd still
have the rule issue as it was never again created by the utility after the
first user was migrated.
Any help would be greatly appreciated.
Thanks

Can't install Exchange Gateway

I'm trying to install the Exchange gateway on an Echange 2003 system. Have installed C1 with snapins and created a secondary GW domain for the gateway on the Exchange server. The secondary domain starts up OK.
However, when I try and install the gateway on the Exchange server, it fails wi the error 'Unable to get Exchange Server Sites for the server servername and the organization orgname'. If I OK that message, it takes me to the dialog to select the server site, etc, but there is nothing to select, so I have to cancel out of the install.
Any ideas?
Rob.

The best approch at installing this gateway is to follow the TID on how to install it.
How to Install the GroupWise Gateway for Microsoft Exchange
TID #7001367
Environment
Novell GroupWise Gateway - 7.x Gateway for MS Exchange
Novell GroupWise 7
Situation
GroupWise Gateway for Microsoft Exchange Install fails to result in working Gateway
GroupWise Gateway for Microsoft Exchange Service will not start
ERROR: "1503: The Service did not respond or the start or control request in a timely fashion."
ERROR: "ERROR (E01) 010012: Unable to get configuration information from the MAPI Session"
ERROR: "ERROR (E01) 010012 MAPI code: 11D"
ERROR: "ERROR (E01) 0323004 - Unable to bind to the Gateway Object"
Resolution
This document is designed to aid in a successful install of the GroupWise Gateway for Microsoft Exchange in regards to "How to Set Rights for Windows users to install and run the Gateway."
The install and configure documentation should be followed in addition to this TID. GroupWise GateWay Documentation Novell Doc: GroupWise Migration Utilities - Table of Contents
The document does not include installation of the Free busy search components. At the time of writting the GroupWise Gateway for Microsoft Exchange is not intended to be used with Exchange 2007. Installing the Gateway on a Exchange 2003 server in an Exchange 2007 environment appears to be a valid work-around for using the gateway in an Exchange 2007 environment.
Install the latest version of the Gateway software. The latest version can be obtained by calling support. The files can be obtained by opening a service request with support. If no additional support is required the service request may be closed at no additional charge.
Assumptions about the server where the Gateway will be installed:
Novell Client is installed
Authenticated to Edirectory as Admin
ConsoleOne is installed
Active directory Users and Computers in installed
Exchange system manager is installed
AdsiEdit is installed (possibly not needed)
The install / running of the GroupWise gateway for Microsoft Exchange has been complicated and usually requires additional attention to rights as a result of change made in Exchange
More information about this change can be noted at “Send As” permission behavior change in Exchange 2003 “Send As” permission behavior change in Exchange 2003.
Preliminary Step to take to insure success before installing the Gateway:
Check for the existance of Gwise address space on current policy and remove. Find Policy in Exchange system manager | go to properties | remove any old Gwise address space and apply the policy to remove address space from invidual users. Check individual users that the Gwise address space was remove.
Find and remove all Gwproxy.dll on all Exchange servers. Delete gwproxy.dll from Program Files\Exchsrvr\address\gwise\i386 directory on ALL Exchange servers. If the file will not delete you may have to stop Exchange services.
Enable the hidden security tab at the top of the Exchange Org to assist in checking for proper rights needed to run the gateway. The following document will assist in enabling the security tab: XADM: Security Tab Not Available on All Objects in System Manager
Create a user to run the Gateway service and remove his membership to groups not needed. IE: remove membership to "users group" as well as any other groups that are not needed. To remove and add membership to a user go to Active directory Users and Computers | properties of the user | membership tab.
Add group membership for user used to install the gateway as well as the user used to run the gateway rights to the following groups: Domain admins, Schema admins, Enterprise admins, Exchange Domain Servers
Use the hidden security tab to verify that the Installer user and the Service Runner user do not have deny rights set to the "send as" and "receive as" attributes. Go to Exchange system manager at the top of the Org | right click and see the new security tab we enabled in Step 3. Check each group the installer and runner are a members of and remove deny attributes from the "send as and receive as" check boxes. If the groups are not visible in the Top portion of the properties page use the ADD button to add the group | highlight the user and check the "send as" and "receive as" rights.
Follow the Install and configure documentation for the GateWay Novell Doc: GroupWise Migration Utilities - Table of Contents
Run the Install for the Gateway.
If the gateway fails to start it is usually an issue with "send as" and "receive as" set to deny. Use ADSIedit.mcs to find a possible deny that is not visible in Step 6. To launch ADSIedit go to Start | run | type ADSIeit.msc (If needed you can install ADSEedit using the following URL suggestions Adsiedit Overview: Active Directory )
NOTE: Use ADSIedit carefully. The goal is to check and set a deny / allow right for the above groups and users. Contact Microsoft support for information regarding the use of this tool.
Using ADSIedit to find Denys to the Mail Store that are not allowing the user to run the gateway:
Set all "Send as and Receive as" rights for the above users and groups to allow. There cannot be any deny on the "Send as and Receive as" for the above groups or users. Not even if the deny is inherited (greyed out.)
Go into ADSIedit by going to Start | run | type ADSIeit.msc
Expand the Configuration Container
Drill down to Configuration/Services/Microsoft Exchange/First Organization/Administrative Groups/First Administrative Group/Servers/Exchange/information Store/First Storage Group/ and not the mail store.
Right click the mail store object in the right hand window of Adsiedit and go to security tab.
Check "Send as and Receive as" and change any Deny to an allow right for the above users and groups.
A Grey check mark set to Deny indicates the right is inherited from above the current container.
Walk up the Tree of containers checking at each section to insure the "Send as and Recieve as" is set to allow for the users and groups noted above.
NOTE: The most common hidden deny that needs to be removed is found for the Exchange Domains Servers Group and at the Servers Container.
Once all Denys for "Send As and Receive As" have been removed allow some time for replication. Server Restart have also shown to be helpful when rights are set correctly but service still behaves as if it is lacking the "Send As and Receive As" allow rights.
Additional Information
What we need to know:
The Gateway needs to login to the Exchange mail store on the local Exchange Server and create a mailbox for the user that is specified to run this gateway. This users rights to the mail store are needed or the gateway will fail to run.
Additional Trouble shooting aids:
Check the Windows Event logs for error when starting the gateway
Set the Gateway in Consoleone to log at verbose logging level
Try starting the gateway as an application during trouble shooting process as it may allow errors to be see that are not logged. To Start the Gateway as an application when installed as a service Go to / GroupWise domain directory / wpgate/ Exchange / Exegate.exe right click and select open to launch.

Exchange Gateway

We were able to get the gateway running. Dirsync and busy search both work and mail flows from exchange to Groupwise, but not from groupwise to exchange. The gateway shows a conversion error, says it can submit mail to exchange. any ideas?

vspence,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Forums Team
http://forums.novell.com

Exchange Gateway or API Gateway

We're running GroupWise 7.02HP1a on both NetWare and Linux. We're looking to cooperate with an Exchange 2003 system (maybe 2007 with a 2003 intermediary).
Not sure whether to use the Microsoft Gateway with API Gateway on the Novell side, or the Novell Exchange Gateway. Does anyone have experience with both that can comment on which one seems to function better? Is it a toss up and just a matter of preference?
Thanks for any feedback,
Ryan

Originally Posted by ukdtom
Use the Novell Exch. Gateway....
The API one was before html was invented, so I doubt it supports html based mails
Also...The Novell Exch. gateway is under constant development, where the API one hasn't been developed
since GW4
Ahh ok :) Thanks for the response... I'll push for the Novell Exch. Gateway.

Exchange Gateway; MIME.822 header missing

Hello!
The MIME.822 header is stripped after passing through the GW 7.x Exchange
Gateway. As told in TID #3878409, this works 'as designed'! Unfortunately we
need the MIME.822 header information for SPAM handling and other reasons
(i.e. compliant e-mail archiving) in our local GW 7.0.2 system. Our (new)
branch offices are running MS Exchange 2003 and we wouldn't like to migrate
to Exchange. That's why we set up the GW 7.x Exchange Gateway (7.0.2) for
e-mail transfer over a central exchange server which - so far - woks fine.
The exchange server is also responsible for x-spam tagging and virus
scanning.
TID #3878409 is from June 2007 and reported to engineering. Did they solve
the 'problem'? If not, we probably have to go the hard way (to exchange)!
This couldn't be the intension of this 'feature'...
Does anybody has some information?
Thank you in advance!
Marco

There may be a hidden switch - contact Novell to find out if that's the
case.
>>> On 11/27/2007 at 12:07 PM, in message
<[email protected]>,
Marco Piesold<[email protected]> wrote:
> Hello!
>
> The MIME.822 header is stripped after passing through the GW 7.x
> Exchange
> Gateway. As told in TID #3878409, this works 'as designed'!
> Unfortunately we
> need the MIME.822 header information for SPAM handling and other reasons
> (i.e. compliant e-mail archiving) in our local GW 7.0.2 system. Our (new)
> branch offices are running MS Exchange 2003 and we wouldn't like to
> migrate
> to Exchange. That's why we set up the GW 7.x Exchange Gateway (7.0.2)
> for
> e-mail transfer over a central exchange server which - so far - woks
fine.
> The exchange server is also responsible for x-spam tagging and virus
> scanning.
>
> TID #3878409 is from June 2007 and reported to engineering. Did they
> solve
> the 'problem'? If not, we probably have to go the hard way (to
> exchange)!
> This couldn't be the intension of this 'feature'...
>
> Does anybody has some information?
> Thank you in advance!
>
> Marco

GroupWise 7 Gateway For MS Exchange error

"The gateway is attempting to reestablish the GroupWise link" when starting
the gateway on the Exchange server. It's in a loop restarting. The user
logged in the the server has full rights to both AD and Edirectory and the
GW Domain. Any ideas what is causing this? The "other" link opens but not
the Groupwise. Rights??
D

Dave,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Do a search of our knowledgebase at http://support.novell.com/search/kb_index.jsp
- Check all of the other support tools and options available at
http://support.novell.com.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://support.novell.com/forums)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://support.novell.com/forums/faq_general.html
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

Groupwise to Exchange gateway full release

Does anyone know where I can find a list of fixes/changes to this gateway
from the beta release to the full?
Thanks.

Astinius,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Do a search of our knowledgebase at http://support.novell.com/search/kb_index.jsp
- Check all of the other support tools and options available at
http://support.novell.com.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://support.novell.com/forums)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://support.novell.com/forums/faq_general.html
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

Exchange 2010 and GroupWIse 7

Hi
We are currently preparing to migrate to Exchange 2010. Our AD domain is w2k8r2 so we are unable to get an exchange 2003 server into the domain thus are unable to use the GroupWise connector.
So I have setup a non-groupwise domain for the exchange server and this is linked to the GWIA. I have added an exchange user to the non groupwise domain and can see this in the system address book. When I try and send this user an email I get a 550 rejecting spoofed message.
How can I get the GWIA to route email to the Exchange system?
Thanks
Andy

Hi Massimo
The issue that I have is that the domain of my users in GW and Exchange is the same. So when you send from GW to Exchange GW is seeing the address as the external address so when it hits the gwia it's being rejected because it thinks it's spam.
Ideally what I need is the Exchange user to appear as a friendly name such as Joe Bloggs but for the address behind to be pointing to the internal Exchange address.
Cheers
Andy
Originally Posted by mrosen
Hi,
AndyTee wrote:
>
> Hi
>
> We are currently preparing to migrate to Exchange 2010.
My sympathy. ;)
> Our AD domain
> is w2k8r2 so we are unable to get an exchange 2003 server into the
> domain
Hey, that's cool. <g>
> So I have setup a non-groupwise domain for the exchange server and this
> is linked to the GWIA. I have added an exchange user to the non
> groupwise domain and can see this in the system address book. When I try
> and send this user an email I get a 550 rejecting spoofed message.
>
> How can I get the GWIA to route email to the Exchange system?
You did. What makes you believe it's GW causing your problem? Because it
duly delivers the Exchange error message?
CU,
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
Untitled Document

Migrate exchange 2003 to groupwise 7.3

I am planning on migrating 600 exchange users on 5 exchange servers to one groupwise server. I plan to use OES linux 64 bit on hp multiprocessor server 6gig ram. The groupwise server will be running poa,mta,gwia,web access agent and webaccess application. My question is do you think one server can handle this? I have netware boxes with 300 users single processor that run like the wind but have not tried linux.

Originally Posted by browndn
I am planning on migrating 600 exchange users on 5 exchange servers to one groupwise server. I plan to use OES linux 64 bit on hp multiprocessor server 6gig ram. The groupwise server will be running poa,mta,gwia,web access agent and webaccess application. My question is do you think one server can handle this? I have netware boxes with 300 users single processor that run like the wind but have not tried linux.
Yeah, it will work fine... I'll got GW running on SLES10 on one old P4 with 2GB Ram with 1200-1300 users :) I will be upgrading it to a new server, not because it can't handle the load but because it is running on old hardware.
Thomas

Install error Exchange Gateway

I am trying to install the Exchange 7x gateway on a Windows 2003 Exchange
2003 server but it gets as far as the screen where I select "Install
Gateway and Addressing components" and an error message comes up:
"Setup requires the Directory Synchronization be running on the Exchange
server" and the install stop.
Any help would be greatly appreciated.
Thanks

> Thanks Tim and thanks Kathy for the response. There is no Exchange
> Directory Synch service. I have searched MS and Goolge to try and find
> out why I do not have this service but have not found anything. Could
the
> fact that I have Exchange 2003 Enterprise server be the cause.
>
> Thanks
> Maurae
>
>
> > Not for me
> >
> > "sounds like the exchange service directory synch is not running. "
> >
> >
> >
> >
> >
> > On Tue, 21 Aug 2007 07:58:48 GMT, [email protected] wrote:
> >
> > >>
> >
>
>c291bmRzIGxpa2UgdGhlIGV4Y2hhbmdlIHNlcnZpY2UgZGlyZ WN0b3J5IHN5bmNoIGlzIG5vdC
> B
> > >y
> > >> dW5uaW5nLiAg
> > >>
> > >It looks like there is a font/format error in Kathy's reply
> > Tim
> > ___________________
> > Tim Heywood (SYSOP)
> > NDS8
> > Scotland
> > (God's Country)
> > www.nds8.co.uk
> > ___________________
> >
> > In theory, practice and theory are the same
> > In Practice, they are different
>

Exchange gateway and sending mail

I can send mail from Exchange to GW, but not the other way. The log reports
a "Error submitting message to Exchange". Exchange is the name of my
gateway.

Hi,
1. You have to Configure the Email connections through SCOT tcode.
2. After that you ccan send/recive a mails from exchange server and SAP R/3 systems.
Look into the following link.
http://help.spa.com--> search for E-mail configuration and aslo search for FAX configuration.
Regards,
Srini Nookala

Portal Gateway configuration for Proxy functionality

Hi All,
Are there any customers out there configuring their Portal Gateway to go through
a Proxy server and then have the proxy server pass requests to the Portal server?
Or do you recommend configuring the Portal Gateway to go through the Portal server(via the gateway proxy add-on)?
Does anyone have pros or cons for the 2 scenarios?
Please email me at [email protected]
Thanks,
Chris Wilt
TransCanada

The proxy add ons with the portal server have both http and netlet proxy deamons, if your using netlet then the recommendation would be to use the netlet proxy for netlets and httpd proxy for http traffic.
If your not using netlets then you can put in a proxy server between the gateway and server. I have seen different customers use either of the two for security and varying reasons specific to their environment.
The httpd and netlet proxies are primarily used when there is a requirement to clamp down the number of open between the gateway and the server. Generally there would be a firewall between the gateway and server and for security reasons you don't want to open a lot of ports, so in that context with the gateway and netlet proxies you only open two ports in addition to profile server port and 443 if your running gateway on ssl.
HTH ..

GroupWise 7 Exchange Gateway "Bad GroupWise proxy"

Similar Messages

Maybe you are looking for