We are having a debate about the naming convention of groups in Active Directory. Some want to follow the Microsoft advice to prefix security groups with sg- and distribution lists with dl- etc. Others would prefer to appply a suffix. And there are those who would prefer neither.  i.e.:

 

  • Prefix groups with sg- (sg-group1)
  • Suffix groups with -sg (group1-sg)
  • no prefix or suffix        (group1)

Those for a prefix argue that it will make searches and ordering of results easier for certain objects. Also Microsoft recommend it so there has to be value in it. Some would compromise and add a suffix. Objects types will still be identifiable but searches  such as *-sg in ADUC won't work. Finally those against both of the above argue that both the icon and the Type column should be enough. Our developers argue that they should be able to query Active Directory for groups which are intuitivly named. As a Sys Admin I agree with this but have reservations about people deciding to use groups without first discussing with the Sys Admins if that group is appropriate to use or not. Like most systems we are reviewing the number of and names of groups because overtime groups develop with similar names.

 

What naming conventions are used elsewhere and just as important what were your reasons for adopting it?

 

 

Views: 2213

Reply to This

Replies to This Discussion

we use TYPE_ROLE_AREA_NAME for ours. For example: DIS_SWDEP_COMPANY_AutoCAD2010_fixed would be a distribution group used for software deployment across the whole company for AutoCAD2010 fixed licence. That's about as big as we get with the names and it's only the software deployment ones that get really long names.

RSS

Sharing problems, tips, and experiences in Systems Administration, especially the human side.

Latest Activity

Wesley "Nonapeptide" commented on Dan Taylor's blog post Learning Rails
"I have no experience with web development or other frameworks aside from passing familiarity with some general concepts. However, since my interest in Ruby, and indeed any language, is to mostly create web applications (and also be able to…"
yesterday
Dan Taylor commented on Dan Taylor's blog post Learning Rails
"Yeah, if you've got the experience in other frameworks or the drive to make web apps it sure makes sense to do so. You only need a subset of Ruby to get started with Rails."
yesterday
Wesley "Nonapeptide" commented on Dan Taylor's blog post Learning Rails
"Ohh, so you say someone should just jump into RoR without worrying about Ruby in specific? Interesting..."
yesterday
Dan Taylor commented on Dan Taylor's blog post Learning Rails
"As a web developer I took the advice to heart that I should learn RoR first (As I make web apps) and Ruby as a language second. I plan to pick up a book on Ruby itself on pay day. I completely understand where you're coming from with the whole…"
yesterday

© 2013   Created by Dan Taylor.   Powered by

Badges  |  Report an Issue  |  Terms of Service