Planet Collab

❌ About FreshRSS
There are new available articles, click to refresh the page.
Before yesterdaythe UC Guys
  • October 20th 2020 at 14:55

Changing a Microsoft Teams Call Queue or Auto Attendant from a Direct Routing phone number to a Microsoft Phone System number

By Dino Caputo

If you find yourself needing to change a Microsoft Teams Call Queue or Auto Attendant phone number from a Direct Routing to a Microsoft Phone System phone number you need to first remove the Direct Routing number before you can assign the new cloud based Phone System phone number. 

Cmdlet invocation error

You might think that since you are applying the new phone number to the same applicationInstance which represents the Teams resource account that is assigned to the Call Queue or Auto Attendant you can just go ahead and assign the new number and it will overwrite the previous one.  Guess again!

PS C:\WINDOWS\system32> Set-CsOnlineVoiceApplicationInstance   -TelephoneNumber  +12895551212
WARNING: Correlation id for the request is bc9f0767-2c29-426a-a1ea-24ce3bce3bfb
Cmdlet invocation error
     + CategoryInfo          : NotSpecified: (:) [Set-CsOnlineVoiceApplicationInstance], CmdletInvocationException
    + FullyQualifiedErrorId : Error processing cmdlet request,Microsoft.Rtc.Management.Hosted.Bvd.SetVoiceAppEndpointCmdlet
    + PSComputerName        :

After some head scratching on this, I ran the following cmdlet to clear the existing phone number. 

Set-CsOnlineApplicationInstance  -OnpremPhoneNumber  $Null

After waiting a few mins and re-trying the previous cmdlet, the new number is assigned!

Pro Tip

If you noticed that first cmdlet I used initially to set the Phone System number was different than the one I used to remove the existing number then bonus points for you!

You see to assign a Direct Routing number you need to use the Set-CsOnlineApplicationInstance cmdlet along with the -OnpremPhoneNumber parameter which specifies the Direct Routing telephone number. 

When working with Microsoft Phone System Service Numbers, you must use the Set-CsOnlineVoiceApplicationInstance cmdlet and the -TelephoneNumber  parameter. 

Yes, I realize this is confusing which is why I’m writing this to help everyone avoid this situation!  I hope it helps at least one person.  😊

  • June 10th 2020 at 05:13

Turn on and use Call Quality Dashboard for Microsoft Teams and Skype for Business Online

By Dino Caputo

Microsoft have released updated documentation to coincide with the Preview of the Call Quality Dashboard (CQDv3)

CQDv3 improves upon bring access to data in near real time. 

You can find all the details here -

Latest changes and updates

CQD version 3 delivers a near real-time CQD dashboard (latency close to 30 minutes), and uses End User Identifiable Information (EUII), giving admins the ability to zoom in to the user level. There is also and report interactivity to support new scenarios such as:

  • Call Quality by Region:

    • date-by-region
    • aggregated down to hour-by-region
    • specific locations
    • specific subnet
    • impacted user or users
  • Call Reliability/Failure by Region:

    • date-by-region
    • aggregated down to hour-by-region
    • specific locations
    • specific subnet
    • impacted user or users
  • Rate My Call (RMC) by Region: from month-by-region aggregated down to specific locations to users who provide low RMC ratings. CQD v3 also includes verbatim feedback.

  • Helpdesk: available for a specific user on P2P calls or Meetings, or for all participants and call details. Helps identify possible system issues based on network location, devices, or firmware.

  • Client Versions: View the Session and Users counts for each Client Version, or drill down to User names for each client version. Pre-built filters for Product and Client Type help focus the versions to specific clients.

  • Endpoints: Shows Machine Endpoints mapped to Make/Model of the PC/Mac. Shows aggregated quality by Make/Model. Mapping data is uploaded similar to Building data.

Version 3 also provides RBAC support, in case EUII access is not available.

  • October 1st 2019 at 14:19

Skype for Business Server 2019 CU1 Hotfix 1 Release

By Dino Caputo

Microsoft have released hotfix 1 to Skype for Business Server 2019 CU1.  You can find it at

This addresses 2 issues listed below as well as enables Location Based Routing for Skype for Business Mobile clients.

Improvements and fixes in the September 2019 update

This update enables Location-Based Routing to support Skype for Business mobile clients. It also fixes the following issues:

  • September 26th 2019 at 16:09

Updated: Skype for Business Server 2015, Management Pack

By Dino Caputo

Microsoft have released an update to the Skype for Business Server 2015 Management pack for use with System Center Operations Manager (SCOM)

What’s New??

Skype for Business Server 2015, Management Pack contain comprehensive monitoring tools including:

  • End-to-End scenario availability from various locations.
  • Call reliability and quality perceived by real users.
  • Component health and performance.

