locked
Cross-Forest Move-Request Exchange 2007 to Exchange 2013 RRS feed

  • Question

  • Hi people!!

    We have two Exchange environments in different forest. We want to do a crossforest migration from Exchange Server 2007 to Exchange Server 2013 (Exchange Resource Forest with Linked Mailboxes). These are the configurations:

    Domain: SourceDomain.local

    Active Directory: 2012 R2 Domain Controllers. Domain functional level 2008

    Exchange: Exchange Server 2007 Service Pack 3 RU15

    • 2 Mailboxes Servers à Cluster Continuous Replication
    • 2 ClientAccess & HubTransport Servers with NLB by Microsoft
    • 2 Edge Servers
    • ISA 2006 to publish OWA, EAS, EWS…

    Domain: TargetDomain.local

    Active Directory: 2012 R2 Domain Controllers. Domain functional level 2012 R2

    Exchange: Exchange Server 2013 Cumulative Update 7 (CU7) (Exchange Resource Forest)

    • 2 Mailboxes Servers à 1 DAG
    • 2 ClientAccess Servers
    • 2 Edge Servers

    Both Exchange works fine. Exchange Server 2007 (SourceDomain.local) is currently in production and Exchange Server 2013 in Resource Forest (TargetDomain.local) is for migrating mailboxes in Linked Mailbox from Exchange 2007. We´ve configured a Linked Mailbox and it works.

    We´ve configured a trust between the forests:

    • Conditional Forwarders in both domains
    • Forest trust, One-way outgoing, Forest-wide authentication: TargetDomain.local, Domains trusted by this domain (outgoing trusts) à SourceDomain.local – Forest- Transitive SourceDomain.local, Domains that trust this domain (incoming trusts) à TargetDomain.local – Forest – Transitive

    We´ve configured following prerequisites for migrating:

    • Accepted Domains à Both Exchanges have an accepted domain: Company.com as Internal Relay Domain
    • Send Connectors à Both Exchange have a send connector (CrossForest) with Address Space: *.company.com and Smart Hosts
    • Test Mailflow. (Currently, MXs for company.com are in Exchange 2007)
      • Mail from external source to mailbox in Exchange 2007 à OK
      • Mail from external source to mailbox in Exchange 2013 à OK
      • Mail from external source to Linked Mailbox in Exchange 2013 an account in Domain SourceDomain.local à OK
      • Internal Mail from Exchange 2007 to Exchange 2013 à OK
      • Internal Mail from Exchange 2013 to Exchange 2007 à OK
    • MRSPROXY. We´ve activated MRSProxy in both Client Access Servers in Exchange 2013

    For Migrating Mailboxes, from Client Access Server in Exchange 2013 in PowerShell, We’ve done these steps:

    • Preparation Mailboxes. Previously We´ve stored credentials with Get-Credential. $SourceCredentials à SourceDomain.local and &TargetCredentials à TargetDomain.local We´ve run this command: Prepare-MoveRequest.ps1 –identity “Testuser”–RemoteForestDomainController DC1.SourceDomain.local –RemoteForestCredential $SourceCredentials –LocalForestDomainController DC1.TargetDomain.local –LocalForestCredential $TargetCredentials –LinkedMailUser –TargetMailUserOU “OU=Mailboxes,DC=TargetDomain,DC=local” –Verbose It finished fine and 1 mailbox ready to move. We´ve checked It´s created a Disable User in TargetDomain.Local.
    • New-MoveRequest. Previously We´ve stored credentials with Get-Credential. $SourceCredentials à SourceDomain.local We´ve run this command: New-MoveRequest –identity “Testuser” –RemoteLegacy –TargetDatabase “DB1” –RemoteGlobalCatalog “DC1.SourceDomain.local” –RemoteCredential $SourceCredentials –TargetDeliveryDomain “company.com” It finished with this error: MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80004005, ec=2423)

    Diagnostic context:

        ......

        Lid: 62184

        Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a

        Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 4480

        Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0415-06-16T07:25:29.0510000Z

        Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18

        Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1722

        Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 323

        Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0

        Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0

        Lid: 62184

        Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a

        Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 4480

        Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0415-06-16T07:25:29.0510000Z

        Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18

        Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1237

        Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 313

        Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0

        Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0

        Lid: 62184

        Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a

        Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 4480

        Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0415-06-16T07:25:29.0510000Z

        Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18

        Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 10060

        Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 311

        Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0

        Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 3

        Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[0]: Long val: 135

        Lid: 15000   dwParam: 0x0 Msg: EEInfo: prm[1]: Pointer val: 0x0

        Lid: 15000   dwParam: 0x0 Msg: EEInfo: prm[2]: Pointer val: 0x2A84C00A00000000

        Lid: 62184

        Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a

        Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 4480

        Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0415-06-16T07:25:29.0510000Z

        Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18

        Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 10060

        Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 318

        Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0

        Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0

        Lid: 45169   StoreEc: 0x977

        Lid: 50544   ClientVersion: 15.0.1044.25

        Lid: 52080   StoreEc: 0x977

        Lid: 51152

        Lid: 52465   StoreEc: 0x977

        Lid: 60065

        Lid: 33777   StoreEc: 0x977

        Lid: 59805

        Lid: 52487   StoreEc: 0x977

        Lid: 19778

        Lid: 27970   StoreEc: 0x977

        Lid: 17730

        Lid: 25922   StoreEc: 0x977

        + CategoryInfo          : NotSpecified: (:) [New-MoveRequest], RemoteTransientException

        + FullyQualifiedErrorId : [Server=MAIL01,RequestId=48ad3e2e-deb3-492d-bfff-1425c231ae6f,TimeStamp=16/06/2015 7

       :25:29] [FailureCategory=Cmdlet-RemoteTransientException] D68807DB,Microsoft.Exchange.Management.RecipientTasks.Ne

      wMoveRequest

        + PSComputerName        : CAS01.TargetDomain.local  

    After this error, We´ve done following changes and tests:

    • To check network permission between both Exchanges and Active Directory. Currently we have any/any permissions.
    • To resolve NETBIOS name and FQDN names beween both Exchange. In TargetDomain.local We added in host file NETBIOS name and FQDN name of all Exchange Servers 2007. In SourceDomain.local we can do ping to NETBIOS and FQDN without to edit host file.
    • Import Root CA Between both Exchange Organizations. In each Exchange server in SourceDomain.local import Root CA we use in Exchange 2013 and in each Exchange server in TargetDomain.local import Root CA we use in Exchange 2007. After this, We´ve checked to access OWA without warning certificate (Internal Access OWA).
    • Restart all Exchange Servers 2013.

    After these steps we carry on with the same error:

    MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80004005, ec=2423)

    I´ve tried as well to do the movement of Mailbox from EAC in Exchange Server 2013. After insert Source Credentials, we have this warning:

    new cross-forest mailbox move
    Confirm the migration endpoint
    We couldn't detect your server settings. Please enter them. AutoDiscover failed with a configuration error: The migration service failed to detect the migration endpoint using the Autodiscover service. Consider using the Exchange Remote Connectivity Analyzer ‎(https://testexchangeconnectivity.com)‎ to diagnose the connectivity issues.

    Remote MRS proxy server:
    The FQDN of the Exchange server that the Mailbox Replication Service (MRS) Proxy is on. 

    I´ve tried to inser FQND of CCR (Cluster Mailboxes) and FQND of each Mailbox Server, but when I press Next button, it tells me:

    Error: The connection to the server "ccr.sourcedomain.local" could not be completed.

    Is possible to do movement Mailbox from Exchange 2007 to 2013?? Please Could someone help me?

    Thank you.


    Wednesday, June 17, 2015 8:47 AM

