I have a scenario of implementing ADS synchorisation over internet . I have a local ADS running in 2003 server .I planned to  install exchange server in a remote location where my production servers are located .I have Ipsec VPN connectivity between local to remote .Which is the best way to replicte ADS with exchange in this case .Do I need to install another ADC in the remote location and create atwo way trust between these DCs or I can directly sync to the remote exchange server ? Si any other way to accomplish this without VPN? I mean through direct internet? .Please give your suggestions.
LVL 11
Who is Participating?
pwindellConnect With a Mentor Commented:
The network connectivity is independent of any of the Domain stuff.  Mainly it just has to "work",...connectivity and routing correct, "works",...your ready to go there.   IP Scheme needs each location to be a different subnet to avoid burdening the slow WAN link with broadcasts,...meaning it needs to be a routed conenction,...not bridged

When you have two locations separated by a WAN link (VPN or whatever) you place a DC in each location. These would be DCs for the same domain,...there is only one domain,...particularly if you want to keep this simple (and there is no reason to over-complicate it).   Then configure Active Directory Sites & Services.  When doing that you create the Subnet Objects, Site Objects (just leave the "Default Site" there and don't use it).  Then create a Site Connector Object.  The built in Help in the AD Sites & Services MMC should have all the details you need, is not complicated as long as you don't make it complicated,..."keep it simple" applies here.  When finished you can set the Replication Rate between the Sites.  If you have a good solid VPN witrh reasonable bandwidth set it to the lowest rate (the fastest).  I think that is 5 minutes or 15 minutes, I forget which.

The AD Sites & Services also ensures that users and their workstations use the DC closest to them to keep excess traffic off the sow WAN link.

Basically it is the AD Sites & Services tha manage all this and it is not that complex.

Exchange,...well just do what you want there. You can place one at each Site or just use one central Exchange,...either way it works.  You can also start with just one and add the other one later after all the other WAN stuff is tweeked and running well,...Exchange depends on AD so it is good to make sure the WAN and AD are all happy and smiling first.  Then it also gives you time to study up on Exchange and how to deal with a "pair" of Exchanges in the same Exchange Organization.  The fact that the two Exchanges being separated by a slow WAN -vs- a fast local LAN Connection is pretty much just irrelevant other than performing a bit slower,...but functionaly nothing changes
sumeshbnrAuthor Commented:
Thanks Any other comments?
It is always recommended to have a ADC in the Exchange site, so that the users doesn't get affected if the ADS in the primary site is down.  

You need not create a trust relationship between the DC's because as soon as you create a ADC the two way trust will get automatically established.
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

pwindellConnect With a Mentor Commented:
There is no ADC here.  This is all one Domain (or should be) and all one Exchange Organization.  You can even create the new DC with it sitting 6 inches away from the existing one then transport it to the new Site afterwards and readjust the addressing.  As far as Exchange the only ADC (Active Directory Connector) with it was with Exchange 5.5 to interact with Exchange2000 or newer because Ex5.5 was not Active Directory enabled.

If it is Exchange2007 or 2010 then it uses the AD Sites & Services to cover it's routing mechanism because the old Routing Groups in Exchange2003 has be replaced with the AD Sites & Services.
Hello Pwindell, Sorry for the confusion.
By ADC I meant Additonal Domain Controller.
Ah!  Ok,...sorry  :-)   I feel stupid now.
All Courses

From novice to tech pro — start learning today.