Hi, We have a Exchange Server 2007 with a room mailbox configured with autoaccept only for some users (AllBookInPolicy=false; BookInPolicy=AllowUsersGroup). If a user sends a meeting request to this room, it accepts or declines the request fine, but a few minutes later it sends the acceptation or declination message again, although the composition of the message is not exactly the same that the previous one: the first (automatic) one is 'signed' by the Exchange Server, but the second one not. It's quite weird... Does anyone know why this could be happening? Thank you all.

can you paste both the meeting acceptance emails with Internet headers, this help to analyse

Hi, Could you please run this command “Get-MailboxCalendarSettings –Identity “Room” | FL And post the result here. Where is the second reply email send from? Could you please check below options? Resource scheduling in Exchange Server 2007

Hi, Could we repro this issue on a newly created room mailbox? In some cases, if the room mailbox was migrated from the legacy Exchange server and the direct booking was enabled on it, we would receive duplicate notification emails from the room mailbox. To check if the direct booking was disabled on the room mailbox, we could following the steps below: 1.Logon the Outlook Logon the Outlook with the room mailbox (it would be necessary to perform this operation on the room mailbox's own Outlook profile), perform the following steps: 2.From the Tools menu, click Options. 3.In Options, click Calendar Options. 4.In Calendar Options, click Resource Scheduling. 5.In Resource Scheduling, clear the Automatically accept meeting requests and process cancellations check box. 6.Click Set Permissions, click the Permissions tab, and then change the Default permission from Author to Free/Busy Time. 7.Save the changes and restart the “Microsoft Exchange Mailbox Assistants” on the mailbox server. 8.Go and see if we could reproduce this issue then.

Thank to everybody for responding. Unfortunately there was a person accepting or declining the requests and I didn't know it (althought he didn't have to do this work, now he's fired lol). So the mystery about the two replies was solved, but now I'm getting another weird problem. I have test that some users belonging to the 'AllowUsersGroup' set in the room configuration are getting declinations that says the user have no permission no book this room (when it's false). But it only happens sometimes, not always. I was trying to find out when or why the server is declining the requests, but I couldn't find any clue. And is very weird because if I send an out of policy request (from those users accounts) I usually get the decline message with the corresponding text about the reason it's declining my request. Here I post the current configuration of one of the rooms: AddAdditionalResponse False AdditionalResponse AddNewRequestsTentatively True AddOrganizerToSubject True AllBookInPolicy False AllowConflicts False AllowRecurringMeetings False AllRequestInPolicy False AllRequestOutOfPolicy False AutomateProcessing AutoAccept BookingWindowInDays 120 BookInPolicy AllowUsersGroup ConflictPercentageAllowed 0 DefaultReminderTime 15 DeleteAttachments True DeleteComments True DeleteNonCalendarItems True DeleteSubject False DisableReminders True EnableResponseDetails True EnforceSchedulingHorizon True ForwardRequestsToDelegates False MaximumConflictInstances 0 MaximumDurationInMinutes 1440 OrganizerInfo True ProcessExternalMeetingMessages False RemoveForwardedMeetingNotifications True RemoveOldMeetingMessages True RemovePrivateProperty True RequestInPolicy RequestOutOfPolicy ResourceDelegates ScheduleOnlyDuringWorkHours False TentativePendingApproval False Could anyone help me?

I've still got no solution to this problem, but we're thinking whether this could be a problem about distributed servers or load balancing, because it works fine sometimes and sometimes not for the same user (who is certainly in the AllowUserGroup). I'm really confused...

Any idea?

I've been investigating and I've found out that the AllowUsersGroup, which defines who can or not book the rooms, just contains another security group which is who really has the users. Besides, both groups are configured as Global instead Universal, which could be a problem if we're using more than one domain (which is the case). Could anyone confirm that my random problems is due to this group configuration? Thanks.