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

  • Thread starter Thread starter hirogen1
  • Start date Start date
H

hirogen1

Guest
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)

Continue reading...
 
Back
Top