Solved

Migration from Exchange Server 2000 to Exchange Server 2003 on new hardware

Posted on 2006-06-25
8
193 Views
Last Modified: 2010-03-06
This is the story, we currently have a Windows 2000 domain with Exchange Server 2000 the databases total about 120Gb. We have built a new Windows 2003 Server domain with Exchange Server 2003. The question is what is the best way of migrating the data, as I know from past experience that migrating a single mailbox that contains about 4Gb through a Gigabit ethernat connection takes about 5 hours, so this will make my migration impossible to complete across a weekend. I was thinking there may be a possibility just to upgrade the old 2000 exchange to 2003, then take a copy of the databases and put them in the correct location on the new server, where I will have created the user accounts with mailboxes already, how will exchange react to bringing up databases on a new server with different computer name and domain, or any other suggestions.

0
Comment
Question by:pete_killick
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 4
8 Comments
 
LVL 104

Expert Comment

by:Sembee
ID: 16978282
What is the link between the new domain?
If they are totally separate then you only have one choice - and that is exmerge.

Trying to move the databases around will not work - a change in domain and servername will not be accepted by Exchange and the databases will not mount.

Simon.
0
 

Author Comment

by:pete_killick
ID: 16978496
The link between the two domains is purely a trust on the same subnet.

If exmerge is the only way is there anyway of speeding up the process?
0
 
LVL 104

Expert Comment

by:Sembee
ID: 16978598
Not really.
Any reason you went with a new domain? With a store that size I would have advised the client to go with the same domain so that it could be done on a conventional swing.
You are doing too many changes to allow for an easy database move.

You could look at one of the migration tools, I would start with Quest. However they will probably suggest the same thing, because you are going across a domain.

Otherwise you are looking at some kind of staged migration plan, with the servers co-existing.

Simon.
0
Office 365 Training for Admins - 7 Day Trial

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

 

Author Comment

by:pete_killick
ID: 16993438
Hi Simon

I just wanted a fresh start on a new system, remove all the old info so start a fresh...

Surely with the way technology is these days there is a more reliable and simplified method.

Pain in the wotsits if you know what I mean...
0
 
LVL 104

Expert Comment

by:Sembee
ID: 16994982
As technology gets more advanced, the applications increase in complexity. That includes moving data around. Hence why companies like Quest develop their products. Exchange is very closely tied in to the active directory, and moving databases around usually fails.

I too like to start a fresh, but sometimes it reaches a point where starting fresh will make things worse because the company cannot tolerate the pain.

Simon.
0
 

Author Comment

by:pete_killick
ID: 17000131
I take it I will have to use the rendom utility with 2003 to add the new network to the old, might winge as both have master browsers, what do you reckon?
0
 

Author Comment

by:pete_killick
ID: 17088839
I am taking the plunge and reloading all the new servers to join them onto the existing domain, will I have to run adprep on all the servers in the existing domain, and if so can I do that on a live system?

Cheers
0
 
LVL 104

Accepted Solution

by:
Sembee earned 500 total points
ID: 17089818
The prep tools are domain wide, not server wide. If you have already prepped for Exchange 2003 then you don't need to do it again.

Simon.
0

Featured Post

NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Read this checklist to learn more about the 15 things you should never include in an email signature.
A couple of months ago we ran into an issue that necessitated re-creating our Edge Subscriptions. However, when we attempted to execute the command: New-EdgeSubscription -filename C:\NewEdgeSub_01.xml we received an error indicating that the LDAP se…
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
Suggested Courses

630 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question