November 28, 2015

Upgrate Lync Room System to Skype for Business Room System.

From Lync Room System to Skype for Business Room System.

Recently Microsoft announced that Lync Rooms Systems will be updated with the Skype for Business experience. On November 10, Microsoft roll out a Cumulative Update to all existing Crestron, Polycom and SMART Lync Room Systems, updating the user interface (UI) and branding to Skype for Business. The Cumulative Update will either be applied automatically, or manually, depending on the policy set by the IT admin. The update does not change the functionality, but users will see a sleeker, darker design theme, attuned to large-screen viewing.
Skype for Business Room System version 15.14.2
How to update Lync Room System to Skype for Business Room System?
You can roll out Cumulative Update which will update LRS to SRS using either be applied automatically, or manually.

Online update

To install an update on a device that has Internet access, follow these steps:
1.     Log on in Administrator mode by using administrator credentials. To restart in Administrator mode, follow these steps:
a.     In meeting mode, select Options at the pre-meeting screen.
b.     To display a prompt for credentials, select Settings.
c.      Enter administrator credentials at the prompt.
d.     At the Windows logon screen, enter administrator credentials to display the Admin Console.

2.     Click the Web Updates tab.
3.     Under Microsoft updates, select Download from Microsoft Update server.
4.     Under OEM updates, select Download from OEM server.
You can these option when you want to use OEM server URL.

E.g. If you are using Smart SRS-LRS then use below URL as internal server URL Or

5.     To update automatically during the daily maintenance time, select the Automatic updates check box under Update frequency.

6.     Click Apply and Restart to save your changes.

Manual Update:

Note If you change any settings, and you want to apply updates manually, follow these steps:
·        On Lync Room System > Options > Settings >
·        Restart the device, and then log on in Administrator mode by using administrator credentials.
·        Click the Web Updates tab again.
·        Select Check Updates and Install.

·        Click OK to restart the device when you are prompted.
Update will take more hour and system restart multiple time.
Once system updates to Skype for Business Room System it will looks like below:

If you don’t want to use OEM, WSUS or SCCM then simply check mark ”Automatic updates” to get update automatically. Image:

What are the new updates?

·        New User Interface -The image below shows the pre-meeting calendar UI on the console. The console, positioned at the center of the meeting room table, is used to control the meeting room experience. The design changes include a dark background theme, round icons and a round presence indicator, as well as the Skype for Business logo.

·        New Private settings - New Private settings added a feature in this Cumulative Update that allows the room admin to turn the room calendar subject line visibility on or off. This feature is accessed on the console in Admin mode, under Options > Settings.

·        Going forward  Previous - Cumulative Updates added quite a number of new features, such as the ability to directly project from a PC in the room into the meeting, a redesign of the dial pad on the console, steps to add a Skype Meeting and the ability for IT admins to install anti-virus software on the Room System.

·        Resolves an issue where video streams were limited to a maximum resolution of 1280x720 (720p) instead of 1920x1080 (1080p) on some systems.

·        In LRS there was feature like ‘Speaker/mic mute prompt when joining LRS meeting (to avoid in-room echo)’ in Skype for Business Room System this prompt is not there however your Skype for Business client get mute when you join Skype for Business meeting.

Issues that the update fixes:

This update also fixes the issues that are described in the following previously released Microsoft Knowledge Base articles:

Improvements that the update provides:
This update provides the following improvements:
·        Rebrands Lync Room System user interface with Skype for Business logo, colors, and icon design styles.
·        Enables the system administrator to prevent subject line information from being displayed on the meeting calendar.
Additionally, this update includes the following Windows Update software updates:

Thank you.

November 22, 2015

Failed to route to Exchange server

