Naming Policy for Security Groups & Distribution Groups

[Qas]

Hi All,

 

I am currently redesigning the AD infrastructure at my school and I am in the process of tidying up the Security & Distributions groups.

 

I just have a few questions:

 

How do you name your security & distribution groups?

How do you organize them? Separate OUs or do you place them all in one?

 

Thanks for your help

[truebluesteve]

Generally all our groups start with HWS (Hazelwick School) which is also how our servers are named. So we have HWS Non Teaching Staff, HWS Students and so on.

 

We keep all the distribution groups in a single OU so that we can sync them with O365

[ADMaster]

I have all the groups in an OU called groups. I give them all a concise meaningful name based on there function / who is in them.

 

staff this is all staff

elementary all staff at the elementary.

students2015 this is all of the current seniors

MS math this is the math team at the middle school.

 

each building and each student year group has their own list. Then most departments and grade levels have their own group.

[Qas]

Thanks for the replies. I am thinking of creating a single OU called Groups which contains 2 Sub OUs, one for Security Groups and one for Distribution Groups. However, some Security groups contain computers and others contain users. How would you organise this? Would you place them all in the same OU or create additional OUs to separate user and computer groups?

 

Thanks again for your help

[Michael]

It really depends, if it's just a single domain/forest, then anything generic. If you have multiple sites/schools all part of a single domain/forest, or even different domains in a single forest, then I'd agree the initials of the school would be the way to go. The same would apply to the naming formats of workstations and other devices.