broonster27 Have you tried the post earlier what i mentioned ? if not the please do the following As per your issue, first resource should be not be allowed double bookings correct ? 1. Open that resource mailbox >> go to options >> Go to resource settings 2. Allow conflicts tab ( I know that will be unchecked ) so please check it again and save the settings . 3 Wait for a mins or two then again UNCHECK again to block the double book if the resource mailboxes and then try . And yes Number 4 is basically setting the AutomateProcessing attribute to AutoUpdate..and then revert back to AutoAccept then give a try . Still get the same message and behaviour. This is only happening with one of my test users remember. Other test users are showing the correct behaviour. Hibs Ya Bass!

Hi Have you tried the same with Outlook Web Access ? what are the results ? When I try with OWA using that user then I get the expected behaviour of an email sent from the resource saying the request has been declined.Hibs Ya Bass!

No, there is no direct booking done. I can replicate the issue myself and I am definitely using the 'invite' method. AutomateProcessing is set to AutoAccept so the mailbox is using the Resource Booking Attendant and AllowConflicts is set to False. The seems to be intermittent. Sometimes the double booking will not allowed, sometimes it will. Hibs Ya Bass!

So with OWA things are working fine so why don't you create a new user profile or try to clean the folders with outlook switch Below is list of switches which you can use accordingly. http://office.microsoft.com/en-us/outlook-help/command-line-switches-for-microsoft-office-outlook-2007-HP001218589.aspx I've logged on with this user on 3 separate PCs (XP, Vista and W7) and get the same behaviour. On one of the PCs I created a completely fresh profile.Hibs Ya Bass!

Having done some further testing it seems that if I am using Outlook Web Access or Outlook 2003 I can still send an invite to an attendee even though a resource is already booked. That attendee can then accept the invitation and then both the attendee and the originator of the meeting have the meeting in their Calendars but with no room to go to. I realise the resource mailbox sends an email at this point saying the resource itself can not attend the meeting but the users still have the meeting in their calendars. Is this the expected behaviour with Outlook 2003 and OWA? When creating a meeting request in Outlook 2007 it simply doesn't allow any emails to be sent if the resource is busy, which is the behaviour I would expect from all clients. Hibs Ya Bass!

When I'm logged in as particular user and attempted to double book a particular room resource (resource A let's call it) I get the below message from Outlook (not exchange). This is not the usual message you get when you attmept to double book a resource. If I click OK then click send again it allows the resource to be double booked - I can even see the double booking in the claendar of the resource in OWA. If a try to double book a different room resource (reosource B let's call it) from the same PC logged in as the same user I get the normal error about the resource already being booked and am not allowed to double book it. If I then log onto the same PC as a different user and try to double book the resource A I get the expected messaage from exchange about the resource already being booked. What's happening between this problem user and this problem resource? Hibs Ya Bass!

I'm having problems with users being able to double book resource mailboxes in Exchange 2007 and from looking into the issue further I'm not the only one. I've configured the mailboxes as explained in the many articles I've read but still I can double book. MS obviously haven't rectified this issue in Exchange 2007 but are there any improvements with Exchange 2010 regarding this issue? I was going to set up a test 2010 environment to specifically check out the Scheduling Assistant functionality but I thought I'd save some time before I did and check out here if it was even worth it. Cheers CHibs Ya Bass!

I hope you have tried the post which i mentioned earlier. Below are some more options which you can look for. Option 1;- 1) Disable Cached Mode and restart Outlook 2) Re-enable Cahaced Mode and restart Outlook 3) Try to book resource again. --------------------------------------------- Option - 2 Can you check the properties of the conference rooms through EMS and paste it here with the below cmdlet. Get-MailboxCalendarSettings <resource mailbox name> |fl -------------------------------------------- Option - 3 Go into Outlook 2007 and Check for the permissions to the Calendar folder was set as Default-Free/Busy. change it to the Default to Reviewer. --------------------------------------------- Option-4 1. Login to a computer using the recourse account (if you have it disabled in Active Directory, you will need to enable it). 2. Then open Outlook. 3. Click on Tools, then select Options. 4. Select Calendar Options. 5. Select Resource Scheduling... 6. Make sure that the "Automatically accept meeting requests and process cancellations" is UNCHECKED! 7. Press OK. 8. Close Outlook and Logout.

