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

There’s update to delegates and moving meeting rooms from on-premises to SfB online but the most interesting i found was the new four cmdlets adding CsHybridApplicationEndpoint for cloud voice and bots in Lync Server 2013 ! more details below ! One came in CU5 but perhaps theres more now. Noted here in CU5

Download

https://www.microsoft.com/en-us/download/details.aspx?id=36820

More Details on Install

https://support.microsoft.com/en-us/help/4019183/july-2017-cumulative-update-5-0-8308-992-for-lync-server-2013-core-com

Update Version Number

5.0.8308.992

Fixes / Improvements

KB4034279 Enables the "Move-CsMeetingRoom" cmdlet to move a meeting room from on-premises to Online in Lync Server 2013

The update supports administrators to move a meeting room object from a Microsoft Lync Server 2013 on-premises environment to Microsoft Lync Online in Microsoft Office 365 by running the Move-CsMeetingRoom cmdlet.

KB4023332 Delegate can pick up Peer to Peer call on behalf of delegator now in a Lync server 2013 environment

This cumulative update enables Microsoft Lync 2013 users to manage delegates and set up simultaneous ring feature. Administrators (delegates) can pick up peer to peer (P2P) calls on behalf of Bosses (delegators).

KB4023330 Enables you to manage delegates and set up simultaneous ring feature in a Lync Server 2013 environment

This cumulative update enables Microsoft Lync Server 2013 users to manage delegates and set up simultaneous ring feature.

KB4023327 Adds "CsHybridApplicationEndpoint" cmdlets to manage cloud voice or bot applications in Lync Server 2013

This article introduces the following four cmdlets to manage voice or bot applications in a Microsoft Lync Server 2013 on-premises environment:

  • New-CsOnPremApplicationEndpoint
  • Get-CsOnPremApplicationEndpoint
  • Set-CsOnPremApplicationEndpoint
  • Remove-CsOnPremApplicationEndpoint

Lync 2013 Server update screenshot.

Screenshots to follow.

Advertisements

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 the tool, and what we could provide in the form of a tool that would better assist you in troubleshooting connectivity or sign-in issues.

I was deleting my downloads and found a copy of it so thought id share it on OneDrive just in case people want a copy, found it useful or looking for it again.

Microsoft did mention in the comments they may bring it back on the understanding its not managed going forward.

I did find it useful when troubleshooting mobile client sign or just running some checks but i didn’t use it heavily tbh.

64bit Download link is below

https://1drv.ms/f/s!AvBNRjYUuhsvjbtI7W-J2JRe7MtaPw

 

Ive added the documentation from TechNet below just in case it disappears as well

https://technet.microsoft.com/en-us/library/jj907302(v=ocs.15).aspx

NextHop Blog Post on it as well here

https://blogs.technet.microsoft.com/nexthop/2013/02/05/the-new-lync-connectivity-analyzer/

 

Using Lync Connectivity Analyzer in Lync Server 2013

Lync Server 2013

Topic Last Modified: 2014-02-11

Microsoft Lync Connectivity Analyzer helps Lync administrators determine whether the deployment and configuration of their Office 365 or on-premises Lync Server environment meets the requirements to support connections from Lync Windows Store app and Lync apps on mobile devices.

Lync Connectivity Analyzer attempts to connect to Lync Server on-premises or Lync Online by using the same services and protocols that are used by Lync Windows Store app and Lync mobile apps. You can perform the connection tests over your internal network or over an external network that connects to Lync Server or Lync Online. Lync Connectivity Analyzer provides a report with detailed information about each connection step to help you validate your configuration and troubleshoot connection problems.

Lync Connectivity Analyzer tests the following Lync Server components:

  • Autodiscover service

  • Authentication Broker (Reach) service

  • Mobility (MCX) service

  • Mobility (UCWA) service

  • WebTicket service

Lync Connectivity Analyzer tests the configuration of the following other components:

  • Publication of DNS records for Autodiscover URLs

  • Certificates

  • Proxy servers

You can download Lync Connectivity Analyzer from the Microsoft Download Center at http://go.microsoft.com/fwlink/?LinkId=277056.

