Greetings all, I have a room calendar set up with auto-accept, resource delegates and the proper out of policy and in policy restriction to force approval before items are added to a resource calendar. But, I have not be able to prevent the person who initiates the request from being able to delete the appointment on the Room calendar without approval from the delegate. I've looked over and tried almost every variation of the cmdlet settings. The test user does not have any elevated permissions. Exchange 2007 standard btw. Thanks for any thoughts on this.

Isn't this normal/expected behavior?Lanwench [MVP - Exchange] ** Do not fold, spindle or mutilate. Fill in the box completely and erase any stray marks. Use only a #2 pencil.

Thanks for your reply. So a user wanting to add an appointment to a room calendar where a delegate must approve before it is confirmed may delete it without confirmation? I'm guessing this is the designed behavior since I cannot find anything to the contrary. And I assume it functions this way because the person who initiated the appointment is considered the "owner" for lack of better words for it and therefore is allowed to delete it? Regardless, what I wanted was for the delegate to have to confirm deletion or even changes before the appointment could be modified to prevent accidental or malicious removal. My use for the calendar is as a master sppointments calendar for all and wanted to have 2 people to approve additions/deletions/modifications so they could be checked for conflicts prior to booking. Am I missing some other way of accomplishing this task? Thanks again for the reply.

Hi abq_santorini, Per your description, in my opinion, it is the behavior as normal, because the organizer is the owner of the meeting/appointment, the owner cancel the meeting/appointment if he want, the the cancel message would be accept by the resource room despite you set a account as the delegates for it. Regards! Gavin

Gavin, sounds like you I and lanwench are all in agreement. Have you ever come across requirements such as what I listed? Any ideas if there is a workaround this behavior? Thanks again to you both.

Isn't this normal/expected behavior?Lanwench [MVP - Exchange] ** Do not fold, spindle or mutilate. Fill in the box completely and erase any stray marks. Use only a #2 pencil.

I have not, sorry. This is working as designed. I would say this is more of a user training, than a technical, issue.Lanwench [MVP - Exchange] ** Do not fold, spindle or mutilate. Fill in the box completely and erase any stray marks. Use only a #2 pencil.

I have not, sorry. This is working as designed. I would say this is more of a user training, than a technical, issue.Lanwench [MVP - Exchange] ** Do not fold, spindle or mutilate. Fill in the box completely and erase any stray marks. Use only a #2 pencil.