fredag den 11. december 2015

Dec15 SfB Client Security patch

Microsoft has released a Security patch - also including non security related elements - meaning 2 new features

The bulletin can be seen here:

The patch contains a list of bugfixes - amongst them one to fix the annoying bug where it is impossible to paste content copyed from IE .. NICE

  • Lync client doesn't show all the fonts if the computer has more than 1,000 fonts.
  • 3114328 "You need to install the April 14, 2015 update" error message is displayed when you start Lync 2013
  • 3112863 Lync 2013 (Skype for Business) sends corporate error reporting (CER) data after every PC-to-PC and conference call
  • 3112864 Media setup may fail and all media diagnostics information is missing in Lync 2013 (Skype for Business)
  • 3114326 A hyperlink that is copied from Internet Explorer can't be pasted into Lync 2013 (Skype for Business)
  • 3114325 Response Group Service group member notification is displayed frequently in Lync 2013 (Skype for Business)
  • 3112796 Adds a new GPO to control which proxy setting is used when both PAC and manual proxy are used in Skype for Business
  • 3101548 Attendees can't see the shared desktop when they join an online meeting as anonymous users in Lync 2013
And also 2 new features - regarding Single sign on and cloud based discovery - still awaitinh further info on details.

There are a few prereqs for this patch

To get the updates - use windows update - either manually or via approval in WSUS/ SCCM
Or use Microsoft Download center to get them

After upgrade verify your new version numbers in the client

Before upgrade: SfB                               15.0.4771.1001 MSO 15.0.4771.1001

After Upgrade: SfB
15.0.4779.1001 MSO 15.0.4771.1001

Happy SKYPE'ing

mandag den 9. november 2015

SKYPE for Business - RGS Reports - BUG

I have recently seen this issue at 2 different customer sites - both with back-end SQL - (Formerly known as Enterprise Edition)

One was inplace upgraded the other one migrated to a clean installed Skype for Busines side-by-side pool

The Response Group usage report is failing - it is trying for a very long time until finally timeout.

The solution is to recreate the index [IX_SessionDetails_CorrelationId_SessionIdTime] on [dbo].[SessionDetails]

I found this posted on  a technet forum also - and indeed it seems to work fine :)

Run this as a new query against the LcsCDR database in SQL Management Studio

DROP INDEX [IX_SessionDetails_CorrelationId_SessionIdTime] ON [dbo].[SessionDetails]

CREATE NONCLUSTERED INDEX [IX_SessionDetails_CorrelationId_SessionIdTime] ON [dbo].[SessionDetails]
 [CorrelationId] ASC,
 [SessionIdTime] ASC,
 [ReplacesDialogIdTime] ASC,
 [ReplacesDialogIdSeq] ASC,
 [CallFlag] ASC,
 [MediaTypes] ASC,
 [User1ClientVerId] ASC,
 [User2ClientVerId] ASC,
 [SessionIdSeq] ASC,
 [SessionStartedById] ASC,
 [User1Id] ASC,
 [User2Id] ASC,
 [ReferredById] ASC
INCLUDE (  [TargetUserId],

DROP INDEX [IX_SessionDetails_ReplacesDialogIdTime_SessionIdTime] ON [dbo].[SessionDetails]

CREATE NONCLUSTERED INDEX [IX_SessionDetails_ReplacesDialogIdTime_SessionIdTime] ON [dbo].[SessionDetails]
 [ReplacesDialogIdTime] ASC,
 [SessionIdTime] ASC,
 [ReplacesDialogIdSeq] ASC,
 [CallFlag] ASC,
 [MediaTypes] ASC,
 [User1ClientVerId] ASC,
 [User2ClientVerId] ASC,
 [SessionIdSeq] ASC,
 [SessionStartedById] ASC,
 [User1Id] ASC,
 [User2Id] ASC,
 [CorrelationId] ASC,
 [ReferredById] ASC
INCLUDE (  [TargetUserId],

Then wait a few minutes a retry the Response Group usage report.

Happy SKYPE'ing - yours truly :)

torsdag den 24. september 2015

SKYPE For Business - UI BUG - Text size.


Today i discovered a rather funky "bug" in the Skype for Business client.

When the following is true:

  • Operating System is: Windows 7 (32- or 64-bit)
  • Office is 2013
  • Windows Update KB3054791 is installed (included in June 2015 Windows Update)
  • And a user changes the text size in screen preferences to 125%
When the user then makes a call transfer - the screen goes :

Yes thats right - it goes blank :)

The also rather funky fix i discovered was changing the DPI to a manual value of 126% instead of 125%

So go to Control Panel, Appearance and Personalization, Display and select "Set custom text size (DPI)"
I apologize for my screendump being in Danish - but I believe you get the picture :)

