Your work around reminds me of another step that you have not yet mentioned.
If you haven't already done so, you must do the following.
Create a Foreign External Domain in GroupWise. Then don't forget to link
your GroupWise domain to the newly created External Foreign domain.
If you have already done this, the only thing else that I can think of is
the Dir Sync setting of the GWAPI gateway set it to both and restart the
This configuration works for me. Beware though, deleting the Exchange
contact or user will delete the GroupWise mailbox too. That's not always
> > You should be able to see them in the address book as well as in
> > when you highlight the Exchange External Foreign domain in the groupwise
> > view.
> Unfortunately, I don't
> > I would check a couple of places. First check the API Gateway object and
> > verify that dirsync is set to Exchange.
> It is.
> > If it is I would then look at the
> > GroupWise connector on the Exchange server. On the Export tab verify the
> > have specified an Active Directory OU to export. This is typically the
> > folder.
> Yup, set to the Users OU.
> > With these two set, force a dirsync both ways from the Exchange server.
> > Within a few minutes you should see the Exchange aliases showing up in
> > GroupWsie address book.
> When I force a Dirsync, I can see the requests pass from the Exchange
> Connector into the API Gateway, but nothing ever shows up in the
> GW address book (nor as NDS objects).
> I've come up with a workaround that involves creating Groupwise
> External Users as I migrate people over to Exchange.
> Thanks for responding.