B
Bill Bryson
Clarification: Free/busy is denied to any user that has been granted
specific access to a user's calendar when EWS is used to add/change a
permission for a person or group. If the user is a member of a security
group listed with access to the calendars, all users in the group will be
denied access to free/busy to the calendar.
We've discovered that when a user uses EWS (version 13.0.3) to modify
calendar permissions (Exchange 2007) on his/her calendar that this causes an
issue where the free/busy info is no longer available to any user
listed/granted specific access to the user's calendar.
When we go into Outlook 2007 to look at the user's calendar permissions they
are all displayed as "Custom". On examination, the permissions are correct
EXCEPT in the Read section the setting has been set to "None" and grayed
out (hence the Custom level). Normally for the permission levels (Reviewer,
Editor, etc). ) granted the Read setting should be "All Details". The
Default entry is still set correctly to Free/Busy.
It appears that at least in our Exchange environment that the free/busy is
being set to None on ALL permission entries (except Default) on a person's
calendar when EWS is used to change or add permissions to any entry. We've
verified this on several EWS installations.
For example:
User A had previously added User B and C as Reviewers to his calendar using
a pre-EWS client. User A upgraded to EWS and now adds User D as Editor to
his calendar. After the User D is added, each calendar permission entry for
all three users (B,C,D) are changed so the Read Attribute is set to
"None"/grayed out rather than "Free/busy". From this point on when Users B,
C or D attempt to schedule a meeting with User A, none of them will be able
to see any free/busy for him.
When User A accesses his calendar using Outlook 2007, he sees all three
Users (B-D) set as Custom with Read attribute None/grayed out. Only the
Default entry is still set to "Free/Busy time" so EWS fortunately is
creating a situation such that free/busy is denied to all users.
specific access to a user's calendar when EWS is used to add/change a
permission for a person or group. If the user is a member of a security
group listed with access to the calendars, all users in the group will be
denied access to free/busy to the calendar.
We've discovered that when a user uses EWS (version 13.0.3) to modify
calendar permissions (Exchange 2007) on his/her calendar that this causes an
issue where the free/busy info is no longer available to any user
listed/granted specific access to the user's calendar.
When we go into Outlook 2007 to look at the user's calendar permissions they
are all displayed as "Custom". On examination, the permissions are correct
EXCEPT in the Read section the setting has been set to "None" and grayed
out (hence the Custom level). Normally for the permission levels (Reviewer,
Editor, etc). ) granted the Read setting should be "All Details". The
Default entry is still set correctly to Free/Busy.
It appears that at least in our Exchange environment that the free/busy is
being set to None on ALL permission entries (except Default) on a person's
calendar when EWS is used to change or add permissions to any entry. We've
verified this on several EWS installations.
For example:
User A had previously added User B and C as Reviewers to his calendar using
a pre-EWS client. User A upgraded to EWS and now adds User D as Editor to
his calendar. After the User D is added, each calendar permission entry for
all three users (B,C,D) are changed so the Read Attribute is set to
"None"/grayed out rather than "Free/busy". From this point on when Users B,
C or D attempt to schedule a meeting with User A, none of them will be able
to see any free/busy for him.
When User A accesses his calendar using Outlook 2007, he sees all three
Users (B-D) set as Custom with Read attribute None/grayed out. Only the
Default entry is still set to "Free/Busy time" so EWS fortunately is
creating a situation such that free/busy is denied to all users.