An update about the Outlook 2013 folder pane issue


The Office Sustained Engineering team has an important update about a potential issue with Outlook 2013 after installing the September 2013 Update. For details about the issue and how to fix affected installations, see Outlook 2013 Folder Pane Disappears After Installing September 2013 Public Update on the Office Sustained Engineering blog.

Exchange Team

Comments (16)
  1. SP says:

    why do we have so much quality issues lately with Microsoft products. Its nightmare for Administrators, when CEO of the company calls us in his cube and screams. Is it a way Microsoft is trying to put every one to O365? and dont want to invest in On-prem. In that case you are opening the gates for us to think of options apart from MS who are providing cloud services.

  2. AJS says:

    SP I totally agree with your comments, then usually the 2nd Tuesday/Wednesday of EVERY month we are bombarded with many updates, and people sitting there waiting for equipment to update or eventually shutdown before they can take their laptops home!  I thought MS was about being more productive, not sitting waiting around, or maybe that's the time people can take a tea break  lol

  3. Low quality release management and testing says:

    I am sorry to see Microsoft drowning in the mud, after firing loads of engineers and programmers, leaving commercial people selling products that do not pass a serious quality check and release management.

  4. Mr Clean says:

    Another sloppy patch from Microsoft. I am now waiting until 4 weeks even when patching desktops now.

  5. AFR says:

    After dealing with a constant stream of craptastic service packs, updates, re-issued updated, re-reissued updates, and Office problems I think it's high time someone was fired. You are obviously not testing your software before releasing it.

    No respectable software company should accept the level of quality control you've been showing over the past year. Please, for the love of all that is holy, please fire someone and get this debacle resolved so we don't have to literally fear patching our Exchange services.

    It's ridiculous. Beyond ridiculous. Please, fire the idiot who is responsible.

  6. SP says:

    The best chances for MS to get on-prem customer to o365 is keeping on-prem administrators and IT management happy. If they think that making life difficult for on-prem will force them to use o365 then I think after 10 years MS name will no longer exist in IT and software industry. People are trying to find reasons to move away from MS and this type of service will be final nail in coffin to move away from MS.

  7. ABCFED says:

    Had a few customers experience this problem yesterday and just this morning. Uninstalling seems to fix the problem. Not sure this is an Exchange team specific issue because it was with Outlook, but…ummm….

    …someone really needs to get on the ball at Microsoft in general. We can't be having problems every single month with patches. It's just killing customer satisfaction with Exchange.

  8. PoA says:

    Problem is: It's not Exchange/Outlook. It's everywhere (blogs.technet.com/…/update-rollup-3-for-system-center-2012-data-protection-manager-service-pack-1-has-been-re-released.aspx as another sample).

    4 options I can see:

    – Forcing customers to their cloud

    – Wrong manager/programmer ratio

    – MS feeling like the big shepherd – we have to follow anyway

    – Complexity: The whole concept 'Windows' is starting to fail

  9. Stunned says:

    "I'm guessing here, but I do think that it must be on senior management radar as a big problem to address. I have no doubt that they're getting lots of complaints, and not just from nobodies posting on support threads, but from large corporate customers, the ones Microsoft listens to carefully. This problem can't be allowed to continue."

    http://www.zdnet.com/why-all-the-errors-in-microsoft-updates-lately-7000020628

    Agree. Enough is enough. Either test the patch correctly or do not issue the patches at all. Your current patch testing methodology sucks and someone needs to be shown the door.

  10. Leave a Comment says:

    Y'all on the Exchange team need to fix this problem asap. We can't have Exchange servers and Outlook client completely shatting all over themselves every single damn month when we are trying to run a business.

    STOP RELEASING UPDATES THAT YOU DO NOT TEST PROPERLY!!!!!!!!!

    Beyond stupid. Whomever is going along with this methodology really needs to reconsider that it has been a complete fail of a process ever since Exchange 2013 was RTM. Not a single patch or update goes by that doesn't cause problems or break things.

    GET YOU SHIP IN ORDER AND START PRODUCING QUALITY PRODUCTS!!!!!!!!

  11. nsa says:

    Even MS developers are coming out about the backdoors and workarounds that have been implemented under their watch. It is not a secret anymore. Which CU or SP will remove the security holes in Exchange 2013 so people will want to start buying this software again? As a MS partner our sales of MS services has dropped in half over this problem. It is not worth it. You are losing billions.

  12. JamesNT says:

    We all know there are super-smart people at Microsoft who can solve this problem.  We all know that some of the smartest people walking the planet work at MS.  

    This is NOT a developer or talent issue.  This is a MANAGEMENT ISSUE.  Once again, developers at MS and the customers of MS are feeling the horror of some moronic bean counter who thinks they know more than anyone else.  The result is that the MS developers who can fix this in 5 minutes have their hands tied and we customers get to pay for it all.  Amazing how often things like this happen.

    JamesNT

  13. tt says:

    Hi all.  Our environment is enterprise and we have phishing attacks which compromise accounts which send spam which then get us black listed.  This is unfortunate.  I'd like to see Exchange do the following: An administrator can set a blanket filter limit on all accounts so if one email from an account is mailed to more than a variable set number of people, say 100 people, approval is required by an administrator before the email can be sent.  The administrator phones the user to confirm the actual user is sending the email.  Exceptions can be made for specific users or limits can be changed for specific users.  The user is able to determine a set number of people who can provide a secondary approval as an alternative to the always optional administrator.   This would make it impossible for spammers to send a single email to high numbers of people without getting approval from a secondary account.

  14. ABCFED says:

    tt,

    I believe the feature you are looking for is the "tips" and that feature already exists in Exchange 2010 and 2013. It will inform the user that they are sending to more than 100 recipients and if they try, you can prevent it. In addition, with Exchange 2013
    you can also create policy tips as well.

    technet.microsoft.com/…/jj649091(v=exchg.150).aspx

    Would this solve you problem?

    :)

  15. ExchAdmin says:

    Just another +1 for the "get your act together" comments. Between the massive increase in defective software updates and the off-shoring and huge quality degradation of Pro Support, you're making it very, very difficult to support your products. A company as wildly profitable as MS should not have these issues: Quality and well-tested software along with top-end support for your partners should be the norm, not the exception. O365 isn't any better: Tech support for it is among the worst I've ever experienced.

Comments are closed.