Online Archives in Outlook 2010 disappeared after Exchange 2010 SP3 upgrade

I have Exchange 2010 and noticed it has never been updated since having it in production for 3 years now. So I downloaded SP3 and installed it after hours. After the install was complete, rollups 5,6,7, showed up in Windows Update so I installed those too.
Before I did the upgrade to SP3, I had Online Archives visible on just my user account mailbox and have about 2 years worth of emails in there. Since the upgrade, it is no longer visible in my Outlook 2010. I have tried to fix to remove SELF and re add it
to the mailbox with no change to the issue. I have tried to disable Archive for my mailbox and re-add. Nothing. Don't really know what else to try. Any ideas?

Anyone?

Similar Messages

  • Missing online archive in Outlook, OK in OWA

    We have Exchange 2010 SP2 and Office 2010 Pro Plus clients.
    One user can't see his online archive in Outlook but can if he logs into OWA.
    I have recreated his Outlook profile, logged in as him on other computers and have the same problem.
    Would be grateful for any advise/ideas
    thanks

    Outlook 2010 which are licensed at the correct level natively support the online archive.
    http://office.microsoft.com/en-us/outlook-help/license-requirements-for-personal-archive-and-retention-policies-HA102576659.aspx
    Outlook 2007 did not initially and needed a hotfix. 
    Are you 100% that this is pro plus ? 
    And check the AutoD response for the additional XML at the bottom of the response for the additional mailbox.
    Cheers,
    Rhoderick
    Microsoft Senior Exchange PFE
    Blog:
    http://blogs.technet.com/rmilne 
    Twitter:   LinkedIn:
      Facebook:
      XING:
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • When printing a Lync Online Meeting from Outlook 2010, it prints out xml code?

    I have a couple of users that whenever they go to print out Lync 2010 Online Meetings from outlook 2010, it prints off a bunch of xml code and extra info (UCCCapabilities, UCInband, UCMeetingSetting, UCMeetingSent) all in XML.
    Any ideas why it would be doing this, and only affecting a couple of users?
    TAG

    The following fix worked in our Exchange 2010, Lync 2010, environment.
    Symptom
    In Outlook, when users are printing (or print previewing) Lync
    online meetings on shared calendars, an XML code is included in the printout.
    Cause
    When the shared calendar is opened, the folder is being
    reported as read-only despite the user having read-write permissions. The Lync
    add-in writes a property to the item (this succeeds) and then to the folder
    (this fails) so then the code is not run that would mark the property as the
    item as non-printable.
    Possible Resolution
    If the owner of the calendar creates an online meeting one time on their own calendar, this will
    result in the property being created in the calendar folder. Then when a
    delegate subsequently creates an online meeting on the calendar, the property
    will already be on the folder, so the Lync add-in will not try to add it. This
    avoids the error condition, and the property on the item will then be
    successfully flagged as non-printable.
    This worked for me. My user was a delegate for the managers mailbox. When she created an online Lync meeting on behalf of the manager, the meeting attendees would see the xml code in print preview as well as the printed document. The simple fix, as described
    above, was just to access the managers Outlook profile from the managers computer, and create and send out an online Lync meeting (to one or more recipients, shouldn't matter). That's it. Now when the delegate goes to create any new online Lync meeting on
    behalf of the manager, the visible code is no longer present. This works, as the description above says, because "the property will already be on the folder (after the manager creates an online Lync meeting on their own calendar), so the Lync add-in will
    not try to add it. This avoids the error condition."

  • Online Archives for Outlook 2013 do not appear in Outlook 2013 running on Terminal Server

    Hello,
    We are currently attempting to get our users away from using PST files and instead use the Personal Online Archive feature but have come across a problem
    Environment
    Windows 2008 R2 Remote Desktop Services (Terminal Server)
    Office 2013
    Citrix 6.5 XenApp
    So on the Exchange side I went through the steps of setting up my PST use as a guinea pig for testing.  I was able to setup the Archive database, enable archiving on my mailbox, and import my PST into the Archive database.  
    I then opened Outlook 2013 on my stand-alone PC and there was my Online Archive. Great!
    I then double checked and also saw it on the OWA site on the Exchange server.  Super!
    I finally logged into our RDS (Terminal) server and opened Outlook 2013 there.  But the Online archive was not there.  Hmmm..
    I did some researching and this article about Outlook 2010 suggested it was a permission issue:
    http://social.technet.microsoft.com/Forums/office/en-US/1e8d5d4b-e26b-4be6-b646-eb6e796c6295/exchange-2010-mail-archive-missing-in-outlook-2010-shows-in-owa?forum=outlook
    So I ran through those steps in Powershell but no change.
    I also don't think it's a licensing issue because the license I have on my stand-alone PC is the same volume license keys (MAK) as on my Terminal Server.
    Soo... I'm a bit stuck and was hoping for some help.  I can't proceed with migrating other PST files to the online archive until I get this resolved.
    Thanks

    Hi,
    In theory,
    Outlook reads the
    msExchDelegateLink attribute of the user in AD to display the additional mailbox (Online Archive folder).
    Since the standalone client can display the archive mailbox properly, it seems this attribute is available in AD. I suspect the issue locates on the way that the terminal
    clients access the server. I suggest we check whether the client has properly permission to connect to AD when accessing remotely.
    Thanks,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • After Exchange 2010 SP3 upgrade, UAG publised OWA is throwing a "You do not have permissions to view this folder or page" error

    Hi,
    We have an issue with our OWA page.  We are currently publishing OWA via UAG.
    We recently upgraded to Exchange 2010 SP3 and then SP3 Rollup7.  Since the upgrade, we are keep getting the following error after entering our credentials on the login page.  I've tried with every possible browser. 
    You do not have permissions to view this folder or page
    Strangely enough, the mobile phones are sending and receiving emails just fine, the phones use the same OWA link, so it's not an authentication issue, the phones login into the UAG servers with no issues.  I can see this on the Active Sessions screen
    on Web Monitor. 
    I've attempted to connect to the OWA by bypassing the UAG server, so putting in the local OWA address of one of my Exchange servers, it works... so the OWA page is up and running. 
    No error logs get generated on Web Monitor when we receive the permission error, I think this is because it's past authentication, it's on the Exchange layer. 
    Any insight would be helpful?  I'm assuming something changed on the Exchange side after the upgrade.
    Just in case, I've upgraded the UAG and TMG servers to the latest SP and Rollup packets.
    UAG > SP4
    TMG > SP2 Rollup 5

    I've found a solution; UAG requires Basic Authentication over OWA.  For some reason Integrated Windows Authentication got turned on after the SP3 upgrade.
    http://technet.microsoft.com/en-us/library/ee921443.aspx
    Turning Integrated Windows Authentication off via the Client Access OWA settings resolved the issue.  Though beware, you
    have do this on all your Client Access servers.  

  • Exchange 2010 SP3 upgrade on Windows Server Standard SP2

    I'm midway through the swing upgrade process of migrating from Exchange 2003 - Exchange 2010 to Exchange 2013.  Everything has gone smoothly between the Exchange 2003 and Exchange 2010 migration which I started two days ago.  it has been running
    great.  I am beginning the final stages of moving from the Exchange 2010 server to a new Exchange 2013 server, but it requires my Exchange 2010 server to be upgraded to SP3.  I am now trying to install Exchange Server 2013 SP3 Upgrade and I'm
    getting (3) Client Access Role Prerequisites errors.  Finding any of these HotFixes and patches is frustrating, because any link provided does not work.  It has gotten me nowhere.  Here is my Readiness Checks:
    Summary: 6 item(s). 5 succeeded, 1 failed.
    Elapsed time: 00:01:06
    Configuring Prerequisites
    Completed
    Elapsed Time: 00:00:00
    Organization Prerequisites
    Completed
    Elapsed Time: 00:00:08
    Languages Prerequisites
    Completed
    Elapsed Time: 00:00:02
    Hub Transport Role Prerequisites
    Completed
    Elapsed Time: 00:00:15
    Client Access Role Prerequisites
    Failed
    Error:
    Install hotfix Microsoft Knowledge Base article 982867 from http:// code.msdn.microsoft.com/KB982867.
    Click here for help... http:// technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex28883C&l=0&cl=cp
    Error:
    Install hotfix Microsoft Knowledge Base article 979917 from http:// code.msdn.microsoft.com/KB979917.
    Click here for help... http:// technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex28883C&l=0&cl=cp
    Error:
    This computer requires the update described in Microsoft Knowledge Base article KB977592 (http:// go.microsoft.com/fwlink/?LinkId=194843). Without this update, the Outlook Anywhere feature may work unreliably.
    Click here for help... http:// go.microsoft.com/fwlink/?linkid=30939&l=en&v=ExBPA.14&id=249bbd89-16b4-4efa-9b66-7ec87f90e44c
    Elapsed Time: 00:00:15
    Mailbox Role Prerequisites
    Completed
    Warning:
    Multi-mailbox search of on-premises and Office 365 mailboxes in a hybrid configuration requires installation of the update mentioned in Microsoft Knowledge Base article 982867 (http:// code.msdn.microsoft.com/KB982867).
    Elapsed Time: 00:00:24
    I put a space between the http://" space "URL so I could display the links.
    Any help/guidance suggestions would be greatly appreciated.
    Chris

    I just got these two to go away:
    Error:
    Install hotfix Microsoft Knowledge Base article 982867 from http:// code.msdn.microsoft.com/KB982867.
    Click here for help... http:// technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex28883C&l=0&cl=cp
    Error:
    This computer requires the update described in Microsoft Knowledge Base article KB977592 (http:// go.microsoft.com/fwlink/?LinkId=194843). Without this update, the Outlook Anywhere feature may work unreliably.
    Click here for help... http:// go.microsoft.com/fwlink/?linkid=30939&l=en&v=ExBPA.14&id=249bbd89-16b4-4efa-9b66-7ec87f90e44c
    still have this one outstanding:
    Error:
    Install hotfix Microsoft Knowledge Base article 979917 from http:// code.msdn.microsoft.com/KB979917.
    Click here for help... http:// technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex28883C&l=0&cl=cp
    I have tried the FIX: WCF services that are hosted by NLB computers to route messages to Exchange Server fail when WebHeader settings are added by using a .NET Framework 3.5 SP1 application
    Windows6.0-KB2637518-x64.msu
    when I run it, it tells me "The Update does not apply to your system.  So im thinking I need to remove the .NET Framework 4 Client Profile and the .NET Framework 4 Extended.  reboot, then install
    Windows6.0-KB2637518-x64.msu and then reinstall .NET Framework 4 Client Profile and the .NET Framework 4 Extended
    this has taken a day or so to figure out the order of dependencies and the order to put them on.
    Frustrating, since I won't be using Exchange 2010, were moving all the way to Exchange 2013 on a brand new server.
    Chris

  • Error Exchange Server 2010 SP3 Upgrade - OWA Already Exists - Event ID 1002

    Hi,
    I have a problem with my Exchange 2010 SP1 deploy in Windows server 2008 R2,
    I try upgrade to Exchange 2010 SP3, an error happened when step progress CAS role
    Error:
    The following error was generated when "$error.Clear(); 
              $InternalOwaUrl="https://" + $RoleFqdnOrName + "/owa";
              new-OwaVirtualDirectory -DomainController $RoleDomainController -InternalUrl $InternalOwaUrl;
              get-OwaVirtualDirectory -server $RoleFqdnOrName -DomainController $RoleDomainController | where {$_.OwaVersion -eq "Exchange2010"} | set-OwaVirtualDirectory -WindowsAuthentication $true;
            " was run: "The virtual directory 'owa' already exists under '(Server Name)/Default Web Site'.
    Parameter name: VirtualDirectoryName".
    The virtual directory 'owa' already exists under '(Server Name)/Default Web Site'.
    Parameter name: VirtualDirectoryName
    Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex88D115&l=0&cl=cp
    Error:
    The following error was generated when "$error.Clear(); 
              $InternalOwaUrl="https://" + $RoleFqdnOrName + "/owa";
              new-OwaVirtualDirectory -DomainController $RoleDomainController -InternalUrl $InternalOwaUrl;
              get-OwaVirtualDirectory -server $RoleFqdnOrName -DomainController $RoleDomainController | where {$_.OwaVersion -eq "Exchange2010"} | set-OwaVirtualDirectory -WindowsAuthentication $true;
            " was run: "The virtual directory for the mini version of Outlook Web App can't be found in the same Web site.".
    The virtual directory for the mini version of Outlook Web App can't be found in the same Web site.
    Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex88D115&l=0&cl=cp
    I already try delete owaVirtualDirectory from adsiedit, Exchange management console, and from IIS manager but still it say virtual directory 'owa'
    already exists in my server.
    Can anyone help me how resolve this problem?
    Thanks.
    Best Regards,
    Henry Stefanus

    Hi Henry,
    Even we can’t see /OWA virtual directory in IIS manager, still doesn’t mean it not exists. The IIS configuration files are located in ApplicationHost.config. This file is located in %windir%\system32\inetsrv\config.
    Found the below entry even with no owa vdir in IIS manager, remove the entries below and try upgrade again. (Note: Before you modify ApplicationHost.config, please take a backup first.)
    <application path="/owa" applicationPool="MSExchangeOWAAppPool">
    <virtualDirectory path="/" physicalPath="C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\owa" />
    </application>
    If the issue still occurs, please do not hesitate to post back.
    Best regards,
    Eric

  • Exchange 2010 SP3 upgrade - Event ID 4999 - Address Book Crash

    0
    I just upgraded an Exchange 2010 SP1 CAS server to SP3 - since then anytime an outlook client connects to the CAS server, the Address Book service crash's and event 4999 is logged in App log.  I can reproduce the issue by attempting to create a new
    outlook profile and checking the name against the CAS server.  This crash's the service and the client recieves an error message.  The contents of event ID 4999 is below.  I've tried re-installing the CAS role, re-applying the schema extension
    for SP3.  I've installed all windows updates, enabled logging but I'm not getting anywhere.  If anyone can help with this issue, I would greatly appreicate it.
    Watson report about to be sent for process id: 10168, with parameters: E12, c-RTL-AMD64, 14.03.0123.004, M.E.AddressBook.Service, M.Exchange.Rpc, M.E.R.R.RfriRpcOperationBase.Complete, System.ArgumentException, a3e, 14.03.0123.002.
    ErrorReportingEnabled: True
    That error is followed by a message that the Address Book service has sucessfully started

    Hello,
    For exchange 2010 sp3, there is no article to explain the issue.
    I suggest you run EXBPA aganist your exchange server health check.
    Cara Chen
    TechNet Community Support

  • Exchange 2010 SP3 Upgrade Failed

    Dear All,
    I'm trying to upgrade Exchange 2010 on SP2 or 3 but I'm getting below error.
    Setup encountered a problem while validating the state of Active Directory: An Active Directory error 0x51 occurred when trying to check the suitability of server 'Server.Domain.Com'. Error: 'Active directory response: The LDAP server is unavailable.'
    I have 3 DCs
    PDC 2003
    ADC 2003
    ADC 2008 R2, All FSMO Roles are on 2008 R2.
    Exchange 2007 SP3 is in place with 1 Exchange 2010 box which is working fine.
    Please help me in this regard.
    Thanks in advance.

    Hi
    Can you ping your DC from your exchange server?  On exchange 2010 can you run the following from your EMS, what does the results give you?
    Get-ADServerSettings | fl

  • Exchange 2010 SP3 upgrade

    Dear Exchange admin,
    We tried to upgrade Exchange 2010 SP1 to Exchange 2010 SP3 .In HQ site all preparation finished smoothly.
    But in DR we are unable to do even preparation.We are getting the following error.
    Please advice me  how can proceed.
    Summary: 4 item(s). 2 succeeded, 2 failed.
    Elapsed time: 00:00:37
    Configuring Prerequisites
    Completed
    Elapsed Time: 00:00:00
    Organization Prerequisites
    Failed
    Error:
    Setup needs to contact the Active Directory schema master but this computer is not in the same Active Directory site as the schema master (Default-First-Site-Name).
    Click here for help... http://go.microsoft.com/fwlink/?linkid=30939&l=en&v=ExBPA.14&id=2376fec1-b9ce-44db-beb6-cb9ac4788988
    Error:
    Setup encountered a problem while validating the state of Active Directory: Exchange organization-level objects have not been created, and setup cannot create them because the local computer is not in the same domain and site as the schema master.  Run
    setup with the /prepareAD parameter on a computer in the domain kfupm and site Default-First-Site-Name, and wait for replication to complete.
    Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex28883C&l=0&cl=cp
    Elapsed Time: 00:00:14
    Languages Prerequisites
    Completed
    Elapsed Time: 00:00:04
    Mailbox Role Prerequisites
    Failed
    Error:
    Setup encountered a problem while validating the state of Active Directory: Exchange organization-level objects have not been created, and setup cannot create them because the local computer is not in the same domain and site as the schema master.  Run
    setup with the /prepareAD parameter on a computer in the domain kfupm and site Default-First-Site-Name, and wait for replication to complete.
    Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex28883C&l=0&cl=cp
    Error:
    Setup cannot continue with the upgrade because the 'mmc' () process (ID: 4508) has open files. Close the process and restart Setup.
    Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex28883C&l=0&cl=cp
    Error:
    Setup cannot continue with the upgrade because the 'powershell' () process (ID: 3808) has open files. Close the process and restart Setup.
    Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex28883C&l=0&cl=cp
    Error:
    Setup cannot continue with the upgrade because the 'mmc' (4508) process (ID: ) has 'Microsoft.Exchange.Management.SnapIn.Esm.dll' loaded. Close the process and restart setup.
    Click here for help... http://go.microsoft.com/fwlink/?linkid=30939&l=en&v=ExBPA.14&id=f0d3f291-5a52-43ea-9121-24aa7cd0c30e
    Warning:
    Install hotfix Microsoft Knowledge Base article 2550886 from http://support.microsoft.com/kb/2550886 to improve Windows Failover Cluster transient communication instability when deploying stretched Database Availability Groups across datacenters.
    Elapsed Time: 00:00:18
    Ashraf

    Hi  Ashraf
    Thank you for your question.
    Exchange update cannot continue because the computer that is running update is not in the same Active Directory site or domain as the server that is assigned the domain schema master role, also known as flexible single master operations or FSMO.
    You can refer to the following link to change exchange site schema:
    http://technet.microsoft.com/en-US/us-cn/zh-hans-cn/library/2376fec1-b9ce-44db-beb6-cb9ac4788988.aspx
    You also notice the order for updated:
    1.Client Access servers (beginning with the internet-facing site)
    2.Hub Transport and Edge Transport servers
    3.Mailbox servers
    4.Unified Messaging servers
    You can refer to the following link to update:
    http://exchangeserverpro.com/installing-exchange-server-2010-service-pack-3/
    If there are any questions, please let me know.
    Best Regard,
    Jim

  • Cannot connect to OWA after Exchange 2007 SP3 and Rollup 13 install.

    Hi,
    Our OWA website isn't accessible after we installed SP3 and rollup update 13 for Exchange 2007.  When we attempt to visit the OWA URL, all we receive is HTTP 403.4 SSL is required to view this resource.  Doug

    Hi,
    I recommend you follow the steps below for troubleshooting:
    1. Open IIS Manager, click Default Web Site -> Authentication, make sure that Anonymous Authentication and Windows Authentication are enabled.
    2. Click Default Web Site -> SSL Settings, check "Require SSL" and click Ignore.
    3. Click Default Web Site -> HTTP Redirect, check Redirect (enter your
    https://URL), check "Only redirect" box and Status code Found 302.
    4. Expand Server Configuration -> Client Access ->double click owa ->Authentication tab. Check the Basic Authentication and check the Use forms-based authentication button Logon Format: Domain\user name.
    What's more, here is a thread for your reference.
    Exchange 2007 SP3 Rollup 2 installed - OWA stopped working
    http://social.technet.microsoft.com/Forums/en-US/8481eb3d-a6ab-42fc-b7ea-fa9a9a625e48/exchange-2007-sp3-rollup-2-installed-owa-stopped-working?forum=exchangesvrdeploylegacy
    Hope it helps.
    Best regards,
    Amy
    Amy Wang
    TechNet Community Support

  • Missing mail when trying to access Outlook 2007 archives with Outlook 2010 Pro Plus

    I recently upgraded a user's laptop and it is currently running Office 2010 Pro Plus.  On their desktop they were running Office 2007 Pro and they recently archived messages in Outlook on the desktop but they don't show up on the user's laptop
    accessing that same archive file. I've tried shutting down Outlook on the desktop, ran the inbox repair tool and I even tried upgrading the desktop to Office 2010 as well with no luck.  This PST files are located on my server and they are backed
    up regularly.
    Any insight would be greatly appreciated.
    Thanks

    Hi,
    You should not use Network Stored PST files, .pst files are used to let users maintain a copy of their messages on their local computers. Please refer to these articles for more information:
    http://support.microsoft.com/kb/297019
    http://blogs.technet.com/b/askperf/archive/2007/01/21/network-stored-pst-files-don-t-do-it.aspx
    Instead of using a Network Stored PST file, you can configure Microsoft Outlook in Cached Exchange Mode. This caches the Exchange Server mailbox data in a local Offline Folders (.ost) file. This configuration lets the remote client work successfully even
    without being connected to the server.
    You can find more workarounds in these articles:
    http://support.microsoft.com/kb/291627
    http://support.microsoft.com/kb/297019
    Thanks,
    Ethan Hua CHN
    TechNet Community Support

  • Weird emails showing in Outlook 2013 Inbox after Exchange 2013 PST Import

    Hi there,
    I've just done an Import PST from Exchange 2013 using the GUI, and when it is finished, I then open Outlook 2013 I am seeing a few strange emails in the Inbox.
    The PST's were from Outlook 2007, and were previously used in with POP mail.
    The message is like this:
    Subject: Undeliverable: Not read: RE: Re: information
    Your message did not reach some or all of the intended recipients.
          Subject:  Not read: RE: Re: information
          Sent:     20/04/2014 11:08 p.m.
    The following recipient(s) cannot be reached:
          Big John on 20/04/2014 11:11 p.m.
                Diagnostic code = MailRecipientUnknown; Reason code = TransferImpossible; Status code = 511
                < #5.1.1 smtp;550 5.1.1 RESOLVER.ADR.RecipNotFound; not found>
    The date and time of the message is during the import process.
    Does anyone have any suggestions? 
    From a PST of around 8GB, I ended up with about 50 of these type of messages, mostly to the same recipients, but there were some different ones. From a mailbox of about 3GB, I got about 5 of these messages. From the smaller mailboxes I got none.
    Thanks in advance,
    Steve.

    Hi Steve,
    Please verify whether this issue occur in OWA.
    If everything is OK in OWA, it seems the .pst import completed successfully. Let's perform troubleshooting on the Outlook client side.
    1. Please run Outlook under the safe mode to avoid some AVs and add-ins.
    2. Please try to re-create profile to refresh the caches.
    3. Please also check whether the missing messages in others' folders or subfolders.
    I want to know that why you exported to .pst from Outlook 2007 and imported it into Exchange 2013. Did you migrated Exchange server from 2007/2010 to 2013?
    If it is the case, I suggest moving mailbox from Exchange 2007/2010 to Exchange 2013.
    Please correct me if there is any misunderstanding.
    Thanks
    Mavis 
    Mavis Huang
    TechNet Community Support

  • Is it possible to switch from Office 365 online user management to Active Directory after Exchange online migration?

    If we utilize the Cutover method to migrate from on-premise Exchange (2007) to Office 365, which to my understanding will hand over user management/authentication to Office 365 online during the process, is possible to later switch from Office 365 user management
    to Active Directory (synced to a future local domain, or even possibly via AD federation single sign-on)? If so, how difficult is this process and is there any documentation available?
    Asking this because the organization  I'm working for plans to upgrade (re-do actually) its entire infrastructure. There will be a completely brand new domain/AD set up that's totally unrelated to the old one. At the same time, we also plan to migrate
    all emails (previously hosted locally on Exchange 2007) to Office 365 and get rid of local exchange. Now because we will set up new domain, we do not want to carry over the older AD to the cloud, hence we will not use the "Staged Migration". 
    So the plan is to to use "Cutover" migration first, which means all authentications will become Office 365 managed. That's fine for now. But later, after we set up our new domain and AD controller etc, we'd like to have Exchange Online switch back
    to syncing with our new on-premise AD. We'd also like to consider the AD Federation Services if it's not too complicated to set up.
    Your advice on this would be greatly appreciated!

    In principle, you cannot sync back from the cloud AD to the on-prem, yet. But you can take advantage of the soft-matching mechanism once you have the new AD in place:
    http://support.microsoft.com/kb/2641663
    Be careful though, as the moment you turn on Dirsync, all the matching users in the cloud will have their attributes overwritten. A very good idea is to do an 'export' of the cloud AD first, using the WAAD module for PowerShell and the Get-MsolUser cmdlets,
    which you can then use to compare or import data in the new on-prem AD. Some links:
    http://technet.microsoft.com/en-us/library/hh974317.aspx
    http://msdn.microsoft.com/en-us/library/azure/dn194133.aspx

  • Cannot open Icloud calendar in outlook 2010 since upgrade to win 8.1

    Since upgrading to Windows 8.1 cannot open iCloud calendars or contacts. I get "This set of folders cannot be opened. Theinformation store could not be opened."

    I uninstalled iCloud control panel, removed any iCloud folders from Outlook, rebooted the computer nad then downloaded and installed the latest iCloud for windows.After going through the reinstall steps and setting up iCloud, Outlook seems to sync with iCloud.

Maybe you are looking for