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 reliability, stability, and performance of Lync Server 2013 web components server which cant be a bad thing Smile

This E9-1-1 issue seems to have occur after applying the November 2016 CU it mentions so recommend you apply this update asap.

This cumulative update actually replaces the Lync Server 2013 November 2016 cumulative update 5.0.8308.974 for Lync Server 2013 web components server.

Download

https://support.microsoft.com/en-us/help/3210185/january-2017-cumulative-update-5.0.8308.984-for-lync-server-2013-web-components-server

Update Version Number

5.0.8308.974

Fixes / Improvements

KB4010079 Emergency call (E9-1-1) fails in Lync Server 2013 To fix this issue, install the January 2017 cumulative update 5.0.8308.984 for Lync Server 2013, Web Components Server.

Lync 2013 Server update screenshot.

Updates to core components, Conferencing Announcement Service, Conferencing Server, Lync Server 2013 and Web Components for this update.

image

Restart Required

After installing i has prompted to restart

Databases

There doesn’t seem to be any database updates required with this CU buts its always worth checking using test-csdatabase.

Post Jan 2017 CU Install

DatabaseName  ExpectedVersion InstalledVersion
rtcxds 15.13.2 15.13.2
rtcshared 5.0.1 5.0.1
rtcab 62.42.3 62.42.3
rgsconfig 5.5.1 5.5.1
rgsdyn 2.2.1 2.2.1
cpsdyn 1.1.2 1.1.2
mgc 1.42.2 1.42.2

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 Microsoft documentation the key feature that most people will be running to get the November 2016 CU is enabling the Mac client with Lync Server 2013.

But PLEASE NOTE when installing the CU there are additional steps that are required to complete the installation so please don’t miss these.

IMPORTANT INSTALLATION STEP

Step 4: Enable the Mobility service

To enable the Mobility service, run the following cmdlet:

Enable-CsTopology

Step 5: Enable the Unified Communications Web API

To enable the Unified Communications Web API (UCWA), you must run the Bootstrapper.exe tool again on all Lync Server 2013 Director servers, Standard Edition servers, and Enterprise Edition front-end servers on which the web components are installed and updated. The command to run the tool is as follows:

%ProgramFiles%\Microsoft Lync Server 2013\Deployment\Bootstrapper.exe

Update Commandlets !!

Also Grieg recommend running Update-CsAdminRole from Lync Management Shell to ensure any new commandlets are updated.

 

Lync Server 2013 November 2016 CU – KB2809243

Version 5.0.8308.974 – Lync update is written as CU8 Hotfix 1 – November 2016

image

What’s NEW !
What’s New !
  • KB 3204553 Lync Server 2013 adds support for Skype for Business for Mac
    • Support for a desktop application type that uses Unified Communications Web API (UCWA). This enables the new Microsoft Skype for Business for Mac client to communicate together with Lync 2013.
    • Support for making emergency calls from web clients, mobile clients , and the new Skype for Business for Mac clients.
  • Note This feature is supported only for non-ADFS deployment.
Improvements and fixes in the November 2016 update

This update improves the experience of moving users in a Lync Server 2013 environment.

For this point i cant find any information on what this means or brings to the Lync Server 2013.

Fix and Improvement Symptom / Cause
I cant find any information to say what this at all.
You cannot see a user’s telephone number (work number) on contact card through a Microsoft Skype for Business mobile client that connects to Microsoft Lync Server 2013.

Note This issue doesn’t occur in desktop versions of Skype for Business.

Assume that you have the Lync Mac Meeting add-in enabled in Microsoft Outlook for Mac. When you click an online meeting link in Outlook, Safari or Firefox is started. Then, you click Join using Lync for Mac or Communicator for Mac, Skype for Business for Mac opens, and you receive the following error message:

You’re not setup to join Skype for Business Meeting.

Consider the following scenario in a Microsoft Lync Server 2013 environment:

  • You’re using an Apple iPhone or Apple iPad that’s running Apple iOS 10.0.
  • You have Microsoft Skype for Business 2015, Lync 2013, or Lync 2010 installed on the device.
  • You try to join a meeting from outside the Skype for Business or Lync app. For example, you tap the Join Meeting link in an email message or calendar appointment in an app other than Skype for Business or Lync.

In this scenario, the device tries to start the desktop version of the website instead of the mobile version. The desktop version won’t try to start the app. Therefore, you can’t join the meeting.
Note The mobile version would try to start the Skype for Business or Lync app and join the meeting, or redirect you to the app store if it can’t join the meeting.

There’s an update for UCMA 4.0 run time – https://support.microsoft.com/en-us/kb/3200080

This notes a Restart of the computer is required.

Restart requirement

You must restart the computer after you apply this cumulative update.

 

When installing i did get prompted to restart

image

 

There seems to be quite a few components that require updating with November 2016 CU Update.

clip_image002[4]

clip_image002

 

Download Link

https://support.microsoft.com/en-us/kb/2809243

References

https://support.microsoft.com/en-us/kb/2809243

https://greiginsydney.com/lync-2013-server-update-november-2016/

https://support.microsoft.com/en-us/kb/2809243

Lync Server 2013 December 2016 CU Update

There’s been an a new Lync Server 2013 CU update release yesterday 13/12/2016 – KB2809243 it seems to have the same KB number as the November 2016 CU and look to be a fix for a detected issue in the November 2016 CU.

