Migration with new domain 1

[markdmac]

I have a customer that is looking to upgrade from Exchange 2003 to Exchange 2007. Also upgrading from Windows 2003 to Windows 2007.

There are about 750 clients and this is a medical facility, so downtime is an issue.

My problem is that the customer want to migrate to a whole new AD. They want to change their domain name. The existing AD has some minor issues that I feel I could clean up, but they have made up their minds.

I'm currently testing in a virtual environment using images of their servers. I upgraded a DC in the old domain to 2008. The new domain currently consists of 4 servers. AD, 2 Exchange Mailboxes servers setup for CCR and a HUB/CAS Server. I've been trying in vain to setup federation between the domains using 2008.

The concern is that it will take a long time to export mailboxes via ExMerge and then import them into the Exchange 2007.

Can anyone suggest an alternative? I'm wondering if it might even be possible to install an Exchange 2007 server in the old domain. Then move mailboxes to it. Could I then dismount the information store there and build the new domain to match that name and see if I can somehow mount that store?

I'm totally grasping at straws here, my brain has turned to pudding. Any suggestions or links to a clear walkthrough to setup federation for the scenario I am in would be greatly appreciated.

 

[ntinlin]

Hi Mark,

Ignoring Federation the safest (and most expensive way) would be with Quest Exchange migrator.
That way you could also run in tandem with no down time.

Neill

 

[58sniper]

Exporting via pst can be troublesome, since you'll lose LegacyDN. And that will make replying to previous email from coworkers difficult.

A trust w/ ADMT is still the best way.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[markdmac]

Thanks guys, the legacyDN issue is not a problem for me, I have a script that sets that.

I'll check out the Quest tool Neil. Do you happen to know the cost? The customer is a non-profit.

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at

http://www.thespidersparlor.com/vbscript

Work SMARTER not HARDER. The Spider's Parlor's Admin Script Pack is a collection of Administrative scripts designed to make IT Administration easier! Save time, get more work done, get the Admin Script Pack.

 

[markdmac]

Neil tht Qwest tool seems to only be for migrating from Exchange 5.5, can you confirm it will work to migrate from 2003 to 2007 and allow cross forest syncronization?

If you can provide clear steps to use Federation I'd be more than happy to give that a try again. I wasn't able to find any clear walk-throughs for this situation.

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at

http://www.thespidersparlor.com/vbscript

Work SMARTER not HARDER. The Spider's Parlor's Admin Script Pack is a collection of Administrative scripts designed to make IT Administration easier! Save time, get more work done, get the Admin Script Pack.

 

[markdmac]

After a review of the quick start guide it looks like the Qwest tool won't work.



I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at

http://www.thespidersparlor.com/vbscript

Work SMARTER not HARDER. The Spider's Parlor's Admin Script Pack is a collection of Administrative scripts designed to make IT Administration easier! Save time, get more work done, get the Admin Script Pack.

 

[theravager]

You can rename a domain fairly easily these days

 

[58sniper]

True, but that has to be completely pre-Exchange 2007. As, as Mark mentioned, the customer is determined to move to a new domain.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[markdmac]

I am wondering if I can perhaps do the following.

1. Add an x64 server to the old environment. Then add an Exchange 2007 server into the Exchange site.
2. Move users to the Exchange 2007 server.
3. Dismount the mailbox store.
4. Move the mailbox database to the new environment.
5. Use the following link to mount the database in the new environment?

http://technet.microsoft.com/en-us/library/aa998340.aspx

With the above I am assuming I'll already have migrated user accounts with ADMT.

Is this even possible?

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at

http://www.thespidersparlor.com/vbscript

Work SMARTER not HARDER. The Spider's Parlor's Admin Script Pack is a collection of Administrative scripts designed to make IT Administration easier! Save time, get more work done, get the Admin Script Pack.

 

[ShackDaddy]

Mark, as you probably know already, database portability is something that only works within the same Exchange org, not in a cross-forest migration. What solution did you come up with for this client? Direct trust and ADMT, then move-mailbox?

Dave Shackelford
ThirdTier.net