In-Place Upgrade from Lync 2013 running Windows Server 2008r2. Services failing to start


Within this blog post is a issue that we’ve seen a couple of times along the way. However finding information on the issue is hard to come by hence this blog post.

So the scenario is.. the client is doing an in-place upgrade from lync 2013 to Skype for business 2015 running on windows 2008r2 OS. **Note: this issue has only been seen on 2008r2 OS..

The In-place upgrade to Skype for Business Server 2015 completed successfully, however when issuing “Start-CsWindowsService” or “Start-CsPool” the Skype for Business Front End Service failed to start with the following error:


it was also noticed that the windows fabric service was also failing to start.
I continued to troubleshooting the following areas:

1. Certificates – Checked for untrusted root certificates using the following PS commandlet:
Get-Childitem cert:\LocalMachine\root -Recurse | Where-Object {$_.Issuer -ne $_.Subject} | Format-List * | Out-File “c:\computer_filtered.txt”
2. Reset Pool Quorum using the following PS commandlet:
Reset-CsPoolRegistrarState –PoolFqdn POOLNAME –ResetType QuorumLossRecovery
3. Ran Install-CsDatabase PS commandlet to ensure backend DB’s was in sync with front end servers – Install-CsDatabase –Update –LocalDatabases
4. Rebooted FE
5. Re-ran bootstrapper.exe (Step2 from the deployment wizard)
6. Confirmed SQL DB’s across all three instances (RTC, RTCLOCAL & LYNCLOCAL) was accessible and online

None of the above helped, the RtcSrv service still failed to start.

After further investigation it would appear the Windows Firewall Service had been disabled. I set the service back to its default setting of “Automatic” and started the service.

Would you believe it, all Skype for Business Server 2015 services would now start!!!

Skype for Business Profile moving to Skype Online – Lync for Mac 2011 ‘adding, removing, tagging’ contacts issue

While im in the mood for another blog post, below is further information around Skype Online and the sketchy Lync for mac automatic supportability.

Ive been moving my profile between Skype for business Onprem and also Skype online and while this is a seamless transition to complete, lync for mac does grumble somewhat with moving your profile.

One of the main pain points of this profile move is the fact that contacts (your buddy lists) stop functioning as you would expect. For example when your profile is moved to SkypeOnline, you cease the ability in adding, moving and tagging of Lync user contacts???

Unfortunately to get this working you need powershell in the backend of the SkypeOnline to invoke some permissions. For some reason putting the profile online causes the UCS *unified contact store to have issues for your -identity

If you run the command get-csuserservicespolicy you should see the USC allowed set as false? so in general you should not be having any issues.?? go figure.!


the solution needed to get you past this issue is another powershell command which is detailed in this link


Once you’ve invoked rollback of your identity, the contacts in the SkypeOnline will start acting as normal.


Iain Smith

Lync and Skype for Mac -moving profile from SkypeOnline back to Skype OnPremise issues


Hello All

Based from experience ,below are details on how to fix your Lync for mac 2011 client or the new Skype for mac client when you have your SkypeFB profile in the 365 cloud then for whatever reason want to bring it back on-premises.

Recently, i’ve been in the Microsoft TAP program for SkypeOnline and more interestingly CloudPBX. Today however i wanted to complete some testing back on the server estate on premises, which to reverse this hybrid profile approach i had is a couple of clicks within the 365 tenant to bring my profile back onprem.

Unfortunately though the Lync/Skype for Mac client does not like this change and without manual intervention will never ever log you back into the client.

So the scenario above then the fix below.

Lync 2011 or Skype for Mac 2016 for MAC

Log out and quit Lync/Skype for Mac.
Go to Finder > press Command+Shift+G > type in /users/<MacUsername>/library >

delete the following files:
Caches >
Internet Plug-Ins > MeetingJoinPlugin.plugin
Keychains > all files beginning with OC__KeyContainer
Logs > Microsoft-Lync-x.log and Microsoft-Lync.log
Preferences >
Preferences > ByHost > MicrosoftLyncRegistrationDB.xxxx.plist
Go to Finder > press Command+Shift+G > type in /users/<MacUsername>/documents > navigate to Microsoft User Data > delete the following folders: Microsoft Lync Data and Microsoft Lync History.
Open Keychain Access from /Applications/Utilities folder.
Delete all keychains startting with OC__KeyContainer.
In your Login keychain, delete all e-mail address certificates.
Finally, empty the Trash.


