Exchange 2007 to 2010 migration TEST before moving namespace over to 2010
-
Wednesday, June 27, 2012 4:53 PM
Hello
My client is doing a migration from Exchange 2007 sp2 to Exchange 2010 sp2. The client wants to perform a test in the current production environment regarding moving the primary namespaces over to the 2010 side, without effecting or interrupting users on the 2007 side, (no mailboxes have been moved over to 2010 yet) Please let me know if this is possible to do without effecting users on the 2007 side? I personaly dont think it is because inorder for Exchange 2010 to proxy ActiveSync connections to the 2007 side we would need to change externalurl to "null" doing this would cause a problem for activesync users, OWA might work because we are doing a redirect from 2010 to 2007, but not sure if Outlook Anywhere would work, because requirement of the outlook anywhere clients having to connect to the name thats configured as the principal name in the cert. For this test I would have to create new urls on the 2010 side, configure a new CERT and import into the 2010 side. Mailboxes that are still on the 2007 side currently point to Mail.domain.com. So even if i got a new cert imported into the 2010 side created DNS records for Mail1.domain.com, all the 2007 OA clients are pointing to Mail.domain.com so again i dont think its a good test.
Thanks for any assistance
Bulls on Parade
All Replies
-
Wednesday, June 27, 2012 5:07 PM
In general, you can test the Exchange 2010 CAS before going into production by using hosts file entreis. However, it's a bit hard to test ActiveSync because you can't exactly create a hosts file on the mobile device, so you might have to make some brief service interruptions to ActiveSync to test it properly.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
- Marked As Answer by Evan LiuModerator Friday, July 06, 2012 9:44 AM
-
Wednesday, June 27, 2012 5:25 PM
I agree with the ActiveSync part, however creating host files on the client i dont think will work either, if i pointed a client to the 2010 side "Mail.domain.com" by editing a host file. The client will hit the 2010 CAS server, but then the 2010 CAS server is either going to do a redirect or a proxy to the 2007 side, and in order for this to work i would need to modify the externalurl on the 2007 side for OWA. I cant do that cause it will interfer with production. Doesnt appear to be a good way to test
Bulls on Parade
-
Thursday, June 28, 2012 4:20 AMYou can test by assigning the legacy name to the Exchange 2010 server to start and verify that redirection works the way you expect, except in reverse. When you're satisfied that everything is going to work, swap all the URLs and NAT configuration.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
.png)
