I always go for the old style method - one group per function (and a good description!). When someone has to follow your work, it's a lot easier following this method than groups that are "nested" into loads of different functions. There's a little more overhead in setup, but it more than makes up for it for ease of use. I have groups for drive mappings, printer mappings, websense access, file share access, distribution group membership, application deployment, etc. etc. YMMV
2009/12/16 David Lum <[email protected]> > Creating AD security groups…do you guys generally have a group for each > department, a group for each file share, and various distribution groups? > > > > It seems it would make sense to have a group for say, the Marketing > department and this group is a member of various file share and distribution > lists. That way as long as Bob is a member of Marketing department he will > then have all the file access and get the proper e-mails. Since we > SharePoint I also figure I can use AD groups instead of SharePoint group > sand basically treat SharePoint the same as file shares when it comes to > group creation. > > > > Am I overlooking anything? > > *David Lum** **// *SYSTEMS ENGINEER > NORTHWEST EVALUATION ASSOCIATION > (Desk) 971.222.1025 *// *(Cell) 503.267.9764 > > > > > > > > -- "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into the machine wrong figures, will the right answers come out?' I am not able rightly to apprehend the kind of confusion of ideas that could provoke such a question." ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
