OUs and Security Groups

Platinum

Platinum

New Member
I'm redesigning the AD for our network. I've already created the OUs and added users to their correct OU, but now I'm creating security groups. Is it OK to create a security group with the same name as an OU?

It's not like it's creating an error. I'm just wondering if it's good practice to not do that? When might problems arise from doing this, if at all?
 
I'm not sure exactly what OU's are for but I do know that security groups are for users's access rights and mail distribution. So it should be pretty separate from the other. If you could give a little background on what OU's are to refresh me I might be able to help. It's been a while since I took my system administration class, and windows server class.
 
OU = Organizational Unit

"An organizational unit (or OU) is nothing more than a container within a
domain. You use it to store similar objects so that they’re in a convenient
location for administration and access."

So yeah, it's just a container, nothing major. I'm just redesigning the Active Directory for my company (it's my first time) and don't want to redesign it, only to find out in 6 months, a year, whatever, that there's problems because I named things the same thing.

I guess the safest bet is just to avoid it all together and give them different names, I'm just curious for my own personal knowledge though.
 
I wouldn't think it would cause a problem, can you give an example of how you'd be using the same name because I wouldn't think you'd really run into that. If the organizational unit is for an entire site you'd name it something like Site A then for your security groups you'd have something like Site A admins, Site A users, Site A bozo employees, Site A Janitors, junk like that. What were you thinking about doing?
 
You must log in or register to reply here.
Back
Top