Outlook 2013 profile might not update after mailbox is moved to Exchange 2013


Update 3/18/2014: The fix for this issue has been released and is a part of March 11 2014 update for Outlook 2013. Please see the following KB article: http://support.microsoft.com/kb/2863911.

We wanted to make certain that Exchange admins are aware of an Outlook issue which may impact your plans to move to Exchange Server 2013. As discussed in KB:2934750, Outlook 2013 customers who deployed client updates released in November and December of last year may experience a profile migration error post mailbox migration. When this occurs, it might not be possible to use normal Profile Repair options to restore connectivity. Older versions of Outlook, including Outlook 2013 without the November and December updates will function normally. An Outlook update which resolves this issue is nearing completion and being worked with priority to be released as soon as possible. The Exchange team is working closely with the Outlook team to verify the fix.

The Exchange Team

Comments (31)
  1. Anonymous says:

    Just wanted to let you know that patch from March doesn’t work. Outlooks 2013 (latest version 15.0.4569.1504) continue to have problems reconfiguring connection settings after mailbox is moved from Exchange 2010 to 2013. It’s a mess guys, really. I would love concrete Outlook patch dates, because I’m stuck with transition.

  2. Anonymous says:

    This is really bad providing the impact of Nov and Dec Month Patch in the Month of Feb…Will this be impacted for the user mailbox moved from Ex2007 to Ex2013 ??

  3. Anonymous says:

    Thank you for this clarification. I just completed my company’s migration to Exchange 2013 and we had an unfortunate amount of desktop issues with the Outlook clients. It seemed to be hit or miss, as I could not find any connection between those people who were able to simply restart Outlook after the move with no issues, and those who had to take many extra steps to reconnect to their mailbox with Outlook. This might have been why. It became a huge strain for our Desktop Support team and had a negative impact on the move with those users who were affected. Hopefully this can be resolved with additional updates so others can have a smoother migration on the user front.

  4. Anonymous says:

    AmbersEd, I can’t find a document but yes, generally its considered a best practice to migrate linked mailboxes (delegated, shared, etc.) at the same time for better experience. I have responded to the issue that you have linked below from the forum. It is similar to a known issue that we’re investigating at this moment.

  5. Anonymous says:

    any update on this issue?

  6. Anonymous says:

    We have been experiencing this issue at about a 35% hands-on required rate for the last month. Profile repair has not resolved the issue for any instance thus far, however we can confirm that profile rebuilds resolve the issue about 90% of the time. Occasionally we have had to remove Outlook from Office 2013 and add it back, reboot and then everything works fine. I hadn’t bothered to escalate the issue as we were able to work through it.

    That being said, I am compelled to mention that we are also seeing anomalies with shared mailboxes moving to Exchange 2013. Is there a documented requirement that users and any shared mailboxes they have access to be migrated at the same time. Both issues appear to be related at this time for us. I have seen this question asked in the Office forums but haven’t seen and answer as of yet:

    http://social.technet.microsoft.com/Forums/office/en-US/fcb09527-3e88-4e71-9607-a11cb3f21913/outlook-does-not-update-connection-for-shared-mailboxes-after-migration?forum=outlook

    Can the details of the bug be elaborated upon while we wait for the fix?

  7. Anonymous says:

    Outlook 2013 profile might not update after mailbox is moved to Exchange 2013
    GOOOOOOOOOOOOOOOOD GOOOOOOOOOOOOOOOB
    THANKSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS

  8. Anonymous says:

    yay, thank you!

  9. Anonymous says:

    @intrepid, yes please see the note just added to the article at the very top. Thank you.

  10. Anonymous says:

    @Ilantz: No, Office/Outlook 2013 SP1 does not have the fix for this issue.

  11. Anonymous says:

    We are moving from Exchange 2007 to Office365 and I confirm we have a fair amount client problems also.
    When Moving a user a new calendar Folder is been created when the OS Language setting is different then English. Is this also part of this bug?

  12. Anonymous says:

    WOW, I did not expcet that from a big company as Microsoft !!!!

    Where were the “Testing” “Testins, and “Testing” before relaesing those patches!!!

  13. John E. says:

    More bugs? How – surprising. Not.

  14. Ilantz says:

    This came right in time for some upgrades at hand! Is this issue affects also customers moving to exchange online? are outlook 2010/2007 affected also?
    Thanks!

  15. @Ilantz – As indicated above, only Outlook 2013 clients who have applied the updates are affected. This does not affect Outlook 2007 or Outlook 2010. At this time this has not been reported by customers migrating to Exchange Online.

    @Exchange Queries – The information was shared as soon as we became aware of the problem. While we have no examples of Exchange Server 2007 customers migrating to Exchange Server 2013 reporting this problem, the nature of the defect indicates Outlook 2013 clients migrating from Exchange Server 2007 to Exchange Server 2013 could also be impacted.

  16. Paul Glass says:

    IMHO, these ongoing issues with Exchange 2013 on-premise clearly demonstrate that MSFT is focusing all its development effort on the on-line O365 variant, with the end game of having on-line offerings only in the future….

  17. Mitchell Guthrie says:

    We are about to start pilot migrations this week from Exchange 2007 to Exchange 2013. The KB article only mentions Exchange 2010 to 2013, does this mean 2007 is not impacted by the problem?

  18. @Jan Aarts – What you describe is not related to the problem discussed in this post. This post only refers to an Outlook defect which prevents profile migration from completing blocking access to the entire mailbox.

    @Mitchell Guthrie – Please see my previous response on migrations involving Exchange Server 2007.

  19. Providing an update on this post. The Outlook development team has confirmed that they will be releasing a Product Update in March via Microsoft Update which resolves the issue identified in http://support.microsoft.com/kb/2934750. The fix will also be available to customers who contact support on this issue.

  20. Ilantz says:

    Thanks for the update!
    Does office 2013 sp1 already contains the fix?

  21. pesos says:

    Brent, will this fix be coming with the regularly scheduled patches on Tuesday March 11?

  22. Gerhard Bechter says:

    Installed the Update for this issue, but the same Problem….

  23. John Kraus says:

    We have the same issue on a Windows 2008 R2 terminal server farm with over a hundred users now getting this popup The Exchange administrator has made a change that requires you to quit and restart Outlook .We are using Exchange 2013 and office 2013. They can continue to work after clicking OK but this message is so annoying. I have ran all updates even office SP1 with no resolve. I have deleted profile and recreated them in outlook. Please Microsoft Fix this issue.

  24. Radek says:

    Hi,
    we’ve applied the fix and it helped indeed, Outlook now connects to Exchange 2013 without any problem but at the same time the Outlook (2013 SP1) is re-downloading all user’s mailbox locally even-though the cache was there before fully downloaded. Is that normal? And why if it is?
    Thanks.

  25. AlanD says:

    I just tested several mailbox migrations from 2010 to 2013 using Outlook 2013 with this 2863911 patch and all my tests failed. Same disconnected mailbox post migration. Tests with and without cached mode both failed.

    FYI my Office installation is 32bit with Office 2013 SP1 and this recent 2683911 update.

    My 3000 mailbox migration is on hold until I find a resolution to this. I’m curious to hear if anyone got the migration to work using this update?

  26. AlanD says:

    Has anyone tested and got the new KB2863911 to work?

  27. Doug says:

    The file information in the KB article makes it seem like there were no changes…versions and sizes appear to be the same? I didn’t compare every single file but wonder if you can identify the specific change that occurs on the client when this update is installed. Thanks.

  28. sog says:

    When can we expect patch for most current 32 bit Outlook 2013 (version 15.0.4569.1506), because patch from 18th March doesn’t solve the issue? I’m in the middle of transition from Exchange 2010 to 2013 and now I have a choice: leave mailboxes on Exchange 2010 (stupid idea since I want to get rid of EX2010) or move them to Exchange 2013 and go to every Outlook 2013 client and manually repair a profile providing EX2013 CAS FQDN server in every Outlook 2013. Do I have to add that second way is extremely time consuming and problematic?!

  29. JanZ says:

    Just as with Sog: the update doesn’t work. Same problems. Creatging a new profile fixes everything, but my users don’t like it and I don’t like it.

  30. IT says:

    The update worked for our Exchange environment.

    We had experienced this issue with approximately 50% of our users (nearly 80% of our Outlook 2013 users) during a pilot in late February. When the March 11 patch was released, we deployed and migrated our entire environment (after testing). We had almost no instances of the Outlook 2013 bug mentioned above following the organization-wide migration.

  31. Anand Sunk says:

    Currently I am facing issues with outlook 2013 not showing Shared Calendar of Exchange 2007 mailbox after applying update of SP1 for outlook 2013. But when I log into the OWA it’s showing there can you tell us what could be the reason?

    Before applying the SP1 for outlook 2013 everything was working fine.

    Please let me know.

    Regards
    Anand S

Comments are closed.