Active Monitoring Management pack
  • Geographically distributable end-to-end scenario validation for Skype for Business Server 2015 deployments. This includes coverage for internal, remote and branch office users.
  • Increased scenario coverage in areas like AV Edge Connectivity and Exchange Unified Message Connectivity.
  • Enhanced troubleshooting logs to streamline root cause analysis of failures.

Component and User Management Pack
  • Increased reliability monitoring of real end user calls and conferences.
  • Integrated media quality alerts driven from Quality of Experience (QoE) data reported by client applications.
  • Full event and performance monitoring for all Skype for Business Server 2015 roles.

If you don’t currently use SCOM you can learn more about getting started on using it to monitor your SfB Server deployment here -

  • September 9th 2019 at 05:52

Cant install Office Web App Server 2013 on Windows Server 2012R2

By Dino Caputo

You attempt to install Office Web App Server 2013 on a machine running Windows Server 2012R2 that has had all its windows updates applied and get the following error:


Expert TIP:  This issue has come up before and there are a few blog sites that refer to it however the recommended fix has become outdated.  The workaround involves uninstalling a patch so I will show you how to solve this yourself as over time even the example I show you will become dated.

Assuming you have followed the pre-requisites for installing the Office Web Apps Server and have installed .NET 45, the issue is that a newer version of .NET 4.5 has been installed due to server patching.  This effectively blocks the installation of Office Web Apps Server and results in the error above.

Find out what version of .NET is installed on your server

In this case I dumped the version of .NET installed on the server using the following cmd:

Get-ItemProperty -Path “HKLM:SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full” | Format-List Release


This shows that release 461814 is installed.  Some searching shows that this is .NET 4.7.2 – see for full list of versioning.

This means we need to uninstall .NET 4.7.2 before we can install Office Web Apps Server. 

Some further searching shows what KB corresponds with .NET 4.7.2. 

In this case its KB4054566. 

Uninstalling the .NET patch

So we must uninstall that patch, reboot the machine and we should be good to go to install Office Web Apps Server.

Goto Add/Remove programs and select uninstall an update.  Search for KB4054566 and uninstall it and reboot the server


After the restart, if you run the same cmdlet you will see the version is now 378675 which corresponds to .NET 4.5.1. 


You will now be able to install Office Web Apps Server!


  • August 19th 2019 at 10:55

Skype for Business Server 2019 Cumulative Update KB4470124

By Dino Caputo

Microsoft have released the first cumulative update for Skype for Business Server 2019

According the the post the update enables Location-Based Routing to support Skype for Business mobile clients. It also fixes the following issue:

KB ID 12290 and "The evaluation period... has expired" error during deployment by using Skype for Business Server 2019 evaluation software

  • June 6th 2019 at 14:35

Important News about 3DES and Skype for business Online

By Dino Caputo

The original date for the deprecation of support for 3DES support in Office 365 (February 28, 2019) has come and gone..  Microsoft has released updated guidance around this topic.

The 3DES encryption cipher is being retired from Skype for Business Online starting on July 10, 2019. This impacts all commercial and GCC customers who are using the following clients to connect to Office 365:

    • Lync 2010 Windows clients
    • Lync for Mac 2011
    • Lync Phone Edition
    • Lync 2010 Mobile clients

If you are using one or more of the above clients with Office 365, please ensure you take the necessary steps to migrate to newer versions. Below is the list of versions that will work with Skype for Business Online:

  • Skype for Business Click-to-Run - Requires the April 2018 Updates:
    • Monthly and Semi-Annual Targeted – 16.0.9126.2152 and higher
    • Semi-Annual and Deferred Channel – 16.0.8431.2242 and higher
  • Skype for Business 2019 volume license
  • Skype for Business 2016 Desktop Client, MSI 0.4678.1000 and higher, including Basic
  • Lync 2013 (Skype for Business 2015) Desktop Client, MSI and C2R, including Basic 0.5023.1000 and higher
  • Skype for Business for Mac 16.15 and higher
  • Skype for Business for iOS and Android 6.19 and higher
  • Certified Skype for Business Online Phones -  Further guidance is located here.


  • Customer admins will be notified via the Office 365 Message Center during the period of April 17-19, 2019
  • If needed, further updates will be communicated via Message Center to customers
  • There are currently no plans for broad-based public communications via blogs or social


There is no impact to customers who are using on-premises servers. However, Microsoft recommends that customers evaluate their encryption needs and consider upgrading if needed.


3DES aka “Triple DES” is a public encryption protocol first defined via RFC1851 in 1995. It first appeared in software products in 1998. The encryption is now over 20 years old and is now longer generally considered a secure option. Microsoft is responding to customer requests to no longer provide it as an option for encryption.


  1. Microsoft public documentation for deploying the SFB client in Office 365
  2. Microsoft public documentation for technical reference details on O365 encryption
  3. Public information on 3DES -
  4. 2016 InfoWorld article on successful attacks against older versions of 3DES
  5. and run the Score Analyzer to see if you have users or devices that are actively using 3DES.
  • April 18th 2019 at 06:48

