Lync 2013 – Setting up the Lync Web Scheduler for Lync Meetings

In this how to guide we will run through the requirement and procedure of setting up the Lync Web Scheduler for Lync 2013 Meetings.

Firstly we need to jump into Lync Management Shell and run a command like the below (Note: Change the domain address to match your own. As with other guides im using my lab domain of

$urlEntry = New-CsSimpleUrlEntry -Url “”

$simpleUrl = New-CsSimpleUrl -Component “WebScheduler” -Domain “*” -SimpleUrlEntry $urlEntry -ActiveUrl “”
Set-CsSimpleUrlConfiguration -Identity Global -SimpleUrl @{Add=$simpleUrl} -Verbose

If you run the following cmdlet in your Lync ManagementShell you will the new scheduler is now listed

Get-CsSimpleUrlConfiguration | fl *

Now from a Lync perspective we are complete in the requirements. Next we need to do a few additional steps to be fully complete.

Next Step is to add the following cname record into DNS

Add CNAME record on DNS for scheduler that resolves to your Lync 2013 frontend or Pool

Next Step we need the following subject alternate name as an additional record onto our internal Lync frontend server certificates

Add as an additional SAN on default internal cert using Lync deployment wizard.

Next Step, Either using the Lync deployment wizard run step 2 on all the frontends in your pool, or if you are a UC Pro you can simply run the Lync bootstrapper.exe on all your frontends

Final Step

Lync 2013 – Lync Phone Edition Update version 7577.4455

Yesterday evening Microsoft released an update to the Lync phone edition endpoints.

there are a number of timezone fixes included and the details can be found here.

 Product Version Download
Lync Phone Edition (for Aastra 6721ip and Aastra 6725ip) 4.0.7577.4455 3004836
Lync Phone Edition (for HP 4110 and HP 4120) 4.0.7577.4455 3004838
Lync Phone Edition (for Polycom CX500, Polycom CX600, and Polycom CX3000) 4.0.7577.4455 3004839

Lync 2013 CU4, CU5 Update installer – Windows Fabric Error 1603

Recently the client I’m working on required their Lync 2013 environment to be patched up to date, which usually is not a problem however the support guy doing the patching soon ran against an issue where the CU update worked on all the elements apart from the update of the windows fabric from version 1.960.0 to 1.1008.0.?

A number of consultants looked at this issue, and also we was hearing from other clients, that their patching was seeing the same issue. (also if you google it, many people have see the same issue) yet no one has sorted or found out what the issue is.

Well after raising a PSS (premier MS support call) with Microsoft who themselves couldn’t find the solution. One of the Modality Systems support guys **Kudos to Matt Thompson!!, found the issue and solution.

it was simple in the end, and the issue was due to many incorrect address paths in the environmental module for PSSmodule. **Example of the problematic one below.

%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;D:\PROGRA~1\BMCSOF~1\Patrol3\bin;%systemroot%\idmu\common;%systemroot%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files\Microsoft SQL Server\110\DTS\Binn\;C:\Program Files\Windows Fabric\bin\Fabric\Fabric.Code.1.0

For some reason still unbeknown, the CU patch had trouble in finding the paths required to complete the fabric update successfully, but instead of the installer telling you this, it returns a 1603 error.

Solution is remove all the elements or at least copy them away if you have paths still required.

Then set the variable back to


and the Windows fabric installer will complete successfully.