Bug has been submitted to MS - so lets hope for a hotfix - i have replicated the error i 3 environments till now.
Still.... HAPPY SKYPE'ing.

torsdag den 10. september 2015

Modify Numbers in SKYPE4B contactcard without absconfig.exe

I recently came across a customer with the need to modify which attributes are sync'ed from AD into the contactcards i SKYPE for Business. However the absconfig.exe (part of ressourcekit) is not yet supported for Skype for Business server 2015 - so what to do ?

Let me walk you through an example of how to modify theese mappings directly in the backend database.

As always when laying hands directly on LYNC / SfB backends databases, proceed with caution :)

I this example we use the IP phone property in AD to store a phonenumber that is unwanted in the SKYPE contactcard.

You start by connecting to your backend SQL with SQL Server Management Studio - and find the RTCAB database.

Then you scroll to dbo.abattribut attribute - and rightclick and select top 1000 rows, to find the value you want to modify
OR use this query:
  FROM [rtcab].[dbo].[AbAttribute]

As you can see from the results, the property we want to modify has the ID 13.
When the property is enabled the "enabled" column will show a "1" 

The you create a new SQL query - and IF nescessary modify the line "where id=13" if you want to disable og enable aother property that "IPPhone"
USE [rtcab]
  FROM [dbo].[AbAttribute]
update dbo.AbAttribute
set Enabled=0
where Id=13
Rerun the select query to verify that the value indeed did change.
Now its time to let SKYPE for Business know that you updated this value.
Open up SKYPE for Business Management Shell - 
First Run update-csuserdatabase cmdlet and then wait app. 15 minutes (keep an eye on the event viewer for ID's 30024, 30027 and 30028
Then run update-csaddressbook - and again wait for event id 62020
Now all data is resynced - and you can clear the address book cache and see the reflected change.

If you are looking for a GREAT in depth article on the addressbook service and sync as a whole - please go to this link by Hans Sleurink;

As always - Happy SKYPE'ing

fredag den 28. august 2015

BSOD on Skype for Business server in-place

BSOD can possibly occure after inplace upgrade from LYNC 2013 server to SKYPE for Business server - when the following is true:

OS is 2012 or 2012R2
Server has or had Antivirus product installed that utilizes a TDI Filter driver
Inplace upgrade is performed from LYNC 2013 Server to SKYPE for business server 2015

BSOD giving Stop Error 0xD1 - caused by TDI Filter driver - a system file used by many different AV vendors - but i only had hands-on with the issue caused by a broken Mcafee client on one server in an enterprise pool.

Confirm that this IS indeed your problem by searching for this specific event ID
Run the following command command from an elevated PowerShell window:
get-eventlog -logname system  | ?{$_.eventid -eq "16001"}

Sadly for 2012 there is no hotfix - issue is being investigated - so best option in my opinion is to create new server from scratch with same name, install prerequisites and run bootstrapper, which also was what i decided to do.

For 2012R2 - there is a hotfix for this specific issue:

In the specific environment where i saw this, the problematic server had a leftover service from a previous Macafee installation named :Mcafee framework service

Still though - Happy SKYPE'ing as always :)

mandag den 27. juli 2015

Smart setup - not so smart afterall.


This Feature works now - just tested it wit ha fresh ISO - and tadaa.. the setup process is doing a "patching" step.

After deploying the first dozen of SKYPE for Business customers mostly Upgrades, but also a couple of greenfields - approximately the last half of them being done POST CU1 release - i finally decided to write this heads-up.
When announced the "Smart setup" sounded great - an exchange 2013-like feature securing that when deploying new servers, you always install the latest and greatest code instead of RTM.

Sadly this does not seem to be the case - YET :)

