For Front line troubleshooting I believe it has gotten somewhat easier to troubleshoot Lync. Lync server is a complex beast. No doubt about it.
This article is for the person who is on the front line, or is put in a position to troubleshoot Lync, when you do not know a lot about the product.
Before you begin, do something simple- Back up the voice portion if necessary.
Get-CSVoicePolicy | export-clixml –path d:\Backup\VoicePolicy.xml
Get-CSDialPlan | export-clixml –path d:\Backup\Dialplan.xml
Now you may do some basic testing to see where the break is:
Lets begin with a test of ports with Lync Port Tester. It is important to use tools that help automate (even magnify), the finding of problems. I found a Test script, which is a very unique and, an elegant approach. See the bottom of this article for the 30 or so workloads tested.
This script asks you questions and then runs some tests. Then it asks you some more and more tests. This thing will test everything from Chat to UM and voice. I ran it last night and collected the steps to make it work. It ran flawlessly, and showed all my Lync Breaks effectively.
I must callout the writer of the script, Murali Krishnan. Thank you for your time on this. I wish I had time to do some of this, but thank you for your time. However, you can see when someone has some time into it. Murali certainly does. Second, I want to call out Leonard, my personal friend. He really loved those synthetic transactions when they first came out. I remember, that was always his first ask, on 2013 RTM cases. It was funny to look back on. I was more partial to using sip stack logs. Neither of us like the CLS logging at the time. It funny how it balances out, when you begin to use them all when you need them. In any case, Enjoy the work below and I hope this is helpful to someone-
Running a full Test set on your lync server configuration with synthetic transactions
1. Create two AD users and lync enable them.
2. Add these users to exchange as mailbox users.
3. UM enable them as well if you want to test full lync and Exchange UM integration.
4. Enable the users as Lync users, Enterprise voice enabled etc…
5. Run the following cmdlet to enable them for synthetic transactions
New-CsHealthMonitoringConfiguration –Identity lyncpool.domain.com –FirstTestSamAccountName domain\LynctestUser1 –FirstTestUserSipUri “sip:LynctestUser1@domain.com” –SecondTestSamAccountName domain\Lynctestuser2 –SecondTestUserSipUri sip:LynctestUser2@domain.com
6. Run the health check script with the syntax -> .\lync2013_testscript_v1.2.ps1 (if this fails you may need to run set-executionpolicy –executionpolicy unsigned)
Once this is complete, you are ready to perform your health check. This check is great “top to bottom test of your environment” by workload. It is a great thing to run, when you have completed your setup, or if you have a problem and you’re not sure where to start.
My only comments about this tool is twofold: 1. you will be interested in some test and, perhaps not others. Just keep going through the tests questions. You will get a compiled report at the end. 2. Make sure you choose the log option at the end of the script. If you don’t, the window closes and report appears to not be created. “UPDATE”. A report will be sitting in the same folder as the script. What a cool feature!!! At least you get a solid report, no matter the outcome.
I included a sample report with the script package. As it turns out, there are several text documents. I just included the workload summary. I really like this tool and I hope you like it and it helps you as well.
From the original post: Tests Performed is pretty Comprehensive: