lørdag den 21. april 2018

LYNC 2013 End of Support

Time flies - and this April of 2018 - all LYNC 2013 server and client version are end of Mainstream Support.

Ending mainstream support for a product means Microsoft will no longer be enhancing that product. What it does NOT mean is there will no longer be fixes for security and reliability issues. Microsoft will continue to issue bug fixes and patches for security and reliability issues.

See lifecycle site here:

When mainstream support ends, this is what occurs:

· Microsoft no longer supplies non-security hotfixes unless you have an extended support agreement

· All warranty claims end

· Microsoft no long accepts requests for new features and design changes

When extended support ends, you can no longer count on any security patches or reliability patches.

Please note this also accounts for:

Exchange Server 2013 and Sharepoint server 2013
More info on this in the Lifecycle FAQ:


What should you do ?

If you are in the progress of migrating to SKYPE for Business, you should continue.

If not you have several options, depending on your situation and business needs.

1. Side by side migration to the upcoming Skype for Business Server 2019 will be supported both from LYNC server 2013 and obviously SFB Server 2015.

2. You could still choose to inplace upgrade your servers to SKYPE for Business 2015

3. To stay in Mainstream support and at the same time upgrade OS on servers to 2016 - do a side by side migration to SFB 2015.

Happy SKYPE'ing

mandag den 26. marts 2018

March CU for SKYPE for Business server released

Howdy Folks - and happy Easter.

A new cumulative patch has been released for SKYPE for Business server 2015.

Version number for Core components is 6.0.9319.516

To find your current patch level run this command on a SFB server

Get-WmiObject –query ‘select * from win32_product’ | where {$_.name –like “*SKYPE for business*”} | ft Name, Version –AutoSize

This Microsoft decided to make this patch only recommended if you actually struggles with one of the issues listed. Or if you wish to utilize Location based routing through mobile devices - which is the only real new feature in this patch.
However it is perfectly safe to install the patch in any case.

Read much more about Location Based Routing in this great article by MVP Mark Vale:

The fixes are theese:

  • 4036626 Missing ApplicationOptions attribute in user object created by New-CsHybridApplicationEndpoint cmdlet in Skype for Business Server 2015
  • 4078589 High memory usage on RtcHost.exe when you deploy Shared Line Appearance in Skype for Business Server 2015
  • 4078588 Can't sign in Skype for Business mobile apps after applying Skype for Business Server 2015 CU6
  • 4078590 Calls to Mac fail when enhanced presence privacy mode is enabled in Skype for Business Server 2015
  • 4078592 Push Notification not working for Skype for Business for iOS in Skype for Business Server 2015
  • 4078587 Voice settings are intermittently reset in Skype for Business on iOS and Android

To download the CU go to: https://support.microsoft.com/en-us/kb/3061064

For installation instructions go to:

As always Happy SKYPE'ing

mandag den 19. marts 2018

Managing Holidays in Response Groups - no problem

If you also find it frustrating to manage RGS Holidays - look no further.

I see alot of customers struggling to get this done, and look to different Powershell GUI's and unsupported addons - but often see issues when moving to a new server version.

So powershell should be your one-stop-shop for this task.

I therefore decided to publish some of the commands that i use, and please note that the below guides are for DANISH holidays, so adjust the dates accordingly :)

For Powershell tips on managing Response Groups in general look to this article:

When you work with the RGS cmd-lets you have to rely on variables.

The Set-CsRgsHolidaySet cmdlet provides a way for you to modify an existing holiday set. (For the most part, this means adding holidays to or removing holidays from the set.) Set-CsRgsHolidaySet is not directly used to make changes to a holiday set. Instead, an object reference is created to an existing holiday set by using the Get-CsRgsHolidaySet cmdlet. (An object reference is a variable that, in this case, refers to an existing holiday set). Changes to the set are made in memory, then the Set-CsRgsHolidaySet is used to write those changes to the actual holiday set. If you do not call Set-CsRgsHolidaySet, then the changes you make will exist in memory only and will disappear as soon as you close Windows PowerShell or delete the object reference.

