Hello, I am having problems with the Set-MailboxCalendarSettings not working like I think it should... I want the resource to not allow conflicts in scheduling.. if Bob schedules from 3-5, Bonnie shouldnt be able to schedule anything for that resource during that time, here is what I used... Set-MailBoxCalendarSettings -identity <resource name retrieved from get-mailboxcalendarsettings> -allowconflicts $false ... I thought that would do it, but I was still able to schedule, so I tried this... Set-MailBoxCalendarSettings -identity <resource name retrieved from get-mailboxcalendarsettings> -allowconflicts $false -MaximumConflictInstances 0 ... Same outcome, now running both of these returned NO ERRORS, so I am curious if I am missing anything or what.. I have update rollup 5 installed, I did just get a copy of SP1 and will be able to try that soon as well, however this should work shouldnt it!?!? Sad, Confused, Beaten.. Cory

As long as you created it (and it shows in EMC) as a resource mailbox it should not allow conflicts by default as well. You can also view/config this setting by enabling the resource user account in ADUC and logging into OWA as that resource mailbox. Its options, then resource options.

Thanks for the reply Knightly, much appreciated. I wasnt aware of the ability to edit some of these options through OWA so I did as you suggested (a handy tip/workaround).. I found the allow conflicts radio button to already be unchecked, I saved and logged out.. I logged into OWA again, I created an Appointment, logged out, logged in as another user and tried to create an overlapping appt. and it worked just fine, which was a bummer. I then went in to the resource again in OWA and unchecked the "all recurring meetings" saved and tried again, same thing happened. I am doing all the resource testing in OWA as I have a limited trial version of Outlook 07. This is very frustrating as the verbage makes me assume this is the correct way to go about it.. Further suggestions are extremely welcome. Thanks.

It sounds like you are doing right if you are able to confirm via OWA. I doubt this is a bug b/c it works fine for me. Have you got anything in the event viewer's app log of interest? Also, does this occur on all resource mailboxes? If you create a new one and take all the defaults does this happen?

Thanks foranother response Knightly , I have reviewed all appropriate logs and have been hard pressed to find anything out of the ordinary. I thought maybe it was a fluke, I have created a few more resource boxes and tested using OWA again and it seems that nothing happens when I schedule appts using resources that have already been booked by a different user. Maybe I am expecting something that I shouldnt. What should happen when you for example I have set the allowconflicts to false (via ems and also confirmed via OWA resource login)? Should some response come up saying its already been booked? I am truly frustrated.