Home

Exchange 2010 Hybrid - Disabled remote mailbox

%3CLINGO-SUB%20id%3D%22lingo-sub-251138%22%20slang%3D%22en-US%22%3EExchange%202010%20Hybrid%20-%20Disabled%20remote%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-251138%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20everyone%20is%20well.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20could%20someone%20assist%20me%20with%20the%20following%20issue.%20So%2C%20I%20got%20an%20Exchange%202010%20hybrid%20environment%20with%20a%20few%20mailboxes%20migrated%20to%20Office%20365%2C%20and%20they%20are%20listed%20as%20remote%20mailboxes%20in%20Exchange%202010.%20One%20my%20clients%20right%20clicked%20on%20one%20of%20these%20remote%20mailboxes%20and%20chose%20to%20disable%20it.%20Now%20the%20mailbox%20exists%20in%20Office%20365%20but%20no%20longer%20as%20a%20remote%20mailbox%20on-premise.%20Migrated%20users%20can%20find%20his%20email%20address%20in%20the%20GAL%2C%20but%20on-premise%20Exchange%20users%20cannot.%20The%20AD%20account%20is%20still%20in%20place.%20What%20would%20be%20the%20best%20way%20to%20resolve%20this%3F%20So%20that%20the%20migrated%20user%20shows%20up%20as%20a%20remote%20mailbox%20in%20the%20Exchange%202010%20organisation%20and%20on-premise%20users%20can%20find%20him%20in%20the%20GAL.%20Appreciate%20any%20advice.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-251138%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2010%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-260261%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%202010%20Hybrid%20-%20Disabled%20remote%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-260261%22%20slang%3D%22en-US%22%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EFor%20the%20missing%20remote%20mailboxes%20repairing%20you%20will%20need%20to%20have%20the%20ExchangeGUID%20of%20those%20O365%20mailboxes.%20Get-mailbox%20is%20the%20proper%20ps%20commandlet%20in%20the%20EXO%20order%20to%20you%20have%20these%20attributes.%20For%20the%20repairing%20process%20you%20do%20not%20need%20to%20revoke%20and%20reassign%20the%20used%20O365%20license%20for%20the%20affected%20users.%3C%2FDIV%3E%3CDIV%3EFixing%20process%20the%20following%3A%3C%2FDIV%3E%3CDIV%3E1.%20Recreate%20the%20remote%20mailbox%20for%20the%20affected%20users%3C%2FDIV%3E%3CDIV%3EEnable-RemoteMailbox%20SAMACCOUNTNAME%20-RemoteRoutingAddress%20SAMACCOUNTNAME%40xxxxxxx.mail.onmicrosoft.com%3C%2FDIV%3E%3CDIV%3EThe%20remoteroutingaddress%20will%20be%20your%20tenant%20mail%20service%20domain.%20If%20it%20is%20done%20the%20recreated%20remote%20mailbox%20will%20have%20ExchangeGUID%20attribute%20with%20null%20value.%20Then%20you%20will%20have%20to%20overwrite%20this%20with%20the%20mentioned%20ExchangeGUID%20of%20the%20user%20O365%20mailbox.%26nbsp%3B%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E2.%20Fix%20the%20remote%20mailbox%20ExchangeGUID%3C%2FDIV%3E%3CDIV%3ESet-RemoteMailbox%20SAMACCOUNTNAME%20-ExchangeGUID%20%3CCOPY%20from%3D%22%22%20office365%3D%22%22%20exchange%3D%22%22%20guid%3D%22%22%3E%3C%2FCOPY%3E%3C%2FDIV%3E%3CDIV%3E3.%20Make%20manual%20ADconnect%20delta%20sync.%3C%2FDIV%3E%3CDIV%3E%3CBR%20%2F%3EThen%20your%20users%20are%20able%20to%20use%20desktop%20outlook%20again.%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-251142%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%202010%20Hybrid%20-%20Disabled%20remote%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-251142%22%20slang%3D%22en-US%22%3E%3CP%3Ethink%20I%20found%20my%20solution%20here%20%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FExchange%2FMigrated-user-mailbox-was-disabled-on-premises%2Fm-p%2F95442%23M1268%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FExchange%2FMigrated-user-mailbox-was-disabled-on-premises%2Fm-p%2F95442%23M1268%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Frequent Contributor

Hi all

 

Hope everyone is well.

 

Please could someone assist me with the following issue. So, I got an Exchange 2010 hybrid environment with a few mailboxes migrated to Office 365, and they are listed as remote mailboxes in Exchange 2010. One my clients right clicked on one of these remote mailboxes and chose to disable it. Now the mailbox exists in Office 365 but no longer as a remote mailbox on-premise. Migrated users can find his email address in the GAL, but on-premise Exchange users cannot. The AD account is still in place. What would be the best way to resolve this? So that the migrated user shows up as a remote mailbox in the Exchange 2010 organisation and on-premise users can find him in the GAL. Appreciate any advice.

2 Replies
 
 
For the missing remote mailboxes repairing you will need to have the ExchangeGUID of those O365 mailboxes. Get-mailbox is the proper ps commandlet in the EXO order to you have these attributes. For the repairing process you do not need to revoke and reassign the used O365 license for the affected users.
Fixing process the following:
1. Recreate the remote mailbox for the affected users
Enable-RemoteMailbox SAMACCOUNTNAME -RemoteRoutingAddress SAMACCOUNTNAME@xxxxxxx.mail.onmicrosoft.com
The remoteroutingaddress will be your tenant mail service domain. If it is done the recreated remote mailbox will have ExchangeGUID attribute with null value. Then you will have to overwrite this with the mentioned ExchangeGUID of the user O365 mailbox.  
2. Fix the remote mailbox ExchangeGUID
Set-RemoteMailbox SAMACCOUNTNAME -ExchangeGUID <Copy from Office365 Exchange GUID>
3. Make manual ADconnect delta sync.

Then your users are able to use desktop outlook again.