Exchange 2010 - Setting up Users Calendar with Free /Busy Details share permssion, Outlook 2007 client cannot open
Setting up Users Calendar with Free /Busy Details share permssion, Outlook 2007 client cannot open the user shared folder but if we use OWA 2010 or Outlook 2010 client no issue opening the user shared calendar with Free/Busy Details setting.
The follwowig error is reported
You do not have sufficient permission to open the calendar folder. you don't have appropriate permission to perform this operation.
thanks,
Hussain
December 14th, 2010 4:12pm
Hi Hussain,
Which version of your outlook 2007, I would upate it for the latest version, and then make a test again.
Regards!
Gavin
TechNet Subscriber Support
in forum
If you have any feedback on our support, please contact
tngfb@microsoft.com
Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
December 15th, 2010 5:31am
Setting up Users Calendar with Free /Busy Details share permssion, Outlook 2007 client cannot open the user shared folder but if we use OWA 2010 or Outlook 2010 client no issue opening the user shared calendar with Free/Busy Details setting.
The follwowig error is reported
You do not have sufficient permission to open the calendar folder. you don't have appropriate permission to perform this operation.
thanks,
Hussain
I built this little command from the "CalendarProcessing" commandlet... it cleared up my issues ...
Set-CalendarProcessing -Identity joeuser -AddNewRequestsTentatively $false -AddOrganizerToSubject $true -AllBookInPolicy $true -AllowConflicts $true -AllowRecurringMeetings $true -AutomateProcessing AutoUpdate -BookingWindowInDays 0 -ConflictPercentageAllowed
50 -DeleteAttachments $false -DeleteComments $false -DeleteNonCalendarItems $false -DeleteSubject $false -EnableResponseDetails $true -EnforceSchedulingHorizon $true -ForwardRequestsToDelegates $false -MaximumConflictInstances 100 -MaximumDurationInMinutes
0 -OrganizerInfo $true -ProcessExternalMeetingMessages $true -RemoveForwardedMeetingNotifications $true -RemoveOldMeetingMessages $true -RemovePrivateProperty $false -ScheduleOnlyDuringWorkHours $false -TentativePendingApproval $false -WhatIf
Look at those settings in technet article dd335046
good luck
JLH
December 15th, 2010 12:20pm
Outlook 2007 (12.0.6539.500) SP 2 mso (12.0.6545.5004)
Just spent 2 hours with Exchange support team and finally they forwarded the case to the Outlook team. Waiting for them to call back.
thanks
hussain
Free Windows Admin Tool Kit Click here and download it now
December 15th, 2010 2:35pm
Hi JLH,
What exactly the command would do. I run in my test lab and resutl with :setting auto-accept mailbox settings.
Pls adv. thanks hussain
December 15th, 2010 2:53pm
after running th command on one user, still outlook 2007 prompt with " You do not have sufficient permssion......"
thks hussain
Free Windows Admin Tool Kit Click here and download it now
December 15th, 2010 2:55pm
Hi hussain,
If any update for your issue from MS support, please post here.
Thank you very much!
Regards!
Gavin
TechNet Subscriber Support
in forum
If you have any feedback on our support, please contact
tngfb@microsoft.com
Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
December 17th, 2010 1:00am
Finally got the answer from teh Senior Microsoft Tech team that its a bug. response here below:
Action Provided by Senior Engineer
This is 99% likely the bug (OfficeQFE -28579)
Summary:
When you set free/busy perms from an OL2010 CLIENT, we do not propagate the permission to the special “localfreebusy” folder.
This is going to be fixed in the February Cumulative Update.
Free Windows Admin Tool Kit Click here and download it now
December 19th, 2010 11:39am