Solved

Exchange 2007 to 2013 upgrade Outlook profile redirection

Posted on 2014-09-28
12
534 Views
Last Modified: 2014-10-06
I have a single Exchange 2007 server running all roles. This weekend I migrated to Exchange 2013 running all roles. Everything seems to be working fine except the Outlook profile is not updating. When I launch Outlook it says the folders are unavailable and when I check the profile settings, it's pointing to the Exchange 2007 server. I have set autodiscover to point to the Exchange 2013 server and if I kill the profile and recreate it connect to the Exchange 2013 server with no issue. I really don't want to have to run around tomorrow to 60 users and redo profiles. I've been researching this for hours and have found nothing that works. I have tried deleting the DNS record for the old server and shutting off the old server. The users are connected via MAPI, not RPC over HTTP. From what i've read MAPI should just redirect.
0
Comment
Question by:Flexible_Systems
  • 6
  • 3
  • 2
  • +1
12 Comments
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 40348693
"The users are connected via MAPI, not RPC over HTTP"

Exchange 2013 the only option is Outlook Anywhere (RPC over HTTPS).
Does Autodiscover return the correct information? If you look at the clients, are the Outlook Anywhere settings being populated?

What exactly have you done to redirect Autodiscover? Remember it works differently internally to external.

Simon.
0
 

Author Comment

by:Flexible_Systems
ID: 40348840
When I say the users are connected by MAPI, mean to the Exchange 2007 server. If I look in the settings in Outlook on an existing profile pointing to Exchange 2007, they are not using Outlook Anywhere.

Keep in mind this if for internal clients. Autodiscover works fine. If i start with a fresh profile it pulls the right info, connects to Exchange 2013 and fills in the Outlook Anywhere. I have an internal DNS record that points autodiscover to the Exchange 2013 server. I have the internal autodiscover url pointing to the Exchange 2013 server on both the Exchage 2007 server and the Exchange 2013 server.

This is my first Exchange 2013 migration and I was under the impression that when Outlook tries to connect to the old server it would be redirected to the new server.
0
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 40348954
What version of Outlook? Maybe it is this issue.

This references moving a mailbox from 10 to 13. But could be a similar problem.
http://support.microsoft.com/kb/2934750
0
 

Author Comment

by:Flexible_Systems
ID: 40348963
Outlook 2010. I did see this one. Thanks though
0
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 40348973
What Service Pack is your Exchange 2007 box on?
0
 

Author Comment

by:Flexible_Systems
ID: 40348975
Service Pack 3, latest rollup
0
NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 40349546
You need to see what Autodiscover is returning to the clients. It should redirect to the new server automatically, for some reason it isn't, which would suggest that there is a problem with your implementation.

Did you run the Best Practises Analyser within Exchange 2007 before you started the migration?

Simon.
0
 
LVL 11

Expert Comment

by:hecgomrec
ID: 40349918
Once you finish the 2013 installation, did you made it your main server on your organization?

Firewall, DNS A and MX settings should be updated to point to the new server.
0
 

Accepted Solution

by:
Flexible_Systems earned 0 total points
ID: 40350262
So it seems that it works on some and not others. I wound up manually recreating the profiles for those that didn't work.
0
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 40350287
Hey Flex,

Can you add a comment to detail what you did. That way others with the same problem can benefit from your experience.
0
 

Author Closing Comment

by:Flexible_Systems
ID: 40361010
I resolved the issue myself
0
 

Author Comment

by:Flexible_Systems
ID: 40363971
I didn't really do anything. The redirection seemed to work fine for people running Windows 7 and Office 2010. Those on the terminal servers needed the profiles redone as Outlook at to be upgraded. All others the did not auto redirect were updated manually.
0

Featured Post

Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
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.

863 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

28 Experts available now in Live!

Get 1:1 Help Now