Lets use this logic to create a new Holidayset containing all Danish holidays for 2018

Please note i sometimes create holidays that run from the previous full business day closing time.
So lets say Easter Thursday is created, the Holiday set could begin already the previous day at office closing hours, but this is individual.

The following examples all run from and to Midnight

First you create the variables by running theese:

$a = New-CsRgsHoliday -Name "Nytårsdag" -StartDate "1/1/2018 00:00:00 AM" -EndDate "1/1/2018 12:00:00 PM"
$b = New-CsRgsHoliday -Name "Påske" -StartDate "3/29/2018 00:00:00 AM" -EndDate "4/3/2018 12:00:00 PM"
$c = New-CsRgsHoliday -Name "St Bededag" -StartDate "4/27/2018 00:00:00 AM" -EndDate "4/27/2018 12:00:00 PM"
$d = New-CsRgsHoliday -Name "Kr Himmelfart" -StartDate "5/10/2018 00:00:00 AM" -EndDate "5/10/2018 12:00:00 PM"
$e = New-CsRgsHoliday -Name "Pinse" -StartDate "5/20/2018 00:00:00 AM" -EndDate "5/21/2018 12:00:00 PM"
$f = New-CsRgsHoliday -Name "Grundlovsdag" -StartDate "6/5/2018 00:00:00 AM" -EndDate "6/5/2018 12:00:00 PM"
$g = New-CsRgsHoliday -Name "Julen" -StartDate "12/24/2018 00:00:00 AM" -EndDate "12/26/2018 12:00:00 PM"

The you need to assign theese holidays to a new holiday set

New-CsRgsHolidaySet -Parent "ApplicationServer:poolname.domain.local" -Name "DK 2018" -HolidayList($a,$b,$c,$d,$e,$f,$g,)

Now you have a complete 2018 Danish Holiday Set ready to use in RGS.

So lets say you are in the middle of March and your boss ask you to make sure that holidays are in place for easter, and you already have your 2018 set in place - no problem - here is how to add an additional holiday to an existing set.
First we make a varialbe containing the new holiday, then we extract and modify the Holidaylist from en existing Holiday Set

$x = New-CsRgsHoliday -Name "Påske" -StartDate "3/29/2018 00:00:00 AM" -EndDate "4/3/2018 12:00:00 PM"
$y = Get-CsRgsHolidaySet -Identity "service:ApplicationServer:poolname.domain.local" -Name "DK 2018"
 $y.HolidayList.Add($x) Set-CsRgsHolidaySet -Instance $y

Same procedure it you wanted to remove a single holiday from the list - in the example i remove Påske from the DK 2018 set

$x = Get-CsRgsHolidaySet -Identity service:ApplicationServer:poolname.domain.local -Name "DK 2018" 
$y = $x.HolidayList | Where-Object {$_.Name -eq "Påske"} $x.HolidayList.Remove($y) Set-CsRgsHolidaySet -Instance $x

Also worth noting that the opening hours also can be created as sets that will selectable in the Repons Group creation process.

$a = New-csRgsTimeRange -Name "Business Hours" -OpenTime "07:00" -CloseTime "17:00"

New-CsRgsHoursOfBusiness -Parent "ApplicationServer:poolname.domain.local" -Name "Business Hours" -MondayHours1 $a -TuesdayHours1 $a -WednesdayHours1 $a -ThursdayHours1 $a -FridayHours1 $a

Thats it for know, hopefully the task of maintaining your company holidays will be less of a headache now.
Happy SKYPE'ing

fredag den 8. december 2017

Office365 Infographic

Kudos to  Matt Wade & icansharepoint.com for creating this EPIC Periodic Table, its really usefull for finding your way around the evergrowing bunch of app's included in your 365 subscription.

Go check it out at http://periodictableofoffice365.azureedge.net/#/periodictable/da

torsdag den 30. november 2017

Bypass prerequisite KB's on SFB2015

Hi all.