So when deploying SKYPE for Business - AND you choose to check for updates - still run the CU installer afterwards, to ensure your servers are up-to-date

So although doing:

And the result being:
 Server still needed updated code from cumulative installer.

So please remeber to keep your servers updated.
Still - Happy SKYPE'ing though.

torsdag den 2. juli 2015

How to autohide the "Call Monitor" in SKYPE for Business

A fantastic new feature in my opinion - however still some customers wishes to disable it.
Quote MS:
"Skype for Business 2015 introduced the Call Monitor, which is a window that will be shown, if the main conversation window becomes hidden by other windows. From the Call Monitor you can mute or end the call and in a video call it will also show the video stream. This is a cool feature in itself, but often you need to get back to the conversation window for instance to check an IM or something similar. This is where it get's extra cool with the call monitor. If you double click in the area right to the photo and with the name and call timer, you will automatically get the conversation window shown."

So great feature right ?.

Still want to disable it - well no problem.

Just introduce this Registry Item and it will go away and stay away
Create new DWORD item named CallMonitorEnabled and give it value 0 (zero)

Also worth noting you can actually control the position on the screen - but stay within pixel range of the monitor please :)
Happy SKYPE'ing

onsdag den 1. juli 2015

Call Transfer Bug i LYNC/ SKYPE4b 4727.1001

Recently i discovered a bug at a client site, and replicated it in my lab - and it seems to be consistent.
Sorry about some of my dumps being in Danish, i did not change language when recreating the error - and prioritized this article over language in the dumps. :)

When you use the "Team Call Group" feature - and you want to transfer a call - the members of the Team Call Group will automatically show on top of the "Transfer call to" list in LYNC and SKYPE for Business client, very nice feature

However if you are running 4727.1001 - the LYNC/ SfB client - where the GUI depends on the clientpolicy setting "EnableSkypeUi $True"
This transfer will fail- the client wont even try to forward the call - but if instead you search for the same person manually it transfers fine.

So members that you add here:
Will show up on top when selecting transfer here:

And then nothing happens.
After changing the policy on the server (Requires CU5 on LYNC 2013 server)
set-csclientpolicy -enableskypeUI $True

The the client restarts and is now running SKYPE for Business.

And then the feature works perfectly


søndag den 21. juni 2015

CU1 for SKYPE for Business server 2015 has been released

The first update for SKYPE for Business server has now been released.
No big news, however af few fixes.

Version is 6.0.9319.45 for this CU.

As all of you presumably are running RTM code, no need to check for installed version, but for future reference this is done by running this in powershell:
Get-WmiObject –query ‘select * from win32_product’ | where {$ –like “*SKYPE for business*”} | ft Name, Version –AutoSize 

Her is the KB article for the CU


KB 3063353 June 2015 cumulative update 6.0.9319.45 for Skype for Business Server 2015 and Unified Communications Managed API 5.0 Runtime
KB 3063352 June 2015 cumulative update 6.0.9319.45 for Skype for Business Server 2015, Response Group Service
KB 3061059 June 2015 cumulative update 6.0.9319.45 for Skype for Business Server 2015 (Front End server and Edge server)
KB 3061058 June 2015 cumulative update 6.0.9319.45 for Skype for Business Server 2015, Skype for Business Web Application
KB 3051960 June 2015 cumulative update 6.0.9319.45 for Skype for Business Server 2015, Web Components server
KB 3051958 June 2015 cumulative update 6.0.9319.45 for Skype for Business Server 2015, Core Components

List of roles targeted by this CU:

Download the Cumulative Server Update Installer

søndag den 14. juni 2015

Speaking @ Colabora UC user group event in DK

