Cross Forest Exchange 2007 to Exchange 2010 Mailbox Move question

Status
Not open for further replies.
B

Baba 20009

We currently have two forest each has one domain with two way trust.

Source Domain = AD 2003 ; exchange 2007 SP3

Target Domain = AD 2008 ; exchange 2010 sp1

I am planning to install exchange 2010 in target domain and Move Mailboxes only. Users and Computers will need to remain in Source Domain. Not sure what it means when it says you have to create mail enabled users in target domain first.

If this is possible what are the steps I need to follow? I have setup a lab to duplicate the production.

Thanks
 
S

Sembee [MVP]

Not sure what isn't clear about having to create mail enabled users first. You will have to create user accounts, which are seen in Exchange. Simple as that.

Cross Forest migration is documented on Technet. If you don't get it correct, then it doesn't work fully automatically, so you should test it as much as possible. The main issue can be different aliases and account names. You need to get everything as similar as possible.

Simon.

Simon Butler, Exchange MVP
Blog | Exchange Resources
 
S

Sembee [MVP]

Yes.
You can't have a mailbox without an account. Mailbox = AD Account.

Simon

Simon Butler, Exchange MVP
Blog | Exchange Resources
 
B

Baba 20009

Thanks for reply Simon,

I recall in Exchange 2003 our AD accounts were in Domain A and our Exchange servers in Domain B. Although I am not sure if they were in different Forest or not.
 
S

Sembee [MVP]

There would be accounts somewhere in the same Forest as Exchange. There had to be.
If the forests were different then you would have accounts in both. Same forest, then one account would be fine.

Simon.

Simon Butler, Exchange MVP
Blog | Exchange Resources
 
G

Gen Lin

Hi,

You can just move the mailbox to exchange 2010 forest, and keep the user in Source Domain. Please refer the following steps:

Step 1. You have target.com and source.com(Separate Forests) and there is a forest trust between them.

Step 2. On exchange 2010 server, run the following commands to prepare Move request:

$Remote=get-credential

Please type in the administrator account in the resource domain.

$Local=get-credential

Prepare-MoveRequest.Ps1 -Identity user1@sourcedomain.com -RemoteForestDomainController FQDN.Sourcedomain.com -RemoteForestCredential $Remote -LocalForestDomainController FQDN.Targetdomain.com -LocalForestCredential $Local -UseLocalObject -Verbose"

This command will create a AD user1 in your target domain and migrate some attribute from the source object.

Step 3. Run the following command to move the mailbox:

New-MoveRequest -Identity " CN=user1,CN=Users,DC=targetDomain,DC=com" -TargetDatabase 'Your database' -remoteGlobalCatalog " FQDN.Sourcedomain.com " -remoteCredential $remote -TargetDeliveryDomain 'targetdomain.com' -RemoteLegacy

Step 4. If you successfully move the mailbox, you will see the mailbox under EMC\Recipient Configuration\Mailbox. Then disconnect the mailbox from the AD user that created in step 2.
Disable-Mailbox -Identity User1

Step 5. Then link the mailbox in exchange 2010 to the user in your source forest:

$cred = Get-Credential

You will be prompted for credentials. Specify an account that has permissions to access the domain controller in the forest where the user account resides. Use the LinkedDomainController parameter to specify the domain controller. This domain controller obtains security information for the account to which you are linking the mailbox object.

To reconnect the mailbox object in the Exchange store to an external user object, use this example.

Connect-Mailbox -Identity User1 -Database " Mailbox Database" -LinkedDomainController FQDN.Sourcedomain.com -LinkedMasterAccount user1@sourceDomain.com -LinkedCredential $cred


Please type in the administrator account in the target domain.2. On exchange 2010 server, run the following commands to prepare Move request:
 
B

Baba 20009

Thanks Gen. I have couple more steps to do to setup the environment. I will test the steps and update.
 
B

Baba 20009

Gen,

I was able to run all the steps successfully except the last one:

Connect-Mailbox -Identity User1 -Database " Mailbox Database" -LinkedDomainController FQDN.Sourcedomain.com -LinkedMasterAccount user1@sourceDomain.com -LinkedCredential $cred

