We've set-up several resources for meeting rooms. 'Author' permissions are
set to a mail-enabled security group that contains all users in our site. The
said group also contains several departmental groups both security &
distribution.
We're having a problem wherein a certain user which is a member of one of
the departmental distribution groups cannot book or view the shared calendar
of our resources. However, other users in the same departmental distribution
group are able to book or view the shared calendar of our resources.
Do groups which has other groups as member do not work well when being
granted permission on resources?
Or can the problem be attributed to the departmental group being a
distribution list? In this case, will converting the group to a security
group solve the issue?
Or what could solve this issue?
Appreciate your inputs on this problem.
I don't have any first-hand experience with this scenaro but I would expect converting the nested distribution group to a security group would solve the problem. Exchange does this automatically if you try to set folder permission with a distribution group, but it sounds like it doesn't if the dg is nested.

Signature
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx
> We've set-up several resources for meeting rooms. 'Author' permissions are
> set to a mail-enabled security group that contains all users in our site. The
[quoted text clipped - 16 lines]
>
> Appreciate your inputs on this problem.
NCantin - 30 Aug 2006 18:37 GMT
We have our Resources set so that the Default permission is set to
Author and this works. I did try to give a group permissions to the
Resource and it didn't work.
Nicole
> I don't have any first-hand experience with this scenaro but I would expect converting the nested distribution group to a security group would solve the problem. Exchange does this automatically if you try to set folder permission with a distribution group, but it sounds like it doesn't if the dg is nested.
>
[quoted text clipped - 26 lines]
> >
> > Appreciate your inputs on this problem.
D_Engr - 31 Aug 2006 02:45 GMT
Thanks Sue!
Converting the nested distribution group to a security group solved the
problem.
> I don't have any first-hand experience with this scenaro but I would expect converting the nested distribution group to a security group would solve the problem. Exchange does this automatically if you try to set folder permission with a distribution group, but it sounds like it doesn't if the dg is nested.
>
[quoted text clipped - 18 lines]
> >
> > Appreciate your inputs on this problem.