On the 24. June I will be giving a presentation on the SKYPE for Business upgrade process at the first Colabora event this year - we hope to see a lot of attendees. Please note that presentation will be given in Danish.

Here is the program for the day where 3 great colleagues of mine also will be presenting.
Especially interesting is the entry at 16:05 - which is-- tadaaa sponsor giveaways :)

Agenda in Danish:
Agendaen for dagen er følgende:
13.00 – 13.05 Kort velkomst og intro.
13.05 – 13.50 – Exchange Online Protection – hvordan kommer man igang og hvad er EOP. (Taler: Peter Schmidt, MVP)
13.50 – 13.55 Pause
13.55 – 14.40 – Skype for Business upgrade – hvordan opgraderer vi fra Lync. (Taler: Thomas Juhl Olesen)
14.40 – 14.45 Pause
14.45 – 15.30 – Office 365 og Azure AD identities (Taler: Jakob Østergaard Nielsen)
15.30 – 15.35 Pause
15.35 – 16.05 – Enterprise Mobility Suite (EMS) – Mobile Management og Conditional Access til Office 365 (Taler: Ronni Pedersen, MVP)
16.05 – 16.15 Afslutning og giveaways

More info:
To register:

onsdag den 13. maj 2015

SKYPE for Business upgrade report

Hello - and thanks for stopping by
Last week at Ignite in Chicago I attended the excellent session by Scott Stubbersfield, where he did the TV-kitchen version af a LYNC > SKYPE migration - meaning that the servers were precooked, in order to do the session in 75 minutes. Thats great - and we all knew from the pre-release material that upgrading a pool will take alot of time, anything from 30 minutes to several hours pr FE server.

So i was with great anticipation I prepared and migrated the first real LYNC server at a customer site.

And i must say so far so good - everything running smooth and as expected

I needed a hotfix on one Front-End:

But apart from that it ran perfectly - the part "uninstalling roles" Took exactly 85 minutes - so dont panic if your Front End seems to hang in the process - also note at the button of the upgrade window the current component is displayed.

And i got me another cup of mocca.
Done after app 4 hours - on a single server standard edition pool - with all roles configured.

Then i just ran the start-cspool cmdlet and wathc the routing group placement taking place, remember to run the SfB management shell as administrator - and after that everything worked as planned - brilliant.

I will not do a complete step by step guide, rather link to one done by my friend and colleague J. Dissing, he is really doing a great series on this.

But in short.
Get the topology builder up and running on a new machine, either dedicated mgmt server or just any PC - install from the SKYPE for Business iso.
Then upgrade the pool in topology builder and publish

Then temporarily shutdown the pool by using the disable-cscomputer -scorch command, this is to prevent that services start by themself after reboot if you only used stop-cswindowsservice !

Then start setup on the servers in the pool one by one - obviously before disabling the pool either get a service window OR move the users to a temporary pool while upgrading - NOTE on that, if you choose side by side migration and create additional pool remember to move the CMS role before disabling the 2013 pool.

So my final point is - get on with it - upgrade, get the benefit of full SKYPE integration, serverside conversationhistory and all the fancy new reporting capabilities for call quality monitoring to name a few. :)

fredag den 10. april 2015

Get Ready for SKYPE for business patch.

This coming patch Tuesday the 14. April things will start to change for your LYNC users - se better come prepared :)

Microsoft will release an Office 2013 patch that will enable the SKYPE for business UI as default - this is whether you are running LYNC 2013 or SKYPE for business server.

I really like the new UI - and especially the great new way of handling call forwarding is nice

It is perfectly fine to let the UI change, but most customers would like to make changes like this in a controlled way, and inform/ train the users prior to such.

More info on the planned patch here:

So how do you control the UI

Running LYNC server 2013 - you need the "latest" CU - which isn't really the latest, what you need is December 2014 CU (5.0.8308.857) for Lync 2013 and February 2015 CU (4.0.7577.710) for Lync 2010. (so maybe "latest" is not the best word.)

This reveals a new policy control for SKYPE UI- this is well documented for both LYNC 2013 and LYNC 2010 aswell as SfB server

