GW 6.5 exchange 2003 co-existance

[kjmikich]

I would suggest using the API only if you are migrating and need the API. Some products such as quest need the API. For simple co-existence I would use the GroupWise Gateway for Exchange rather then the API.

I have set up the GW connector on Exchange and the 4.1.5 API gateway on Groupwise.
Mail goes out from both systems to the cloud without a problem
Mail coming into a user on exchange with no account on GW is forwarded by the GWIA /fut switch and arrives in outlook.
Mail coming into a user with an account in the Groupwise post office arrives in Groupwise
I am able to pass mail from one system to the other using the following:

From exchange mail sent to (exchange.first administrative group.first last) arrives in the groupwise mailbox
From groupwise mail sent to (doman_dom.domain_main_po.gwusername) arrives in the exchange mailbox.

This is where the problem starts. I need both systems to run as my client does not want to migrate all at once.
So the plan was to use the dirsync to put tags on the accounts to refer to the other system so all mail from inside or out is delivered to both gw and exch. (there are matching accounts in both systems) However when I run the dirsync I get an error on the API that says ERROR – Directory service message was not in the DS input directory. I have setup the gwconnector to archive everything that passes through \exchsvr\conndata\gwrouter. I have checked these folders and found the correct files in the dirsync folder as well as the togwise folder so it seems that the lsdxa process is working except my app log shows a few errors (511, 8243 and 8265) all seem to indicate a problem with file handling.

I have noticed however that the gwise addresses appear in most AD accounts. There are two of them. one points to exchange.First administrative group.user and the other points to the gw domain and PO for that user.
I have read that on the groupwise account there should be an entry in custom attribute 5 pointing back to exchange but I am not sure where to find the custom attributes in the nwadmin console or in console 1.

So my question is 1. Am I taking the right approach here or is there an easier way and 2. What could cause the dirsync to fail in this way and if it does work correctly will it deliver all mail to both systems.