Yes i know the subject sounds a bit - well - tricky - however, recently I came to work with a customer that had updated their topology and thus were running the bootstrapper which failed, so something had to be done - for some strange reason the OS patchlevel somehow must have been modified since initial deployment, because the reason for the failure was down to missing prerequisites.

This was the error message

Allright, no problem, lets go and request this hotfix, that is actually a prerequisite for SFB2015 as described here: https://technet.microsoft.com/en-us/library/dn951388.aspx

 So now the fun started, running the downloading MSU file returned this lovely messagebox:

And when checking the Event viewer on the FrontEnd server, we found this:

Oh...2149842967 - I see.... or rather not - when recieving strange numbers always run them against a Hex converter for instance: http://www.binaryhexconverter.com/decimal-to-hex-converter
And then google the result:

This leaded to the site "Windows update agent result codes" Finally something usefull

Oh - i guess not, thanks for nothing. :)

So - what now, well after reading prerequisites for the Hotfix itself, we found this:
“To apply this hotfix, you must first install update 2919355 on Windows 8.1 or Windows Server 2012 R2. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 2919355 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 Update April, 2014 – https://support.microsoft.com/kb/2919355

This KB Also had prerequisites-
“To apply this update, you must have the following update installed on Windows RT 8.1, Windows 8.1, or Windows Server 2012 R2: 2919442 A servicing stack update is available for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2: March 2014″

Here we decided to make a shortcut, and utilize DISM's online servicing function.

DISM is built in to the operating system as documented here: https://technet.microsoft.com/en-gb/library/hh825236.aspx

Initially make sure that KB2919355 and KB2919442 are installed

In powershell, run: Get-Hotfix KB2919442,KB2919355,KB2982006

Then we have to expand the MSU file (the Hotfix downloaded above), because DISM does not support MSU files using online mode.

Create a folder (could be under c:\TEMP) called KB2982006
Now open CMD as administrator cd in c:\temp
and type Expand -F:* C:\temp\Windows8.1-KB2982006-x64.msu C:\temp\KB2982006

Now we can manually add the cab file to the OS using this command:

dism /Online /Add-Package /PackagePath:C:\temp\KB2982006\Windows8.1-KB2982006-x64.cab

Now verify that KB2982006 is in the list

In powershell, run: Get-Hotfix KB2919442,KB2919355,KB2982006

Now rerun Bootstrapper and Oh Joy - it finishes with success.

As always - Happy SKYPE'ing

onsdag den 14. juni 2017

LS Data MCU error on SfB 2015 after May OS Patch

The May 2017 .NET patches introduced a problem in both Skype for Business 2015 and LYNC 2010/ 2013 servers - after the patch the way that .Net handles EKU's in a certificate has changed.

The issue you will find is seen in the event viewer at both all frontends, and on the edge server aswell.

Front End event log every minute, Event ID 41026 followed by 41025:

And on the Edge server you will find:

 Microsoft has confirmed this issue:

Follow the above article to mitigate the problem - either fix the CA template and reissue the Edge server internal certificate OR add this RegKey that will omit this check.

Run the following regadd in a CMD as administrator - that will add this key with the default path of Web conferencing components.

NOTE if your install path is anything but default, change the corresponding path in the reg add cmd.

LYNC Server 2010
reg add HKLM\SOFTWARE\Microsoft\.NETFramework\v2.0.50727\System.Net.ServicePointManager.RequireCertificateEKUs /v "C:\Program Files\Microsoft Lync Server 2010\Web Conferencing\DataMCUSvc.exe" /t REG_DWORD /d 0 /f

Lync Server 2013:

reg add HKLM\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\System.Net.ServicePointManager.RequireCertificateEKUs /v "C:\Program Files\Microsoft Lync Server 2013\Web Conferencing\DataMCUSvc.exe" /t REG_DWORD /d 0 /f

Skype for Business Server 2015:

reg add HKLM\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\System.Net.ServicePointManager.RequireCertificateEKUs /v "C:\Program Files\Skype for Business Server 2015\Web Conferencing\DataMCUSvc.exe" /t REG_DWORD /d 0 /f

After adding the registry key simply restart the Web Conferencing service and the errors will go away - and any related conferencing errors will also reolve.