IF you don't have a patched LYNC environment - luckily this can be controlled through registry alone - but as always I recommend patching to get the latest and greatest updates. for LYNC Server 2013
and for LYNC server 2010

The EnableSkypeUI REG_BINARY can be set to either 01 00 00 00 (True) or 00 00 00 00 (False).  Beats me why they did not go for a REG_dword instead.

So how does the user experience change:
Server versionEnableSkypeUI settingClient experience
Skype for Business Server 2015DefaultSkype for Business
Skype for Business Server 2015TrueSkype for Business
Skype for Business Server 2015FalseUser asked to switch to Lync mode (user can switch to Skype for Business later if you change the UI setting to $true)
Lync Server 2010 or Lync Server 2013 (with correct patches) DefaultUser asked to switch to Lync mode (user can switch to Skype for Business later if you change the UI setting to $true)
Lync Server 2010 or Lync Server 2013 (with correct patches)TrueSkype for Business
Lync Server 2010 or Lync Server 2013 (with correct patches)FalseUser asked to switch to Lync mode (user can switch to Skype for Business later if you change the UI setting to $true)
Lync Server 2010 or Lync Server 2013 (without patches) DefaultUser asked to switch to Lync client experience (user cannot switch to Skype for Business later)

To prepare your users there is a really great awareness and adoption toolkit released from MS, that I really would urge you to take a look at:

Happy SKYPE'ing :)

tirsdag den 17. marts 2015

Skype for Business - What to expect

Skype for Business - We salute You :)

For the last couple of years, often when I was talking to new customers about LYNC I heard the comment - "Well isn't it just like Skype" When explaining LYNC's place in the infrastructure.
And with a serious expression, answering. No No No - and YES.

Where LYNC is a centralized, serverbased, secured, manageable and scalable communications and collaborationsplatform - Skype is "just" a P2P client with video.
This has been true until now

Research from Telegeography projected that at the end of 2011, SKYPE accounted for 33 percent of all long-distance minutes – 145 billion of the total 438 billion minutes. According to Skype CEO Tony Bates, Skype has 254 million monthly active users and is “growing somewhere around 40% year on year.”
So from a marketing perspective I guess, rebranding LYNC was the clever decision.
But enough about names

Now just announced GA will be APRIL this year !! according to the SfB blog
So companys must begin to plan now for the upgrade and/ or deployment process.
Already possible now to download the preview client and try it on for size here:

Here is a little on what we know so far:
  • Video calls between Skype for Business clients and Skype consumer clients, no matter if SKYPE users is using LiveID or SKYPE-ID
  • New VIS (Video interoperability Service) B2BUA with Legacy video conferencing systems
  • Smart Setup - New installation procedure now secures that you always is installing the latest and greatest bits on new servers - so no more RTM trouble revisited.
  • New support for SQL "always-on" technology.
  • New patching process - simplified patching when running multiple frontends.
  • UI totally reworked for users - and also server UI will change.
  • Usability improvements for end-users - a significant improvement on procedure for forwarding calls, which now is much easier.
  • New MQD (Media quality Dashboard)
  • New user feedback feature for quality measurement.
  • Server-side conversation history captures chat conversation history and calls history and present to all clients, including mobile (Requires Exchange 2013)
  • Cold Pool Starts can now be done using one PowerShell Commandlet Start-CsPool.
  • SILK will be the default codec for all Skype for Business and Skype P2P session, with RTA being retained in Skype for Business for backward compatibility.
Upgrade Process:

First of all, you will meet a new upgrade GUI:

Great News for company's that can allow downtime on the LYNC environment, for all Lync 2013 only topologies, the upgrade process is in-place. This means it is an install over process rather than the traditional side by side upgrade / migration process traditionally adopted.

