<div>
My guess is that your calendar processing is set to allow conflicts. &nbsp;If you run this command, is the value for AllowConflicts set to &quot;True&quot;?<br />
<br />

<pre><code id="code-20-41882361-1">Get-Mailbox | Where { $_.RecipientTypeDetails -eq &quot;RoomMailbox&quot; } | Get-CalendarProcessing | ft -auto Identity,AllowConflicts</code></pre>
<br />
If they are, run this command (for each room mailbox) that you want to prevent overbooking...<br />
<br />

<pre><code id="code-20-41882361-2">Set-CalendarProcessing -Identity &quot;ROOMMAILBOXNAME&quot; -AllowConflicts $false</code></pre>
</div>


My guess is that your calendar processing is set to allow conflicts.  If you run this command, is the value for AllowConflicts set to "True"?



Get-Mailbox | Where { $_.RecipientTypeDetails -eq "RoomMailbox" } | Get-CalendarProcessing | ft -auto Identity,AllowConflicts


If they are, run this command (for each room mailbox) that you want to prevent overbooking...



Set-CalendarProcessing -Identity "ROOMMAILBOXNAME" -AllowConflicts $false

<div>
It appears this was a silly issues. The user was booking appointments in the past. Somehow Exchange accepted these.
</div>


It appears this was a silly issues. The user was booking appointments in the past. Somehow Exchange accepted these.

<div>
<div class="content wysiwyg-content">
We have a few rooms configured in resources in Exchange 2013 that are not declining when overlapping a schedule.<br />
<br />
Anyone?
</div>
</div>


We have a few rooms configured in resources in Exchange 2013 that are not declining when overlapping a schedule.

Anyone?

Exchange 2013 resources bookings

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.