Re: Exchange 2000 to 2003 migration

Tech-Archive recommends: Speed Up your PC by fixing your registry

I think the Exmerge option should be a last resort. I always prefer to do
an intra-organizational transition using Move Mailbox because fewer things
get broken in that process.

This question is still best posted to an SBS newsgroup because you're
migrating from SBS, a process different from what most of us Exchange
practitioners perform, and the MVPs and others who work those groups are
much more familiar with those processes.
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
..

<compsosinc@xxxxxxxxx> wrote in message
news:4926b6ef-f7bc-4e4a-9b9b-4d25dd857d3c@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Sep 3, 11:10 pm, "Lanwench [MVP - Exchange]"
<lanwe...@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
compsos...@xxxxxxxxx wrote:
On Sep 2, 7:00 pm, "Lanwench [MVP - Exchange]"
<lanwe...@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
compsos...@xxxxxxxxx wrote:
We use SBS2000 and we are getting new hardware with SBS2003 OEM
installed by Dell.

If you're wise you'll do a clean reinstall rather than using any
preinstalled OS. Also, why hose your AD entirely and start from
scratch when you don't have to? Post in
microsoft.public.windows.server.sbs and some nice person will
probably reply recommendingwww.sbsmigration.com. Your user profiles
will need to be manually recreated otherwise, and it's a huge PITA.

How do we get the Exchange mailboxes (14GB) from 2000 to 2003?

Should we:

1. Open Outlook on each Client PC and Export Contacts/emails to
PSTs?

You could, but that's a nightmare & you lose single-instance support.

If so, how do we import those to Exchange 2003?

You could use Outlook for that side, too - but don't import.
Instead: open PST, select items, copy to mailbox folders, close PST.
It's arduous, but importing in Outlook runs the risk of data
corruption (it's happened to me many times) and is not recommended
by the Outlook gurus.

OR

2. How would EXMERGE work?

It would still lose single-instance storage & your mailboxes can't
exceed 2GB (really more like 1.8) or Exmerge can't handle it.

3. What size partition whould we use for Exhange 2003? Less than
75GB?

Well, E2003 with SP2 could in practice go up to 75GB per store. So
that's 150GB max if you add up the public & private stores. You'll
likely not get to that point, but you *could*. Plus you need
somewhere for your transaction logs to go, which shouldn't be on the
OS partition. Since you're using SBS you're probably not going to
have a standard "best practice" Exchange server setup where RAID is
concerned (separate arrays, etc), which is fine - but just make sure
you're doing the math.

Concerning Exmerge limitation with mailboxes greater than 2GB (of
which we have one user with that issue)...does that mean we would be
forced to use Swing It from SBS Migration? Or can the Exchange 2000
DB files be copied to external USB drive and copied to Exchange 2003?

Hi - please stick to the thread yuo've got going in the SBS group.- Hide
quoted text -

- Show quoted text -

Ok, but Ed just presented good information here so I am glad we posted
as my thread in SBS has taken a different path. Trying to present
specific questions to the right group.

What if we were going from SBS2000 to a separate Exchange 2003 Server
(not part of SBS2003) --how would we move the large mailboxes since
Exmerge has a problem with those over 1.8GB? We did purchase the Swing
It kit last night and are looking through the documentation as it
relates to going from 2000 to 2003. However, in hind sight with our
small network (less than 15 users) we may be better off doing the new
SBS2003 from scratch, new domain, new Server name, etc...

Our main concern is copying Exchange data from one system to the
other...just need to do more reading and our test environment is
limited as is time. Looks like we can still do the "forklift" approach
used by Swing It, but not sure yet

Thank you.


.

Quantcast