ohmErnie
asked on
Certificate question regarding Exchange 2007 and 2013 Coexistence
I understand that for coexistance, I need the following host names:
mail.mydomain.com
autodiscover.mydomain.com
legacy.mydomain.com
Currently for our Exchange 2007, clients apps connect to a host name called outlook.mydomain.com.
Do I use this same name in place of mail.domain.com? If so, what would the name for legacy.mydomain.com?
Or does the legacy.mydomain.com become replaced by outlook.mydomain.com and a new host name is chosen for mail.mydomain.com.
Long term, I would like to keep outlook.mydomain.com since all my client apps currently point to it and I dont want to have to reconfigure them.
Also, do I apply this new certificate to both my 2013 server and replace the current cert on my 2007 with this one as well?
mail.mydomain.com
autodiscover.mydomain.com
legacy.mydomain.com
Currently for our Exchange 2007, clients apps connect to a host name called outlook.mydomain.com.
Do I use this same name in place of mail.domain.com? If so, what would the name for legacy.mydomain.com?
Or does the legacy.mydomain.com become replaced by outlook.mydomain.com and a new host name is chosen for mail.mydomain.com.
Long term, I would like to keep outlook.mydomain.com since all my client apps currently point to it and I dont want to have to reconfigure them.
Also, do I apply this new certificate to both my 2013 server and replace the current cert on my 2007 with this one as well?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
If I want to start using mail.domain.com now instead of outlook.domain.com, what do I need to do for coexistence? Create a new cert on 2007 for that will include...???
mail.domain.com
autodiscover.domain.com
internalserver.domain.loca
2013 Cert:
mail.domain.com
autodiscover.domain.com
legacy.domain.com
I assume any mobile device or app that connects to outlook.domain.com will need to reconfigured for mail.domain.com?
I am trying to make this upgrade as seamless as possible so the end user does not need to do anything so am hesitant to change the host name from outlook to mail. Not sure why it was ever setup this way to begin with.
mail.domain.com
autodiscover.domain.com
internalserver.domain.loca
2013 Cert:
mail.domain.com
autodiscover.domain.com
legacy.domain.com
I assume any mobile device or app that connects to outlook.domain.com will need to reconfigured for mail.domain.com?
I am trying to make this upgrade as seamless as possible so the end user does not need to do anything so am hesitant to change the host name from outlook to mail. Not sure why it was ever setup this way to begin with.
Then allow Exchange to sort out what is redirected and what is sent over the proxy.
Thus on Exchange 2007 you would configure the legacy host name, legacy.example.com is the standard one used, but you can use anything you like. Then Exchange will redirect the users who need access to Exchange 2007 to that host name instead.
Exchange 2013 will proxy Outlook Anywhere and ActiveSync, so both of those don't need an external URL or the legacy host name configured.
While you could start using mail.example.com instead, you should still direct the existing host name to the new server so that everything is caught. Exchange will downgrade easily, it doesn't upgrade well, or even at all in some cases.
Simon.
Simon.