How manny cascaded DL-Groups
hi all,
in our structure, we have a distributionlistgroup CONTOSO_PL which contains the DL's GER_PL and FRA_PL and both of them contain location specific DLs like Berlin_PL, Wolfsburg_PL and Hessen_DL. on the location specifics we have the users added.
so, what would you recommend, how many cascaded DL's are the best? is there a best practice? or do you say, try to reflect the whole organizational structure? or just use as litle as possible?
thanks for your feedback,
uerueluem
September 3rd, 2010 6:19pm
The less nesting, more easy to manage..
I don't entertain nested groups in my domain..
Good luck
Shaba
Free Windows Admin Tool Kit Click here and download it now
September 3rd, 2010 8:32pm
I am the complete opposite and would disagree that less nested groups are easier to manage.
I recently designed a structure for a client that was all nested groups. It was a structure for over 100,000 users, and when complete, a user only had to be added to a single group to be a member of all relevant groups for their job and location.
Where exceptions are required, it also allows users to be placed outside of their usual structure at the correct place easily.
It all depends on the planning and the number of users involved. Group structure often isn't planned well, and it can be a pain to undo it. However if the time and effort is spent to configure the groups correctly, it makes life a lot easier, both for
the management and the users.
Simon.Simon Butler, Exchange MVP. http://blog.sembee.co.uk , http://exbpa.com/
September 3rd, 2010 11:49pm