For companies that can not allow pool downtime, side-by-side is still the path to choose.
During the upgrade process you will need to convert the Lync topology into a Skype for Business topology. This is done in the new Skype for Business topology builder by simply selecting your front end servers and choosing to upgrade to Skype for Business server. Once these have been moved in the topology builder the initial publishing of the topology can take many hours. Microsoft say that this is largely dependent of the amount of front end servers in a pool and the amount of users the pool supports. They say that this publishing process can take upwards of 2 hours to complete. During this time, it may seem like the topology builder has crashed, or not doing anything, but the advice is to leave it well alone until it finishes.
Important to note is ALWAYS install latest CU for LYNC2013 before you begin upgrading.

Important to note is that ALL Front End servers in a pool, must be completely upgrade before any services are started.

Upgrading a Standard Edition server to Skype for Business will also upgrade SQL Express on the front-end server to 2014. However, as a pre-requisite this server must be running SQL Express 2012 SP1. The SQL upgrade itself will require a reboot and while the Standard Edition server is upgrading no users will have access to Lync services. So also here plan for downtime.

 Tri-existence is NOT supported, so if you run Lync 2010 and 2013 coexistence then you must first complete the 2010 to 2013 migration and decommission your 2010 Lync servers before thinking of upgrading to Skype for Business. Once you have all your users on 2013, you can use the in-place upgrade process.

 So for a clean LYNC 2013 environment with more than one pool, upgrade can be performed with minimal downtime - by moving users between pools.
So Upgrade from 2013 to SfB could look like this

Upgrade From LYNC 2010 directly to SfB:

