Update 4/16/2009: We have corrected an incorrect permissions entry in this blog post.
Heard of the term calendar concierge? Look up http://msexchangeteam.com/archive/2006/07/24/428390.aspx. In th...
Updated Jul 01, 2019
Version 2.0
Blog Post
I've notice weird behavior with the Set-MailboxCalendarSettings command. Specifically, I'm setting the AllBookInPolicy to $false for a room resource. After I make this change, the Calendar Permissions for the resource change - the Default changes from 'Free/Busy time' to 'None'. Not sure why changing AllBookInPolicy should be changing the Calendar permissions. When I change AllBookInPolicy back to $true, the Celendar permissions change to 'Free/Busy time, subject, location' and not back to the 'Free/Busy time'.
So, if a resource has been restricted (AllBookInPolicy $false), then the resource is reconfigured (AllBookInPolicy $true), the view permission to the resource are more open than you may want.
Is this by design, or potentially a bug with the Set-MailboxCalendarSettings cmdlet?
So, if a resource has been restricted (AllBookInPolicy $false), then the resource is reconfigured (AllBookInPolicy $true), the view permission to the resource are more open than you may want.
Is this by design, or potentially a bug with the Set-MailboxCalendarSettings cmdlet?