Lync Server 2013 July 2017 CU – Move Meeting Rooms, Delegate updates and adds CsHybridApplicationEndpoint cmdlets!

There's been a new Lync Server 2013 July 2017 CU update 5.0.8308.992 released 10/07/2017 and its KB 2809243. Perhaps this is CU9. https://support.microsoft.com/en-us/help/4019183/july-2017-cumulative-update-5-0-8308-992-for-lync-server-2013-core-com The CU adds the following KB4034279 Enables the "Move-CsMeetingRoom" cmdlet to move a meeting room from on-premises to Online in Lync Server 2013 KB4023332 Delegate can pick up Peer to Peer call … Continue reading Lync Server 2013 July 2017 CU – Move Meeting Rooms, Delegate updates and adds CsHybridApplicationEndpoint cmdlets!

Copy of Lync Connectivity Analyzer Download link

A fairly recent announcement was that the Lync Connectivity Analyzer tool has been retired noted below and in a blog post from Microsoft here As some of you may have noticed, the Lync Connectivity Analyzer tool has been retired and is no longer available for public download.  We are interested in hearing how you used … Continue reading Copy of Lync Connectivity Analyzer Download link

Lync Server 2013 January 2017 CU – Emergency calls Fix

There's been a new Lync Server 2013 January 2017 CU update 5.0.8308.984 released 18/01/2017 looks to be a critical one for Emergency calls with E-9-1-1 fix ! The CU looks to address issue with Emergency Calls for E-9-1-1 so this may be of high interest to get deployed asap. It also notes It improves the … Continue reading Lync Server 2013 January 2017 CU – Emergency calls Fix

Lync Server 2013 November 2016 Cumulative Update 8 HF 1

Saw this last week and got some time to read up on the CU and wanted to wrote a quick summary and video of CU install process. Whilst researching this CU i came across Grieg's blog post which i highly recommend reading  here and also Guy Bachars blog here On review on Grieg's post and … Continue reading Lync Server 2013 November 2016 Cumulative Update 8 HF 1

Lync 2013 Edge Server – Error returned while installing Server.msi (Feature_Server_Edge), code 1603

Came across this error last week whilst decommissioning an Lync 2013 Edge Server. I had removed the Edge server from topology, published previously, Edge had received CMS update and knew it was removed from the topology and was running step 2 of the Lync deployment wizard to remove the Edge role from the Server and … Continue reading Lync 2013 Edge Server – Error returned while installing Server.msi (Feature_Server_Edge), code 1603

Lync 2013 Server – SQL 2012 Express Service Pack 2 Manual Install

In preparation for your Skype for Business InPlace Upgrade remember you need have update your SQL Express 2012 to at least SP1. You need to do this on all Lync servers so you may be busy if you have updated already. By default Lync 2013 installed only SQL 2012 Express with no SPs. Heres the … Continue reading Lync 2013 Server – SQL 2012 Express Service Pack 2 Manual Install

Lync Phone Edition apply cumulative update

Been meaning to write this down for while as I can never remember fully. So wanted to blog this to record it mainly for myself. By default Lync provides no Cumulative updates for Lync Phone Edition Devices you can check from the Lync Control Panel as shown below. in my lab i have aastra and … Continue reading Lync Phone Edition apply cumulative update

Skype for Business: Hardening The Backend Databases

Great Blog Post from Mark on Skype4B / Lync Server Database hardening 🙂

Mark Vale Consulting Blog

We all know that Lync uses SQL server to store it’s backend databases such as the Central Management Store. However, do we pay much attention as to how the Lync Front End servers connect to the database? Let’s look at a scenario.

You have 3 front end enterprise edition servers in a single pool. You are using SQL server 2012 as a backend database server for the Lync databases. This SQL server has multiple instances running other LoB applications. The installation of SQL was completed only accepting the default settings from the SQL installer.

So what security implications does this have on your SQL estate? To begin with SQL will use the static TCP port of 1433 to allow external connections access to the default instance (usually MSSQL) and TCP port 1434 for the SQL Browser service. The SQL browser service is used to allow connections to databases from external…

View original post 685 more words