In a mixed 2010+2013 environment, upgrade would look like this:
If you don't have the possibility to move users to a temporary pool, use the offline approach.
Important notes:
  • Upgrade all front-end servers in a pool during the same upgrade process.
  • Only utilize coexistence for short periods
  • Once upgrade has started do not use invoke-CsPoolFailover commandlets
  • Don’t start services in mixed mode (i.e. keep all front-end servers offline until last node updated).
  • Do not un-pair pools before upgrade begins.

  • Server support:
    Skype for Business requires the use of Window Server Fabric v2  to provide new HA capabilities within the front-end pool. Windows Server 2008 R2 is still going to be a supported OS for Skype for Business. However this will be the last iteration on this OS.
    recommended is Server 2012R2

    Upgrade prereqs:
  • Install CU5+ latest hotfix to Lync 2013 topology
  • PowerShell RTM version (6.2.9200.0) or later
  • Have at least SQL server 2012 SP1 installed
  • Kb2533623 Windows Server 2008 R2
  • Kb2858668 Windows Server 2012
  • KB2982006 Windows Server 2012 R2

  • So sit back and relax - while waiting for GA
    I am looking very much forward to Ignite conference in Chicago where we can dig deep into Sfb.

    Don't hesitate to contact me for more info.

    mandag den 23. februar 2015

    LS Storage Service event 32054

    Finally this little 'bugger' has been addressed and fixed by Microsoft.

    I always find it hard to explain customers when "ERROR" level events are expected, it smells like teen spirit and buggy code. This is one of these expected errors seen is many LYNC environments, due to the fact a lot of customers are still running Exchange 2010

    But finally this is now in the past.

    The latest and greatest CU for LYNC 2013 has this bug fixed among others

    The KB describing this specific error

    The article describing the CU Feb 2015 in general

    For deloyment please see my other articles on LYNC Cumulative updates, the process is exactly the same - and since Microsoft are so clever to utilize the same link for CU - the links are even reusable - nice :)

    onsdag den 7. januar 2015

    Troubleshooting EWS issues in LYNC 2013

    The EWS not implemented error in LYNC - can be a pain to troubleshoot, because it can be caused by many different factors.
    I will try to give you my experience on troubleshooting this issue.

    First of it is important to understand how the EWS integration works in LYNC.
    Lync uses the following DNS-based discovery method
    http://<smtpdomain>/autodiscover/autodiscover.xml https://<smtpdomain>/autodiscover/autodiscover.xml
    SRV: _autodiscover._tcp.<smtpdomain>

    So wery often I see customers having a perfectly good working autodiscover setup, seen from Outlook because it utilizes SCP in AD - and when LYNC is deployed integration fails.

    So which features are serviced by EWS:
    Conversation History
    Missed Conversations
    Missed Calls
    Voice Mail Playback
    High-Resolution Photos on contacts
    Meeting tab - with meetings from calendar
    Contact Information Presence based on Calendar Information
    And Unified Contact Store

    So EWS is extremely important for LYNC to work correctly
    And therefor DNS based autodiscover needs to be setup corrently.
    Please note that if EWS fails LYNC will failback to MAPI for some features

    Also internal URL for EWS needs to be configured on Exchange - more info:

    When all the above is set correct , and EWS integration still fails - well.. start diggin :)

    First off, lets get an idea of what LYNC actually tries to do.

    Sign in to local pc as the failing user, and with LYNC client running, find the LYNC icon in systray - press CTRL and rightclick icon and select "configuration information"

    Check to EWS URL lines, and EWS status.

    IF EWS not deployed shows up then first thing to check is this reg key:

    Start regedit.exe
    Go to HKLM\software\Microsoft\office\outlook\addins\UCAddin.LyncAddin.1
    Make sure that value of “LoadBehavior” is = 3, if not then change it to 3

    Note: It might be under HKLM\software\Wow6432Node\Microsoft\office\outlook\addins\UCAddin.LyncAddin.1

    Restart LYNC client and wait a couple of minutes.
    If still "not deployed" Then try

    On the Edit menu, point to New, and then click DWORD Value.
    Type OverrideDirectHttpConnection, and then press Enter.
    Right-click OverrideDirectHttpConnection, and then click Modify.
    In the Value data box, type 1, and then click OK.
    Exit Registry Editor.

    At one particular customer this issue was resolved by adding to Local intranet sites in explorer, where we found that otherwise LYNC would not go from autodiscover method one and move on to metohd 2, 3 and so on.

    This article is a work in progress - more troubleshooting tips to come
    To be continued...

    mandag den 5. januar 2015

    LYNC Server 2013 CU10 patches

    The list of included fixes is short for this one - most important is that the Google chrome browser supportability issue introduced with CU9 is now history.

    More info on this issue here:
    Google Chrome no longer supports Lync Web App” message when you join a Lync meeting by using Google Chrome” – as described in KB3025563

    And like always a CU includes generel improvements described by MS as:
    The version number of this update is 5.0.8308.866.
    Detailed patch info here:

    To find out which version your server is running, you could look into "programs and features" or by using get-wmiobject i a LYNC Shell
    My lab is running 831 (October Patch)
    Get-WmiObject –query ‘select * from win32_product’ | where {$ –like “Microsoft Lync*”} | ft Name, Version –AutoSize 

    (For SKYPE for business use this one)
    Get-WmiObject –query ‘select * from win32_product’ | where {$ –like “*SKYPE for business*”} | ft Name, Version –AutoSize 

    It will run for a couple of moments.

    Now for the installation procedure.
    Enterprise edition do as follows:

    Begin by opening a LYNC Management shell and rund the following cmd-let
    It is important that it returns "Ready" - If it returns "busy" then wait 10 minutes and retry. If you see Busy for at least three consecutive times after you wait 10 minutes in between each attempt, or if you see any result of InsufficientActiveFrontEnds for the State value of the pool, there is an issue with the pool.
    The Get-CsPoolUpgradeReadinessState cmdlet also returns information about the upgrade domains in the pool, and about which front end servers are in each upgrade domain. If the ReadyforUpgrade value for the upgrade domain that contains the Server that you want to upgrade is True, you can upgrade the server. To do this, you must follow these steps:

    Stop new connections to the front end server(s) by using the Stop-CsWindowsService -Graceful cmdlet.

    Run the Cumulative Server Update Installer by using the UI or by using a command to upgrade the front end server(s) associated with an upgrade domain.

    NOTE: If you upgrade or update front end servers during scheduled server downtime, you can run the cmdlet in step 2 without the -Graceful parameter. More specifically, run the cmdlet as Stop-CsWindowsService. This action immediately shuts down services, and the server does not wait until each existing service request is fulfilled.

    To download the ”lyncserverupdateinstaller.exe” goto

    The GUI clearly indicates which versions are currently installed afor the installed components and which versions will be installed when selecting "Install updates"

     Now continue with the next server.

    Standard edition do as follows:

    To download the ”lyncserverupdateinstaller.exe” goto
    And run the installer.
    The GUI clearly indicates which versions are currently installed for the installed components and which versions will be installed when selecting "Install updates"

    Backend Database update.
    For an easy way to tell if you need database updates, see this article:

    After you install the update for the Core Components server role on a Lync Server 2013 Enterprise Edition front end server or on a Lync Server 2013 Standard Edition server, the updated SQL database files are dropped to the computer that has the Core Components server role installed. To apply the database changes, you have to run the applicable cmdlets run the applicable cmdlets that are described in step 2.

    Note The -Update parameter is not required when you run the Install-CsDatabase cmdlet to update the Lync Server 2013 databases.

    Lync Server 2013 Standard Edition

    Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn SE.FQDN -Verbose

    Note You must run the cmdlet on the Lync Server 2013 Standard Edition server.
    Lync Server 2013 Enterprise Edition

    You must perform several configuration operations, depending on the kind of Lync Server 2013 Enterprise Edition back end servers that you are using.

    Note If Persistent Chat is collocated (Persistent Chat front end service and back end database are running on the same server), you must run the following command together with the ExcludeCollocatedStoresparameter.

    Note If database mirroring is enabled for your back end databases, we strongly recommended that you use the Invoke-CsDatabaseFailover -NewPrincipal Primary cmdlet and verify that the primary server is principal for all databases before you run the Install-CsDatabase cmdlet.

    Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn FEBE.FQDN -Verbose

    Lync Server 2013 Enterprise Edition

    You must perform several configuration operations, depending on the kind of Lync Server 2013 Enterprise Edition back end servers that you are using.

    Note If Persistent Chat is collocated (Persistent Chat front end service and back end database are running on the same server), you must run the following command together with the ExcludeCollocatedStoresparameter.

    Note If database mirroring is enabled for your back end databases, we strongly recommended that you use the Invoke-CsDatabaseFailover -NewPrincipal Primary cmdlet and verify that the primary server is principal for all databases before you run the Install-CsDatabase cmdlet.

    Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn FEBE.FQDN -Verbose

    Lync Server 2013 Persistent Chat Databases 
    When Persistent Chat Services are collocated with the SQL BE Databases, run the following command:
    Install-CsDatabase -DatabaseType PersistentChat -SqlServerFqdn PChatBE.fqdn -SqlInstanceName DBInstance -Verbose

    Lync Server 2013 Monitoring/Archiving/Persistent Chat Databases
    When Lync Server 2013 Monitoring/Archiving/Persistent Chat databases are deployed on stand-alone SQL databases, run the following command:
    Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn SQLServer.FQDN -Verbose

    Step 3: Apply the Central Management Database update

    Note You do not have to update the Central Management Database in the following instances:
    If the Central Management Store is homed on a Lync Server 2010 Standard Edition Server or Enterprise pool, do not run the Install-CsDatabase -CentralManagementDatabase cmdlets.
    If the Central Management Store is homed on a Lync Server 2013 Standard Edition Server or Enterprise pool that was previously updated with the Lync Server 2013 February 2013 cumulative updates.

    After the Lync Server 2013 Enterprise Edition front end server or the Lync Server 2013 Standard Edition Server backends are updated, run the following cmdlet to update the Central Management Store:
    Install-CsDatabase -CentralManagementDatabase -SqlServerFqdn CMS.FQDN -SqlInstanceName RTC -Verbose

    Note In a coexistence environment that contains both Lync Server 2010 and Lync Server 2013 in which the Central Management Service is located on a Lync Server 2010 pool, do not run the Install-CsDatabase -CentralManagementDatabase cmdlet. If you later move the Central Management Service to a Lync Server 2013 pool, you have to run the Install-CsDatabase -CentralManagementDatabase cmdlet to apply the changes.

    Thats it - your done !