Performance: Exchange calendar delegation
Last Updated:
2010-06-21 04:00:00
Event:
2010-06-08 04:00:00
Status:
Closed
Brief Description:
Exchange
User Impact:
N/A
Workaround:
There is no workaround for this issue
Current Status:
N/A
Services Affected:
Full Description:
CIT has received numerous reports that individuals are unable to set up calendar delegation in Exchange. CIT is developing a fix for the problem.
CIT TDX ID:
Timeline of Changes
| Description | Current Status | Date | Time |
|---|---|---|---|
| The delegation issues have been resolved. \n\nFor delegation involving Exchange Group Accounts or calendar resources: When setting permissions, please do not modify or delete entries that start with "ga.ACCESS" or "ga.ADMIN". Deleting those entries will cause errors. | The delegation issues have been resolved. \n\nFor delegation involving Exchange Group Accounts or calendar resources: When setting permissions, please do not modify or delete entries that start with "ga.ACCESS" or "ga.ADMIN". Deleting those entries will cause errors. | 2010-06-21 | 04:00:00 |
| CIT is still researching the issue. In the meantime, we're testing with some users a manual fix that should address the issue on the server side. | CIT is still researching the issue. In the meantime, we're testing with some users a manual fix that should address the issue on the server side. | 2010-06-11 | 04:00:00 |
| CIT is investigating. | CIT is investigating. | 2010-06-08 | 04:00:00 |
| CIT has identified the issue as occurring with units that have their own Active Directory domains. The error happens when the client tries to update the catalog in their domain rather than in Cornell AD. We are developing a client-side fix that should be available soon. We have tested the fix with several reported cases and seen good results. | CIT has identified the issue as occurring with units that have their own Active Directory domains. The error happens when the client tries to update the catalog in their domain rather than in Cornell AD. We are developing a client-side fix that should be available soon. We have tested the fix with several reported cases and seen good results. | 2010-06-08 | 04:00:00 |