Issue: Unable to leave Voice Mail on Skype for Business (Lync).
Error messages:
Skype for Business and Lync Monitoring report shows following diagnostic error.
1.     15030; reason="Failed to route to Exchange server"
2.     15032; reason="Re-directing request to the destination in 302"
3.     24019; reason="Remote participant mismatch"
4.     1041; reason="Peer server pool is out of service"
5.     1010; reason="Certificate trust with another server could not be established"
6.     15010; reason="Routing to UM for voice mail deposit"
7.     Lync Server shows error event ID: 44022 (An attempt to route to an Exchange UM server failed) and 44009 (Attempts to route to servers in an Exchange UM Dialplan failed).
Most of the above errors tide with certificate. So first place to look is certificate see if certificate is assigned or not, If certificate is assigned then check if assigned certificate to UM and UMCallRouter services are valid or not.
Here are the more troubleshooting steps which you can follow to resolve UM issue:
Check on S4B or Lync Front Server and see if error event 44022 and 44009 are logged.
1.     First step is to make sure, that your partner applications in Skype for Business Server or Lync server and Microsoft Exchange Server are correctly configured. Refer complete process.
Note:  Exchange 2013 Client Access servers running the Microsoft Exchange UM Call Router service and Mailbox servers running the Microsoft Exchange UM service.

a.     Log on to Skype for Business or Lync front Server and run below command on PowerShell and verify the exchange application. E.g. result shows like below.
b.     Get-CsPartnerApplication

c.      Means Exchange is added as partner application on Skype for Business or on Lync server.

d.     You can run same command to exchange server on PowerShell. E.g Get-PartnerApplication

e.     Now test Lync-Exchange connectivity using S4B or Lync Server PowerShell. E.g. command let .

Test-CsExStorageConnectivity -SipUri ""

Test passed.

2.     Second step to check security mode for the dialplan in Exchange Server, if it set to unsecured then change it to "SIP Secured" or “Secured”. It must resolve event ID: 44022 error.

Test Voice mail and check. If voice mail not working then follow below steps.

3.     Check event log on exchange server and see if any specific error shows which causing voice mail issue on Exchange server.

4.     Check S4B or Lync front Server error event log and see what exchange server name flag for error and check that server.

5.     Check Exchange server has correct certificate. Do not use self-signed certificate when you’re integrating UM with S4B or Lync Server.

A.    You can check assigned certificate, services name, thumbprint using below PowerShell command on Exchange server.

Login to exchange server and see what certificate assigned to UM and UMCallRouter services using below PowerShell command. If certificate is not assigned then assign the correct certificate to these services:

Get-ExchangeCertificate -server Exch-server1 | fl subject,services,thumbprint


B.     Check assigned certificate thumbprint and see if this cert is self-signed or corporate CA issued certificate. E.g.

Certificate thumbprint: 139B785E5B63777C43F9BA7885CF7A2424694148  - assigned to UMCallRouter service. However this certificate is self-signed (Issued by name shows same server name instead of corporate CA). See the below image.

C.     Assign new certificate which is issued by corporate CA (you can us public CA certificate as well.) to UMCallRouter and UM service and not self-signed certificate.

Assign certificate using PowerShell command:

Enable-ExchangeCertificate -Thumbprint -Services “UM, UMCallRouter 

6.     In case if you are seeing diagnostic header error like below:
1010; reason="Certificate trust with another server could not be established"

Check assigned certificate to each Exchange services (UM and UMCallRouter) and install correct Root certificate.
You may see below error on certificate information.

7.     Make sure the UMCallRouter component is in set to”Active” state. If UMCallRouter component is set to "Inactive” state then you need to change it to “Active” state.
You can check all components using below PowerShell command.

Get-ServerComponentState -Identity Exch-Server1
You can set UMCallRuoter to Active state using below PowerShell Command.
Set-ServerComponentState -Identity Exch-server1 -Component UMCallRouter -State Active -Requester HealthAPI 

8.     Make sure you exchange UM dial plan is set correct. To create UM dial plan Refer:

9.     Now you can test UM. 

Thank you.