Question Locked

One or two Domain servers for branch offices?

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have just installed a brand new Win 2003 Server in office A. Branch office B's network is currently a mess comprised of Win Home Ed. PCs and laptops with no domain server, one device firewall and an Internet link. There is no domain set up for site B.

The plan is to unify management of both offices centrally. A VPN is planned between the two offices.

I would also like to use the two sites as data replication centers for one another to provide some data loss protection. It is also important that I can manage domain account access rights for users in departments with sensitive information on their PCs at both sites A and B.

Question 1: Should I install a second domain server at site B that would sync account credentials with site A's domain server?

Question 2: Could I get site B's computers to log onto the domain server at site A across the VPN link to save me the cost of buying an extra server, OS software, and CALs for site B? If the VPN fails for some reason wouldn't this adversely affect users at site B?

Question 3: What would the Pros and Cons be for having two domain servers as opposed to only one, if any?

Thnx for your input.
Mike

9 replies

by sgt_shultz

more data needed. how many pcs at site b. what kind of a link between the two. i think you want a dc at each site...
keep in mind xp home can't join a domain...

by spamgambit

1. Site B has approximately 30 PCs
2. 10Mbps cable WAN links to ISP at both sites A and B
3. XP Home: I'm fully aware of this fact which is why I'd like to reduce the total cost on my proposal price tag to management to sort out this network since I'd have to buy Vista lics and install XP Pro to replace the OS on the Home Ed. PCs. Another Win2k3 Server including hardware, lic, CALs and media kit is going to add approximately $3k to the proposal price tag; a nice saving if it's viable. That having been said I'm not inclined to buy myself a bag of problems for the future by saving the costs now but paying the price on support later.

by why me worry?

and must be upgraded to XP Pro or replaced. Also, there is no need to deploy a Global Catalogue in every site as was needed with Windows 2000 because Windows Server 2003 has Universal Group Caching to alleviate having to throw GCs' all over the place. The only requirement for Universal Group Caching is to be running at Windows 2003 Forest Functional Level, which would ensue that no Windows 2000 servers or workstations still exist on the network.

by bkinsey1

Taking your questions in order to start with:

1) Probably. If you're talking very few users you might get by without. Also depends on speed and reliability of your internet connection you're using to VPN.

2) You could, but, yes, a link outage in this case would adversely affect site B. And depending on the quality and bandwith of the VPN link, logins, etc. might be noticeably laggy even when the link's up.

3) Primary reason to have more than one DC is simply redundancy. While there are performance advantages in a branch office setup with large numbers of users, that's really secondary to the simple fact that, with one DC, if it fails, your network just went bye-bye.

If operations at Site B are important, either in terms of lots of users, or just important functions, I'd spend the money for a DC at that location. Doesn't take much investment, if all you're doing with the machine is running it as a DC. The Site B users will be happy with fast logins, and you'll sleep better with a second DC in the event of a catastrophe. . .

by cg it

what requires access to site A for users to do their job?

If they don't access anything on site A accept for log on, then if site A ever goes down, they can use cached credentials.

If it was me, disaster recover plans should not be based on a site having a copy on their server.

Do a NAS/SAN.

redundancy give flexibility. If Site A goes down and site B has DNS, [and DCs with Global Catalog] then site Bs servers can be listed as 3rd and 4th to try.

by spamgambit

My gut feeling was to install a server on both sites for exactly the reasons you mentioned and if for nothing else then just for the peace of mind. I felt that I would like to get some more opinions and you've definitely confirmed it for me.
Thanks for taking the time to respond.
Mike

by why me worry?

You have to replace the desktops with XP Pro to join a domain. Also, it is a minimum requirement to have 2 domain controllers per site for DNS (assuming DNS integration with AD) and login redundancy.

by cg it

Best Practice is to have redundancy. Since Active Directory requires DNS to function properly and uses a DC, 2 DNS & DCs would be prudent. Best Practive with sites [back in the days of W2K] was if the WAN link was unreliable, 50% or more utilized, the site had a server and have more than 5 or 6 users, stick a DC [DNS,Global Catalog role] at the site. If the WAN link was reliable and underutilized, didn't have a server and 5 to 6 users, you didn't need to put in a DC [& DNS].

This discussion is closed to new replies.