Exchange 2007 - 2013 Transition OWA

Hi everybody,

We are in a lab testing the Exchange 2013 coexistence with Exchange 2007.

We have one Exchange 2007 and three Exchange 2013 (one DAG).

After the Exchange 2013 installation we have some mailboxes in Exchange 2007 and some mailboxes in Exchange 2013.

All seems be fine with outlook client. But OWA is not working, so when we connect to Exchange 2013 Server we cannot to access to mailboxes in Exchange 2007. This is normal.

Then, we added the A registry with legacy name (for the Exchange 2007) in DNS and it doesn't work.

The question is...we need a certificate with legacy name for Exchange 2007 or can we update to CU2 and then we don't need any more?

Thanks in advance.

Best Regards. 

September 2nd, 2013 5:48am

You must have legacy namespace created for your Exchange 2007 resources. Also, you must have certificate issued for legacy DNS name, and that certificate should be on your Exchange Server 2007.

CU2 does not eliminate the need for legacy namespace in scenario when Exchange 2007 is migrated to 2013.

Free Windows Admin Tool Kit Click here and download it now
September 2nd, 2013 7:55am

Hello,

Thank you for your response

Now i  have legacy namespace created, and a certificate for legacy name.

But when i try to go to a mailbox in exchange 2007 i have the error: internet explorer cannot display the webpage.

I can see https://mail.mydomain.com/owa/auth/owaauth.dll

I hoped https://legacy.mydomain.com/owa/auth/owaauth.dll but seems like if the redirecction is not working.

Do you know what could be the problem?

Thanks in advance.

September 2nd, 2013 1:51pm

Hi,

Finally i get it!!! the solution is:

1. The DNS Host Name legacy.domain.com pointing to Exchange 2007

2. The certificate with de name legacy.domain.com in Exchange 2007.

3. after all i needed set the correct Urls in the diferents virtual directories in Exchange 2007.

4. The certificate in Exchange 2013 is the same that i had in Exchange 2007 i imported it.

Now all its OK.

Thank you

Set-OwaVirtualDirectory -identity E2010_CAS_NAME\OWA (Default Web Site) internalUrl https://owa.new.com/owa ExternalUrl https://owa.new.com/owa -FormsAuthentication $True -BasicAuthentication $True

Set-ECPVirtualDirectory -Identity E2010_CAS_NAME\ECP (Default Web Site) -InternalURL https://owa.new.com/ecp -ExternalURL https://owa.new.com/ecp -FormsAuthentication $True -BasicAuthentication $True

Set-Webservicesvirtualdirectory -identity E2010_CAS_NAME\EWS (Default Web Site) -InternalURL https://owa.new.com/ews/exchange.asmx -externalUrl https://owa.new.com/ews/exchange.asmx -WindowsAuthentication $True -BasicAuthentication $True

Set-Activesyncvirtualdirectory -identity E2010_CAS_NAME\Microsoft-server-activesync (Default Web Site) -InternalURL https://owa.new.com/Microsoft-server-activesync -externalUrl https://owa.new.com/Microsoft-server-activesync -BasicAuthEnabled $True

Set-OABVirtualDirectory -Identity E2010_CAS_NAME\OAB (Default Web Site) -InternalURL https://owa.new.com/oab -ExternalURL https://owa.new.com/oab -WindowsAuthentication $True -BasicAuthentication $True -RequireSSL $True

Set-ClientAccessServer -Identity E2010_CAS_NAME -AutoDiscoverServiceInternalUri https://owa.new.com/Autodiscover/Autodiscover.xml

Free Windows Admin Tool Kit Click here and download it now
September 3rd, 2013 4:26pm

Hi,

Thanks for sharing the solution with us.

It's  really appreciated.

Thanks,

Angela Shi

September 3rd, 2013 9:42pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics