locked
Version 1908 Build 16.0.11929.20562) Outlook slow as hell onprem and off prem users 0 4 to 8 seconds switching between emails RRS feed

  • Question

  • We went back to Semi-annual and now we have issues with the outlook being very slow other updates include the below, I did notice that outlook using process explorer when looking at outlook.exe under GPU the Committed GP memory for outlook can go from 20mb to averaging about 80mb and uptp 140mb when switching between emails and mailboxes this is unusually high considering we're a xendesktop W10 environment without GPU nvidia grid in our datacentre so it's all cpu driven, any ideas?

    A restart of outlook can help but for heavy users this is a pain 

    2.05b 15/01/2020

    ==============================================

    Added                  -              January 2020 OS Updates

    Replaced             -              Microsoft_OneDrive_19.86.502.10_x86 with Microsoft_OneDrive_19.174.902.13_x86

    Replaced             -              Microsoft_Office365ProPlus_16.0.12130.20344_x86 with Microsoft_Office365ProPlus_16.0.11929.20562_x86  - going back to semi-annual channel, new version 1908)

    Replaced             -              Microsoft_Teams_1.2.00.27559_x64 with Microsoft_Teams_1.2.00.32462_x64

    Replaced             -              Adobe_AcrobatReaderDC_19.012.20034_x86 with Adobe_AcrobatReaderDC_19.021.20058_x86

    Replaced             -              Condeco_OutlookAdd-in_6.6.004_x86 with Condeco_OutlookAdd-in_6.6.502_x86_2

    Replaced             -              Lakeside_SystemsManagementAgent_8.03.0689_x86 with Lakeside_SystemsManagementAgent_9.00.0302_x86 

    Replaced             -              CrowdStrike_WindowsSensor_5.11.9204.0_x64_2 with CrowdStrike_WindowsSensor_5.23.10504.0_x64 amended install command line)

    Modified             -              executing Citrix_OptimizationEngine_2.1_1.0 v1.8 (add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY\MACHINE\Software\Wow6432Node\Microsoft\Office\16.0\Access Connectivity Engine\Engines WorkingSetSleep REG_DWORD = 1" fixed access DB issue)

    Moved                 -              Office 365 and its dependent components under Citrix VDA install step in the MDT Task Sequence (to fix FSLogix, Ivanti EM, Citrix VDA and Teams install issues which began with December O365 Monthly Channel release)

    Thursday, February 20, 2020 9:59 AM

Answers

  • We have an onsite MS engineer apparently there may be a memory leak detected in outlook, so I believe they are running some diagnostic tools on users machines to collect the information. I guess they're using debug diag 2.0? Anyway this can be closed as it's WIP
    • Marked as answer by hirogen1 Monday, March 9, 2020 9:49 AM
    Monday, March 9, 2020 9:49 AM

All replies

  • we use fslogix too so will test deleting the ost files too via the vhdx's of course. 
    Thursday, February 20, 2020 10:42 AM
  • Hi,

    Are you using a local Exchange on-prem server?

    Do you mean that GP memory for outlook keeps improving with constantly clicking on messages?

    >> A restart of outlook can help but for heavy users this is a pain.

    Does everyone in your organization have this problem? If so, this may be a issue related to your environment.

    What's the version of your Outlook client and Windows? (File > Office Account > About Outlook). Please make sure you have upgraded your Outlook and Windows to the latest version.

    In this situation, it is suggested to temporarily turn off your antivirus software to check if the issue will be gone, because some antivirus programs perform email scanning may cause this issue.

    For Outlook client, there could be some add-ins in your Outlook client that cause this issue, so it is suggested to start your Outlook in safe mode (Press Win + R, type “outlook /safe”, press Enter.) and see if the issue continues.

    It is also suggested to create and use a new Outlook profile via Control Panel > Mail > Show profile and see if there is any difference.

    In addition, how about turning to other update channel such about Monthly Channel.

    Hope this can be helpful.

    Regards,

    Aidan Wang


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Friday, February 21, 2020 3:03 AM
  • yes it would seem going from monthly to semi annual has introduced this issue, we're looking at the new condeco addon which was installed into the image about 3 weeks ago, I've asked the helpdesk to try deleting the ost/create a new profile.

    outlook version MSO 16.0.11929.20436 32bit, note we don't have nvidia grid on our blades and we're a W10 11908 build xendesktop environment.  

    See the difference


    • Edited by hirogen1 Friday, February 21, 2020 10:26 AM
    Friday, February 21, 2020 10:22 AM
  • We use both onprem and off prem we have a site whcih is onprem exchange only and they have severe slowness, I beleive the 0365 mailboxes may also be experiencing slowness but its certain;y onprem users. 
    Friday, February 21, 2020 10:35 AM
  • Hi,

    Thanks for your reply.

    Have you tried my suggestions above? What's the result?

    Regards,

    Aidan Wang


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Tuesday, February 25, 2020 8:34 AM
  • Hi,

    I'm writing to see if the reply above is helpful to you. If yes, would you mind helping mark the reply as answer? So that others who might have a similar question can benefit from your thread? Thanks for your understanding and support.

    Regards, 

    Aidan Wang


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.



    Tuesday, March 3, 2020 7:02 AM
  • We have an onsite MS engineer apparently there may be a memory leak detected in outlook, so I believe they are running some diagnostic tools on users machines to collect the information. I guess they're using debug diag 2.0? Anyway this can be closed as it's WIP
    • Marked as answer by hirogen1 Monday, March 9, 2020 9:49 AM
    Monday, March 9, 2020 9:49 AM