Improve company productivity with a Business Account.Sign Up

x
?
Solved

Moving Exchange 2003 DB

Posted on 2011-02-14
4
Medium Priority
?
263 Views
Last Modified: 2012-05-11
Setup a new 2003 server to migrate stores to get them off our DC.  The new server is setup as a member server in our domain.  Will run replication process for the Public Folders and then move mailboxes.  Is there anything I should watch out for and do I need to login to each client and change the Outlook settings or will they re-home to the new server?

Thanks
0
Comment
Question by:Webcc
  • 2
  • 2
4 Comments
 
LVL 29

Accepted Solution

by:
mass2612 earned 2000 total points
ID: 34893646
Hi,

There should be no major issues. Is the idea that you will eventually un-install Exchange from the DC or at least shut down the Exchange services on the DC?

You need to make sure that along with rehoming the public folders you need to move the RUS, OAB, free busy, etc. Also I would move a couple of mailboxes to the new server and test everything first then move the others.

If you keep the Exchange services running on the DC you do not need to update the clients as they will automatically re-direct when the Outlook client is started as long as they can still communicate with Exchange on the DC.

This article has a good overview of everything you need to do to move Exchange off the first Exchange server in your Org.

How to remove the first Exchange Server 2003 computer from the administrative group
http://support.microsoft.com/kb/822931

0
 

Author Comment

by:Webcc
ID: 34908705
Ok thanks.
If at some point in the future I want to shut down exchange services on the DC do I have to then re-direct the Outlook clients or would those settings be saved permanently?  Also, would it cause any performance issues if I were to leave Exchange on the DC, but with the services shutdown - for D/Recovery purposes?
0
 
LVL 29

Expert Comment

by:mass2612
ID: 34912028
Once the clients are updated its saved in their Outlook profile. If it were me I would migrate, test, monitor, shutdown the Exchange services on the DC, monitor and test some more and then remove Exchange from the DC. But it should not cause any perf issues leaving it there.
0
 

Author Closing Comment

by:Webcc
ID: 34913176
Thanks
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

This article explains how to move an Exchange 2013/2016 mailbox database and logs to a different drive.
This is a very interesting topic. Ransomware has been around for a while but has increased drastically over the last year or so.
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online) The email signat…
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…

608 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