When I am trying to troubleshoot a situation in Skype or Lync with the Centralized Logging Service (CLS), one of the biggest challenges is knowing which scenario to use. I found that it was cumbersome to search with the Cmdlets every time I needed to gather logs for something new. Sometimes I would need to check which components a scenario used and their levels and flags and other times I knew a component but not which scenario it was in. So, I wrote a script that would allow me to quickly find either of these things. I am sure you may find more ways to use it than I did.
The way I use it is to create a shortcut on my taskbar to the HTML file. That way the information is easy to access and quick to search. When it is open, I simply press Ctrl + F and start typing what I am looking for.
Let’s look at the Output
Here are a couple of sample shots to see what it will look like:
As you can see, it lists the Scenario Name, Components with each of their Levels and Flags. This will allow you to check to see if the scenario you are running will gather the correct information. If it doesn’t, you can always run my Create-CsClsCustomSceneario.ps1 script found here with the corresponding NextHop blog found here.
How to Use
This one is not too complex. Just run the script with the –OutputFolder parameter and point it to the folder you wish to save the output. If the folder doesn’t exist, it will stop the script.
.\List-CsClsScenariosHtml.ps1 –OutputFolder C:\Temp
Once the script is done, it will launch the browser and open the file.
To start collecting CLS Logging, check out my blog on Collecting CLS Logging easily.
- Windows PowerShell 3.0
- Must be run from a Front End server
- This is needed because the CLS .Net assemblies have to be available and are only available on front end servers (From what I have found)
- Lync/Skype on premises administrator with RTCUniversalServerAdmins, CsServerAdministrator, or CsAdministrator rights.
- This is required by the Lync/Skype Cmdlets to create CLS Scenarios without throwing access errors.
- PowerShell opened in “Run as Administrator” mode
- This is required by the script Cmdlets to gather the correct information without throwing access errors.