Quantcast
Channel: Exchange Server 2013 - Outlook, OWA, POP, and IMAP Clients forum
Viewing all articles
Browse latest Browse all 10580

Conference room calendar permissions not functioning for Default account

$
0
0

In general, the permissions settings on room mailboxes do not work in our environment.  Exchange 2013 SP1 (migrated from 2007), Outlook 2013 currently patched up to 4/24/13.

What we want and had worked previously: Default can see FreeBusy time/subj/loc, create new items, edit own items, delete own items, folder visible.  I and another admin are "owners" with all rights.  These permissions were set using Outlook, although I've tried using Set-MailboxFolderPermission as well.

What happens: I and the other admin work fine and can do whatever we want.  When we view the calendar properties in Outlook, the permissions are exactly as described above for "Default".  Users can create a meeting and "invite" the room.  The problem is that many of them need to be able to view the calendar and create meetings in it directly.  When they attempt to do so, the options for creating a meeting/event/appointment are all grayed out.  If they view the permissions on the room in question, they are showing that they have Create/FolderVisible/EditOwn/DeleteOwn, yet they can't create or delete.  

If I run Get-MailboxFolderPermission against the calendar, I get the following:

FolderName     User        AccessRights ----------     ----        ------------

Calendar       Default     {CreateItems, EditOwnedItems, DeleteOwnedItems, FolderVisible} Calendar       MyAccount   {Owner} Calendar       OtherAdmin  {Owner}


IMO, this is exactly what it should be, although I don't see any reference to the FreeBusy rights and I haven't been able to find anything online regarding that.  

So, with the above rights, why can't my users create new meetings in shared conference rooms and what can I do about it?


--smthng


Viewing all articles
Browse latest Browse all 10580

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>