Computing.Net > Forums > Windows Server 2003 > Splitting DC and Exchange

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

Splitting DC and Exchange

Reply to Message Icon

Name: altu
Date: November 19, 2005 at 03:36:28 Pacific
OS: Win2k3
CPU/Ram: P4, 512
Comment:

Hello,

I've been handed down an Exchange server 2003 which has been installed on the company's AD.

I want to split it into a separate exchange server and another one with active direcory.

Please help.



Sponsored Link
Ads by Google

Response Number 1
Name: Curt R
Date: November 19, 2005 at 05:55:50 Pacific
Reply:

So get a second server, install 2003 and promote it to a DC. Put a copy of the GC on the second DC and move some of the FSMO roles to the second DC. I wouldn't demote your Exchange server to just a plain standalone server if it's the only DC presently in your environment. Having two DC's minimum is always a good idea for your own protection. Done properly, two (or more) DC's will give you redundancy. Should the one crash, the second one can take over reducing down time on your domain.


0

Response Number 2
Name: altu
Date: November 19, 2005 at 22:08:01 Pacific
Reply:

So, you're essentially saying:

http://www.swinc.com/resources/exchange/faq_db.asp?status=questions&faqID=1001&faqname=Exchange%202000§ionID=1024§ionName=Exchange%202000%20Move%20Server%20Method

Essentially it's straightforward. New server, join domain, install exchange, replicate PF's, move mailboxes, and then follow the MS KB's (referenced in doc) to decomission the Exchange on the current box.

Right?

Please correct me if I'm wrong.

Thanks again.


0

Response Number 3
Name: heropsycho2177
Date: November 19, 2005 at 22:51:08 Pacific
Reply:

Ideally, you would want three servers:

2 DC's, and an Exchange server.

Please help survivors of Hurricane Katrina!

www.redcross.org


0

Response Number 4
Name: Curt R
Date: November 20, 2005 at 09:32:01 Pacific
Reply:

Agreed, 3 would be best. However, if your budget prohibits 3 servers, I would just leave exchange where it is....there's not much point in moving it to the new server. That's just more work and creates chances for problems.


0

Response Number 5
Name: heropsycho2177
Date: November 20, 2005 at 11:27:43 Pacific
Reply:

"However, if your budget prohibits 3 servers, I would just leave exchange where it is."

Depends on how many users and how much mail is expected, as well as which is more important - redundancy with authenticating to the domain, or Exchange performance.

Please help survivors of Hurricane Katrina!

www.redcross.org


0

Related Posts

See More



Response Number 6
Name: Anand (by anandnet)
Date: November 21, 2005 at 01:01:01 Pacific
Reply:

i recommend not to move exchange ..
create another DC...
move all roles to newly created DC...
move GC to DC...
Then demote exchange server from DC by running DCpromo..

Best Wishes & Regards,
Anand Kale
Mumbai,India.


0

Response Number 7
Name: wanderer
Date: November 21, 2005 at 08:40:49 Pacific
Reply:

Anand, if he loses his one DC, you do realize he has to rebuild his entire network from scratch? After all he lost the GC.

If only two servers both should be dcs with dns and the GC

Golly gee wilerkers everyone. Learn to Internet Search


0

Response Number 8
Name: heropsycho2177
Date: November 21, 2005 at 09:25:42 Pacific
Reply:

He could restore from backup.

Wanderer, he's basically saying do one DC and one Exchange server, which again isn't a bad idea of there's going to be a lot of mailflow, or if his two servers aren't particularly beefy. It's a lot to ask one machine to be a domain controller and an exchange server if there's a lot of mail, or if there aren't enough disk spindles.

If you go the two DC's with exchange on one of them, that DC with Exchange should be the infrastructure master, schema master, and domain naming master. The other DC w/o exchange should be the PDC emulator and RID master. Both could be global catalogs, but be very aware of your disk i/o. Exchange does lots of random reads and writes to its transaction logs and database files, as does a busy domain controller/global catalog server. Try to get the Exchange and AD transaction logs on one physical drive or array, and their respective databases on a different one (or better yet, all four on different drives/arrays).

Please help survivors of Hurricane Katrina.

www.redcross.org


0

Response Number 9
Name: altu
Date: December 28, 2005 at 23:07:58 Pacific
Reply:

Thank you all for your input.

I'm picking up bits and pieces from all your posts. I'll update this as soon as I implement it.

Thanks again.


0

Sponsored Link
Ads by Google
Reply to Message Icon






Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows Server 2003 Forum Home


Sponsored links

Ads by Google


Results for: Splitting DC and Exchange

Migration of Users and Exchange Ema www.computing.net/answers/windows-2003/migration-of-users-and-exchange-ema/6649.html

windows server 2003 and Exchange se www.computing.net/answers/windows-2003/windows-server-2003-and-exchange-se/5479.html

Upgrade from w2kDC+MXS2k3 to w2k3 www.computing.net/answers/windows-2003/upgrade-from-w2kdcmxs2k3-to-w2k3-/712.html