Incredibly useful post by Mark Vale(@unifiedvale) on how to recover from a corrupt CMS. Please do note the points in the article about making a backup of your Lync environment. You never know when you need it.
In a scenario with Lync 2013 Standard Edition and Enterprise voice, I recently experienced problems with voice calls to PSTN users. All calls would connect normally and last for about 5 mins and 20 sec, and then it looked like the Lync client terminated the call normally(at least thats what the Monitoring reports told me). Continue reading “Lync Enterprise voice calls disconnecting.”→
With the new Windows Server 2012 and the enhanced certificate control, some may have experienced different “strange” error scenarios. Features stop working, and servers are behaving strange.
In Lync, one of the most common situations is when federation stops working. In most cases, you’re able to see Messages in the event log on you Access edge server indicating that something is wrong with the certificates. The Server 2012 has a more strict certificate handling than previous server versions, and the placing of certificates in the certificate store is critical.
Make sure that no intermediate certificates are placed under Trusted Root Certificates. If they are, this will break the certificate structure on the server and strange errors will start to appear in the event logs.
To check if you have certificates in the wrong stores, the following PS command can be run(it will list the certificates with wrong location):
A common challenge when deploying Lync in an enterprise voice environment, is to have the Lync Client behave as close to an “ordinary” phone as possible.
One common “problem” is the busy-on-busy. When an incomming call is routed to a Lync Client already in a call, you would want the caller to get a busy tone. This is, by default, not a function in Lync. To get this behavior, one would have to do it by using MSPL scripting as referred to in this article(not tested, so I don’t know if this actually Works) or use a Third party Application.
This post focuses on some key points I’ve come accross when migrating from Lync 2010 to Lync 2013(causing small delays in progress :)).
Static Routing: One of my first migrations took a bit longer to Complete due to faulty routing on the new Edge server. The static routes were created on the server prior to activating the NIC, which lead to failure to communicate. Once the routes were deleted and recreated, everything worked like a charm.
Office Web apps has to be published to the internet using HTTPS and SSL certificate, otherwise you won’t be able to share Powerpoint’s with your federated contacts. Consider using the same URL for internal and external use because this allows for the SSL certificate to be used on both sites on the IIS. How to publish Office Web Apps server
Mobility login: Problems with Exchange Web Services(EWS). Make sure Exchange Web Services External URL is set correct. Consider using the same URL for internal and external web services.
This script provided by MVP Ståle Hansen is an excellent Resource for setting Exchange URL’s.
External web services URL: Remember to change External Web Services FQDN on the new Front End pool, your web services won’t work unless you do 🙂
Client Version policy: Remember to allow legacy clients to login to the new Lync 2013 server(for Legacy). Default is Blocked for Lync 2010 Clients older than 4.0.07577.4103(CU6, June 2012).
This applies only to Lync 2013 on Windows Server 2012.
After installing Lync on Windows Server 2012, replication between Edge server and Front End stops working. This could be as a result of the stricter certificate handling on Windows Server 2012. Check out this post by Terence Luk on how to fix this problem. Another solution to the problem could be found in this article by Herman Seminiano. Both solutions fixes the problem.
This post will be updated as I discover more points to remember during future migration projects.
So, Publishing Office Web Apps using Forefront TMG:
If you would like to securely publish Office Web Apps to the internet in a Lync environment, you can use a number of solutions. A widely used method is to do this with Microsoft Forefront TMG server, as this solution often is used in connection with Lync web services.
The procedure is to generate a new web publishing rule pointing towards the Office Web App server internal web URL(recommend using the same URL internally as for public publishing eq. https://OfficeWebApps.domain.com in public and internal DNS). The listener would be the same as for Lync web services, and the Office Web Apps URL should be registered with the public IP address of the Forefront TMG server used by the Lync listener.
You would also have to update the excisting SAN certificate used by Lync or create a New Public SSL certificate containing the SAN for the Office Web Apps server(eq. officewebapps.domain.com) and install this certificate on the Office Web Apps Server and the reverse proxy used for internet publishing(the TMG Server).
To test the publishing of the Office Web App server, go to the published URL from an external client and verify that the page displays the XML-output.
If you try testing the Web Publishing Rule from the TMG server, you might experience a “test failed” as shown in this picture.
Even though it seems like the rule won’t work, if you try testing from the internet with the published URL and are able to get the XML-output, you’re good to go.
The test from the TMG server fails because there are no content present in the Virtual web Directory of the Web App server.