In an earlier blog post I wrote about publishing Lync services using TMG 2010. One of the Microsoft alternatives for reverse proxy is the Application Request Routing module or ARR, a module that’s running on top of Internet Information Server (IIS).
In my lab I have a Lync 2013 Enterprise Edition, in the perimeter network I have a Lync 2013 Edge Server, but instead of a TMG I now have an IIS/ARR server.
When testing your Lync 2013 environment it sometimes happens that you cannot logon to your Lync server. If this happens it can be useful to enable logging in your Lync 2013 client.
In your Lync 2013 client, go to Tools en then to Options. In the General section set Logging in Lync to Full.
The log files will be stored in C:\Users\Jaap\AppData\Local\Microsoft\Office\15.0\Lync\Tracing. In there you’ll find a file called Lync-UccApi-0.UccApilog which contains a wealth of troubleshooting information.
A Lync 2013 Edge server is using external, 3rd party certificates for authentication and encryption of data for federation purposes and external clients connecting to the Lync 2013 environment. I’m using Digicert certificates for this since these work fine in almost all situations.
So I got a message from Digicert to renew my certificate, which I did. Renewed the certificate, same Common Name (CN=access.exchangelabs.nl) and the same Subject Alternative Names entries. The order of the SAN entries was different and so was the Friendly Name of the certificate but this should not cause any problem.
Continue reading Polycom CX600 fail to login after Certificate renewal on Lync 2013 Edge Server
After a (successful) migration from Lync 2010 to Lync 2013 I wanted to decommission the old Lync 2010 servers. In my previous blog post I already explained why the CMS didn’t want to move, but the next issue was challenging as well.
Before removing the last Lync front-end server you have to remove all Lync 2010 objects from this front-end server. Well known issue for example is the conference directory that for some reason always stays at the front-end server.
Continue reading Unable to delete Lync 2010 Front End Pool after migrating to Lync 2013
After upgrading from Lync 2010 to Lync 2013 I was not able to move the CMS from the Lync 2010 front-end server to the Lync 2013 front-end server using the Move-CsManagementServer command. It constantly returned this error:
Jaap Wesselius 
You must be logged in to post a comment.