I have some major inconsistencies with the resource mailboxes in our Exchange 2007 SP1 environment. When I create a new test resource mailbox - set the type as equipment (or room), and set mailboxcalendarsettings to 'autoaccept', it works as expected. A user can invite the resource when booking, and the AutoAttendant Agent automatically books the appointment in the resource's calendar and send an 'Accepted booking' reply to the user. Great! There are a good number of resources that do not behave this way. The mailboxcalendarsettings on these mailboxes are identical to the example described above. I have tried with the AD accounts on these mailboxes, disabled or enabled (I know they should be disabled for resources). The behavior is different in that some of the mailboxes do not AutoAccept, instead they set the event as 'pending'. In some cases, the resources do a direct booking - I want to turn this off and have them be consistent with our resource AutoAccept settings. In some other cases, the resources will not book anything at all - nothing shows up on the resource's calendar (not even a pending item), nothing happens. The following are the settings for such resources: AutomateProcessing : AutoAccept AllowConflicts : False BookingWindowInDays : 365 MaximumDurationInMinutes : 1440 AllowRecurringMeetings : True EnforceSchedulingHorizon : True ScheduleOnlyDuringWorkHours : False ConflictPercentageAllowed : 0 MaximumConflictInstances : 0 ForwardRequestsToDelegates : True DeleteAttachments : True DeleteComments : True RemovePrivateProperty : True DeleteSubject : True DisableReminders : True AddOrganizerToSubject : True DeleteNonCalendarItems : True TentativePendingApproval : True EnableResponseDetails : True OrganizerInfo : True ResourceDelegates : {} RequestOutOfPolicy : AllRequestOutOfPolicy : False BookInPolicy : AllBookInPolicy : True RequestInPolicy : AllRequestInPolicy : False AddAdditionalResponse : False AdditionalResponse : RemoveOldMeetingMessages : True AddNewRequestsTentatively : True ProcessExternalMeetingMessages : False DefaultReminderTime : 15 RemoveForwardedMeetingNotifications : False Identity : domain_bane/Users/RES: Car I should mention that I believe these irregular resources were migrated over from exchange 2003 and not created from scratch when we were on Exchange 2007 (I wasn't working at this organization when the migration happened so I don't know the details). Any help would be appreciated

For anyone who has run into this issue, deleting and recreating the resource in Exchange 2007 worked just fine, my question was regarding how to fix this without recreating the resource. The issue is definitely only related to mailboxes migrated from exchange 2003 - exchange 2007 incorrectly.

On the mailboxes moved from 2003, did you do a set-mailbox -type command on them? The Type parameter specifies the type for the mailbox. You can use the following values: Regular Room Equipment Shared Karl

Yeah, it was set to type equipment in this case - i.e. in the Exchange 2007 environment.

Did you compare settings with a working resource, and set the non working ones the same using Set-MailboxCalendarSettings?Karl

Yeah had the settings identical to a working one. I recall seeing a post somewhere that a vbs script needs to be run against the resource when migrating from 2003 to 2007 and as I wasn't around when the migration was done, I'm not sure if that ever took place

I'm having the same exact issue. I don't think the script was run prior to migrating. Can this be resolved without deleting and creating the resource from scratch?