Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy Unrestricted So open a PowerShell window with “Run as Administrator” and type the following to permit this to run: And if there’s one thing you’ve learned about running PowerShell scripts it should be this: You need to set the Execution Policy before you can run somebody else’s script, even Microsoft scripts.
So, now that the directories have been defined, it’s time to launch CLSLogger, right? Yeah well not quite.ĬLSLogger is really a super elaborate PowerShell wrapper.
New-CsClsConfiguration -Identity "site:Site 2" -ETLFileFolder "d:\logging" -CacheFileLocalFolders "d:\logging"Įven if you only have a C: drive, you may want to change the directories to something you can find more easily than %WINDIR%\ServiceProfiles\NetworkService\AppData\LocalĬLS will automatically create the directory you define, so that saves time connecting to every server in your site to create a directory. Below is an example creating a new configuration for a Site named “Site 2” and changing the logging folders to e:\logging: This is done with the New-CsClsConfiguration cmdlet. You may want to edit this to get them off of your C: drive so you don’t accidentally fill it up.Īnd since I never like editing the Global configuration of anything (if it can be avoided), create a new CLS Configuration for your Skype for Business Site(s). These directories are important because this is where the log files are going to be created. %WINDIR%\ServiceProfiles\NetworkService\AppData\LocalĬ:\windows\ServiceProfiles\NetworkService\AppData\Local By default this is set to %TEMP%\Tracing. For the most part, ignore everything returned except for the “ETLFileFolder” and “CacheFileLocalFolders” values. This will let you know how you are set up. If you are a CLS ninja, then you can probably skip the CLSLogger altogether and just go on about your business.īefore you even fire up the tool, run Get-CsClsConfiguration. There is nothing that the CLSLogger can do that you can’t do via PowerShell. But it’s new, and newer is always better.Īlso, CLSLogger can be used against Lync 2013 servers as well as Skype for Business. There has been the addition of a “Codepoint” menu which ….I’m guessing….is used to load external diagnostics…or something. Snooper remains the same though it is a newer version. The primary change is that the OCSLogger.exe from Lync 2013 has been replaced with the CLSLogger.exe program. The Lync debugging tools have to be run independently on each server. This makes it far easier to do logging across multiple servers at the same time. However the new debugging tools leverage the Centralized Logging Service (CLS) feature introduced in Lync 2013. First off, the Lync debugging tools will work on a Skype for Business server. The Skype for Business debugging tools are a replacement for the Lync Server Debugging tools. If someone has, please let me know and I’ll give you props and a link right up top. I’m surprised no one has written about this yet. Note: Updated 28 August 2015 to reflect changes in newer version.