Groupwise-Exchange migration 2

[ovs8]

Hi there,

I'm going to test-migrate our email system from our working Groupwise5.2 Server to the "test" MS Exchange 2003 server.

I wondering, does the migration move users and email to MS Exchange or only copies them? Can I continue using GW5.2 as our only email system after the test?

Thank you,
oleg

 

[sstoppel]

The migration is non-destructive, you can migrate mailboxes over and over if you wish.

Co-existence stinks on toast, however, so I would plan to move all the way as fast as possible.

 

[ovs8]

This is just a test migration. My other worry is that after I establish the link between the GW and the "test" MS Exchange server am I going to be able to safely break this link and establish a new one with the actual Exchange server?

Thanks,
oleg

 

[marvhuffaker]

I'm worried that your exchange migration is going to be outrageously expensive. Plus your users won't like getting viruses. They take the 'no viruses spread via email' for granted now, but will soon learn to appreciate it once you force exchange on them.



Marvin Huffaker, MCNE

http://www.redjuju.com

 

[sstoppel]

Marvin, you and I know that GW is an admin's dream of affordability, stability, and security. That, however, is no way to build yourself an IT empire. If you are alone doing network admin, you can quickly get to be a supervisor of several just by making the switch.

 

[ovs8]

Well, I hope that our Symantec AV servers with Exchange protection are going to be able to handle the virus thing.

And actually migration is not going to be much more expensive for us than upgrading.

But, what about my previous question?
<<My other worry is that after I establish the link between the GW and the "test" MS Exchange server am I going to be able to safely break this link and establish a new one with the actual Exchange server?>>

Any suggestions?
Thank you,

 

[marvhuffaker]

sstoppel, that reminds me of something a certain bluehaired punk said once...

http://www.bluegunk.com

Marvin Huffaker, MCNE

http://www.redjuju.com

 

[ITsmyfault]

Couple notes:
- A/V products are *all* reactive, not proactive. You will always be behind the threats. Think about that.

- Take the time you won't spend patching and go home and see your family.

- If Exchange is so wonderful, why are ~70% of users still not upgrading to Exch '03? Why are 30% still on 5.5? For contrast, there are more folks on GW 6.5 than there are on Exchange 2003 due to the pitifully low uptake rate for msft. The obvious reasons are that upgrades are rip and replace (max cost, max risk) and that the newer versions don't offer enough value to make the upgrade worthwhile. At the same time, lots of folks put it in.. and are now stuck with it. Admitting you spent millions putting in exchange and then reccomending migrating could be viewed as a CLM.. or I think more folks would switch honestly.

What are the business drivers for changing? Both products have near parity on the feature/funtionality scale. Sequoia (due this summer) is going to support either client via a new 'shim' - Groupwise Win32 or OL2000-2003, so if there is some client issue going on you could save your money and wait 3 months. Sequoia also has some very cool calendaring features which I don't beleive OL can replicate.

Yes, you won't get to manage a dept running GW, bc one person can run the thing easily with thousands of users. And they will get complacent when email is always 'up'.

Did you know that most corp mail systems experience 8 hours of unplanned downtime a month? And that Exchange shops experience more than the average? GW was not used in these figures btw. And informal poll of admins from a GW listserve had most folks guestimating they were below 8 hrs of unplanned downtime a year.

I don't know the answer to your other question.. but I can say it's sad to even have to worry about something like that. If Exch used a config file that a human being could understand, such an issue would simply not exist. But instead, to attempt to 'hide' the complexity of the systems these settings get written in hex to obscure registry keys so that when something breaks you are SOL.

jm2c