Exchange 13 - Can't remove resource delegates

Recently migrated a client to Exchange 2013 from 2007. 2013 is running on SP1 (CU4).

The 10 resource mailboxes (all rooms) after the migration are not behaving properly. All of the resources had Booking Delegates on them. Per request, I removed the Booking Delegates and set it to auto accept/deny and not allow conflicts.

1st. If a user sends a calendar request to the room, they receive a confirmation email back but it still says it was on behalf of the booking delegate (despite them being removed as a delegate).

2nd. Free/busy doesn't seem to be working for the migrated ones as they always show as Free. In addition, it auto-accepts all requests even if there is a conflict.

I created a new room mailbox with default settings without a booking delegate, it behaved as expected and desired. Free/busy works for it too.
LVL 10
Schuyler DorseyAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Schuyler DorseyAuthor Commented:
I did a get-mailbox and get-calendarprocessing and compared the new test one versus one of the problematic one and do not see any differences.
Schuyler DorseyAuthor Commented:
After we removed the booking delegates, the room stopped working. Users would not receive email confirms, room was not accepted and it was never added to the calendar. Found that if we added a booking delegate back in, the room would start working again but the confirmation emails would still come from the OLD booking delegate.

Spent 6 hours on phone with Microsoft Support over the course of two days and after all their diagnostics and troubleshooting, their final recommendation was to export the calendars, delete the mailbox, create a whole new one and import the data.

We went through adsiedit, ldap, A.D., Exchange properties and found zero difference between the migrated non-working mailboxes and the 2 new test room mailboxes I created directly in Exch13 which worked correctly.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Schuyler DorseyAuthor Commented:
MS support provided the only answer.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.