Feb 21 2018 12:10 AM
Hello,
we use OneDrive for Business for synchronization with SharePoint 2013 on-premise. Since one of last Office updates the client started to consume CPU constantly. I found out that the client is still writing some .etl files into following directory that is becoming realy huge because of it.
C:\Users\username\AppData\Local\Microsoft\Office\Spw\logs
Please don't give me recommendation to move to the classic OneDrive client since that is working only with SharePoint online product.
Does anyone have any idea how to stop the CPU drain?
Thanks
Mar 13 2018 04:37 AM
1st: You cannot use the new sync Client to sync data from any OnePremises Version. You must sync with the old OneDrive for Business (Groove) Client.
2nd: The first onPremises SharePoint you will be able is SharePoint Server 2019 !!
3rd: The Picture showd "OneDrive for Business" and Not OneDrive
4th: The log Files from the new Next Generation Sync Client are stored on a diffrent Location:
C:\Users\[USER]\AppData\Local\Microsoft\OneDrive\logs
Hans Brender, MVP Office Servers and Services
Mar 13 2018 04:45 AM
1st - Yes, I wrote that I cannot use it.
2nd - Sharepoint server 2013 is still supported product as same as OneDrive for Business (Groove) so why do I need to wait? Microsoft should fix it's issue.
3rd - Yes thats the point. I wrote it. Whole issue is about OneDrive for Business, read more carefuly please.
4th - I cannot use new generation sync client so I don't care about it's log location.
Mar 13 2018 05:05 AM
During the years, Microsoft only develop new feature for the latest Version or the new expected Version. (Exception: Security issues).
As I said, the Next Generation Sync Client will only work with SharePoint Server 2019.
Fakt.