Teams: Check client version using PowerShell

Update May 18th 2022: Now available as Get-UcTeamsVersion in UCLobby Teams PowerShell Module An easy way to check MS Teams version is in the client by going to About > Version: The version will be displayed near the Command Box: The MS Teams client is installed per user and the version is stored in the settings.json file: %AppData%\Microsoft\Teams\ … Continue reading Teams: Check client version using PowerShell

Lync/SfB: Check client version using PowerShell

During troubleshooting we often need to check the installed version, for Lync/SfB Server we already know how to check the installed version using PowerShell: Skype for Business Server Component Version using Get-CsServerPatchVersion Skype for Business Server 2015 Component Version using PowerShell Lync Server Component Version using PowerShell (Windows Registry) On the client we can check the version by using … Continue reading Lync/SfB: Check client version using PowerShell

Lync/SfB Server: Stop Front End service in Starting state

Some of the cases we work have the Front End service in a Starting state: In PowerShell the status is StartPending: We cannot stop it on the Services Management Console: We can go to Task Manager and try to manual stop the service: If that doesn't work we need to Go to Details and End task that is associated with … Continue reading Lync/SfB Server: Stop Front End service in Starting state

SfB Server Component Version using Get-CsServerPatchVersion

The recent November 2015 Cumulative Update for Skype for Business Server 2015 added the Get-CsServerPatchVersion to the available PowerShell cmdlets. This new PowerShell cmdlet replaces the previous methods (Windows Registry and WMI Classes). To get the Skype4B Server Component Version: Skype for Business Server 2015 Component Version using PowerShell We need to make sure that … Continue reading SfB Server Component Version using Get-CsServerPatchVersion

Lync/SfB Server: Test-CsDatabase uses local server to determine ExpectedVersion

While doing some lab testing we notice the Test-CsDatabase uses the local server current update to verify which is the expected version. As an example, in our lab we have pool.gears.lab with January 2014 Cumulative Update and it will return the following: Test-CsDatabase -ConfiguredDatabases -SqlServerFqdn sql01.gears.lab | Select SqlServerFqdn, SqlInstanceName, DatabaseName, InstalledVersion, ExpectedVersion | ft -AutoSize … Continue reading Lync/SfB Server: Test-CsDatabase uses local server to determine ExpectedVersion

Hyper-V: Configure VLAN Trunk on Kemp LoadMaster

One of the Load Balancers that we have in our lab is LoadMaster from Kemp Technologies. We already published an article on how to deploy it: UC Lobby: Deploying Kemp Technologies Free LoadMaster as Lab Load Balancer/Reverse Proxy Why do we need to enable VLAN Trunk? The reason for this is that our lab "router" reached … Continue reading Hyper-V: Configure VLAN Trunk on Kemp LoadMaster

PSScript: Lync/SfB Server Certification Store Validation

In a previous post, we published the checks/validations that we should do in the Certification Store in the Lync/SfB servers. Checks to do in the Lync/SfB Certificate Store We decided to write a PowerShell with all these checks to make it simple to use. The script will be kept in sync with the post, meaning that … Continue reading PSScript: Lync/SfB Server Certification Store Validation

Lync 2013 won’t change to Skype4B when deployed using OCT

We found out that there is a scenario where the icon isn't changed to Skype for Business after the April 2015 update. The Start Menu shortcut was also Lync 2013: While troubleshooting the issue, we discovered that the C:\Windows\Installer\{91150000-0011-0000-1000-0000000FF1CE}\ folder contained two different files with Lync and Skype4B icons: After testing it, we discovered that the … Continue reading Lync 2013 won’t change to Skype4B when deployed using OCT

Changing back to Lync 2013 Icon after the April 2015 update

Some of us were surprised by the Lync 2013/Skype for Business Client update, since this security update also included the Skype4B User Interface. Lync/Skype4B administrators could still use the recently added EnableSkypeUI setting to the Client Policy in order to manage which UI they want the user to see. In our Lync Lab, we have … Continue reading Changing back to Lync 2013 Icon after the April 2015 update

Skype for Business Server 2015 Component Version using PowerShell

There are two methods to get the Skype for Business Server component version: using Windows Registry or the WMI Classes. Both methods were previously published for Lync Server 2010 and Lync Server 2013: Lync Server Component Version using PowerShell (Windows Registry) Lync Server Component Version using PowerShell (WMI Classes) The preferred method is using the … Continue reading Skype for Business Server 2015 Component Version using PowerShell