Forum Discussion
The type of the resource mailbox can't be blank. It should be either Room or Equipment.
Hi JrouziesM,
The error message you posted indicates a problem with the mailbox type. To try to resolve this, you can try this:
1. Check that the mailbox type is set correctly as "Room" in Exchange Online. You can do this using PowerShell with the following command:
Set-Mailbox -Identity "HoChiMinhViettelTower_MeetingRoom01" -Type Room
2. Verify the mailbox type for the remote mailbox by running:
Get-RemoteMailbox "HoChiMinhViettelTower_MeetingRoom01" | Select-Object -Property RemoteRecipientType, RecipientType, RecipientTypeDetails
Ensure that `RemoteRecipientType` is "Migrated, RoomMailbox," and `RecipientTypeDetails` is "RemoteRoomMailbox."
3. Permissions: Ensure that the account running the PowerShell script has the necessary permissions to modify resource mailbox types.
4. Ensure there are no duplicate mailboxes or conflicting settings that might be causing the issue:
Get-Mailbox -Filter {DisplayName -like "HoChiMinhViettelTower_MeetingRoom01"} | Select-Object DisplayName, RecipientType
5. Review AD Attributes: check the Active Directory attributes for this mailbox, ensuring they match those of other working room mailboxes.
- look for attributes related to mailbox type and permissions. Common attributes to check include:
msExchRecipientTypeDetails: This attribute specifies the recipient type of the mailbox. For a room mailbox, it should be set to a value corresponding to "Room Mailbox."
msExchRecipientDisplayType: This attribute indicates the recipient's display type. For a room mailbox, it should be set to "Conference Room."
msExchResourceMetaData: This attribute may contain additional information about the resource mailbox.
6. Run Mailbox Repair: detect and repair mailbox issues. Here's an example:
New-MailboxRepairRequest -Mailbox HoChiMinhViettelTower_MeetingRoom01 -CorruptionType ProvisionedFolder,SearchFolder,AggregateCounts,Folderview
This command initiates mailbox repair for various types of corruption.
6. Remove and Recreate the Remote Mailbox: if the issue persists, remove and recreate the remote mailbox. You can use these commands:
Disable-RemoteMailbox "HoChiMinhViettelTower_MeetingRoom01"
Enable-RemoteMailbox "HoChiMinhViettelTower_MeetingRoom01" -Room
Please click Mark as Best Response & Like if my post helped you to solve your issue.
This will help others to find the correct solution easily. It also closes the item.
If the post was useful in other ways, please consider giving it Like.
Kindest regards,
Leon Pavesic
Thanks for detailled reply, unfortunately all those things were already tried.
The types are already good as said in my post.
Online command:
Set-Mailbox -Identity "HoChiMinhViettelTower_MeetingRoom01" -Type Room
WARNING: Couldn't convert the mailbox because the mailbox "HoChiMinhViettelTower_MeetingRoom01" is already of the type "Room".
OnPremises command throw the error as indicated also in my original post.
The mailbox work properly, so repair commands Online are not going to fix an error on the OnPremises command.
Active Directory Attributes are filled properly:
Get-ADUserByUPN -UserPrincipalName email address removed for privacy reasons -Properties * | FL *recip*
msExchRecipientDisplayType : -2147481850
msExchRecipientTypeDetails : 8589934592
msExchRemoteRecipientType : 36
Example of another room that does not have the error:
Get-ADUserByUPN -UserPrincipalName email address removed for privacy reasons -Properties * | FL *recip*
msExchRecipientDisplayType : -2147481850
msExchRecipientTypeDetails : 8589934592
msExchRemoteRecipientType : 36
Again I compared all properties with a room without this error / warning, and everything match.
Yes last time it happened, disabling and re-enabling did the trick, but this is not a satisfying solution. Microsoft should find the source of the error and allow us to run a fix.
How do we report this kind of bug officially so Microsoft finds a fix?
- Check also the following AD Attribute: msExchUserAccountControl
https://blog.icewolf.ch/archive/2020/06/23/active-directory-attributes-for-diffrent-mailbox-types/
Regards
Andres - Can I ask what you are trying to achieve? From what you have provided here, the mailbox in EXO is already a room mailbox, so I fail to see why you are trying to convert it to a room when it already is that
- We have provisioning systems that simply re-run some commands / re-apply calendar processing stuff etc. We get this error for those Rooms.
Yes this is the biggest issue: all the attributes look good, still, as you can see, a Get-RemoteMailbox or Set-RemoteMailbox brings the warning / error.
And there is nothing we can do to fix it except disabling and re-enabling it.- But what exactly are you fixing? Is anything broken when the provisioning system re-runs the commands? Again, everything looks set correctly when you get the error, so maybe the error is because the attribute values are already set correctly. It wouldn't be the first time Microsoft error messages aren't very helpful 😉