onsdag den 31. maj 2017

Manage Response Groups in Powershell

When managing Response Groups in SKYPE for Business, the tool needed is the Classic "Manage or edit Workflows" Website - very often customers ask if they can control these options by powershell, or even automate some actions.

This is indeed possible, the powershell way may seem a bit wrinkled - but it works. :)

I will describe the two most commonly used task - that is changing the PSTN forward location for out of Business Hours, and also changing the prompt (audiofile) and Voicemail

First the Process for changing the Audio File and setting forward to Voicemail - if for example you want change the wording from "You are now being forwarded to VoicemailA" - to "You are being forwarded to VoicemailB"

First of you should identify your Response Groups workflows - we need the Identity string for later.

Run this in Powershell:

get-CsRgsWorkflow | ft Identity,Name -auto

If you want to you can now save the current config to a txt file

get-CsRgsWorkflow service:ApplicationServer:FE1.spinne.local/d546f544-1443-1443-1234 > C:\Workflow.txt
In the meantime prepare the new audiofile - keeping requirements in mind:
And then load it into a variable as a new CsRgsAudioFile:
$audioFile = Import-CsRgsAudioFile -Identity "service:ApplicationServer:FE1.spinne.local" 
 -FileName "Audioprompt.wav" -Content (Get-Content C:\Audioprompt.wav -Encoding byte -ReadCount 0)
Now create a new CsRgsPrompt that links to the file.
 (Type the text here if you were instead going to use Text To Speech) 
$prompt = New-CsRgsPrompt -AudioFilePrompt $audioFile
Now Create a new CsRgsCallAction that is the Action the workflow will take when Outside Business Hours.
 In this case two Actions will occur, play a prompt and then transfer the call to voicemail
$action = New-CsRgsCallAction –prompt $prompt -Action TransferToVoicemailUri -Uri "sip:voicemail@spinne.dk"
Now Read the whole workflow into its own Variable
$workflow = get-csRgsWorkflow “service:ApplicationServer:FE1.spinne.local/d546f544-1443-1443-1234”
Now we can customize the workflow by adding the action defines earlier:
$workflow.NonBusinessHoursAction = $action
And finally write the whole thing back to existing workflow - and thereby owerwrtiting existing config.
Set-CsRgsWorkflow $workflow
So a script doing the whole process in one step would look like this:

$audioFile = Import-CsRgsAudioFile -Identity "service:ApplicationServer:FE1.spinne.local" 
 -FileName "Audioprompt.wav" -Content (Get-Content C:\Audioprompt.wav -Encoding byte -ReadCount 0)
$prompt = New-CsRgsPrompt -AudioFilePrompt $audioFile
$action = New-CsRgsCallAction –prompt $prompt -Action TransferToVoicemailUri -Uri "sip:voicemail@spinne.dk"
$workflow = get-csRgsWorkflow “service:ApplicationServer:FE1.spinne.local/d546f544-1443-1443-1234”
$workflow.NonBusinessHoursAction = $action
Set-CsRgsWorkflow $workflow

Now you could save different PS1 files named by name of Workflow, or even take it at step further, 
putting the whole thing into Orchestrator and making e.g. Voicemail destination as an variable.
Also worth noting the power of the New-csRGScallaction cmdlet - read more here:

The next example is more simple, but also more commonly used - it simply changes the PSTN number that the
Workflow forwards to when outside business hours.

$action = New-CsRgsCallAction -Action TransferToPSTN -Uri "sip:+4511111111@spinne.dk"
$workflow = get-csRgsWorkflow “service:ApplicationServer:FE1.spinne.local/d546f544-1443-1443-1234”
$workflow.NonBusinessHoursAction = $action
Set-CsRgsWorkflow $workflow
Thats it :)
Lastly i wanna point your attention to a brilliant script made available on Technet - making it possible to automatically 
cycle between PSTN forwards, for example if you have a IT hotline where We rotate the on call responsibility weekly between the techies on duty. 
That script can be found here:

As Always Happy SKYPE'ing