Started the Skype for Business Persistent Chat Service
When I then went to manage the service, via the Skype for Business Server Control Panel, I was presented with the following error;
The first area I checked was the event viewer logs, initially the “Lync Server” logs were not showing any issues and were only capturing my starting and stopping of the service.
After reviewing the application log, the following error was being presented;
After seeing this, I updated the permissions, on the MGC databases, under the RTC SQL instance located on my Standard Edition Server and then for good measure, restarted the server – which corrected the issue and allowed me to continue on with my pChat configuration.
For those wondering, Secondary Extension Feature Activation – SEFA 🙂
I am slow off the mark with this one, but for those Administrators that have been using Lync Server 2013 SEFA Util, you will be pleased to know what a Skype for Business iteration has now been released!
So as Day 1 Keynote has now taken place, several additional anouncements have been made; with respect to UC, the most significant being the announcement of Office 365 E5 Licensing SKU…
From a recent summary email;
New Office 365 E5 offering: In October, we will introduce a new premium Office 365 enterprise suite. The new E5 plan will include Cloud PBX, analytics, Power BI, and advanced security capabilities, providing partners with a complete productivity and communications offering for their enterprise customers.
We were teased with the inclusion of an introduction screen in a recent update to Lync 2013 Mobile for Windows Phone, but as of Monday 6th July, version 6.0.1430.0 has been released – Skype for Business for Windows Phone.
At the moment, it seems to only be available for Windows Phone, with pretty much the same features, with an updated UI as it seems, but I will update if and when I find any differences, also as and when the iOS and Android apps are released – Happy Monday!
I hope everyone is well and enjoying their Skype for Business experiences, today’s post is more of a quick tip as opposed to in depth troubleshooting.
The fix will help you with you when troubleshooting at the component level though!
So a colleague of mine was having issues with Unified Messaging integration (which turned out to be a quick fix with OCSUMUTIL.exe), during the troubleshooting process I suggest he used the CLS logging tool.
During a recent engagement, I had ran into an issue updating the firmware version on Lync Phone Edition Devices.
I initially kicked off with checks around DNS, Certificates, Ports and everything checked out but phones would still not update.
Test Devices had been configured correctly (using serial number and one using MAC) – still no joy.
The IIS logs are extremely useful; Jeff Schertz has excellent blog posts on Configuring LPE for Lync and Updating LPE devices which go into reviewing the IIS logs. In summary, it enables you to confirm whether devices are communicating with the device update site running on within the front-end pool, or in our case – NOT.
The Skype for Business Server management experience has introduced some very useful commands and processes. Firstly, the In-Place upgrade process itself, which introduced you to the Smart Setup and the Start-CsPool command, all which on their own reduce the operational loads significantly!
In this post, I will walk you through the simplified process of performing maintenance on your Skype for Business Enterprise Edition Front End Servers.
Now to summarise the overall process, I will let these two images do all the talking, on the left is the Lync Server 2013 Patching Process, on the right the same for Skype for Business Server 2015
Good News – Skype for Business Server 2015 RTM components have been released!!
Bad News for some – VLSC\MSDN Subscription required at the moment 😦
As I haven’t created a walkthrough post yet, I thought there would be no better time to get one on the board and kick off with my experience whilst migrating Lync Server 2013 to Skype for Business Server 2015.
Now an unfortunately a lab demon haunted me (in the form of a Windows Update to Server Technical Preview) on release day (1st May) that completely killed my lab, I did have mirrored databases along with persistent chat and an OWA farm deployed and it would have been interesting to see the Persistent Chat process.
For the purposes of this walkthrough this is what I will be starting off with:
Microsoft released KB on Saturday 2nd May via its FAST PUBLISH process, so clearly there is some urgency behind this patch.
So what’s the issue?
As we know, when migrating from one pool to another, to maintain scheduled conference IDs we leverage the Conference Directory structure (in addition to SQL).
Prior to KB3062801, if administrators leverage the Lync Server 2013 Management Shell to complete the conference directory move to a Skype for Business pool, there is the potential for data to be lost, which will not provide a pleasant experience to your end users.