Now that Microsoft has released Skype for Business 2015 it’s time to have a look at the upgrade possibilities. I’m running Lync 2013 Standard Edition in my environment (Lync 2013 Front-End Server, Lync 2013 Edge server and Lync 2013 Mediation server), and lucky enough there is an in-place upgrade possibility. A downtime if required, but when scheduling off business hours this should not be a problem. In this blog post I’ll discuss a step-by-step upgrade from Lync 2013 Standard edition to Skype for Business 2015.
Before the servers can be upgraded to Skype for Business 2015 a number of requirements need to be met, depending of the underlying Operating System:
- Microsoft Lync Server 2013 CU5 (February 2015 update) or above
- PowerShell RTM version (6.2.9200.0) or later
- SQL Server 2012 SP1 or later
- Kb2533623 Windows Server 2008 R2
- Kb2858668 Windows Server 2012
- KB2982006 Windows Server 2012 R2
I’m running Windows Server 2012 R2 on all my servers, so the only updates I have to apply is the Cumulative Update for Lync (to be safe, the May 2015 Cumulative Update (https://support.microsoft.com/en-us/kb/3051949) and the SQL Server 2012 SP1 update.
Continue reading Upgrade Lync 2013 to Skype for Business 2015 Step-by-Step
In an earlier blog post I wrote about Using an F5 LTM Load Balancer for Reverse Proxy with Lync 2013. This works fine for the domains that you have entered when configuring the Lync 2013 iApp in the F5.
If you have multiple SIP domains and thus multiple Simple URLs like meet.contoso.com, meet.fabrikam.com and meet.alpineskihouse.com it doesn’t work out-of-the-box and your Lync client will fail using these URL’s.
To get this working you have to manually configure the Lync Revese Proxy iRule in the F5. To do this you first have to disable Strict Updates, otherwise updating the iRule will fail (for security reasons this makes sense).
When Strict Updates is disabled navigate to the proper iRule as shown in the following figure:
You’ll notice that the initial FQDN’s are configured here, in our example for lyncweb, meet, dialin and lyncdiscover. To get this working for other URL’s just add the other domains and you’re done (and don’t forget the lyncdiscoverinternal name).
When done, don’t forget to enable Strict Updates again, just in case…
Bad news for hosters… or as a fellow MVP said ‘another kick in the nuts for hosters’ but at the Worldwide Partner Conference (WPC) 2014 Microsoft announced the end-of-life for Lync Hosting Pack version 2 (which is based on Lync Server 2013). This was already known for some time, but now it’s official.
Continue reading Lync hosting Pack Discontinued
For a couple of week one of my customer was complaining about little hickups in their Lync 2013 environment. It was working, but every now and then they had these strange little issues. When I moved my own accounts to Lync Online I was not able to federate with this customer anymore so it was time to start investigating.
Continue reading Lync 2013 Replication not working
During a migration project I ran into a nasty issue where I was not able to perform any outbound calls via the mediation server and the SIP trunk. As soon as I entered a phone number in my Lync 2013 client and hit the ‘dial’ button the call failed, immediately.
Continue reading A call to a PSTN number failed due to non availability of gateways in Lync 2013