I hope you have tried the post which i mentioned earlier. Below are some more options which you can look for. Option 1;- 1) Disable Cached Mode and restart Outlook 2) Re-enable Cahaced Mode and restart Outlook 3) Try to book resource again. --------------------------------------------- Option - 2 Can you check the properties of the conference rooms through EMS and paste it here with the below cmdlet. Get-MailboxCalendarSettings <resource mailbox name> |fl -------------------------------------------- Option - 3 Go into Outlook 2007 and Check for the permissions to the Calendar folder was set as Default-Free/Busy. change it to the Default to Reviewer. --------------------------------------------- Option-4 1. Login to a computer using the recourse account (if you have it disabled in Active Directory, you will need to enable it). 2. Then open Outlook. 3. Click on Tools, then select Options. 4. Select Calendar Options. 5. Select Resource Scheduling... 6. Make sure that the "Automatically accept meeting requests and process cancellations" is UNCHECKED! 7. Press OK. 8. Close Outlook and Logout. Below is the output requested. I have carried out the suggestions in 1, 2 and 4 but no change. Number 4 is basically setting the AutomateProcessing attribute to AutoUpdate, correct? How long should I wait before trying to make a new double booking when testing suggestion 4?Hibs Ya Bass!

So with OWA things are working fine so why don't you create a new user profile or try to clean the folders with outlook switch Below is list of switches which you can use accordingly. http://office.microsoft.com/en-us/outlook-help/command-line-switches-for-microsoft-office-outlook-2007-HP001218589.aspx

Hi Have you tried the same with Outlook Web Access ? what are the results ?

broonster27 Have you tried the post earlier what i mentioned ? if not the please do the following As per your issue, first resource should be not be allowed double bookings correct ? 1. Open that resource mailbox >> go to options >> Go to resource settings 2. Allow conflicts tab ( I know that will be unchecked ) so please check it again and save the settings . 3 Wait for a mins or two then again UNCHECK again to block the double book if the resource mailboxes and then try . And yes Number 4 is basically setting the AutomateProcessing attribute to AutoUpdate..and then revert back to AutoAccept then give a try .

Are you sure that users with access aren't creating appointments right in the calendars rather than inviting them in a meeting request? That'll bypass the Scheduling Assistant.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Hi, These behaviors are expected. This is due to different versions. ThanksSophia Xu TechNet Community Support

Hi, As per my knowledge, if you don’t want to double book resource mailbox in Exchange 2007, you need to ensure the AutomateProcessing as AutoAccept and AllowConflict as False. So, you can use get-mailboxcalendarsettings command to check: Get-MailboxCalendarSettings –Identity <roommailbox> | fl If you don’t configure before, you can use the following command to configure: Set-MailboxCalendarSettings –Identity <roommailbox> -AutomateProcessing AutoAccept After configuring all these, when you double book this room in the same time, you will receive the declined message, which will give you the conflict messages. Hope it helps. ThanksSophia Xu TechNet Community Support

Hi, I was having problems with users being able to double book resource mailboxes in Exchange 2007, so you can give a try below 1. Open that resource mailbox >> go to options >> Go to resource settings 2. Allow conflicts tab ( I know that will be unchecked ) so please check it again and save the settings . 3 Wait for a mins or two then again UNCHECK again to block the double book if the resource mailboxes Then give a try that will fix the issue. Same can be done through cmd shell make the settings for the allow conflicts set to true and then False. Hope this helps ..

thanks I try it and its good. Hi, I was having problems with users being able to double book resource mailboxes in Exchange 2007, so you can give a try below 1. Open that resource mailbox >> go to options >> Go to resource settings 2. Allow conflicts tab ( I know that will be unchecked ) so please check it again and save the settings . 3 Wait for a mins or two then again UNCHECK again to block the double book if the resource mailboxes Then give a try that will fix the issue. Same can be done through cmd shell make the settings for the allow conflicts set to true and then False. Hope this helps .. Certified translation Legal translation services Court interpreting Court interpreters Technical translation Interpreting services

No more word on this? I've subsequently found another two user accounts with which the exact same behaviour is occurring.Hibs Ya Bass!

Fixed it myself in the end. I went into the Calendar Permissions of the resource mailbox and for Default I set the permission level to 'Author' which set the 'Delete items' permission to 'Own' - and this specific permission that fixed the issue.Hibs Ya Bass!