Remote Sites and AD

  • Thread starter Thread starter Jeff
  • Start date Start date
J

Jeff

Currently we have several remote sites, but they do not have domain
controllers at the site. All users authenticate back to our headquarters
over the WAN links. We want to ensure that users can logon even if the WAN
link goes down. What is the best way to do that? If I install an additional
domain controller at the sites, will users be able to authenticate even if
the WAN goes down?

Where are some resources I can get info on this?

Thanks for the assistance.

Jeff
 
thanks for the reply. I am familiar with sites in AD and will configure
that in this case. However, I have 2 main questions:

1. If the remote site has a domain controller, will users there be able to
login even if the link to our headquarters goes down?

2. What is the best way to setup and configure the domain controller for the
remote site? Can I set it up at headquarters and then take it to the remote
site, change the IP address, etc.?

Thanks,

Jeff
 
1. If the remote site has a domain controller, will users there be able
to
login even if the link to our headquarters goes down?
Yes.

2. What is the best way to setup and configure the domain controller for the
remote site? Can I set it up at headquarters and then take it to the remote
site, change the IP address, etc.?
Click to expand...

I believe you can do it either way. I prefer to do it at the site.

DDS
 
A followup question to my initial one:

I have one site in particular that I am going to set up a domain controller
at. The site only has a 128 kb/s connection back to our main headquarters.
I would like to do the dcpromo at the site, but the initial replication
could take a really long time with their slow connection. How much time can
I expect the dcpromo to take if I do it at the site? Is there a way to set
up the DC at my main site and then move it to the remote site (Change the
IP, site location, etc.)?

Thanks,

Jeff
 
Back
Top