To set permission’s on a room mailbox in Exchange 2010, you have to execute the PowerShell command Add-MaiboxFolderPermission.
Add-MailboxFolderPermission -identity <roomname>@<domain.com> -user <email address of user who needs access> -AccessRights <AccessRight>
The parameter AccessRight specifies the permissions for the user, you can use the following values:
- ReadItems The user has the right to read items within the specified folder.
- CreateItems The user has the right to create items within the specified folder.
- EditOwnedItems The user has the right to edit the items that the user owns in the specified folder.
- DeleteOwnedItems The user has the right to delete items that the user owns in the specified folder.
- EditAllItems The user has the right to edit all items in the specified folder.
- DeleteAllItems The user has the right to delete all items in the specified folder.
- CreateSubfolders The user has the right to create subfolders in the specified folder.
- FolderOwner The user is the owner of the specified folder. The user has the right to view and move the folder and create subfolders. The user can’t read items, edit items, delete items, or create items.
- FolderContact The user is the contact for the specified public folder.
- FolderVisible The user can view the specified folder, but can’t read or edit items within the specified public folder.
AccessRight also accepts a Roles definition as a value:
- None FolderVisible
- Owner CreateItems, ReadItems, CreateSubfolders, FolderOwner, FolderContact, FolderVisible, EditOwnedItems, EditAllItems, DeleteOwnedItems, DeleteAllItems
- PublishingEditor CreateItems, ReadItems, CreateSubfolders, FolderVisible, EditOwnedItems, EditAllItems, DeleteOwnedItems, DeleteAllItems
- Editor CreateItems, ReadItems, FolderVisible, EditOwnedItems, EditAllItems, DeleteOwnedItems, DeleteAllItems
- PublishingAuthor CreateItems, ReadItems, CreateSubfolders, FolderVisible, EditOwnedItems, DeleteOwnedItems
- Author CreateItems, ReadItems, FolderVisible, EditOwnedItems, DeleteOwnedItems
- NonEditingAuthor CreateItems, ReadItems, FolderVisible
- Reviewer ReadItems, FolderVisible
- Contributor CreateItems, FolderVisible
So.. for example if I wanna give all users the rights to review the calendar of the Meetingroom and a user named John Doe will receive the contributer permission, I use the following commands:
- Add-MailboxFolderPermission -identity meetingroom@domain.com -user john.doe@domain.com -AccessRights contributer
- Add-MailboxFolderPermission -identity meetingroom@domain.com -user Default -AccessRights reviewer
Hi Mark
We have a number of rooms in Exchange 2010 and our users can create meetings using Outlook 2010 and add a room as a resource. The user then gets a confirmation that they have booked the room.
But
User keep viewing the rooms and making the bookings in the rooms calendar rather than their own calendar. The result is that the user doesn’t get a confiration that they have booked the room, they don’t have a meeting appointment in their own calendar and when you look at the room booking you cannot tell who made the booking.
Are there any access rights parameters that will allow users to view the room bookings, users to make bookings from their own calendar but will prevent them from making bookings directly into the rooms calendar.
Many thanks
Richard
I had to set permissions on the folder as follows to allow users to view all items but only edit their own reservations.
Add-MailboxFolderPermission -Identity conferenceroom@domain.com:\calendar -user user@domain.com -AccessRights Author
I set the user to a distribution group with all users in the group (e.g. everyone@domain.com)
Richard Finlay – were you ever able to limit users to only booking rooms by scheduling and not through the resource calendar itself?
Most of my rooms can be booked by any user. But I do have a requirement to limit the right to view/book a room to one group of users. How can I do this in powershell?
Found that the users had Full Access permissions to the rooms. Once this was removed in exchange they were only able to use scheduling and not the resource calendar