I've been testing this on a few exchange deployments and I found an issue with the exchange module. And I know this used to work correctly. I'm not sure when or what changed but here goes.
Previously, I am certain it worked this way, the domain security group was added to all mailbox calendars as a reviewer. This maintained the effect that anyone that was part of the organization could view the mailboxes free/busy information. I had someone report that free busy information was not available. Upon investigation, when creating a new mailbox I would get the resulting information from the calendar permissions:
[PS] C:scripts>Get-MailboxFolderPermission jmcnab@nowayitsbroke.com:Calendar
FolderName User AccessRights
---------- ---- ------------
Calendar Default {None}
Calendar Anonymous {None}
This definitely coincides with the free busy information not being available.
Checking an older domain I get the following results:
[PS] C:scripts>Get-MailboxFolderPermission jmcnab@anolddomain.com:Calendar
FolderName User AccessRights
---------- ---- ------------
Calendar Default {None}
Calendar Anonymous {None}
Calendar anolddomain.com {Reviewer}
The free/busy information is working correctly.
I'm currently on the 1.2.1 version of SolidCP. Is this the intended behavior and if so, why? If its not is it fixed in the next release?
Hello,
It has been changed in version 1.4.0.
The reason why is pretty simple: the default before allowed people to view the calendar for everyone in the organization, this is ofcourse not wanted behaviour for quite a few companies (normal employees shouldn't see HR's calendar or bosses calendar you name it).
Therefor the default has changed to none, if you do want to have everyone able to view everyones calendar you simply need to add the permission to the mailbox you want (in the end it's possible to add calendar permissions, but it was not possible to remove default calendar permissions).
Regards,
Marco
There is no way to add the organization security group as a calendar user (i.e. everyone) through the portal. The end users can however remove any and all permissions to their calendar through the outlook client, including the Default and Anonymous users. While I agree that having "Reviewer" permissions may be too much for some organizations, making all free/busy unavailable as a default i feel is a also too much in the other direction, especially with no way to add it easily back without going to each mailbox and adding each person individually, Or accessing the back end.
Adding the organization at mailbox creation with "AvailabilityOnly", would for the organization security group, mimic the default exchange mailbox creation.
I'm unclear on how it functions in 1.4.0? No availability? Or was this reverted?
It is scheduled to fix up so you can add the default group to calendar (and other) permissions for mailboxes (it was actually planned to be released with 1.4.0 however due to bugs it got reverted).
In this case there's really a choise of can not please everyone at the same time (as their complete opposite goals).
To which i prefer to have too less information where you can add additional rights then the other way around.. too much information with no way to stop it.
(in the end many companies don't want employees to see if their bosses are busy, it's litterally none of their business ;))
I get that you can't please everyone all the time and all that. But this is also default out of the box behavior. Not reviewer mind you, which grants more access then just AvailablityOnly.
Now comes the arguement about if you have an organization of 100 people. And want to see free/busy information. You need to add it to 99 people vs removing it from the 1?
I get that I can add these permissions on the back end. But isn't the design of this to allow end users access to manage these?
