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.
Friday 1st May was a very good day for the Unified Communications community, particularly if you are pro-Microsoft, as Skype for Business RTM components released to MSDN/VLSC customers. Keep an eye out for a constant steady stream of new information as Microsoft Ignite is also currently underway – so a lot of information will soon be going from NDA to public domain classification – I can already see the blog posts currently in draft mode 😉
Everyone is talking about Skype for Business, why? How does this impact your business?
After the success of our Skype for Business webcast, we have invited Microsoft down to our offices in Stafford to discuss the main changes to you. The event will enable you to discover the changes to your business as well as the overall technical changes. We will be providing a free lunch and a unique networking opportunity with break out session for both public and private sector organisations in the afternoon.
– An in depth look at the exciting new changes and what these mean for your organisation – Breakout sessions for Private and Public Sector including case studies, customer speakers, demo sessions and round table discussions
– A unique opportunity to network with similar sized organisations from both sectors
In order to secure your place, please click on the RSVP link and we will do the rest!
Agenda 09.00 – 09.30: Arrival and refreshments
10.00 – 10.15: Introduction
10.15 – 11.00: Skype for Business what does it mean for your business?
11.00 – 11.45: Guest speaker Leigh Smith – Microsoft
11.45 – 12.30: Guest speaker Gill Furlong – Essex County Council
12.30 – 13.15: LUNCH
13.15 – 14.00: Technical update
14.00 – 14.15: Refreshments and networking
14.15 – 15.00: Breakout sessions – choice between Public Sector or Commercial session
15.00 – 16.00: Refreshments and networking
16.00: Event close
For those that have missed it, Microsoft have now released the Skype for Business client, KB2889923. Although the Skype for Business Server 2015 server components haven’t been released yet, we can still use the new clients against Lync Server 2010 or 2013.
In this post, I will be running through the client experience, when using the new client against a Lync Server 2013 Pool, as well as the experience when changes are made to the client policy switch parameter, EnableSkypeUI.
Microsoft have released a new version to the [Amazing] Lync Network Planning, Monitoring and Troubleshooting guide.
I have recently passed 74-335 Network Readiness Assessment and must say that understanding the Microsoft Network Assessment Methodology along with this guide was absolutely crucial.
Now at v2.3, it seems to have been updated with additional Wi-Fi and QoS Guidance, the following extract has been taken from the download site;
“An updated version of the Networking Guide is now available including the new Microsoft Call Quality Methodology Scorecard for Lync Server. This scorecard should be used to implement the Lync Call Quality Methodology or CQM as outlined in Appendix C. CQM is a holistic way to systematically define and assert call quality based upon the methods outlined in the Networking Guide. CQM divides a Lync implementation into ten discrete areas that impact quality, defining targets and a remediation plan for each one. CQM is a framework to tackle call quality problems – you can modify or extend it to address the particular conditions on your network. Appendix D includes techniques to troubleshoot poor streams that CQM surfaces.
The Networking Guide download now includes the list of Lync Server 2010 and an updated list of Lync Server 2013 KHIs to validate server health, a complete set of CQM queries, and a PowerShell script file to collect KHI data.”