I'm in my lab working out migration plans. I'm having troubles with understanding the whole "legacy" domain name thing. I thought I had it understood by I'm stumped.
Envirnment:
I have Exchange 2007 installed in a subdomain. I installed Exchange 2013 in the root domain. (We're talking about collapsing our environment so I'm setup for this scenario to test that.)
Right now I'm simply working on the Virtual Directories and trying to get the users from the subdomain, whom have mailboxes in 2007 to be able to login to the 2013 OWA interface.
In the instructions about the upgrade it goes over basically configuring the 2013 CAS to have the right URLS and then it mentions creating a hostname called legacy in DNS and pointing that to the 2007 instance. This way you can "flip" dns to the 2013 OWA.
I did this and for users in root domain where 2013 is installed they can get in. But I'd expect this since their MB's are already 2013. But the 2007 users never get past authentication.
Some of my thoughts are that the SSL keys are all messed up with 2007 since the legacy name isn't in the certificate. I really don't want to have to get new keys for the outgoing exchange server.
I think the documentation kind of drops the ball in this area. It mentions configuring Virtual Directories, goes over creating the legacy domain then stops short of explaining what to do with the legacy name. Uggg.
David Jenkins
