I_T_MAN
asked on
company acquisition.
We are about to make an acquisition of a company and would be interested in comments on a procedure to follow when looking at the migration. i.e. best practice to merge. We run already with large domain 10,000 users with a global footprint. What is best practice to migrate them into our domain based on the fact they currently have communications, Exchange, file and print, voip etc set up at 2 locations. What to do with old domain emails, files. How to handle old emails? How to handle VOIP migration. Just looking for general ideas based on experience and best approach.
I've been through this a few times. Step one create a two way trust.
ADMT allows you to migrate accounts between domains. You are either going to maintain two directories or integrate. ADMT makes it easy to move one domain to another including exchange.
ADMT allows you to migrate accounts between domains. You are either going to maintain two directories or integrate. ADMT makes it easy to move one domain to another including exchange.
ASKER
Aqquired company currently runs with:
50 Users
Exchange 2003 we run 2007 (migrating to 2010)
We use Cisco call manager they have a Mitel VOIP system
IT Support - we will support remotely to start (We have 38 IT Staff globally) then appoint local IT staff (Employed by us)
Their old computers will be migrated across to our domain
Servers the same as above
Their website will be redirected to ours
Old mail redirected
50 Users
Exchange 2003 we run 2007 (migrating to 2010)
We use Cisco call manager they have a Mitel VOIP system
IT Support - we will support remotely to start (We have 38 IT Staff globally) then appoint local IT staff (Employed by us)
Their old computers will be migrated across to our domain
Servers the same as above
Their website will be redirected to ours
Old mail redirected
It looks like you will prefer to continue having one domain and use a new OU (at least one) for the 50 users.
In this case, we are talking about Cross-Forest Mailbox Moves (a.k.a Remote mailbox move). Considering the fact that you are going to upgrade to Exchange 2010 (SP1 aleviated the process), you have to plan the different phases of the project very carefully.
You will create the two-way trust, as Dacasey suggests, but you have to keep in mind that ADMT migrates a limited set of attributes. Hence you have to use the Prepare-MoveRequest.ps1 script:
http://technet.microsoft.com/en-us/library/ee861103.aspx
Dean
In this case, we are talking about Cross-Forest Mailbox Moves (a.k.a Remote mailbox move). Considering the fact that you are going to upgrade to Exchange 2010 (SP1 aleviated the process), you have to plan the different phases of the project very carefully.
You will create the two-way trust, as Dacasey suggests, but you have to keep in mind that ADMT migrates a limited set of attributes. Hence you have to use the Prepare-MoveRequest.ps1 script:
http://technet.microsoft.com/en-us/library/ee861103.aspx
Dean
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The below script can help you.
http://msexchangehelp.wordpress.com/2010/03/23/gui-script-for-exchange-2003-to-exchange-2010-cross-forest-move-mailbox/
http://msexchangehelp.wordpress.com/2010/03/23/gui-script-for-exchange-2003-to-exchange-2010-cross-forest-move-mailbox/
ASKER
Great help any comment on voip
Are you talking about OCS or Exchange UML role?
I am afraid that the Awinish post is quite misleading - about the Mailbox migration.
Anyway, case closed.
Good Luck:)
Anyway, case closed.
Good Luck:)
There is no way you can migrate the mailbox using ADMT, it can be only through exchange Management Shell using move request, which i gave in another link.
http://technet.microsoft.com/en-us/library/ee861103.aspx
http://technet.microsoft.com/en-us/library/ee633491%28EXCHG.140%29.aspx
http://technet.microsoft.com/en-us/library/ee861103.aspx
http://technet.microsoft.com/en-us/library/ee633491%28EXCHG.140%29.aspx
Here is what you say, Awinish: "Exchange mailbox migration is not possible,exchange 2010 support with special consideration.
The option is migrate the user,take the mail into pst & you can import/export the mailbox."
That's quite different from using "Cross Forest Mailbox migration" (a.k.a. Remote Mailbox Move request).
And again, you are misleading: " it can be only through exchange Management Shell using move request"
Of course, it can be done in Exchange Management Console - you have two types of Mailbox Move reqquests in it - local and remote.
Dean
The option is migrate the user,take the mail into pst & you can import/export the mailbox."
That's quite different from using "Cross Forest Mailbox migration" (a.k.a. Remote Mailbox Move request).
And again, you are misleading: " it can be only through exchange Management Shell using move request"
Of course, it can be done in Exchange Management Console - you have two types of Mailbox Move reqquests in it - local and remote.
Dean
I forgot the weird statement:"exchange 2010 support with special consideration" :)
You can do Cross-forest mailbox migration with Exchange 2007, Exchange 2003 and even Exchange 5.5, Awinish.
Have fun.
Dean
You can do Cross-forest mailbox migration with Exchange 2007, Exchange 2003 and even Exchange 5.5, Awinish.
Have fun.
Dean
NetoMeter: I think, i didn't give enough time to express & i was considering only aspects of ADMT, i accept it i didn't give clear description & yes i would apologize for it.
I have seen issue migrating mailboxes using management Shell & you have to remove request manually after the move request has been completed from mailbox,but using powershell or script is much better.
I read in few posts,there is issue migrating mailboxes using management shell where few attributes go on missing, so i recommended go for shell.
NetoMeter: Thanks for pointing.
I have seen issue migrating mailboxes using management Shell & you have to remove request manually after the move request has been completed from mailbox,but using powershell or script is much better.
I read in few posts,there is issue migrating mailboxes using management shell where few attributes go on missing, so i recommended go for shell.
NetoMeter: Thanks for pointing.
That's really a huge topic, I T Man:)
There is a lot of politics, on the first place: do you want to centralize management or you would prefer to restrict access and leave the network management of the new company to the existing IT team?
Based on what I've seen, most probably you would prefer to keep the new company in a separate domain.
Using ADMT (Active Directory Migration Tool) is a suitable approach which will help you integrate the existing company into your network.
What version of Exchange are you using, and what is the Exchange version of the acquired company?
Are you using VOIP, and what kind of VOIP solution is in place in the new company?
How many users and what's the size of the Exchange DB-s? How fast is the connection between the two networks and are you considering implementing redundancy or CDP (continuous data protection)?
Are you or the new company preparing for AD or Exchange upgrade?
As I've said that's a huge topic and there are a lot of aspects involved in it.
Regards,
Dean