my exact command was:

Connect-Mailbox -Identity Test1 -Database " MDB-1" -LinkedDomainController labdc.labdallas.local -LinkedMasterAccount test1@labdallas.local -LinkedCredential $cred

i might add

source user location ou\users = Test Users\Test1

target user location ou\users = Users\Test1
 
G

Gen Lin

Hi,

What error you got after runnning the command:

Connect-Mailbox -Identity Test1 -Database " MDB-1" -LinkedDomainController labdc.labdallas.local -LinkedMasterAccount test1@labdallas.local -LinkedCredential $cred



 
B

Baba 20009

Hi Gen, here is the error:

A positional parameter cannot be found that accepts argument '-LinkedDomainController LabDC'.
+ CategoryInfo : InvalidArgument: :)) [Connect-Mailbox], ParameterBindingException
+ FullyQualifiedErrorId : PositionalParameterNotFound, Connect-Mailbox
 
G

Gen Lin

Hi,

Are you running the Mailboxes in DAG?

Please use the FQND of the DC for the parameter '-LinkedDomainController, also make sure that:

1. You are able to resolve the name of " labdc.labdallas.local.

2. The AD user Test1 is disabled. Please open ADUC to check it.

Connect-Mailbox -Identity Test1 -Database " MDB-1" -LinkedDomainController " labdc.labdallas.local" -LinkedMasterAccount test1@labdallas.local -LinkedCredential $cred

If the issue persists, please try the following steps:

1. Create a mailbox user Test2 in target domain (exchange 2010). Then disconnect the mailbox from the AD user by the disable-mailbox command.

2. Open ADUC, disable the user test2.

2. Run the following command to link this normal mailbox to the user in your source domain:

Connect-Mailbox -Identity Test2 -Database " MDB-1" -LinkedDomainController " labdc.labdallas.local" -LinkedMasterAccount xxx@labdallas.local -LinkedCredential $cred

What's result?


 
B

Baba 20009

Answering your questions:

1. You are able to resolve the name of " labdc.labdallas.local. YES

2. The AD user Test1 is disabled. Please open ADUC to check it. YES

Connect-Mailbox -Identity Test1 -Database " MDB-1" -LinkedDomainController " labdc.labdallas.local" -LinkedMasterAccount test1@labdallas.local -LinkedCredential $cred

STILL THE SAME

If the issue persists, please try the following steps:

1. Create a mailbox user Test2 in target domain (exchange 2010). Then disconnect the mailbox from the AD user by the disable-mailbox command.

DONE

2. Open ADUC, disable the user test2.

DONE

2. Run the following command to link this normal mailbox to the user in your source domain:

Connect-Mailbox -Identity Test2 -Database " MDB-1" -LinkedDomainController labdc.labdallas.local -LinkedMasterAccount test1@labdallas.local -LinkedCredential $cred

Still the same error

I am rebooting all servers. if that does not do it, I will re-install 2010 server with no DAG.
 
G

Gen Lin

Hi,

How troubleshoot is going on?

I tested the command in exchange 2010 dag, it also worked without problem. I think the problem may be in the name of your database. Please create a new database, and named it MDB2 (Do not use MDB-2).


 
B

Baba 20009

I took the DAG out, tried to uninstall and reinstall exchange 2010 but were not successful. So will continue the new Database and update you.

Thanks for reply.
 
B

Baba 20009

Hi Gen,

I setup a a new user / mailbox in the source, and a new Database in target MB1 and still get the same error during step 5.

I have couple questions:

1- Would you happen to have the shell commands to move several users from a text file?

2- when would I use Microsoft Identity Lifecycle Manger (or Forefront Identity Manager), before the mailbox move or after to sync the Gal.

3- Is it still necessary to install exchange 2007 before installing exchange 2010 in Target forest if we have plenty outlook 2003 users?

Thanks
 
