Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

At our organization we use a series of shared Outlook calendars to schedule out our conference rooms. All domain users are setup as authors of these calenders. We are now running into a problem where the end user is either not checking/caring if a room already has an appointment assigned to the room for the period of time that they want to use it. So my question is this: Is there any way to prevent a user from scheduling an appointment or meeting on one of these calendars when there is already a preexisting one on it?

We've already tried going into Options -> Resource Scheduling and checking "Automatically decline conflicting meeting requests," but this did not resolve the issue.

share|improve this question
What version of exchange are you running? – Zoredache Jul 8 '09 at 20:26
Server is Exchange 2007--Clients are mostly Outlook 2003 with a couple running 2007. – Psycho Bob Jul 8 '09 at 20:45
up vote 4 down vote accepted

I'd recommend that you set up your conference rooms as resources. You can then use resource booking to prevent this from happening. Have a look at this article from for Exchange 2003.

Here are articles for Exchange 2007 for making Resource Mailboxes.

share|improve this answer

I believe you would have to set these up as shared resources (Resource Mailboxes in 2007) and use the "Invite" feature rather than giving users the ability to directly schedule appointments in the calendar. Then your Resource Scheduling options would apply.

share|improve this answer

If they are already not looking at the meeting responses coming back from the resources (I think that's what you are describing) what do you want to have happen when the response comes back declined? I think this is more of a user education issue than a technical one. That being said, exchange has a whole event sink architecture you can hook into. It involves writing code but you can do pretty much anything you want.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.