Notes room internet address was shortened to meet Microsoft 20 characters sAMAccountName attribute limit:
All Users have already been migrated but rooms still exist as contacts in AD. After the Notes room address got shortened, re-provision the room in AD and sync the contact to O365, the FreeBusy info is not showing when looking at pre-existing meetings, for instance a migrated user that booked the room in O365 before the address was shortened.
WORKAROUND:
x500:/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=90b9a6bb4e9f44ea9c151ed1432f34d5-NotesRoom
Otherwise you need to use a tool that allows you to view the Recipient Table of a message as well as the MAPI properties. Either of these tools will work, MfcMapi or Outlook Spy. Using either one of these tools, you need to open a calendar item where the room was reserved using the old name and open the Recipient Table. Look for the room within the Recipient Table, and look for the PR_EMAIL_ADDRESS MAPI property. This contains the old legacyExchangeDN of the room. Copy the property value. It will look something like this:
“/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=90b9a6bb4e9f44ea9c151ed1432f34d5-NotesRoom”.
Finally add the legacyExchangeDN found as another entry in the proxyAddresses attribute for the new created room AD contact:
x500:/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=90b9a6bb4e9f44ea9c151ed1432f34d5-NotesRoom
7.- Try to see the FreeBusy info for a Notes Room from an appointment that was created when the room was still using the long name address.
When a user’s mailbox is first migrated everything should appear fine. The issue would only show up AFTER the room is provisioned because the legacyExchangeDN attribute value changes. The issue will occur when looking at pre-existing meetings, such as when rescheduling a meeting. New meetings would not see this issue. From the user’s perspective it can also easily be resolved by removing the room from the meeting and adding it back again.
Additional information:
The correct process to migrate to O365 should be as follows:
