Forum Discussion
JrouziesM
Sep 15, 2023Brass Contributor
The type of the resource mailbox can't be blank. It should be either Room or Equipment.
Hello, We are having errors on some Room Remote Mailboxes, and cannot find any reference on Internet or apply any fix unless Disabling and Re-enabling the Room mailbox. Get-remotemailbox HoCh...
Dan_Snape
Sep 19, 2023Iron Contributor
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
JrouziesM
Sep 21, 2023Brass Contributor
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.
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.
- Dan_SnapeSep 22, 2023Iron ContributorBut 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 😉
- JrouziesMAug 14, 2025Brass Contributor
Hey, well I see this is an old reply, sorry I guess I never saw it
The issue is: even if I want to run a legit Set-RemoteMailbox commands, e.g. changing the DisplayName property or whichever, I get this error OnPremises. So I cannot edit my Remote mailbox in that state, unless as said before I fully Disable-RemoteMailbox and redo it again.