Exchange and AD replication

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Hi,

I just wanted to clarify something regarding Exchange Server 2003. Here goes:

If I have 2 Domain Controllers, DC01 and DC02, and I install Exchange server 2003 on to DC01, Exchange will integrate with Active Directory on DC01.

Will this integration be replicated to DC02? So I can go to DC02 and select a user and perform Exchange type tasks from this domain controller even though Exchange is not installed on the server.

Cheers,

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

As far as I know, yes.

 

Though it is not best practise to place Exchange on a DC it can be done, noting that the link to Petri's knowledge base contains several valid points.

The main objection I think is shutting down and restarting and the box seesm to hang - the solution is to script shutdown for the Exchange services prior to full shut-down.

I have often setup Exchange boxes at remote sites using slower links with the Server also a Dc/Gc due to budget constraints etc.

Just get your milestones right first..such as IP, DNS, and AD - noting that AD integrated helps as you basically have a choice of integrating a timely login with better AD support OR maximising the link capacity for file transfers, user emails and web traffic.

The link to remember is that users will always complain no matter how much of a slow link you give them. So get what you need to keep the network functioning - if the remote office manager complains give him the price of an upgraded WAN link and get him help you obtain approval for a WAN upgrade.

..works for me...and I lower my ongoing support obligations to remote sites.

supa

 

Thanks for the info guys.

We are planning to remove AD from this Exchange server because we will have a couple of servers available soon. Exchange will be on its own box then.

Not too sure what the best way of doing this will be yet. It appears that the original install was not done very well so it could be a start from scratch job!

 

About 50+ users and a handful of admin mailboxes. Not the most complex of Exchange setups i know!

 

Yeah that's the general plan. Demote the DC and then remove AD.

This DC is also our only DNS server! I was going to put DNS on our 2nd DC, make it the primary DC and Global Catalog, then promote another server to become a DC. Then remove everything off the Exchange box except Exchange (unless things go tits up and it needs re-installing!).

I then need to add a DNS server and AD on the other side of our WAN link at our main office. I should then not have to worry about 1 server falling over and our whole network grinding to a painful halt! lol

 

That is actually a good idea and quite common nowadays to do this for DHCP scopes.

Note that if you have a DC in each office connected via WAN they also should be Global Catalogs so that both logins and stuff like finding email addresses is available quickly at both sites.

Sure the AD replication adds abit for bandwidth, but you are better of providing a resilient AD/DNS offering compared to maximising user bandwidth as no matter how much bandwidth you give users over a WAN..it is NEVER enough...