How To Create Room Mailbox In Exchange 2013
- Home
- Collaboration
- Microsoft Exchange
We did some updates to our Exchange 2013 Server, which caused the inability to Search Items in Current Folders in a Resource Room. I have searched many threads and tried all the "fixes" I could find and nothing is resolving the Search function. I'm thinking of converting the Resource to a Regular User mailbox would fix this issue.
My question is: Has anyone tried converting a Resource to Regular Mailbox successfully?
If I were to convert the Resource Room to a "Regular" Mailbox is there a chance of losing email messages or folder structure during this process?
Below are a few links I'm reviewing and going to try on a TEST Mailbox:
https://docs.microsoft.com/en-us/exchange/recipients-in-exchange-online/manage-user-mailboxes/conver...
https://www.codetwo.com/kb/migrate-room-mailbox/
https://docs.microsoft.com/en-us/exchange/recipients/user-mailboxes/convert-mailboxes?view=exchserver-2019
Any advice would be most appreciated!
Brand Representative for Microsoft
Super easy to do via powershell
Set-Mailbox MailboxAlias -Type Regular
converting mailboxes does nothing but change the RecipientTypeDetails attribute so don't fret about data loss.
Get-Mailbox -Identity MailboxAlias | Format-List RecipientTypeDetails
12 Replies
Brand Representative for Microsoft
Super easy to do via powershell
Set-Mailbox MailboxAlias -Type Regular
converting mailboxes does nothing but change the RecipientTypeDetails attribute so don't fret about data loss.
Get-Mailbox -Identity MailboxAlias | Format-List RecipientTypeDetails
Gregory for Microsoft wrote:
Super easy to do via powershell
Set-Mailbox MailboxAlias -Type Regular
converting mailboxes does nothing but change the RecipientTypeDetails attribute so don't fret about data loss.
Get-Mailbox -Identity MailboxAlias | Format-List RecipientTypeDetails
Thank you for responding... I'm going to give it a try and cross my fingers! Wish I could get the Search function working but I think that's a lost cause as I have exhausted every avenue. This is my "Only Hope"!
Yes, we can use Set-Mailbox "Alias" -Type regular -verbose to convert the resource mailbox to user mailbox. But please set a password on the Room mailbox you're converting before running the command.
In addition, you also can export the mailboxes to pst file, then recreate the mailboxes.
Lucid Flyer wrote:
Did you check if your index is broken by any chance?
https://support.microsoft.com/en-ca/help/2807668/content-index-status-of-all-or-most-of-the-mailbox-...
Get-MailboxDatabaseCopyStatus
Yes... checked/rebuilt indexing, repaired/reinstalled office, removed/added Users from/to Resource mailbox, etc... the odd thing is 2 out of 5 cannot search Current Folders inside the Room Resource. The only difference between machines is the 2 have Windows 7 and the other 3 have Windows 10 and the Windows 7 updates are current.
The only thing that changed, was an update to the Exchange Server. They were able to Search fine last Friday, updates were done on Sunday, and we do not know what broke come Monday morning.
jaycekakay wrote:
Yes, we can use Set-Mailbox "Alias" -Type regular -verbose to convert the resource mailbox to user mailbox. But please set a password on the Room mailbox you're converting before running the command.
In addition, you also can export the mailboxes to pst file, then recreate the mailboxes.
Thank you for the information we did not see that in the instructions we found on Microsoft KB... we made a Test Resource, we made a backup of the PST before conversion and we were prompted for a password during the this process. We are going to check out the Test today and see if it's functioning properly before converting the "problem child" Room Resource.
What CU are you on? Have you updated Windows server on which Exchange runs with the latest updates?
Lucid Flyer wrote:
What CU are you on? Have you updated Windows server on which Exchange runs with the latest updates?
Yes ... the Exchange Windows Server was updated with the latest greatest.That's when the trouble with Searching started.
Start-Transcript log0 . txt Get-OabVirtualDirectory | fl server , Name , * URL *, * auth * Get-WebServicesVirtualDirectory | fl server , Name , * URL *, * auth * Get-EcpVirtualDirectory | fl server , Name , * URL *, * auth * Get-ActiveSyncVirtualDirectory | fl server , Name , * URL *, * auth * Get-OutlookAnywhere | fl server , Name , * URL *, * hostname *, * auth * Get-OwaVirtualDirectory | fl server , Name , * URL *, * auth * Get-ClientAccessServer | fl Name , OutlookAnywhereEnabled , AutodiscoverServiceInternalUri Get-ExchangeCertificate | fl FriendlyName , Subject , CertificateDomains , Thumbprint , Services , Issuer , * not * Get-MapiVirtualDirectory | fl server , Name , * URL *, * auth * Get-ClientAccessArray | fl Get-OutlookProvider Get-ExchangeServer | fl * version * Get-OrganizationConfig | fl * mapi * Stop-Transcript
Lucid Flyer wrote:
Attach log0.txt with your config, replace your real FQDN with domain.comStart-Transcript log0 . txt Get-OabVirtualDirectory | fl server , Name , * URL *, * auth * Get-WebServicesVirtualDirectory | fl server , Name , * URL *, * auth * Get-EcpVirtualDirectory | fl server , Name , * URL *, * auth * Get-ActiveSyncVirtualDirectory | fl server , Name , * URL *, * auth * Get-OutlookAnywhere | fl server , Name , * URL *, * hostname *, * auth * Get-OwaVirtualDirectory | fl server , Name , * URL *, * auth * Get-ClientAccessServer | fl Name , OutlookAnywhereEnabled , AutodiscoverServiceInternalUri Get-ExchangeCertificate | fl FriendlyName , Subject , CertificateDomains , Thumbprint , Services , Issuer , * not * Get-MapiVirtualDirectory | fl server , Name , * URL *, * auth * Get-ClientAccessArray | fl Get-OutlookProvider Get-ExchangeServer | fl * version * Get-OrganizationConfig | fl * mapi * Stop-Transcript
What will this affect? I don't like running Scripts without knowing what this may "break".
Nothing, get commands just retrieve information, it doesn't change anything.
Based on your description, it seems that the search issue is only for this room mailbox, and if yes, I suggest you export the mailbox to pst fine. Then recreate the room mailbox, import the pst file. Since the mailbox is new and the search should be work. If the search issue is for all the mailboxes and this is should be Exchange server level issue, you need to check the Exchange configuration and event log and so on.
This topic has been locked by an administrator and is no longer open for commenting.
To continue this discussion, please ask a new question.
How To Create Room Mailbox In Exchange 2013
Source: https://community.spiceworks.com/topic/2166842-convert-a-resource-mailbox-to-a-user-mailbox-in-exchange-2013
Posted by: rodriguezalmou1981.blogspot.com
0 Response to "How To Create Room Mailbox In Exchange 2013"
Post a Comment