what is the best practice for creating and managing groups, specifically for Exchange distribution groups? should you just create email groups as distribution groups, or is it better to create them as security groups? just looking to see what other peoples thoughts/pros/cons are to this?

Hi, It all depends on what is the purpose, if its for mail purpose then mail enabled distribution list & if it security related then security group.Ripu Daman Mina | MCSE 2003 & MCSA Messaging

Sorry for the vague description on my part. What i have in my office is several groups that are security groups but are mail enabled as well for emailing purposes. what i am trying to understand is if its better to separate the functions into two groups (a distribution group for email, and a separate security group) is there any performance impact by putting them as one group like i have now, and or anything else that should be known about separating them or putting those functions together as one group?

On Wed, 6 Oct 2010 18:51:36 +0000, xchangepatewon wrote: > > >Sorry for the vague description on my part. > > What i have in my office is several groups that are security groups but are mail enabled as well for emailing purposes. what i am trying to understand is if its better to separate the functions into two groups (a distribution group for email, and a separate security group) is there any performance impact by putting them as one group like i have now, and or anything else that should be known about separating them or putting those functions together as one group? Depending on the number of security groups in which a user is a member, the security token can become quite large. If it becomes so large it won't fit in a single UDP packet you may have problems with Kereros authentication and you may begin to run out of paged memory pool on 32-bit machines with lots of logons. It's usually a good idea to keep the functions of groups independant. Just becasue someone want to receive e-mail sent to a group doesn't always mean they should have access to resources that other members of the group have. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP