Hello. I have set up autoattendant previously for our corp environment and it worked flawlessly. It wasn't until a few weeks ago that it broke (while out on PTO nevertheless). As far as everyone knows, there have been no updates nor changes in our lean IT team. So I am now puzzled as to why it has not worked for the past two weeks. Here are the configuration settings pulled from the Exchange Managment Shell: AutomateProcessing : AutoAccept AllowConflicts : False BookingWindowInDays : 180 MaximumDurationInMinutes : 1440 AllowRecurringMeetings : True EnforceSchedulingHorizon : True ScheduleOnlyDuringWorkHours : False ConflictPercentageAllowed : 1 MaximumConflictInstances : 0 ForwardRequestsToDelegates : False DeleteAttachments : True DeleteComments : True RemovePrivateProperty : False DeleteSubject : True AddOrganizerToSubject : True DeleteNonCalendarItems : True TentativePendingApproval : True EnableResponseDetails : True OrganizerInfo : True ResourceDelegates : {Some Delegate} RequestOutOfPolicy : {} AllRequestOutOfPolicy : False BookInPolicy : {} AllBookInPolicy : True RequestInPolicy : {} AllRequestInPolicy : True AddAdditionalResponse : False AdditionalResponse : RemoveOldMeetingMessages : True AddNewRequestsTentatively : True ProcessExternalMeetingMessages : False RemoveForwardedMeetingNotifications : False MailboxOwnerId : AD ID Identity : AD ID IsValid : True Any help is appreciated.

Hi, The configuration is incorrect. I noticed that you set some delegates and enable “AllRequestUnPolicy”, however, “ForwardRequestsToDelegates” is set to False, and the “ConflictPercentageAllowed” is 1. These settings may conflict. If you want the resource mailbox to auto accept the meeting requests when it is available, and forward meeting requests to delegate when it is conflict, use the settings below: AutomateProcessing : AutoAccept AllowConflicts : False BookingWindowInDays : 180 MaximumDurationInMinutes : 1440 AllowRecurringMeetings : True EnforceSchedulingHorizon : True ScheduleOnlyDuringWorkHours : False ConflictPercentageAllowed : 0 MaximumConflictInstances : 0 ForwardRequestsToDelegates : true DeleteAttachments : True DeleteComments : True RemovePrivateProperty : true DeleteSubject : True AddOrganizerToSubject : True DeleteNonCalendarItems : True TentativePendingApproval : True EnableResponseDetails : True OrganizerInfo : True ResourceDelegates : {Some Delegate} RequestOutOfPolicy : {username} AllRequestOutOfPolicy : False BookInPolicy : AllBookInPolicy : True RequestInPolicy : AllRequestInPolicy : True AddAdditionalResponse : False AdditionalResponse : RemoveOldMeetingMessages : True AddNewRequestsTentatively : True ProcessExternalMeetingMessages : False RemoveForwardedMeetingNotifications : False MailboxOwnerId : AD ID Identity : AD ID IsValid : True If you are not familiar with the cmdlet (see http://technet.microsoft.com/en-us/library/dd335046.aspx), set the resource mailbox in OWA Resource Option (enable the AD account first). Besides, it is recommended to use one delegate for a mailbox. For more, see “Outlook meeting requests: Essential do’s and don’ts” at http://office.microsoft.com/en-us/outlook-help/outlook-meeting-requests-essential-dos-and-donts-HA001127678.aspx. Best regards, Fiona Liao Email: v-fiolia@microsoft.com IBS TechNet Forum Exchange Support Team