Solved

Exchange Transition "2007 SP2 to 2010 SP1"

Posted on 2011-09-27
12
217 Views
Last Modified: 2012-05-12
Scope of work: Transitioning a client from an Exchange 2007 to Exchange 2010. The Exchange environment consist of 2 Exchange 2007 SP2 servers as stated below and will be in a coexistence period. The Exchange servers will all reside in the same AD Site.

Server1:
CAS and HUB TRANSPORT
OWA: mail.clientdomain.com

Server2:
MAILBOX ROLE ONLY

I have spent several hours reading through all known MS KB articles and forums explaining how to place 2 2010 servers into coexistence, order the roles must be installed, legacy URL, etc The specific task I am most concerned with in the installation of the 2010 CAS and Hub Transport roles. From what i am reading most phones are not capable of CAS redirection and this client has over 130 EAS devices. So this has lead me to want to install the new 2010 CAS/HT using another External URL such as webmail.clientdomain.com instead of their existing mail.clientdomain.com.

What are everyone's thoughts about taking this route? How will autodiscover work internally and externally since i can only point the DNS records to 1 CAS server? What about all the Service Connection Point URLs, i assume each of them will point to their respective server. Does anyone have any real world experience with this that can point me in the right direction. All help is greatly appreciated.
0
Comment
Question by:bushido2006
  • 7
  • 5
12 Comments
 
LVL 49

Expert Comment

by:Akhater
ID: 36714756
You don't need the device to know CAS redirection, all you need to do is install you 2010 cas point the URL to it and remove the external URL form the 2007 cas, the 2010 cas will then proxy the request and not redirect it
0
 

Author Comment

by:bushido2006
ID: 36720474
Does this mean that all phones will contnue to work with the existing 2007 CAS/HT server without any intervention? How will the 2010 CAS/HT server proxy the request? I was not planning on changing any routing initially.

As far as autodiscover service, I assume this goes unmodified and contnues to point to the 2007 CAS/HT both internally and externally?

Sounds like i may need to read up more in regards to CAS Proxy as i still dont understand how they will coexist with 2 seperate external URL's
0
 
LVL 49

Accepted Solution

by:
Akhater earned 500 total points
ID: 36720502
You point the current external activesync url to 2010, you configure 2010 external url with the correct url, you remove the external url from your 2007 cas and 2010 cas will take care of the rest.

Once the 2010 is in place and configured autodiscover shoild point to 2010 cas not to 2007
0
 

Author Comment

by:bushido2006
ID: 36905919
Thanks fr the info, my concern is that all MS articles i can find don't refer to your method as an approach to transistiong from a CAS 2007 Server. It appears that i must configure the 2007 CAS with the legacy host name.

http://blogs.technet.com/b/exchange/archive/2009/11/20/3408856.aspx
http://technet.microsoft.com/en-us/library/dd351133.aspx

I am in the process of building a 2007 Exchange Server and will perform a test pilot migration to ensure that i have the correct steps down....guess i should have invested time to pilot this transition first before trying to do it in a live enviroment =). As soon as i have tested the transition i will report back how it went......
0
 
LVL 49

Expert Comment

by:Akhater
ID: 36906325
legacy hostname you talk about is valid only for owa not for activesync
0
 

Author Comment

by:bushido2006
ID: 36962266
okay just to confirm
install 2010 CAS and point the existing external URL to the 2010
remove the external URL from the 2007 cas
Disable Outlook Anywhere from 2007 CAS
Autodiscover and Mail.clientdomain.com point to 2010 CAS
2010 CAS will then proxy the request for all Active Sync connections
the legacy URL can be configured but only is used for OWA
0
Too many email signature changes to deal with?

Are you constantly being asked to update your organization's email signatures? Do they take up too much of your time? Wouldn't you love to be able to manage all signatures from one central location, easily design them and deploy them quickly to users. Well, you can!

 
LVL 49

Expert Comment

by:Akhater
ID: 36962479
install 2010 CAS and point the existing external URL to the 2010
  Yes
remove the external URL from the 2007 cas
  Yes on activesync that is
Disable Outlook Anywhere from 2007 CAS
   No why ?
Autodiscover and Mail.clientdomain.com point to 2010 CAS
   Yes
2010 CAS will then proxy the request for all Active Sync connections
   Yes
the legacy URL can be configured but only is used for OWA
  Yes and owa 2003 not 2007
0
 

Author Comment

by:bushido2006
ID: 36962904
Disable OutLook Anywhere on 2007 CAS??
Truthfully i dont have a good answer for this step, as I read through a co-existance guide and this was a step that was called for.

the legacy URL can be configured but only is used for OWA
So you are saying that if i dont have exchange 2003 mailboxes the legacy URL is not even required.  
0
 
LVL 49

Expert Comment

by:Akhater
ID: 36963058
Yes no needfir kegacy url if you dont have 2003
0
 

Assisted Solution

by:bushido2006
bushido2006 earned 0 total points
ID: 36996852
http://technet.microsoft.com/en-us/library/dd638158.aspx

AKhater i wanted to than you for responding to all my questions, but it does appear that you need the Legacy URL. I was able to complete a successful coexistance setup using the above URL from Technet and some other purchased deployment guides from the web. if you would like to see all the steps that i used i would be more than hapy to share just send me an email address.

I am still not sure why steps call for diabling CAS 2007 Outlook Anywhere. Everything worked EAS, OA, OWA...etc.
0
 

Author Closing Comment

by:bushido2006
ID: 37016651
http://technet.microsoft.com/en-us/library/dd638158.aspx

the above url in my opinion is lacking details but for the most part it has all the steps required to coexist the 2 environments
0
 

Author Comment

by:bushido2006
ID: 36996862
just trying to close out the ticket
0

Featured Post

How to improve team productivity

Quip adds documents, spreadsheets, and tasklists to your Slack experience
- Elevate ideas to Quip docs
- Share Quip docs in Slack
- Get notified of changes to your docs
- Available on iOS/Android/Desktop/Web
- Online/Offline

Join & Write a Comment

Resolve DNS query failed errors for Exchange
"Migrate" an SMTP relay receive connector to a new server using info from an old server.
In this video we show how to create an Address List in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Organization >> Ad…
how to add IIS SMTP to handle application/Scanner relays into office 365.

743 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now