none
Can't move user to Office365 because msExchMailboxGUID # does not exist

    Question

  • When attempting to move a single user from On-Premesis Exchange (2010) server to the cloud (Office365), we get the following error:

    ---------

    Error:
    The operation couldn't be performed because object 'c8be3e40-c97d-440a-8c15-bcafe9e7ddda' couldn't be found on 'SN2PRD0510DC006.namprd05.prod.outlook.com'.

    Exchange Management Shell command attempted:
    'c8be3e40-c97d-440a-8c15-bcafe9e7ddda' | New-MoveRequest -Remote -RemoteHostName 'webmail.liberty.edu' -RemoteCredential 'System.Management.Automation.PSCredential' -TargetDeliveryDomain 'service.domain.com'

    --------

    Thursday, November 15, 2012 4:31 PM

Answers

  • We have found a solution. Here goes ...

    Conditions:

    1. Mailbox is in the Cloud
    2. Want to move to Exchange
    3. ExchangeGUIDs do not match

    In O365 PS, type:

    PS C:\Users\username> get-mailbox <user-alias> |fl exchangeguid

    Results =

    ExchangeGuid : b4d1df17-5057-4756-9a71-70a346e516c2

    In Exchange PS, type:

    [[PS] C:\Windows\system32>get-remotemailbox <user-alias>  |fl exchangeguid

    Results =

    ExchangeGuid : 9fe7d96d-3918-43b3-a8f3-bf392c193c4b

    THEN, in Exchange PS, Type:

    [PS] C:\Windows\system32>set-remotemailbox <user-alias>  -exchangeguid b4d1df17-5057-4756-9a71-70a346e516c2

    To Test that the change has taken effect, type:

    [PS] C:\Windows\system32>get-remotemailbox <user-alias>  |fl exchangeguid

    Results =

    ExchangeGuid : b4d1df17-5057-4756-9a71-70a346e516c2


    Thursday, June 13, 2013 8:08 PM

All replies

  • Are you sure that user's directory object is properly synchronized to Office 365?


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

    Thursday, November 15, 2012 5:04 PM
  • Yes, we have completed full sync, multiple times.
    Thursday, November 15, 2012 5:18 PM
  • Issue:

    The operation couldn't be performed because object couldn't be found on 'xxx.prod.outlook.com'

    Resolution:

    The object has not been replicated to Office 365, check Dirsync error logs, dirsync email errors. Ensure these errors have all been resolved before the users are added to migration list and ensure the object has been sync’d to O365

    Office 365 Migration Issues:

    http://blogs.technet.com/b/danielkenyon-smith/archive/2012/04/10/office-365-migration-issues.aspx

    @RabbitRunner, I would also suggest you seek the solution in the Office 365 forum:

    http://community.office365.com/en-us/forums/default.aspx


    Frank Wang

    TechNet Community Support

    • Marked as answer by emma.yoyo Wednesday, November 21, 2012 2:16 AM
    • Unmarked as answer by Michael R. Emmert Thursday, June 13, 2013 8:11 PM
    Friday, November 16, 2012 7:19 AM
  • We have found a solution. Here goes ...

    Conditions:

    1. Mailbox is in the Cloud
    2. Want to move to Exchange
    3. ExchangeGUIDs do not match

    In O365 PS, type:

    PS C:\Users\username> get-mailbox <user-alias> |fl exchangeguid

    Results =

    ExchangeGuid : b4d1df17-5057-4756-9a71-70a346e516c2

    In Exchange PS, type:

    [[PS] C:\Windows\system32>get-remotemailbox <user-alias>  |fl exchangeguid

    Results =

    ExchangeGuid : 9fe7d96d-3918-43b3-a8f3-bf392c193c4b

    THEN, in Exchange PS, Type:

    [PS] C:\Windows\system32>set-remotemailbox <user-alias>  -exchangeguid b4d1df17-5057-4756-9a71-70a346e516c2

    To Test that the change has taken effect, type:

    [PS] C:\Windows\system32>get-remotemailbox <user-alias>  |fl exchangeguid

    Results =

    ExchangeGuid : b4d1df17-5057-4756-9a71-70a346e516c2


    Thursday, June 13, 2013 8:08 PM
  • RabbitRunner

    This looks promising, but I don't understand how this works.  In our Hybrid setup our mailboxes either exist on the on-premise server or out in the Office 365 cloud, but not both at the same time.  How are you checking this?

    Monday, July 08, 2013 5:00 PM
  • what we have to do if Mailbox is OnPremise?

    is there an equivalent cmdlet to change ExchangeGUID?

    is there any side-effect when changing ExchangeGUID?

    Tuesday, July 30, 2013 9:57 AM
  • The following command will modify the exchange GUID for the on-premise user

    set-remotemailbox <user-alias>  -exchangeguid <exchangeGUID-Number>

    Thursday, November 20, 2014 12:30 PM
  • Is this the same process if you are migrating to the cloud from an on premise mail server?
    Friday, March 17, 2017 4:39 PM