This question is in reference to differences we are seeing with -type "shared" calendars in Exchange (SP1) / Outlook 2007. These are not resource calendars (room/equipment). Note, we are not using room/equipment resource calendar types because we have to allow double booking, including double booking recurring meeting requests. There appears to be a problem with room/equipment type calendars not allowing double booking recurring meeting requests for those times that double book over an existing entry. If this problem did not exist, we would most likely go to one of these resource types instead see http://social.technet.microsoft.com/Forums/en-US/exchangesvrgeneral/thread/36b865a0-7c8e-4d5a-bd88-4c0f35059bef for more info. We have several calendars that were set up new as the "shared" type calendar. The objective is to allow any user to automatically book their time (PTO, Out of office, Etc) on the respective calendar for their department. The calendars are set up with author permissions to the groups to allow this. We then opened the mailbox for the calendar in Outlook and (under Tools, Options, Calendar Options, Resource Scheduling) checked the box to "Automatically accept meeting requests and process cancellations", and un-checked both "Automatically decline conflicting & recurring meeting requests" checkboxes. The outcome of these settings are as follows for all the shared department calendars except the one in question: with no delegate specified on the mailbox for the calendar, if a user requests the calendar using the "Resource" field of their meeting request, it automatically books the calendar immediately and gives a popup notification that the resource was booked successfully. If the user requests the calendar using the "Required" or "Optional" fields, the request generates a meeting invite (email) which goes to the calendar's mailbox and sits un-answered in the Inbox. With a delegate specified in the calendar's mailbox, the only difference is that with the "Required" or "Optional" fields, the email invite is instead forwarded to the Delegate who answers the invite. This behavior is expected as we understand the design of the "Shared" mailbox type. However, we have another calendar which has been around for many years through several exchange versions. This calendar has been set up with the same calendar settings as the others, however, it auto answers the email requests when users request the resource using the "Required" or "Optional" fields. With a delegate specified, the invite is automatically answered immediately by the delegate (on behalf of the calendar) without them doing anything. The user received an email back as such, and the answered invite can be found in the delegate's sent items. With no delegate specified the request is still automatically answered with an email back with "Your request was accepted" (sent by Microsoft Exchange Server 2007). We used to have certain mailboxes configured to use an Auto Accept Agent (not sure if this one ever was), however I am told these have been disabled/discontinued and I do not see it set to do so. Obviously it appears Exchange 2007 is auto-answering these like a resource calendar (room/equipment), but I cannot see the difference in ones that do not auto accept "required/optional" versus this one that does. My understanding is the expected results would be that a delegate would be required in this case, however I am very interested in what setting may be allowing this one calendar to auto answer these requests differently. If possible, I would like to set the other calendars the same. Below are the settings as retrieved from the Get-Mailboxcalendarsettings command for the calendar in question. Again, these match exactly with the other calendars. I have tried switching this calendar to and from a resource (room type) and back, as well as changing the "AutomateProcessing" setting to Auto Update and back to Auto Accept again. However, my understanding is that most of these settings should only take effect on 2007 resource calendars (room/equipment), and not Shared anyway, as they cannot be set unless the calendar is set to a room or equipement resource. What else should I check to find the differences in the calendars? AutomateProcessing : AutoAccept AllowConflicts : True BookingWindowInDays : 730 MaximumDurationInMinutes : 0 AllowRecurringMeetings : True EnforceSchedulingHorizon : True ScheduleOnlyDuringWorkHours : False ConflictPercentageAllowed : 100 MaximumConflictInstances : 100 ForwardRequestsToDelegates : True DeleteAttachments : False DeleteComments : False RemovePrivateProperty : True DeleteSubject : False DisableReminders : True AddOrganizerToSubject : False DeleteNonCalendarItems : False TentativePendingApproval : True EnableResponseDetails : True OrganizerInfo : True ResourceDelegates : {Delegate Name Is Here} RequestOutOfPolicy : AllRequestOutOfPolicy : False BookInPolicy : AllBookInPolicy : True RequestInPolicy : AllRequestInPolicy : False AddAdditionalResponse : False AdditionalResponse : RemoveOldMeetingMessages : True AddNewRequestsTentatively : True ProcessExternalMeetingMessages : False DefaultReminderTime : 15 RemoveForwardedMeetingNotifications : False Identity : Domain name/path of calendar

ok lets begin, what is "disableReminders" set to?

Hello, The disablereminders setting is set to True, which is also the same as the other calendars similar to this one. The settings for the calendars are in my original post. All these settings match between the calendars. Thanks