How to temporarily block room from being reserved in Exchange 2010
We have equipment that is going to be upgraded in several of our conference rooms and want to place a block on the rooms from being booked during this two week period. Is there a way I can black out the rooms for this temporary time.
I would just book the rooms but they already have reservations and my invites would just be declined.
I would just book the rooms but they already have reservations and my invites would just be declined.
ASKER
Is this the same thing as going through the EMC to Resource In-Poilcy Requests and setting the requests to myself? It would be easier to use the EMC than OWA because there are several to do this for.
This info is super helpful, thank you. Do you know if I can "pre-block" out the date? ie: If today is the 3rd of the month and I'd like the room blocked out from the 15-30th of the month, can I block that today to prevent people from booking it ONLY during that time frame (and allow them to still use it for now)?
This info is super helpful, thank you. Do you know if I can "pre-block" out the date? ie: If today is the 3rd of the month and I'd like the room blocked out from the 15-30th of the month, can I block that today to prevent people from booking it ONLY during that time frame (and allow them to still use it for now)?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I am not aware of being able to pre-block a date. If you have many rooms to change, using the Exchange shell is the way to go.
get-mailboxcalendarsetting
Will provide all of the settings for the room/mailbox
Set the AutomateProcessing to None
set-mailboxcalendarsetting
The main parameter that interests us is AutomateProcessing which allows enabling or disabling calendar management on the resource mailbox. The three possible values are:
* None Both resource booking and Calendar Attendant will be disabled on the mailbox. (Meeting requests will not be processed and stacked in the inbox of room mailbox).
* AutoUpdate This is the default value. The Calendar Attendant will process meeting requests which will sit in the calendar of the room in a "tentative state" waiting a delegate approval. (The meeting organizer will receive only the decision of the delegate)
* AutoAccept Resource booking will be enabled on the room mailbox. This means that the room will take into account the policies for the incoming requests (who can schedule.). (With automatic booking configuration, the organizer will receive the decision of the room. Otherwise organizer will first receive a message of recognition pending delegate approval).
get-mailboxcalendarsetting
Will provide all of the settings for the room/mailbox
Set the AutomateProcessing to None
set-mailboxcalendarsetting
The main parameter that interests us is AutomateProcessing which allows enabling or disabling calendar management on the resource mailbox. The three possible values are:
* None Both resource booking and Calendar Attendant will be disabled on the mailbox. (Meeting requests will not be processed and stacked in the inbox of room mailbox).
* AutoUpdate This is the default value. The Calendar Attendant will process meeting requests which will sit in the calendar of the room in a "tentative state" waiting a delegate approval. (The meeting organizer will receive only the decision of the delegate)
* AutoAccept Resource booking will be enabled on the room mailbox. This means that the room will take into account the policies for the incoming requests (who can schedule.). (With automatic booking configuration, the organizer will receive the decision of the room. Otherwise organizer will first receive a message of recognition pending delegate approval).
If you use OWA, click on Options, go to Resource Settings, then in the specify users section, change it to be yourself.
Or you can use EMS - Set-MailboxCalendarSetting
http://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/managing-resource-mailboxes-exchange-server-2007-part3.html