Exchange 2007 to 2013 upgrade Outlook profile redirection

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.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Simon Butler (Sembee)ConsultantCommented:
"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.

Flexible_SystemsAuthor Commented:
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.
Gareth GudgerSolution ArchitectCommented:
What version of Outlook? Maybe it is this issue.

This references moving a mailbox from 10 to 13. But could be a similar problem.
Protecting & Securing Your Critical Data

Considering 93 percent of companies file for bankruptcy within 12 months of a disaster that blocked access to their data for 10 days or more, planning for the worst is just smart business. Learn how Acronis Backup integrates security at every stage

Flexible_SystemsAuthor Commented:
Outlook 2010. I did see this one. Thanks though
Gareth GudgerSolution ArchitectCommented:
What Service Pack is your Exchange 2007 box on?
Flexible_SystemsAuthor Commented:
Service Pack 3, latest rollup
Simon Butler (Sembee)ConsultantCommented:
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?

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.
Flexible_SystemsAuthor Commented:
So it seems that it works on some and not others. I wound up manually recreating the profiles for those that didn't work.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Gareth GudgerSolution ArchitectCommented:
Hey Flex,

Can you add a comment to detail what you did. That way others with the same problem can benefit from your experience.
Flexible_SystemsAuthor Commented:
I resolved the issue myself
Flexible_SystemsAuthor Commented:
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.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.