Building AD for a multi-location business.

Hi, I am in the process of building and applying AD in a business with 17 separate locations. Until now everyone has been using local generic profiles named per department. We want to integrate AD so everyone has a user account and we can apply security groups and GPO and so on. My question is, how should I initially structure it? I have one DC and so far I just created a Computers OU and Users OU and listed all locations in sub-OUs under each. According to my boss, the same departments in different locations will have access to different things so there will probably be a lot of different departmental security groups.

Should I:

  1. Make a separate DC for each location?

  2. Create one OU containing all locations and then have Users and Computers sub-OUs in each location? I feel this would be too many clicks.

  3. Keep it the way I have it?

Posted Aug 24, 2020, 1:29 PM UTC

313
Test-NetConnection•

Please god don't put a domain controller at each location. Only put DC's at your datacenters and let your expensive WAN do what it was meant to do. Domain controllers at every site is a legacy architecture that is entirely unnecessary with WAN speeds measuring in the Mbps.

I like flat AD structures, and prefer using security groups with GPO security filtering to apply policies to specific departments. So I would have a generic OU for all of your users, one for computers, and under the computer OU break out two more for servers and workstations.

Keep in mind OU delegation when designing your AD structure. You will want your helpdesk to be able to add new computers/users, but not delete servers. They should be able to create new, normal users but not touch elevated groups (think domain admins). A 'privileged' OU that only your super users have access to is best practice.

9
rarmfield•

As you pointed out DCs only in the Datacenters unless you only have a single datacenter (unlikely) then I would put at least 1 in one of the remote sites for redundancy. Unless the connection between the remote locations and the datacenters are extremely slow and unreliable. If that is the case you would need to look into putting a domain controller (virtual maybe even Read Only) at those locations. you could then configure AD Sites and Services to replicate those DCs at times when it would not negatively impact other network services.

I cosign the GPO security filtering policies however, I would create a computer and a User OU for each location. The reason being is that this way you can delegate certain helpdesk roles to people at each location without them being able to modify all Users or computers .

2
PyroKid883OP•

I like this idea the most. Should I still create separate DCs for each location or just keep all users and computers of all locations in one DC and just apply security groups by location?

1
IowaOrganics•

"Should I still create separate DCs for each location or just keep all users and computers of all locations in one DC and just apply security groups by location "

Domain Controllers are replicated. Just create a centralized DC at a datacenter and then use it for DNS at your on site firewalls that are facilitating DHCP. IPSEC tunnel, vpn whatever.

The following will give you great flexibility when creating group policy, and easy LDAP queries.

-company.com
|-Company Users
||-Location A
||-Location B
||-System Administrators Local Admin
|||-jim.bob.Ladmin
||-Privileged users (if you must)
||-Service Accounts
||-Security Groups (for shared drive GPO etc)
|||-Accounting
|||-HR
|||-Company Users
|||-Company Administrators
|||-Company Remote Users
||-Distribution Groups (for emailing)
|||-All employees
|||-Location A employees

|-Managed Computers
||-Location A
|||-Servers
|||-Workstations
||-Location B
||-Datacenter A
|||-Workstations
|||-Servers
||-Security Groups
|||-Firewall on
|||-RDP Allow

Do not use domain user, domain admin, group nesting, default OU for user and computer. Use default domain controller OU. Do not edit default domain policies, override specific settings with subsequent policy. You have a fresh domain, cherish this opportunity.

2
harthin•

Start with something like this. Utilize Sites and Services.

Be aware of the limitations depending on your facilities. Take into account things like available WAN speeds and expected service levels. Hospitals need domain controllers because not being able to log into a system because some idiot dug up your fiber won’t go over well. If it is just another office site, they don’t need dedicated Domain Controllers.

Oh, and be prepared to alter your design because of politics. Concessions almost always occur, be prepared to make the ones that make the least permanent impact.

1

One should always use WAN failover in mission critical sites like a hospital.

1
Frank_Signfium•

How many total users are we looking at? I agree with other comments to not install DC at every location.

1
PyroKid883OP•

About 1000-ish.

1

I have managed a company that had locations in Arizona, California, Kansas, New York, London, and China.

Two DCs in Arizona. That's. It. In the same data center.

Let your networking equipment handle everything else. Do not put 17 DCs in 17 locations! Looking back, we COULD have put a DC in China, and another in London, but we didn't go this route. First time logons took only slightly longer in those locations, but nothing too bad to write home about. Speed of the connection is important too.

1
readingyourmail•

There are lots of approaches and lots of best practices.

Its difficult to give a solid answer without understanding your organization, how its laid out, what your IT team looks like, etc.
There are also lots of pieces to this, not just number of DC's and OU structure.

That said, some general best practices that I look at when scoping a new environment:

  • DC at each location (but this can vary depending on actual numbers of users at that location and what apps have AD dependencies)
  • Sites and Subnets defined in AD
  • One Root company OU with Users and Workstations and Servers under that
    ... You could then break out by location under Users and Workstations, but again depending on the org, I may or may not suggest that
    ... Servers would have Datacenter OU's under that
  • For groups, look into the AGDLP best practice concept
    ... the idea is that you have Resource groups tied to things like file shares, servers, etc.
    ... and Role groups contain the actual users in their various roles
    ... then Role groups are nested into Resource groups
0
hagenlund•
  1. For redundancy, you'll need two DCs at each location.
  2. You shouldn't need to split the computer OUs into different locations. Just use a single OU for all computers, a different one for all servers, and so on. For user accounts it's prolly best to split them into location-based OUs.
-1†

So you’re saying this guy needs 34 DCs and no OUs?

That doesn’t sound feasible....

0