Adding second DC to the domain with Exchange server 2003 on first one

I amadding second Dc to the current domain  which is ver workable but the only confusion i have is that the DC has Exchange server also on the primary/First  DC ,

--My plan is to gave seocnd dc and
- then have seperate server with exchnage and move allmail boxes formthe first DC

please advice me some quick pro and crons or your past same sort of experience and the checklist i ned to went thgouh before proceeding this plan.or any help ful doumnet son this


Who is Participating?
flyingskyConnect With a Mentor Commented:
You don't want Exchange on DC (you can google it, lots of problems, a quick one here Try avoid that as much as possible.
Transfering FSMO roles is much easier than install a second Exchange server then move mailboxes.
So my suggestion is
1. Add the new server as the second DC.
2. After AD replication, transfer the 5 FSMO roles from the first DC (Exchange server) to the new added server.
3. Demote the Exchange server so it's NOT a DC any more (Exchange still running on it).
4. Now your AD has only one DC. Later if you have another server, add it as another DC for fault tolerant.
I don't know your future plan of adding more servers, but basically it's not suggested to run Exchange on a DC. You can add this server as a DC, transfer all the FSMO roles from the Exchange box to the new one, then demote the Exchage as DC. It's better to later add another server as a second DC. Hope this helps.
suriiAuthor Commented:
Elaborating my Orignal question I am adding second Dc to the current domain  which is very workable but the only confusion i have is that the DC has Exchange server also on the primary/First  DC ,

--My plan is to have seocnd dc first  and AD replication  
- then woul;d like to have  seperate Exchange server and move all mail boxes form the first DC , ot he new exchange server 2003

please advice me some quick pro and crons so the second DC will also be able to  create Ad users as well as Exchnage mail boxes  on the First DC
your past same sort of experience and the checklist i need to go through before proceeding this plan.or any help ful doumnets on this

Environment Windows 2003 standard edition 32 bit - SP2
AD version :Active Directory Users and Computers Microsoft Corporation
Version: 5.2.3790.3959
MS EXCHANGE 2003 SP2 :Exchange System Microsoft Corporation
Version: 6.5.7638.1
Config auto : 389 ( LDAP port )
DC (auto) : 389

Please let me know if you want to any thing more than above.

GC (auto ) : 3268

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Old UserConnect With a Mentor Commented:
Install OS on the new server install all updates and SPs, add server to existing domain, follow the instructions in link below to add addition DC to existing domain.

Transfer all FSMO roles to new DC see link below

You now have  a domain with two DCs primary being the new server without Exchange.

Now build new server update add to domain install Exchange do not DCPromo this server

Install Exchange
Replicate Public folders
Move mailboxes

Leave the first exchange server running for a couple of weeks so Outlook clients swicth to new server

uninstall exchange from server

You end up with 2 DCs
one Exchange server on a member server not a DC
Old UserCommented:
Instructiions on how to remove exchange
Old UserCommented:
You should step through one item at a time.
Add a second server to the network making it a DC. The AD schema will replicate from the existing DC to the NEw DC.
You might want to explore using vbscript that add users to AD and also create exchange mailbox.
suriiAuthor Commented:
flyingsky & dpreston68

Your replies makes lot sof sense to me but there is one more problem that Primary/First DC is having trust relation with another domain   .  Although this trus is outbound and only with domain name not the computer name so should i presume that second DC with all 5 FSMO roles on it can have trust relation ship intact withe another domain and i dont need to create trust relation ship again with the second  and also DC with all 5 FSMo roles , that was why i have planned keep intact my first DC and just move mailboxes to another new EXchnage server 2003

please advice

And thanks all of you for your suggestions and replies


Trust relationship will stay once the DCs are fully replicated.
suriiAuthor Commented:
Thanks , I added second DC successfully and transferred roles as well which is very good

Now what I have to do to enable second DC to create user with mail boxes , because when i tried creating user  it didn't went further to create mailbox for the user.

Should i have to extend schema to the new DC although it is the owner of all five FSMO roles including schema master

Please advice
flyingskyConnect With a Mentor Commented:
All You need is to install the Exchange system management tools on the new DC.
To do this, run Exchange Server 2003 Setup (using the Exchange cd, run on the new DC).
On the Component Selection page, set the installation action to Custom, and then click Microsoft Exchange System Management Tools.

suriiAuthor Commented:
Thanks flyingsky: . it worked
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.

All Courses

From novice to tech pro — start learning today.