I’ve been sitting on this one for quite a while, but someone at the recent PowerShell Summit kindly reminded me to get it published.
Lync 2013 Servers generate Windows Fabric logs, Flinchbot has already done a great write up.
These don’t appear to be causing a lot of issues, but it is something you might want to check on, as they could potentially fill your hard drive.
I haven’t seen any official guidance, but as Flinchbot points out, you can set the logging to circular (Admin CMD prompt):
Logman update trace FabricLeaseLayerTraces -f bincirc –cnf
Note, there are two hyphens before cnf, but for some reason wordpress doesn’t show them correctly
I’ve written a little script that, when run from a Lync Server, gathers all the Lync Front End servers, checks for a Windows Fabric log path, and measures the size of the logs directory.
Here is an example of the output:
You can grab the latest version of the script on my github.
I am interested to hear what sizes others find.