Thats it you should be now again fixed and able to log back into the client.

Iain Smith




AnyNode SBC Review – TE-Systems


Good Morning All

Recently. I had the pleasure of meeting the guys from Anynode. If your not aware, Anynode are a German based company who provides a software based solution as in Session Boarder controllers which are certified to work with Skype for Business and the predecessors Lync 2010/2013. Interesting of late they have announced that they also can provide telephony capabilities into the new SkypeFB cloud Connector which I’m sure will become of interest to a lot of people.

The underlaying technical architecture is a well guarded secret, however on face value Anynode states their SBC solution can work with any Telcos SIP platform, so with the challenge laid, i set about building the Anynode SBC in my lab to work along side my PureIP SIP trunk.

Below are my findings.

From the start as you can see the interface is one that is a lot different to what we might has seen before (in relation to Sonus, Audiocodes), yet it was one of simplicity. There are a number of things you need to align within the wizard build before the wizard takes over and completes, however if you have all the necessary FQDNs & IP addresses etc at hand literally within 10 minutes you can be up and running with calls traversing between your SIP carrier and Skype for Business.

Anynode 1wizard 2
wizard 3

In my lab i wanted to ensure that the SBC can do all the things a hardware appliance is capable of, meaning smart routing, DDI transformation, cause code rerouting, message  header manipulation etc etc. so with this in mind i started to tweak my configuration.

Back at the main page, on the left hand pane you see your configuration from the wizard on the select down tabs and from there you can start to get cute with your configuration to make it work exactly how you want.

mainconfig 4

Other things of interest are..

If the Server running the Anynode software is being hammered with traffic or maybe there has been a dodgy OS patch which is causing the CPU to spike, Anynode has built in resilience to specify CPU load conditions and for the software to make a judgement on what happens next, whereas more traditional hardware appliance will try and soldier on and in turn provide poor audio quality calls due to the CPU ramping.

My Synopsis on Anynode the company and also the SBC software

The guys at Anynode could not be more forthcoming with help and assistance and are willing to provide time to suit the customer to get the Software configured to your requirement.

The SBC software is excellent in truth and for any customer looking for a SIP only solution and maybe doesn’t have the outlay of money to purchase a physical appliance, then running Anynodes SBC on a VM would be a perfect option. Like i say there has been nothing lacking i can see within the software which you would get from a Sonus/Audiocodes hardware based solution.

Its worth mentioning in terms of physical\Virtual hardware, the footprint is minimal and the software is happy running on a small subset of CPU and RAM.

All in All, i really like this solution and at the time of writing in the UK the likes of Audiocodes and Sonus don’t have a low end/user software based solution which in some respects opens the door for a company like Anynode to provide an offering.

If you are interested in reviewing, trailing or even speaking to the guys at Anynode about something you are trying accomplish within your company then they are more than happy to assist.

Details are below

Contact Nick DiCiaccio on Email :



Lync for Mac 2011 ver. 14.3.3 -instability and balloon Spinning hanging


Hello All

Recently i have suffered from a real pain in the ar5e issue with Lync for Mac 14.3.3

Backtracking to February when 14.3.3 arrived as GA, i noticed that my Lync for mac client became really unstable with random crashes and general instability of the client. As this only become present with the 14.3.3 update, i downgraded back to the 14.1.1 build which brought the client back to a workable/normal state. At the time of going to 14.3.3 i had also been running a few Microsoft UC TAP/beta programs and i was thinking that it could be these clients causing the issues and instability i was seeing.

So, i decided that it was time for a new OSX rebuild of my machine and to get a good clean image to build upon. Following the OSX installation, i loaded Office 2016 for mac, and set my profile correctly before installing Lync for Mac 14.3.3 **without any TAP/Beta installations!..  AGAIN i saw the same random instability issues including the spinning beach ball cursor (not responding) from the Lync for Mac client. Again i ran with this setup for a few days, but then decided that the client was physically unworkable and was left again with no choice but to downgraded back to 14.1.1 which like before worked flawlessly.

