Groupwise Migration - Advice

[timmoat]

Dear all,

I've been testing a migration scenario from Groupwise 7.02 to Exchange 2007 via an Exchange 2003 server.

Connector is working between all three servers, as is the free/busy lookups so all is well on that front.

I had 2 questions:

1) Whilst emails from the Exchange server do reach the Groupwise client they take many minutes to appear - unless the groupwise user clicks another folder within groupwise and then goes back to the inbox in which case it immediatley appears! This reminds me of how Exchange Cache Mode works sometimes. Does anyone know how I can speed this 'polling' up? Ideally I want as little delay as possible. 65 mailboxes will be moved in the final migration so we are dealing with a relatively small environment

2) What do you recommend with regards to email flow inbound and outbound to the Internet for the 2 systems? On my test environment I changed port 25 to be delivered to the Exchange 2007 box, which then forwards onto the GroupWise clients via the connector.

a) I have to cater for additional smtp aliases in the groupwise accounts if I do it this way. Is there a way to ensure these are taken across to Exchange from Groupwise?

b) Should my GroupWise box continue to send direct to the Internet for Outbound or should I be sending those across the connector?

Systems will co-exist for a few weeks I would imagine whilst migrations occur and the new box's stability is tested.

Any advice would be VERY helpful!

Cheers

Tim

 

[timmoat]

Ok, ignore problem 1!

Forgot to check the obvious - windows firewall was blocking the polling. Knew I had seen it before somewhere!

Still really need a hand with the Internet mail flow as i'm having problems sending outbound for GroupWise users.

Can anyone give me an idea as to what works best for Internet mail flow during the coexist period?

1) Changed MX records so that mail enters Exchange 2007 server and this works well

Should Groupwise send directly to Internet for outbound mail or should these go over the connector and out via the Exchange 2003/2007 server?

 

[58sniper]

I think that's personal preference. I would have all outbound mail going out via Exchange 2007 if you have any transport rules setup, or if that's where your hygiene is.

Watch out for HTML email though, as the connector tends to not like that.

Pat Richard
Microsoft Exchange MVP
Contributing author Microsoft Exchange Server 2007: The Complete Reference

 

[timmoat]

Well we send all outbound mail via a smarthost (Email Systems/Webroot and an excellent service it is too!) so I guess there is no real reason to send over the connector - especially as you rightly say HTML does not come across correctly.

May be down to my Groupwise config as I threw this test box together in a rush. Seems to be when I do a reply to all when there are multiple parties involved some external, some from exchange, some from groupwise.

Will try to track down and be more specific.

Cheers

Tim

 

[58sniper]

How is inter-org email mail being routed during the migration? Typically, it's over the connector.

Pat Richard
Microsoft Exchange MVP
Contributing author Microsoft Exchange Server 2007: The Complete Reference

 

[timmoat]

Over the connector.

I have that all working and mail flows from Groupwise to Exchange 2007 via a Exchange 2003 box. Calendar free/busy lookups working well.

Its literally how to deal with external mail.

I've read in many places (some in this forum and the groupwise forum) that inbound should go to the Exchange side first other wise it can fudge up some addresses.

 

[58sniper]

That's generally true. You don't mention the setup, such as if you're using an Edge Transport or anything like that. But bringing mail into the environment and through the connector for those still on GroupWise.

Nathan Winters has worked on a 6 part series on migrating from GroupWise to Exchange 2007 @ MSExchange.org. Check it out.

http://www.msexchange.org/articles_...ge-2007-interoperability-migration-part1.html

Pat Richard
Microsoft Exchange MVP
Contributing author Microsoft Exchange Server 2007: The Complete Reference

 

[timmoat]

Thats the guide that I followed - and fantastic it is too. Would recommend for anyone attempting to do this.

We will not be utilising the edge transport server role initially due to hardware costs. We are a relativly small firm (only 65 users) and as such there is little need immediately.

As firewall locks down our mail flow to and from our 3rd party mail filtering company the risks are already minimised although I would be happier using edge transport down the line.