Solved

Transitiong exchange 2007 to Exchange 2010 after updating the other servers before internet facing server

Posted on 2014-12-10
17
65 Views
Last Modified: 2015-01-24
I have our main internet facing cas 2007 at our main sight. I had to add exchange 2010 servers to a couple of new facilities in remote sights but they are all connected. I'm now transitioning  our last,  but main 2007 exchange to a new box with exch 2010 (all 2008r2 OS).  I was fallowing  the articles to make the 2007 legacy.domain.com to work with exch 2010and then realized that won't work because I needed to upgrade this server first before the others.  I had already changed everything on 2007 to legacy.domain .com and the new 2010 to mail.domain.com.  Email seems to be working fine on the new server and I believe I can move everyone over to the new server that does not access email remotely ( smartphones, owa, etc) I assume then after movng all users over then  I just need to move all the remote users at the same time and change the ip to that of the old server and send connectors?  Am I missing anything.  Right now I have various users still on the old exch 07 getting the whole pop up box to log in to email, (mail.domain.com) so I'm guessing outlook anywhere is not configured correctly as all their outlooks are set to "connect using http" or the fact that I changed it to legacy.domain.com. Usually I just have to change their authentication to ntlm and they work okay.
0
Comment
Question by:jtano
  • 9
  • 8
17 Comments
 
LVL 7

Expert Comment

by:Satyendra Sharma
ID: 40491379
Well seems like you kinda started backwards, always upgrade your CAS boxes first because they are backward compatible with older mailbox servers and can proxy/redirect connection depending on the environment.

Instead of moving non remote accessing users over to 2010, I would recommend to focus on replacing your 2007 server with 2010 for internet facing services and let exchange 2010 proxy/redirect the request and than you can move the mailboxes after the fact without worrying about who remotely accesses and who doesn't.

Read the - Transitioning an Exchange 2007 environment to Exchange 2010 section from below article thoroughly and follow the steps.
http://blogs.technet.com/b/exchange/archive/2009/11/20/3408856.aspx
0
 

Author Comment

by:jtano
ID: 40492260
yes. I am backwards because they bought a new facility last minute and wanted an exchange server asap. that being said is it still going to work correctly because this warns that internet facing needs updated first and its too late for that?  First question is. Do I have to do the cas array? 2nd question. I have changed all the exch 07 directories to legacy.domain.com and new 2010 to mail.domain.com ( what old exch used to be) Is that correct?  I am following the directions in the article as I get time. Just checking on those things first. Thanks
0
 
LVL 7

Expert Comment

by:Satyendra Sharma
ID: 40492472
For cas array it depends if you need to have redundancy for your exchange environment, are these dedicated CAS servers or all-in-one box?

So if you have already changed all your 2007 url's to legacy.domain.com have you also changed it on the internet facing CAS servers? What is the url published on the internet legacy.domain.com or mail.domain.com?
0
 

Author Comment

by:jtano
ID: 40493024
So I don't need redundancy and can not worry about the cas array for now.  These are all in one box. Don't use Edge transport either.  Yes, its changed on the internet cas server to legacy.domain.com.  mail.domain.com is the url published on the internet.
0
 
LVL 7

Expert Comment

by:Satyendra Sharma
ID: 40494662
Is this server also responsible for the internet email flow?
0
 

Author Comment

by:jtano
ID: 40494744
Yes, This 2007 exchange is
0
 
LVL 7

Assisted Solution

by:Satyendra Sharma
Satyendra Sharma earned 250 total points
ID: 40494939
Man you have bunch of things to consider for this cutover, here are the steps I can think of top of my head.

- Set all the external url's on 2010 server to mail.domain.com (same for internal if split dns)
- Set all the external url's on 2007 server to $null and internal url to legacy.domain.com
- Point your internal autodiscover to 2010 if deployed
- Point your external dns records for mail and autodiscover to 2010 box
- Make sure email flow works properly between 2007 and 2010 environment
- Create send connectors for outbound email flow on 2010
- Delete send connectors on 2007
- Enable anonymous permission on the receive connector on 2010 (if the box receives directly from internet)
- Update the MX record in the public DNS to point to 2010 box (if the box receives email directly from internet)
- Update the SPF record to include the new outbound connecting ip if it is changing