Answers

  • Hi guys!

    Finally I could resolve my problem... It was a problem with network permissions...

    Thanks a lot for your advices.

    • Marked as answer by Niko.Cheng Thursday, June 25, 2015 2:09 AM
    Monday, June 22, 2015 10:10 AM

All replies

  • Hi Andrew,

    First of all, thank your for your reply.

    I´ve been the technet blog, but this guide is for migrating Exchange 2007 to 2013 in the same organization, with local mailbox moves. In my case is cross-forest moves.

    I´ve used Deployment Assistant, but i havent seen cross-forest option...

    I understand this process is supported by Microsoft (Cross-forest migration from 2007 to 2013), but I havent seen any official document by Microsoft.

    One year ago, I did the same process from Exchange 2007 to 2010 and it works!

    Network team told me the permissions are ok (any-any) between both Domains... but If i see the error ( MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80004005, ec=2423)) 

    I´ve jus opened a case with Microsoft... I hope they can help me.

    Thank you!!!


    Thursday, June 18, 2015 8:19 AM
  • Hi

    You can refer the link : careexchange crossforest

    Thursday, June 18, 2015 9:50 AM
  • Hi AMBF,

    Yes, I checked careexchange crossforest guides... but It doesnt exist about Exchange 2007 to 2013.

    I saw the guide crossforest from 2003 to 2010 with Move-Request with -RemoteLegacy. I did the same stepst... but it didnt work...

    In my case is a little bit different, because is an Exchange Resource Forest migration, but I understand it doesnt change, only in attribute LinkedMailbox in Prepare-MoveRequest...

    Thanks for your reply mate!!

    Thursday, June 18, 2015 10:08 AM
  • Hi guys!

    Finally I could resolve my problem... It was a problem with network permissions...

    Thanks a lot for your advices.

    • Marked as answer by Niko.Cheng Thursday, June 25, 2015 2:09 AM
    Monday, June 22, 2015 10:10 AM
  • Hi Tropoglar!

    I am in the same kind of implementation and I was be able to do the mailbox migration, but my question is, "what is the reason of the MRSPROXY configuration?", because I did not do anything about it and the migration was succesful anyway.


    Cristian L Ruiz

    Wednesday, February 3, 2016 3:34 PM
  • Hi Cristian,

    When I started to prepare the Migration, I read a lot of documents and I could see It was necessary to active it for migrating mailboxes cross-forest.

    You have more information here:

    https://technet.microsoft.com/en-us/library/dn155787(v=exchg.150).aspx?f=255&mspperror=-2147217396

    Probably the migration of mailboxes are succesfully without activate it... but I did it.

    Wednesday, February 3, 2016 3:44 PM