It looks like this is a minor CU update and includes an update to resolve an issue with no contacts being resolved on the mobile client after the November 2016 CU as been installed.

Improvements

Link to issue here

Issue Details

You install the November 2016 Cumulative Update for Microsoft Lync Server 2013. When you search for a user by using Lync Mobile, no results are returned. Additionally, an error entry is logged in the Application event log on the Lync Server that contains the following:

Event ID 20003
Source: LS UCWA

Server update screenshot.

Updates to core components and Web Components only from November 2016 update.

image

Databases

There doesn’t seem to be any database update required after Nov 2016 CU update buts its always worth checking using test-csdatabase.

Post Dec CU Install

DatabaseName  ExpectedVersion InstalledVersion
rtcxds 15.13.2 15.13.2
rtcshared 5.0.1 5.0.1
rtcab 62.42.3 62.42.3
rgsconfig 5.5.1 5.5.1
rgsdyn 2.2.1 2.2.1
cpsdyn 1.1.2 1.1.2
mgc 1.42.2 1.42.2

Also install notes still recommend two steps below so dont forget these. If you have applied Nov 2016 CU already then i dont believe you need to do this but it wont hurt to do it again.

If you haven’t installed Nov 2016 make sure you do !

Step 4: Enable the Mobility service

To enable the Mobility service, run the following cmdlet:

Enable-CsTopology

Step 5: Enable the Unified Communications Web API

To enable the Unified Communications Web API (UCWA), you must run the Bootstrapper.exe tool again on all Lync Server 2013 Director servers, Standard Edition servers, and Enterprise Edition front-end servers on which the web components are installed and updated. The command to run the tool is as follows:

%ProgramFiles%\Microsoft Lync Server 2013\Deployment\Bootstrapper.exe

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 came across this.

edge error

I restarted the server first and re ran the Lync deployment Wizard but the error was the same.

I next looked into the text above the error stating

“Microsoft Lync 2013 Server installation or uninstallation requires that Microsoft Visual C++ 2012 x64 Minimum Runtime – 11.0.50727 Package is already installed.failure code 1603”

I checked programs and features on the server and C++ 2012 version 11.0.50727 was missing but i did have a newer version.

image

I decided to install the version it was mentioning which is installed as part of the Lync 2013 installation. I grabbed the Lync 2013 Server media and ran setup.exe which installed the C++ 2012 version 11.0.50727 🙂

image

I then went to step 2 again and the removal was successfully 🙂 Bye Bye old Edge 🙂

Summary

It appeared as noted to install or remove Lync 2013 component you require Visual C++ 2012 x64 Minimum Runtime – 11.0.50727 and newer versions wont allow you to remove Lync components, so if its missing either download and install it or run the Lync 2013 Server media as its the first thing it installs when you deploy Lync 2013 Server.

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 steps i did to update from RTM to SP2

  1. First Check SQL DB Version (Test-CSDatabase is good for this)

clip_image001

2.Download sql 2012 sp2

http://www.microsoft.com/en-us/download/details.aspx?id=43340

3. Stop lync services (stop-csWindowsService)

clip_image002

4. Run sql 2012 update you downloaded

clip_image003

By default it selects all instances

clip_image004

clip_image005

clip_image006

clip_image007

clip_image008

5. Check Database version after install with Test-CsDatabase again.

Woohoo we have SP2!

clip_image009

6. Restart Lync Services

clip_image010

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 Polycom so lets get the latest Aastra LPE update for my lab first.

To start lets just review the current current LPE updates if any are available and approved.

image

Also LPE updates are uploaded and stored in the Lync File Share here we can see there are none.

image

1. From the Lync Updates here select the model of LPE handset that you have HP, Aastra or Polycom and download the latest CU update.

2. Copy update to your Lync Server for example “UCUpdates.exe”

image

 3. Double click and run UCUpdates.exe

image

4.Select Language – for me that english and click next

image

5. select accept if you agree after you have read the agreement of couse then click Next>

6.Select Location to extract update to

image

7. Once the bad boy is extracted click Finish

image

8. After all that you will see one new file “ucupdates.cab”

image

9. Time to get Lync management shell on the go

image

10. We need “import-csDeviceUpdate –identity service:WebServer: –filname

image

11. Press Enter

image

12. Following this lets look at whats happened following this update

image

Lync File Share now has Aastra folder and models

image

more details

image

Following this we STILL need to approve updates and i recommend setting up a test device to test updates first.

13. Lets setup a test device

image

14. Click New select either Global or Site test device

image

15. Add a Device Name as you wish and select identifier type.

For MAC Address enter the MAC address of the LPE device. You can view this can the phone selecting menu system info. Do NOT enter : or – only digits and characters.

image

After the device is specified as a Test Device

image

16. Make a note of the current version of the LPE handset and the new version you are installing. So you can check later.

17. To trigger the update ive tried to reboot handsets before and waited 10 minutes of non acitivity on the handset but overall ive seen mixed results and updates have done it when they wanted so be very patient here and check it later in the day and check by checking the software version and see if it changed.

18. After the test device has been updated go to Device update and approve all the updates. Select all and from action select approve.

image

Approved

image

19. After approving the updates monitor the updates which you can also do from the Lync Monitoring reports.