Less Clutter coming to Teams!

By Dino Caputo

Do you belong to too many Microsoft Teams?  Well Microsoft has announced that they will be rolling out changes to Teams to automatically move Teams you have not visited in 45 days to a “More” category at the bottom of your left rail in Teams.  This is a great new addition for those that a members of many teams and find the Teams list in the left rail a bit cluttered.  

These changes will begin happening to all tenants in May 2019 and gradually hit all tenants worldwide by end of June.  There is no action required on your part to enable this feature. 

Once this change takes effect in your tenant, you will receive a notice like the one below indicating inactive teams have been moved.

Teams Left Nav

  • April 16th 2019 at 04:46

Skype and Teams April 4, 2019 update

By Dino Caputo

Microsoft have released the following updates for the Skype for Business Windows Desktop Clients

Skype for Business 2016 MSI

Release Date: April 2, 2019

Version: 16.0.4834.1000

This update includes the following fixes (Roll Up KB4462234):




Skype for Business stops responding when receiving a toast notification of an IM or an incoming call in Citrix VDI environment


Skype for Business 2016 doesn't display the "accepted by" information for a Call Queue call that's picked up by one of the call agents


Skype for Business online user can't access the voicemail messages left on Azure voicemail from the Skype for Business 2016 client

Skype for Business 2015 MSI

Release Date: April 2, 2019

Version: 15.0.5127.1000

This update includes the following fixes (Roll Up KB4462207):




Skype for Business stops responding when receiving a toast notification of an IM or an incoming call in Citrix VDI environment


Update the country name from "Macedonia, Former Yugoslav Republic of" to "North Macedonia" for Skype for Business 2015 (Lync 2013)

These fixes are for MSI clients; C2R updates for the O365 channels are documented on the Office 365 client update channel releases page. 

Visit the Overview of update channels for Office 365 ProPlus page for more information about the O365 channels.

  • April 4th 2019 at 08:45

Skype and Teams Feb 25th Updates

By Dino Caputo



What's new in Microsoft Teams


  • Dark theme support!

  • Record and send audio messages.

  • Improved support for iPhone XS Max and XR devices.

  • Bug fixes and performance improvements.


  • Dark theme support!

  • Record and send audio messages.

  • Improved PDF viewing experience.

  • Improved file upload experience.

  • Bug fixes and performance improvements.

  • February 24th 2019 at 07:41

Skype and Teams Jan 14, 2019 Updates

By Dino Caputo

Happy New Year Everyone! 

There’s a lot of new updates for Teams and Skype coming out of the gates in 2019! 


· Microsoft Releases the Service Adoption Specialist Certification

· 3 new ways Microsoft Teams empowers Firstline Workers to achieve more

· Empower your Firstline Workers with new capabilities in Microsoft Teams

· Update! Harnessing machine learning and natural language processing to improve employee productivity

· What’s new in Microsoft Teams – December round up

· Microsoft named a 2018 Gartner Peer Insights Customers’ Choice for UCaaS and UC

· Teams Toolkit is Live - An online flipbook to accelerate adoption

Roadmap updates

· Microsoft Teams for Firstline Workers

· Microsoft Teams Availability for Office 365 Government DoD

Yealink phones now available for Teams

· Software:

· Documentation:


· Microsoft telephony solutions

· Upgrade Microsoft Teams free to Office 365 subscription version

· Call park and retrieve in Microsoft Teams

· Call sharing and group call pickup in Microsoft Teams

· Shared line appearance in Microsoft Teams

End user documentation

· Park a call in Teams

· Share a phone line with a delegate

· Call forwarding, call groups, and simultaneous ring in Teams

Lync Server 2013 CU10HF1 and Skype for Business Server CU8

· Skype for Business Server

· Lync Server 2013

Skype for Business MSI Desktop Client January 2019 Update

· 2016:

· 2015:

  • January 14th 2019 at 12:41

Skype and Teams Dec 1st Updates

By Dino Caputo


Microsoft Graph community call

Teams PowerShell Module

This update includes a bug fix to ensure that owners are added as members when creating the team, allows users with the appropriate permissions to create groups on behalf of another user.
Additionally, at the time of publishing Global and Teams Service administrators can get and set information about all teams in the organization using all modules, and admins do not need to be licensed for Microsoft Teams to run these commands.


New Office icons announced!

Microsoft’s new Office logos are a beautiful glimpse of the future

  • December 1st 2018 at 11:05

Stats Man and KHI released for Skype for Business Server 2019

By Dino Caputo

Two more tools have been released for Skype for Business Server 2019. The Real-Time Stats Manager and Key Health Indicators (KHI) are now available for download here:

Real-Time Statistics Manager

Key Health Indicators

  • November 14th 2018 at 08:32