Hello, I seem to have an issue with the PFDavAdmin tool for Microsoft Exchange. If I give a user Owner access to 10 other user calendars and open the shared calendar for the user who needs access, they cannot write to the calendar. I have simply though it may have been theone organisation, however it is now a number of our clients who are having the same issue with the calendar permissions when I use the PFDavAdmin tool. I have had to share calendars from all user Outlook profiles one by one and then open them on the one user calendar who needs access -this is a nasty solution because it is time consuming when there are 250+ users in the company. I'm thinking there has been an update which has caused the PFDavAdmin tool to no longer function correctly. If there's any news on this an update would be much appreciated. Thankyou for readingmy post, Regards, Zac

Hi Zac, Whether you have rebooted Users Outlook after delegating the User Owner permission to access 10 other user calendars and adding the shared calendar in Users Profile. Please also let me know whether any error is encountered when editing the shared calendar such as unable to open the free/busy information In addition, please view the Application Log on the Client computer to check whether any error/warning is recorded. Mike

Hi Mike, I have tried restarting the user's Outlook after setting the permissions as well as rebooting the server after-hours to forece replication. Yes, the error Unable to open the free/busy information - never had that before. Unable to view the event log as of now because the business has closed for the day (handling this remotely) Cheers for the reply!

Hi Zac, I suggest that we firstly attempt the following method to troubleshoot the issue: 1. Please disable Cached Exchange mode to troubleshoot the issue 2. Check whether the latest Windows/Outlook updates have been installed on the delegate computer 3. Create a new profile to troubleshoot the issue If the issue persists, Zac, I would like to explain that the delegate will firstly attempt to access the FreeBusy Data folder of the user mailbox who shared his calendar to get the LocalFreeBusy information. Thus, if the delegate does not sufficient permission to access the FreeBusy Data folder, the issue will occur. I suggest that you use the PFDAVAdmin tool to check whether the delegate user has Editor permission to the FreeBusy Data folder of the user mailbox who shared his calendar. Note: The FreeBusy Data folder may not exist as it was created when the first calendar items is received or created. If the issue persists, please post the entire error message and application log error here. Mike

Mike, I'll try this with an account in use when I need to do this again and I'll let you know how it goes. Cheers for the help. Zac

Hi Zac, I have further tested the issue. The following is the conclusion. Hope the information is helpful to you. 1. If we give a user Owner access to other user calendars by using PFDavAdmin, the tool will assign Owner permission to Calendar folder and Editor permission to FreeBusy Data folder (If the folder exists). If the FreeBusy Data folder does not exist, it will not create the folder 2. If we give a user Ower access to other user calendars through Outlook, it will assign Owner permission to Calendar folder and Owner permission to FreeBusy Data folder. If the FreeBusy Data folder does not exist, it will be created automatically. Thus, if we give a user Owner access to other user calendars folder by using PFDavAdmin and the other user mailbox does not have FreeBusy Data folder, the following error will be encountered: Unable to open free/busy information. You do not have permission to create a subfolder in this folder. Mike

Mike, Thanks very much for your reply, I really appreciate it. Iwill give the user(s)Publishing Author permissions through PFDavAdmin instead of Owner to see how it goes. I'll do a bit of research on the free/busy information. Wondering why it isn't created by default? Thanks Mike! Zac

Has a resolution for this bug been found? I've seen many cases of this on other support forums with no solution.