Re: AD replicate to server in Co-Location

I'm not sure how many domains do you have....

But it seams only one, so you can define two ipsubnets linked to the same
site, and configure the domain controllers with the proper Ip configurations
settings for each site. Configure DNS to have a AD integrated Zone and
configure replication to be domain or forest wide.

In the Exchange situation you can only use Clustering to provide full
tolerance.
http://www.microsoft.com/technet/prodtechnol/exchange/2000/library/dme2ksc.mspx

In the File Server you can use DFS - Distributed File System:
http://www.microsoft.com/windowsserver2003/techinfo/overview/dfs.mspx

Make sure that users will have always access to name resolution (DNS)
available to find the Domain controllers, and that the firewall allows
clients to query AD, allow zone transfers to one site to another.

Best Regards.






"ferg" <ferg@xxxxxxxx> wrote in message
news:O9$iNncTGHA.5808@xxxxxxxxxxxxxxxxxxxxxxx
G'Day List,

Greetings and best wishes.

Can someone point me in the right direction to get my AD to replicate to a
server that's in a co-location ?

I am setting up for Disaster Recovery/Business Continuity.
In the co-location site I plan to have:
Citrix/Terminal Server
Exchange 2003 Server
File/Application server
Domain Controller.
Firewall
Router

with the idea that if we have to shutdown the production LAN due to a
raging Florida hurricane, users will connect to the co-location through
Citrix/TS and work just as though they were connecting to the office. I am
still undecided on which one but , DoubleTake or NeverFail will be
handling the real-time replication of the E2K3 and File and Application
servers right up until the moment we failover the system.

Now how do I go about getting the Active Directory in the office to
replicate to the DC in the colocation site real-time with the idea that if
the office is shutdown, users connecting to the colo will still get AD
authentication?

Any ideas and thoughts welcome on all parts of the colocation setup.

Thanks



.

Relevant Pages

  • AD replicate to server in Co-Location
    ... Can someone point me in the right direction to get my AD to replicate to a ... In the co-location site I plan to have: ... Exchange 2003 Server ...
    (microsoft.public.win2000.active_directory)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... I just promoted the remote DC last week, so I still have time to solve the replication issues. ... Domain Controller Diagnosis ... Connecting to directory service on server alpha. ... Performing upstream analysis. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... alpha server as soon as you can to get things going. ... A simple DNS replication test is to create a host record in the SBS server ... Domain Controller Diagnosis ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... I did make the changes that you suggested on the DNS of my alpha server and rebooted. ... I did run the simple DNS test that you suggested by adding a host record to my SBS server. ... A simple DNS replication test is to create a host record in the SBS server and wait till it shows up in the remote server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Unable to decommission a Windows 2008 DC via dcpromo
    ... Can you open and compare sysvol and netlogon share on both DCs? ... Verifying that the local machine server2, ... The File Replication Service Event log test ... Latency information for 8 entries in the vector were ...
    (microsoft.public.windows.server.active_directory)