Quantcast
Channel: Exchange Server 2013 - Setup, Deployment, Updates, and Migration forum
Viewing all articles
Browse latest Browse all 7129

Exchange 2007 integration

$
0
0

I currently have Exchange 2007 installed for a small org of 30 users.

We don't use any external Exchange services.

We are going to upgrade to Exchange 2013 - again, we won't use any external Exchange services.

In 2007 we use the default Exchange cert which uses the internal server name in the cert maile2k7.test.com

If I install Exchange 2013 I know the default URLs will point to the new server name maile2k13.test.com - this is ok.

Again, I will use the default Exchange cert that is installed with 2013 - this is ok.

My concern is that clients will automatically try and connect to the newer 2013 CAS before they are migrated...is this correct? If so...see my concerns below:

  1. 2013 CAS will redirect requests to 2007 automatically - true?
  2. Will users get an Outlook certificate popup as soon as Exchange 2013 is installed (as they will directed to new CAS?)   

a.) Can I fix this by pointing all Exchange 2013 URLs (autodiscover SCP, EWS etc.) to Exchange 2007 in the meantime?

b.) Can I fix this by just installing the Exchange 2013 certificate on all clients in advance.

c.) I will also have to add the new CAS server into proxy exceptions.

Note: I am not considering a 3rd party SSL (I know it is cheap!) - so no need to suggest it nor legacy namespace etc.

Any other considerations to think about?



Viewing all articles
Browse latest Browse all 7129

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>