Here are some more articles for you to read:
http://technet.microsoft.com/en-us/library/bb738138(v=exchg.141).aspx
http://technet.microsoft.com/en-us/library/gg232715(v=exchg.141).aspx
http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
0
 

Author Comment

by:jtano
ID: 40495353
I have followed so many different routes on how to do this,,,I'm lost. The last article sounds promising, but I have no idea how to do this:  
2.Create a publishing rule for the legacy host name in your reverse proxy or firewall solution to point to your legacy Internet-facing Exchange server. Refer to your proxy/firewall solution's user manual for instructions for how to do this. Nor can I find anything helpful for directions.
  I was considering using Microsoft but it looks like they raised their price from $250 to $499.  
So, I'm guessing the best thing to do is just move all users to 2010 at one time and change the ip to be that of the 07 server, fix send connector.
0
Integrate social media with email signatures

Is your company active on social media? Do you also use email signatures? Including social media icons in your email signature is a great way to get fans for free. Let all your email users know you’re on social media quickly and easily, in a single click.

 
LVL 7

Expert Comment

by:Satyendra Sharma
ID: 40496493
The step you are talking about is only required if you want to do redirection for the external connection for exchange, the alternate is to set the external url on the 2007 servers to $null so that 2010 server will just proxy request instead of redirect and this way you won't have to publish legacy.domain.com on the internet.
0
 

Author Comment

by:jtano
ID: 40496998
At this point I just want to move everyone over to the new 2010 exch server and shut the 07 down. I have given up trying to make them coexist together and the random box that pops up asking for user name/password for our mail.domain.com. If anyone has a link that clearly shows the easiest path for that please let me know.  Thanks
0
 
LVL 7

Expert Comment

by:Satyendra Sharma
ID: 40497301
You have to cutover all the externally exposed services over to 2010 and then you should move all the remaining mailboxes. I wish there was a magical article that includes everything that you want to do but you somewhat need to know what you are doing.
0
 

Accepted Solution

by:
jtano earned 0 total points
ID: 40505227
Thanks. Setting up a 2nd external ip on the firewall and external dns and pointing to new 2010 server fixed smartphone users. Still having problems with id/pass randomly popping up, but I will post that as a new question. Thanks for trying to help. I have never had these issues in the past transitioning over starting from exch 5.5. I don't know why this one was so difficult for me.
0
 
LVL 7

Expert Comment

by:Satyendra Sharma
ID: 40505389
So you have legacy and mail published on the external DNS now?
Is the external URL still set on the 2007 servers?

If answer to the above two questions is yes then you are doing URL redirection and not proxy.
0
 

Author Comment

by:jtano
ID: 40505414
Yes its still on 2007
0
 
LVL 7

Expert Comment

by:Satyendra Sharma
ID: 40505425
As I mentioned earlier there are basically two option proxy and redirection, most people normally go with proxy if they have only 1 internet facing side since the 2010 internet exposed server will proxy the request the request to the 2007 environment.
0
 

Author Comment

by:jtano
ID: 40505635
Proxy would have suited me better, but I just did what the MS guy told me to do.
0
 

Author Closing Comment

by:jtano
ID: 40567961
Had to set up a 2nd external ip address for the new server
0

Featured Post

Do email signature updates give you a headache?

Constantly trying to correctly format email signatures? Spending all of your time at every user’s desk to make updates? Want high-quality HTML signatures on all devices, including on mobiles and Macs? Then, let Exclaimer solve all your email signature problems today!

Join & Write a Comment

"Migrate" an SMTP relay receive connector to a new server using info from an old server.
Disabling the Directory Sync Service Account in Office 365 will stop directory synchronization from working.
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.

747 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

14 Experts available now in Live!

Get 1:1 Help Now