Status
Not open for further replies.
Thread starter Similar threads Forum Replies Date
W installing exchange 2010 with multiple forest (Cross-forest) Exchange Server Administration 2
R Migrate Exchange 2003 to Exchange 2007 Cross-Forest Exchange Server Administration 4
N Cross Forest Mail routing from Exchange 2003 to Exchange 2010 Exchange Server Administration 3
S Cross Forest Migration from 2003 SBS to Exchange 2010 Exchange Server Administration 2
B Exchange Availabilty - Cross-Forest/Trusted - Calendar Permissions Using Outlook 3
J Cross Forest Coexistence routing Exchange 2007 and Exchange 2010 with a shared namespace Exchange Server Administration 3
E Exchange 2003 Cross-Forest Migration to Exchange 2010 - Outlook? Exchange Server Administration 7
C Exchange 2010 Cross-Forest Administration Problems Exchange Server Administration 16
J Exchange 2007 to Exchange 2010 cross forest migration Exchange Server Administration 16
T Exchange 2010 Public Folder Migration Cross Forest Exchange Server Administration 11
A Exchange 2010 Move mailbox Cross Forest Exchange Server Administration 11
S Cross forest migration Forefront Identity Manager 2010 Exchange Server Administration 2
S Cross forest migration legacy namespace OWA Exchange Server Administration 2
M cross forest DAG for mailbox database replication Exchange Server Administration 3
2 moving mailbox cross forest Exchange Server Administration 14
S Federation: Share GAL in Cross-Forest Topology Exchange Server Administration 0
M Cross-Forest Availibility Service Exchange Server Administration 3
S Prevent Cross-Forest New-MoveRequest from deleting the source mailbox Exchange Server Administration 10
K Compacting mailboxes after cross-forest migration? Exchange Server Administration 4
F Re: Cross Forest Migration Issue Exchange Server Administration 9
F Cross Forest Migration Issue Exchange Server Administration 1
R Cross forest mailbox move fails 2003 - 2010 EMC Exchange Server Administration 6
M Cross forest mailbox move from Ex2003 to Ex2007 Exchange Server Administration 4
J Failed to find the address type 'SMTP:AMD64' during cross-forest mailbox move Exchange Server Administration 2
M Cross-Forest mailbox move and linked mailbox Exchange Server Administration 8
K Cross forest migration Ex2007 to Ex2010, Mailbox replication Service restart unexpectally Exchange Server Administration 8
F cross forest shared namespace mailbox move Exchange Server Administration 6
D Red cross Using Outlook 1
J Cross AD Site Free Busy / Availability Issue Exchange Server Administration 3
P Exchange 2010 SP1 Cross Site CAS connection disable Exchange Server Administration 2
S single DAG two AD sites cross site database failure Exchange Server Administration 3
C RBAC Cross Domain issues Exchange Server Administration 8
S cross post please read: Exchange Account password prompt in Outlook 2010 Using Outlook 2
B missing cross contact field in the bottom of the contact card Using Outlook 4
K Cross Subnet Client Access Array Exchange Server Administration 8
K Cross site DAG and CAS Exchange Server Administration 7
S Can a DAG Cross Site Bounderies Exchange Server Administration 1
S Re: Exchange 2010 Archive mailbox cross domain access Exchange Server Administration 1
T BLUE CIRCLE WITH A CROSS IN OUTLOOK BOX. Using Outlook 1
S NDR when sending cross-domain-mails from Office 2007 Exchange Server Administration 6
R Exchange 2010 CAS high availibility cross datacenters Exchange Server Administration 9
C Manage OWA access during the migration from Exchange 2003 to Exchange 2010 (Resource Forest) Exchange Server Administration 4
2 Moving Public Folders to Resource Forest Exchange Server Administration 2
2 Adding new mailboxes to resource forest setup? Exchange Server Administration 2
2 resource forest trust Exchange Server Administration 7
J Resource Forest Auto Outlook Setup Exchange Server Administration 5
J Change Scope to include Account Forest in EMC Exchange Server Administration 1
2 Decommissioning Exchange 2003 after creating Resource forest Exchange Server Administration 3
A Move mailbox from Exchange 2003 to Exchange 2010 but crossed different forest Exchange Server Administration 2
R Can I set categories forest/domain wide? Exchange Server Administration 1
Similar threads


















































Top