none
Performance issue caused by Office Telemetry RRS feed

  • Question

  • Hi there,

    We use Interop (Office 2016) on our server running on Windows Server 2012 R2 to programmably process Office files. Recently, we found a performance issue and after investigation, figured out it is due to generation of the Telemetry files. Every time Word opens a file, there are 10 OTele files generated automatically (under the name of xxx.winword.exe - OTele.dat and xxx.winword.exe.OTeleMediumCost.dat), which results in slower Interop processes. Right after deleting those files, the performance issue is gone. Note we performed some load tests to Interop, and the volume in C:\Users\UserName\AppData\Local\Microsoft\Office\OTele impacts the performance - the larger size the folder is, the slower it will be.

    We would like to know:
    (1) why those files are generated? What are the settings for this and since when this is enabled by default?
    (2) how to prevent those files from generating?
    (3) if (2) is done, what's the impact will be?
    I have tried to do the following Office setting change via Registry keys:
    [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\16.0\OSM]
    "Enablelogging"=dword:00000000
    "EnableUpload"=dword:00000000
    [HKEY_CURRENT_USER\Software\Microsoft\Office\Common\ClientTelemetry]
    "DisableTelemetry"=dword:00000001
    "VerboseLogging"=dword:00000000

    However, only the "DisableTelemetry" entry works with 4 of the files avoided. 

    Tuesday, February 6, 2018 6:41 PM

All replies

  • Hi,

    By default, telemetry data collection is disabled in Office. Please check if your environment is enabled the telemetry agent before. Check the registry settings under:

    HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\OSM
    HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\16.0\OSM
    HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\OSM
    HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\15.0\OSM

    If you are using Office 2016 upgraded from Office 2013 before, please also disable the Office 2013 telemetry agent. Please check the registry settings mentioned in the article below:
    https://technet.microsoft.com/en-us/library/f69cde72-689d-421f-99b8-c51676c77717%28v=office.16%29#configure

    Disable all Telemetry settings for Office users:
    https://technet.microsoft.com/en-us/library/jj591589(v=office.16).aspx#Disable data collection for the telemetry agent

    Disabling logging does not delete the data that has already been collected from a computer. To delete this data on the local client computer, delete the files evt.tbl, sln.tbl, user.tbl that are located under %LocalAppData%\Microsoft\Office16.0\Telemetry\Microsoft\Office\16.0\Telemetry\.


    Best Regards,
    Winnie Liang


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


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Wednesday, February 7, 2018 6:55 AM
    Moderator
  • Hi, 

    Just checking in to see if the information was helpful. Please let us know if you would like further assistance.

    Regards,

    Emi


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


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Wednesday, February 14, 2018 2:24 AM
    Moderator
  • Thnk you ChangSun !
    I have same error on 2012 R2 server

    I use Office 365 2016 oneclick installation with monthly update
    currently build 1803 build 9126.2116

    Your DisableTelemetry did the trick too for me
    [HKEY_CURRENT_USER\Software\Microsoft\Office\Common\ClientTelemetry]

    "DisableTelemetry"=dword:00000001

    Thursday, April 5, 2018 11:09 AM
  • We had the same problem on our build server where we run some interactive tests using Word.

    The special problem was that after closing the Word application, the winword.exe process hung for up to 16 seconds. Using procmon.exe we saw that in that time there was a lot going on regarding telemetry.

    Setting the DisableTelemetry entry did not help right away, because we had almost 9000 files in the OTele folder under %LocalAppData%.

    Emptying that folder then did the trick.

    Thanks for mentioning all that.

    On a side note:

    With the DisableTelemetry entry in place, just firing up Word and closing it right away wrote three entries in that OTele folder. Without that key, it were five entries and the files were bigger. Setting the entries under the OSM key mentioned does not change that behaviour either.

    So it might be a good practice to keep an eye on that folder even if telemetry is disabled.

    Wednesday, November 28, 2018 10:40 AM