Troubleshooting

Recently I posted a blogpost on Finding the correct patch version of a Lync server. After writing the blogpost I realized that it would be very cool to automate this using PowerShell. The result is Get-CsInstalledLyncVersion.ps1 which is available to TechNet Gallery. This is a great tool to do an initial assesment of a Lync deployment where you get a good overview of installed servers and their current patch level.

Get-InstalledLyncVersion.ps1 script to check patch level on all Lync servers in an environment

Like this:

Recently I have been troubleshooting and doing health checks on a couple of Lync systems. When troubleshooting it is good to know what patch level your servers are on, whether they are on the same patch level or the newest patch level.

I discovered at one client that the Edge servers in DMZ was being patched through Windows Update, but the internal Front End servers where not being patched, they where not part of the patch system the customer where enforcing. The result was that at one point, with the january 2014 cumulative update on the Edge server and the RTM patch level on the Front End servers, the gap became too large and the it ended up with the Front End servers not supporting and working with the Edge AV relay server. We saw the error occur with unsupported realy server in the diagnostics header before the Front End servers even tried setting up the media traffic on the Edge servers. Quite a strange problem to troubleshoot, but best practice is that all servers should be on the same patch level. Patching the internal Lync servers solved the issue.

Here is some notes on finding what patch level your servers have

To find the patch level of your Lync server, the easiest way is looking at the installed components under control panel and programs and features

Like this:

Recently I had to troubleshoot Office Web Apps Server deployments at a couple of customer sites. I had to work through the config and sometimes the Office Web Apps server feels disconnected from the rest of the Lync configuration and can be a difficult role to troubleshoot. I have tried to collect my notes and if I have missed something, let me know.

How to check that the Office Web App Server Web farm is deployed correct

Like this:

The Lync Mobility service and the Lync Clients was released 13.12.2011. Since then as we get more hands-on with the service there are in some cases trouble getting the it up and running. This post is dedicated to how you can test and troubleshoot the mobility service deployment. I will update this post when I find more information on how to troubleshoot and how to solve certain scenarios.

Like this:

When deploying Lync Server 2010 you will most likely come across a lot of strange behaviour and stuff that don’t work as expected due to configuration errors or environmental issues. I will in this post try to collect the solutions and articles I find and update along the way, to have troubleshooting tips in one place. Please let me know if any good blog posts or articles that solve some specific problems is not listed here.

General Troubleshooting
Troubleshooting Lync may be a daunting task since there is a lot of elements that is involved in a deployment. Over the years troubleshooting OCS and Lync I have found a routine for eliminating problems. If you have deployed Lync Server and there is connectivity issues or some features not working I usually go about it in the following order: Continue reading →