Have a read of this guide, I found it very helpful:
Migration | Exchange 2010 & PowerShell
We are in the mists of a domain rebuild to reflect our new combined school (and rid ourself of CC3)
Everything is hunky dory, except for working out the strategy with exchange.. I've read a lot on it and its still not too clear in my head.. The best way it seems is to move our exchange 2007 standard server on another to server upgrading it to 2010 but keeping it on the same domain, then migrating across to a exchange server 2010 in the new domain?
Where I get confused is the way the usernames link, i.e. if i admt the users over to our 2008 r2 domain, will they still link to the same mail boxes as they were linked to a different internal domain name? We are going to give the server we are putting exchange 2010 on the new domain the same IP details as our old one so we do not have to reconfigure MX records?
1. How may Forests do you have?
2. How many Exch Orgs do you have or plan on having?
As sukh asked, how many forests will be merging, and how many exchange orgs will you be merging. One thing you could do is have a DC and Exchange Server and have it replicate across your future network so each site has 1 domain/1 exchange. That works very very well in places I have been on contract
1 forest, 1 exchange org is what we have and will likely be the same when we rebuild domain
what do you mean rebuild the domain? Are you not doing a intra migration then?
Sounds like you're going to scrap everything and start again?
Probably the best way if they are amalgamating the sites into 1 domain forest structure
Also, you may have to update your MX records if your external IP is changing, and NAT address, but seems like youre keeping the same IP. Which I dont know how you can do without bringing Exch down therefore you will have downtime and users will receive NDR if you ISP can park messages for you.
There are currently 1 users browsing this thread. (0 members and 1 guests)