This now led me to believe (in error) that it was either el-capitan OR office 2016 for Mac. ? so i set about investigating both with more several rebuilds… On builds i did notice that applying my profile before Office 2016 meant the issue was still seen.??? arghh.

One common dominator though was on a fresh rebuild of OSX THEN the installation of Lync for Mac 14.3.3 without Profile and Office 2016 would work perfectly and that the issue would only arrive back when i installed either Office 2016 or on the configuration of my profile (dock, power setting, screen saver etc).

Anyhow after a far to long and drawn out process of elimination, i finally cracked the riddle of the problem, and this being……

There is a bug in Lync for Mac 14.3.3 which is nothing to do with El-Capitan OR Office 2016  but was in fact the use of a OSX profile picture greater in mb size of 5mb.! IF you changed your picture to > greater than 5mb you will start to see instability of the Lync for mac client 14.3.3. (this didn’t happen in 14.1.1).

Simple resolution was to downgrade the profile picture to less than <5mb and the client became workable using 14.3.3 **note: this has been raised with Microsoft.


Skype for Business – Moving the Fileshare Error


Hello All

This blog post is to share the experience seen with issues around moving the Skype for Business fileshare from one windows server to another.

Its worth noting that this was a real life issue seen on a clients site so elements of the image are blackout to hide the clients identity.

Below is the details and scenario seen

I followed this set Microsoft procedure to move the actual file share:

  1. Create the new file share and configure the correct permissions;
  2. Stop all Skype for Business services across all FE’s in the Enterprise pool;
  3. Configure topology to include new file store and associate with the Enterprise pool before publishing changes;
  4. Run bootstrapper on all FE’s;
  5. Copy data from old file share to new one using robocopy;
  6. robocopy \\OldServerFQDN\OldShare \\NewServerFQDN\NewShare /S /R:10 /W:10 /XF Meeting.Active /MT;
  7. Start the Skype for Business Enterprise pool using Start-CsPool commandlet;

After following each of the steps about, all services started successfully however after a basic health check it appeared that there was an issue with the backup service (pool pairing), see below:Image1


So go figure….?

My next steps was to de-configure the pool pairing and re-configure it, however the error same occurred.

I then proceeded to reboot each Frontend in turn, same error occurred after rebooting all Frontend’s.

Everything looked good at this point in terms of File Store association with the Enterprise pool. The old file share was not referenced anywhere.


The fix was to move the WebServices* directory on the old file share into a temp directory, very bizarre as the old share was not referenced anywhere in Topology/PowerShell. 

After moving this directory and restarting the backup service again, all the errors cleared and the backup service returned to normal state.


Skype for Business CMS Pool Failover Issue


Good Morning All

Last week, while working on a clients deployment one of the Modality team came across a rather interesting issue around failing over a Standard Edition SkypeFB pool pairing.

What started out to be a simple failover test became a monster of an issue without any real good reason. The situation was when the pool faileded over the CMS , it became kindof orphaned in the process with the secondary front end not becoming the master and also what was the primary releasing itself as the master. Its also worth confirming that the procedure to failover was completed without error and issue and it was only when the services restarted that we saw the issue. **The Master replicator service would not start.

As this was the first time of seeing such an odd issue, we referenced the usual channels and came across Mark Vales blog almost detailing word for word the same situation/issue.

Doing some investigation we could see that the CMS was no longer attached to the primary frontend and also the secondary frontend, yet the SkypeFB client was happily working??. Also running powershell commands we could also see that the replication was now false across all the frontends/edge.


We tried a number of steps to resolve this issue including the ones Mark detailed in his blog, without success. It seems this issue can morph itself into many factor.

We tried to failback to the primary without success and got the following error


And when we attempted to restart the services we were getting the following error


Also we went to the extent of deleting the xds/lis databases and reinstalling them and importing the backup we had onto the clean databases. Still we was seeing the same errors.

The solution that worked for us was a simple one really.

Uninstall-CsDatabase –CentralManagement


Install-CsDatabase –CentralManagement

and restoring CMS from backup did the trick.