Ok...here's the situation...
I haven't been spending a lot of time lately in the mechanics of
Exchange...I have been concentrating on backups and antivirus...so
don't flog me. ;0)
Unfortunately, we are not getting the funding right now to move from
Exchange 5.5 to Exchange 2003, so I have to do a 5.5 ---> 5.5
migration. We will be doing another 5.5 ---> 2003 migration, later
this year.
The migration will be from an old site in one org, to a new site in a
new org with a new domain name, on new hardware. I was thinking with
5.5, that it was kind of brain-dead and that I could just forklift the
DB file over, run ISInteg and ESEUtil on it and start it up. It
doesn't appear that it's going to be that easy.
I have looked in the 5.5 books I have and Googled the web for Exchange
5.5 migration...all it comes up with is 5.5 ---> 2003 migration
plans....nothing straight across.
I asked this question on another list I belong to, but most of you
don't belong to that list, so I thought I'd ask here too.
So far, I have three strategies of attack:
STRATEGY 1
1A. Build new ex5.5 box in current ORG/Site
1B. Move users to new server
1C. Replicate and then Rehome PF's to the new server.
1D. Export all DL's, mailbox info and PF info to a .csv file as a backup.
1E. ExMerge a copy of all mailboxes off to .pst files as a backup.
1F. Copy the Custom Forms Library before moving.
1G. Use Move Server Wizard to move new server to new ORG/Site
1H. Change the domain membership.
1I. Import all DL's.
STRATEGY 2
2A. EXMerge everyone off.
2B. Create the new box.
2C. Create the accounts.
2D. EXMerge everyone back in.
(This plan still doesn't address the issue of public folders)
STRATEGY 3
Right now, we share an Exchange org with another company. We are
in one site, they are the other...only two sites in the organization.
They have their own e-mail domain name, we have our
own...completely seperate there. Our MX record for our domain name
points to our external mail relayer, which then forwards mail on to
our IMS...Their setup is the same.
We lost connectivity between the two sites for the better part of
four days before, with no adverse affects to our e-mail system (with
the obvious exception that we couldn't send e-mail to the people in
the other site)...Internet mail was fine. Sooooo...given that, would
the following steps for strategy 3?
3A. Full backups of the existing e-mail servers.
3B. Remove the bridgehead connector for the other site in the org.
3C. Push a new Outlook shortcut to all our workstations that clears
the Exchange cache.
3D. ExMerge all of their people out of the GAL (so that Outlook
doesn't try and resolve them anymore).
3E. Continue on with business, until we are ready to migrate to Exchange 2003.
Will that work, or is removing the bridgehead connector going to kill
Exchange? Will the clients wind up breaking? There are no PF's or
anything else in the sites that is shared.
So...any other ideas or directions?
TIA,
Jim Blunt
E-mail / AntiVirus / Backup Admin
Infrastructure & Information Services
Washington Closure Hanford, LLC
509-372-9188
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange
To subscribe: http://e-newsletters.internet.com/discussionlists.html/
To unsubscribe send a blank email to [EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]
To unsubscribe via postal mail, please contact us at:
Jupitermedia Corp.
Attn: Discussion List Management
475 Park Avenue South
New York, NY 10016
Please include the email address which you have been contacted with.
