T
Tec-Quadrat
Guest
We have two remotedesktop servers with Microsoft Office.
OS: Windows Server 2019
MSO: 365 ProPlus shared licensing
Both of the servers have huge I/O-load because of outlook.exe working in userprofile\localappdata\temp\..\outlook logging\OUTLOOK-date-time-v2.etl
Relevant threads:
What is the Enable logging (troubleshooting) option?
https://support.microsoft.com/en-us...al-and-advanced-logging-for-microsoft-outlook
No outlook has the "Enable troubleshooting logging"-option selected. No Registry Keys were set. It even happens for a user that I just created with 0 data and 0 mailstore. There was no "debugmode" or anything similar selected when MSO was deployed via xml.
It happens on both servers. I cannot get it to stop logging. Is there another way?
We have a similar installation (WinSrv 2016 with one RDS with MSO 2016 Standard). There we do not have any problems with I/O-traffic because of logging
Continue reading...
OS: Windows Server 2019
MSO: 365 ProPlus shared licensing
Both of the servers have huge I/O-load because of outlook.exe working in userprofile\localappdata\temp\..\outlook logging\OUTLOOK-date-time-v2.etl
Relevant threads:
What is the Enable logging (troubleshooting) option?
https://support.microsoft.com/en-us...al-and-advanced-logging-for-microsoft-outlook
No outlook has the "Enable troubleshooting logging"-option selected. No Registry Keys were set. It even happens for a user that I just created with 0 data and 0 mailstore. There was no "debugmode" or anything similar selected when MSO was deployed via xml.
It happens on both servers. I cannot get it to stop logging. Is there another way?
We have a similar installation (WinSrv 2016 with one RDS with MSO 2016 Standard). There we do not have any problems with I/O-traffic because of logging
Continue reading...