Restricting Room Mailbox Bookings to Specific Groups in Exchange Server 2010

In the comments of the Exchange 2010 Room Mailboxes article a reader asks:

I was wondering, is there anyway to make only a specific group being able to book a specific conference room? We have mailboxes set up and is working perfectly, but we want only one specific section/unit to be able to book that conference room, is that possible?

Yes, this can be configured on room mailboxes quite easily.

In the Properties of the room mailbox go to the Resource In-Policy Requests tab and configure selected recipients who are permitted to book the room.

When a person who is not a in that selected recipients list tries to book the room they will receive a “Declined” message similar to this.

About Paul Cunningham

Paul is a Microsoft Exchange Server MVP and publisher of Exchange Server Pro. He also holds several Microsoft certifications including for Exchange Server 2007, 2010 and 2013. Connect with Paul on Twitter and Google+.

Comments

  1. Hi,
    I tried to add a Dynamic Distribution Group which did not seem to work.

    Any idea on how to add the rights to book in-policy to a group of people?
    By ‘a group of people’ I mean 100-250 accounts, not only 10 ;-)

    Thanks in advance!

    Regards,
    Mark

  2. Thanks for the hint Paul!
    I created an universal security group in AD and created a distribution group in Exchange from this one.
    This finally seemed to work :)

  3. I am trying to get this working but when a person who is not in the selected recipients list books a meeting, they get a “Your request was received and is pending approval” response!
    People who are in the selected recipients list have their meeting request automatically approved.
    I want people not in the list to get a “Declined” message as in your example rather than pending approval. What am I doing wrong? Thanks

    • SimonT,
      I had this same issue, but it was resolved by turning on the Resource Booking Attendant (defaulted to off for me). This assumes you have the other policy settings in place and correct, however, for those outside of your selected recipients list to receive the declined message.

    • I was only able to reproduce the issue by having the room calendar set to AutoUpdate for calendar processing, which is the default setting.

      Once I changed it to AutoAccept (which is the same as Adam suggests above) it processed the invite and declined it for people not in the allowed group.

      • Thanks for the responses.
        It looks like I has a setting wrong………

        On the “Resource In-Policy Request” tab I had the
        “Specify who can submit in-policy meeting requests that are subject to approval by a resource mailbox delegate”
        option set to “All Users”.
        Changing it to “Selected recipients” with no users added led to declined meeting requests as wanted.

        Thanks

  4. Adding user in group, would definetly resolve the purpose but what if user want to propose new timings

    any idea

  5. Using the “In-Policy” request function, I was able to have the room mailbox deny requests from non approved users. My problem is that it puts the cancelled room request on the room calendar. Any ideas?

    • Of course it now that I’ve posted an issue it stopped putting the cancelled room requests on the room calendar.

    • We had this same problem. No matter how we config’d the resources, we absolutely could not get them to reject double-bookings. So, we followed a forum suggestion from another site, and it worked.

      Set-CalendarProcessing -Identity -AllRequestOutOfPolicy:0

      This will also reject bookings that fall outside the maximum number of days. e.g. If you set your resource to only allow meetings to be booked up to 365, this setting will enforce that rule. Better, upon rejection, it gives the end-user a clear reason code.

      • whoops. Misread your question. That solution is to keep a resource from tentatively accepting double-bookings.

        The canceled meeting problem you’re seeing is due to user error. The booking party is not sending the update to the resource. Although this is more common in 2003 and 2008 environments.

Leave a Comment

*

We are an Authorized DigiCert™ SSL Partner.
Loading...

Still running Exchange 2003? Time to get moving and start your upgrade. Find out how - Click Here