Checkout my download link above.

 

To Analyze Your Connectivity

  1. Enter the credentials for a valid Lync account (either an on-premises Lync account or an Office 365 Lync account) that will be used by the tool to test the connection:

    • In Lync Account Type, select Office 365 or On-Premises.

    • In SIP URI, enter the SIP sign-in address for the Lync connection in the format user@domain.com.

    • In Password, enter the password associated with this account.

    • In User name (optional), enter a user name if applicable. The user name is also known as the User Principal Name (UPN). If the user name and the SIP URI are the same, you do not need to enter a user name. If they are not the same, enter the user name in the format user@domain.com or domain\user, as appropriate.

    • Network access, choose From inside my organization if you are running Lync Connectivity Analyzer from a computer connected to your internal network. Otherwise, choose External (Internet). Lync Connectivity Analyzer always performs both internal and external tests, but specifying whether you are inside or outside of your own network helps the tool interpret whether certain failures are expected.

    • In Client, select whether to perform connectivity tests for the Lync Windows Store App, Lync Mobile 2010 App, or Lync Mobile 2013 App.

    • Under Server Discovery, select the type of test to perform:

      • If you want the tool to discover the Lync server automatically, select Automatic.

      • If you want the tool to bypass the autodiscover test, or if you know the name of the server you would like to connect to, select Manual using address: and specify the fully qualified domain name (FQDN) of the Lync server—for example, lync.company.com.

  2. (Optional) Under Log File, select the checkbox if you would like to create a log file at the specified path. If logging is enabled, click Clear to clear the log file, click Open to open and view the log file, click Email to open an email message to send the results to your support team (you must manually attach the log file from the path specified).

  3. Click Start.

The following figure shows sample results from Lync Connectivity Analyzer.

Lync Connectivity Analyzer

Screenshot of the Lync Connectivity Analyzer

Components Tested by Lync Connectivity Analyzer

Lync Connectivity Analyzer attempts to discover the Lync server and establish a connection by using the same steps used by Lync Windows Store app and Lync mobile apps. It performs the tests as described in this section.

If Automatic discovery is selected, Lync Connectivity Analyzer does the following:

  • Queries Domain Name Service (DNS) for autodiscover URLs.

  • Attempts discovery by using the secured internal channel. For example, HTTPS://lyncdiscoverinternal.company.com/.

  • Attempts discovery by using the unsecured internal channel. For example, HTTP://lyncdiscoverinternal.company.com/.

  • Attempts discovery by using the secured external channel. For example, HTTPS://lyncdiscover.company.com.

  • Attempts discovery by using the unsecured external channel. For example, HTTP://lyncdiscover.company.com.

If Use the following server discovery address is selected, Lync Connectivity Analyzer does the following:

  • Queries DNS for the server’s FQDN.

  • Attempts discovery by using the secured channel. For example, HTTPS://serverFQDN/.

  • Attempts discovery by using the unsecured channel. For example, HTTP://serverFQDN/.

If Lync Windows Store app is selected under Test the requirements for, Lync Connectivity Analyzer does the following:

  • Verifies that the WebTicket service is available and tests authentication of the Lync account credentials.

  • Verifies that the Authentication Broker (Reach) service is available.

If Lync Mobile 2010 App is selected under Client, Lync Connectivity Analyzer does the following:

  • Verifies that the WebTicket service is available and tests authentication of the Lync account credentials.

  • Verifies that the Mobility (MCX) service is available.

If Lync Mobile 2013 App is selected under Client, Lync Connectivity Analyzer does the following:

  • Verifies that the WebTicket service is available and tests authentication of the Lync account credentials.

  • Verifies that the Mobility (UCWA) service is available.

While performing these tests, Lync Connectivity Analyzer validates the certificates installed on Lync Server, hardware load balancers, proxy servers, and the computer on which you are running the tests.

 

References

https://blogs.technet.microsoft.com/nexthop/2013/02/05/the-new-lync-connectivity-analyzer/

https://technet.microsoft.com/en-us/library/jj907302(v=ocs.15).aspx

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.