Hi everyone, In our old environment we had Outlook 2003 clients and Exchange 2003. For shared calendars used as booking systems for meeting rooms and equipment, we had "Do not allow duplicate / conflicting appointments" turned on for these mailboxes. This was done through Outlook when logged as on as the Resource Account (eg MeetingRoomA1) We have moved over to Exchange 2007 and installed SP1 and the rollup pack for SP1. We still have Outlook 2003 as our client. Outlook 2003 clients can now (despite the settings being otherwise) create duplicate meeting room requests. We have configured these as actual Room Mailboxes through the Exchange 2007 console and ensured they are not "legacy mailboxes." We have the autodiscover virtual directory configured on our Client Access Mail servers. We don't however have the autodiscover hostname configured in our internal or external namespace. For internal we understand it uses Service Connection Points in Active Directory so is not needed at this time. I think Autodiscover may be related but this should only effect Office 2007 users right? The user rights to the Calendar on the mailbox are "Author" meaning they can create their own appointments and delete their own, but no one elses. We have also encountered errors supposed to be fixed by the Rollup Pack 1 for Service Pack 1 which I am at a loss with. These are: Event Type: Error Event Source: EXCDO Event Category: General Event ID: 8206 Description: Calendaring agent failed with error code 0x80040215 while saving appointment. 941655 (http://support.microsoft.com/kb/941655/) The Store.exe process stops responding, and event ID 9659 is logged on an Exchange Server 2007 server 942374 (http://support.microsoft.com/kb/942374/) Legacy free/busy information no longer appears for appointments that are booked against a mailbox in Exchange Server 2007 (not sure if this is what we are experiencing) 943163 (http://support.microsoft.com/kb/943163/) The Test-OwaConnectivity cmdlet and the Test-ActiveSyncConnectivity cmdlet do not run successfully on a computer that is running Exchange Server 2007 943371 (http://support.microsoft.com/kb/943371/) Event IDs 8206, 8213, and 8199 are logged in an Exchange Server 2007 environment (see above error from Event Log) 945938 (http://support.microsoft.com/kb/945938/) The Information Store service intermittently stops responding after you apply Microsoft Exchange Server 2007 Service Pack 1 on an Exchange Server 2007-based server Any advice would be greatly appreciated as this is a very tricky one. I'm an Exchange 2003 admin and this is quite new to me so flying by the seat of my pants. Cheers, Ian

Hi, Have you tried the command "Get-MailboxCalendarSettings meetingrooma | fl" to see what this command tells you about the duplicate meetings? (if it is configured to true or false) Leif

Hi Leif, here is the output given by the command you sent me. It says Allow Conflicts = False which is what I thought. I'm not sure if there's something else in this list that could cause a problem. Can you see any problems? Get-MailboxCalendarSettings meetingrooma | fl AutomateProcessing : AutoAcceptAllowConflicts : FalseBookingWindowInDays : 180MaximumDurationInMinutes : 1440AllowRecurringMeetings : TrueEnforceSchedulingHorizon : TrueScheduleOnlyDuringWorkHours : FalseConflictPercentageAllowed : 0MaximumConflictInstances : 0ForwardRequestsToDelegates : TrueDeleteAttachments : TrueDeleteComments : TrueRemovePrivateProperty : TrueDeleteSubject : TrueDisableReminders : TrueAddOrganizerToSubject : TrueDeleteNonCalendarItems : TrueTentativePendingApproval : TrueEnableResponseDetails : TrueOrganizerInfo : TrueResourceDelegates : {}RequestOutOfPolicy :AllRequestOutOfPolicy : FalseBookInPolicy :AllBookInPolicy : TrueRequestInPolicy :AllRequestInPolicy : FalseAddAdditionalResponse : FalseAdditionalResponse :RemoveOldMeetingMessages : TrueAddNewRequestsTentatively : TrueProcessExternalMeetingMessages : FalseDefaultReminderTime : 15RemoveForwardedMeetingNotifications : False Thanks in advance, Ian

Hi Ian, From Your MailboxCalendarSettings for the resource mailbox meetingrooma, I think that the configuration is correct: AutomateProcessing : AutoAccept AllowConflicts : False ConflictPercentageAllowed : 0 MaximumConflictInstances : 0 At this time, please let me know whether the meetingrooma was a Resource Mailbox which upgraded from the original Exchange 2003. If I am right, I suggest that you create a new Room Mailbox to test the conflict meeting issue again by using the new Room Mailbox. Mike