Media Optimization for Microsoft Teams

The Media Optimization for Microsoft teams leverages the (Web Real-Time Communication) WebRTC features and offloads the audio and video processing from the virtual desktop to the client machine. 

I’ve summarized the steps below, which would help you to understand what is required from the VMware’s standpoint to configure Media Optimization for Microsoft teams.  

The brief note from VMware TechZone article below explains how this is achieved using the Horizon Client for Windows 2006 and Horizon Agent 2006 version. 

Text

Description automatically generated

The feature to support Media Optimization for Microsoft teams was introduced in Horizon Client for Wndows 2006 and is also incorporated in Horizon Client for Windows 5.5

Therefore, for configuring media optimization for Microsoft teams, the Horizon client version should be minimum at Horizon Client for Wndows 2006 (compatible with Horizon 8/2006) or at Horizon Client for Windows 5.5 (compatible with Horizon 7.13)

Table

Description automatically generated

High level steps to configure the Media Optimization for Microsoft teams

  • Horizon platform should be running on Horizon version 7.13 or Horizon 8 (2006 – as per the new versioning standards)
  • Download the Horizon Client for Windows 2006 or Horizon Client for Windows 5.5 and during the installation, select custom installation and scroll down to select “Media Optimization for Microsoft teams”
  • After the installation, reboot the Windows Client
Graphical user interface, text, application, email

Description automatically generated
  • The code in the Horizon Agent is also installed by default, but it is controlled with a GPO, which is not enabled by default. As stated in the email below, the media optimization for Microsoft teams is not supported in Horizon agent 7.12 or earlier. So, the Horizon agent version should be minimum at 7.13 or Horizon Agent 2006
  • Download the Horizon GPO bundle and use the ADM template files to enable the relevant GPO.  
  • The GPO can be enabled using the Group Policy Editor by navigating to Computer Configuration > Administrative Templates > VMware View Agent Configuration > VMware HTML5 Features > VMware WebRTC Redirection Features > Enable Media Optimization for Microsoft Teams. After setting this policy, you must log off from the Horizon desktop for the GPO policy to take effect.
  • Besides, the below GPOs under the VMware WebRTC Redirection Features can be configured based on the requirement.
Graphical user interface, text, application, email

Description automatically generated

Keys points from the Microsoft Article  Microsoft Teams for Virtual Desktop Infrastructure

  • You can deploy the Teams desktop app for VDI using a per-machine installation or per-user installation using the MSI package. Deciding on which approach to use depends on whether you use a persistent or non-persistent setup and the associated functionality needs of your organization
  • In a dedicated persistent setup, users’ local operating system changes are retained after users log off. For persistent setup, Teams supports both per-user and per-machine installation.
  • In a non-persistent setup, users’ local operating system changes are not retained after users log off. Such setups are commonly shared multi-user sessions. VM configuration varies based on the number of users and available physical box resources.
  • With per-machine installation, automatic updates is disabled. This means that to update the Teams app, you must uninstall the current version to update to a newer version. With per-user installation, automatic updates is enabled. For most VDI deployments, Microsoft recommends to deploy Teams using per-machine installation.
  • To update to the latest Teams version, start with the uninstall procedure followed by latest Teams version deployment.
  • For Teams AV optimization in VDI environments to work properly, the thin client endpoint must have access to the internet. If internet access isn’t available at the thin client endpoint, optimization startup won’t be successful. This means that the user is in a non-optimized media state.

High level steps to install Teams on VDI

  • The minimum version of the Teams desktop app that’s required is version 1.3.00.4461. (PSTN hold isn’t supported in earlier versions.)
  • Install the MSI to the VDI VM by running one of the following commands:
  • Per-user installation (default)
msiexec /i <path_to_msi> /l*v <install_logfile_name> ALLUSERS=1
 
This process is the default installation, which installs Teams to the %AppData% user folder. At this point, the golden image setup is complete. Teams won't work properly with per-user installation on a non-persistent setup.
  • Per-machine installation
msiexec /i <path_to_msi> /l*v <install_logfile_name> ALLUSER=1 ALLUSERS=1

This process installs Teams to the Program Files (x86) folder on a 64-bit operating system and to the Program Files folder on a 32-bit operating system. At this point, the golden image setup is complete. Installing Teams per-machine is required for non-persistent setups.

Graphical user interface, text, application

Description automatically generated

IMP NOTE – For beta testing, VMware built support for Microsoft Teams into the Horizon Client for Windows versions 5.3, 5.4, 5.4.1, 5.4.2, and 5.4.3. If you enable the optimization GPO in the virtual desktop, these clients, although not officially supported, will begin implementing offload. The bugs we found in these clients during beta testing are fixed in Horizon Client for Windows version 2006 or later, which is officially supported and which VMware recommends using.

Procedure to check if Microsoft teams is running in optimized mode

A user can check if Microsoft Teams is running in optimized mode, fallback mode, or natively (no optimization) in the virtual desktop. In the top-right corner of the Microsoft Teams interface, click the user icon and navigate to About > Version to see a banner under the user icon describing the Microsoft Teams version and pairing modes:

·         Optimized – If the banner shows VMware Media Optimized, the Enable Media Optimization for Microsoft Teams GPO is enabled, Microsoft Teams is running in the virtual desktop, and audio and video have been offloaded to the client machine. 

·         Fallback – If the banner shows VMware Media Not Connected, then Microsoft Teams is running in fallback mode. In this mode, the Enable Media Optimization for Microsoft Teams GPO is enabled, and Microsoft Teams has tried to start in optimized mode, but the version of Horizon Client being used does not support Microsoft Teams optimization. Audio and video from Microsoft Teams is not offloaded to the client machine. Fallback mode has the same limitations as optimized mode. When you make a call in fallback mode, you see a warning message on the call:

Your device doesn’t support connection via VMware. Audio and video quality may be reduced

·         No optimization – If the banner does not show VMware text in the message, the Enable Media Optimization for Microsoft Teams GPO is not enabled. Audio and video from Microsoft Teams is not offloaded to the client machine.

The VMware TechZone article Microsoft Teams Optimization with VMware Horizon covers the detailed procedure to configure Media Optimization for Microsoft teams and Microsoft article Microsoft Teams on VDI covers important considerations and procedures from Microsoft’s standpoint

vRealize Log Insight Upgrade from 4.8 to 8.1

Important note about the change in architecture

The vRealize Log Insight 4.8 is based on SLES (Suse Linux Enterprise Server), whereas vRealize Log insight t 8.0 and higher versions are based on Photon OS. Because of this, as compared to the earlier version, there is a change in the architecture of the vRealize Log Insight 8.0 appliance operating system  in terms of number of partitions and the size of partitions.

Before upgrading from an SLES-based vRealize Log Insight 4.8 to a Photon OS based vRealize Log Insight 8.0, ensure that the root partition has enough space for the upgrade. If the root partition is smaller in size, for example, 8 GB, increase the disk size to 20 GB, so that the root partition size increases to 16 GB. You must increase the disk size for each node that has a root partition with less space. The KB article 76304 provides detailed steps to increase the root partition size.

Prerequisites and important upgrade notes

  • As per the Supported Upgrade Path, direct upgrade to vRealize Log Insight version 8.1.1 is supported from vRealize Log Insight version 4.8, 8.0 or 8.1.0
  • Confirm the interoperability / compatibility of vRealize Log Insight 8.1.1 with other VMware components in the environment using the VMware Interop Matrix.
  • Before starting the upgrade from a vRealize Log Insight 4.8 cluster to 8.1.1, verify that each node has enough free space in the root partition. For more information, please refer KB article 76282. The KB article 76304 provides detailed steps to increase the root partition size.
  • As stated in the KB 76304,  please ensure to remove any snapshots before you attempt to increase the disk size to support the larger root partition. Please take the snapshot immediately after increasing the virtual disk size and before increasing the root partition size from within the operating system.
  • As per the KB 76067, upgrade to vRealize Log Insight 8.0 fails when default gateway is missing. On each of the vRealize Log Insight Appliance, login as root and check the /etc/sysconfig/network/routes and /etc/sysconfig/networking/devices/ifcfg-eth0  file to confirm if the entry for default gateway is configured correctly. If not, please configure the default gateway as suggested in the KB 76067. Please ensure that you have a latest snapshot of the vRealize Log Insight appliance in appliance before making changes to any of the configuration files.
  • The sshd customized service configuration (/etc/ssh/sshd_config) resets to its default when you upgrade the SLES-based vRealize Log Insight 4.8 to the latest Photon-based vRealize Log Insight. As a workaround, save the /etc/ssh/sshd_config configuration before upgrading and then reconfigure manually after upgrade.
  • When performing a manual upgrade, you must upgrade worker node one at a time. Upgrading more than one workers at the same time causes an upgrade failure. When you upgrade the master node to vRealize Log Insight 8.1.1, a rolling upgrade occurs unless specifically disabled.
  • Upgrade must be performed from the master node’s FQDN. Upgrading with the Integrated Load Balancer IP address is not supported.
  • vRealize Log Insight does not support two-node clusters. Add a third vRealize Log Insight node of the same version as the existing two nodes before performing an upgrade.
  • Create a snapshot or backup copy of the vRealize Log Insight virtual appliance.
  • Ensure that you have the correct admin and root credentials for the vRealize Log Insight appliance master and worker nodes

License requirements

  • As per the vRealize-Suite-2019-Release-Notes, the vRealize Log Insight 8.1 is part of the vRealize Suite 2019. So, if you are using vRealize Suite licenses, ensure to upgrade your license key to vRealize Suite 2019. Please make a note of the existing license key before upgrading the vRealize Suite license key to 2019. The KB article 2006974 provides detailed steps to upgrade a license key using my VMware portal.

Upgrade procedure

  • Login to the vRealize Log Insight master node user interface using the admin credentials.
  • Navigate to the Administration tab and under ‘Management’, click on ‘Cluster’
  • Under ‘Cluster’, click on ‘UPGRADE CLUSTER’
  • Click Upgrade from PAK to upload the upgrade .pak file
  • When the upload of .pak file completes, click ‘ACCEPT’ to accept the EULA and start with the upgrade
  • When the upgrade process completes, check the version in the cluster tab
  • Once the upgrade of master node completes, the remaining nodes will be upgraded automatically.
  • The upgrade logs are written into /storage/core/loginsight/var/upgrade.log

Rollback procedure

For rollback procedure, please refer KB article 75150. The rollback logs are written into /storage/core/loginsight/var/rollback.log

Important points to check post upgrade

  • If the vRealize Log Insight upgrade (.pak file) has a new JRE version, the user-installed certificates in a vRealize Log Insight setup (such as for event forwarding) become invisible after upgrade)
  • If integration destinations provide untrusted certificates for SSL connections, their integration with vRealize Log Insight does not work correctly after an upgrade because the certificates are not added to the truststore. These integration destinations include vSphere, vRealize Operations Manager, event forwarder, Active Directory, and SMTP. As a workaround, in each integration configuration page, test the connection and accept the untrusted SSL certificate if a dialog box appears with the details of the certificate. Accepting the certificate adds it to the truststore.
  • Photon OS has improved security policies, which might require you to change the root password after a successful upgrade to Photon OS. This happens only when the root password in SLES expired, but unlike Photon OS, SLES OS did not enforce the update.
  • The sshd customized service configuration (/etc/ssh/sshd_config) resets to its default when you upgrade the SLES-based vRealize Log Insight 4.8 to the latest Photon-based vRealize Log Insight. As a workaround, save the /etc/ssh/sshd_config configuration before upgrading and then reconfigure manually after upgrade.
  • Photon OS has strict rules for the number of simultaneous ssh connection. Because the MaxAuthtries value is set to 2 by default in the /etc/ssh/sshd_config file, the ssh connection to your vRealize Log Insight virtual appliance might fail in the presence of multiple connections, with the following message: “Received disconnect from xx.xx.xx.xxx port 22:2: Too many authentication failures”. You can use any of the following workarounds for this issue:
  1. Use the IdentitiesOnly=yes option while connecting via ssh: #ssh -o IdentitiesOnly=yes user@ip
  2. Update the ~/.ssh/config file to add: Host* IdentitiesOnly yes
  3. Change the MaxAuthtries value by modifying the /etc/ssh/sshd_config file and restarting the sshd service.

New features introduced in vRealize Log Insight 8.0

The vRealize Log Insight 8.0 Release Notes  provides the details of key new features introduced in vRealize Log Insight version 8.0, which are also applicable to minor release 8.1.1

This concludes the vRealize Log Insight upgrade to version 8.1.1

Please feel free to provide your feedback or comments.

vExpert Applications are Open – Don’t Miss Out!

vExpert Applications are Open – Don’t Miss Out!

vExpert Applications are Open! Don’t miss out on the opportunity to join this amazing program & community. Applications will be open from June 1st, 2020 to July 19th, 2020 and the awards will be announced on July 17th. Apply for vExpert 2020 What the Program is About The vExpert Program is […]


VMware Social Media Advocacy

vRealize Operations Manager 8.1 Upgrade – Step by Step procedure

Hi Folks,

vRealize Operations Manager 8.1 was released on 14th April, 2020 and it comes with some really cool and exciting features like ability to discover vSphere with Kubernetes objects, ability to auto discover newly configured SDDCs under VMC on AWS account, advanced network troubleshooting with vRealize Network Insight integration, ability to leverage Slack channel to collaborate on issues and concerns and much more.

For the complete list, please refer vROps 8.1 Release Notes

Now let us understand the upgrade process. In this blog, I’ve covered the procedure for upgrading vROps from version 7.5 to 8.1.

The success of any upgrade task largely depends on the prerequisites. If you have your prerequisites in order, it is very unlikely that you would hit any issue during the upgrade process. So, let us first go through the prerequisites.

Prerequisites

  • Firstly, go through the release notes, specifically the vROps 8.1 known issues section
  • Check the VMware Interoperability Matrix and ensure that vROps 8.1 is compatible with other VMware components in your environment.
  • Run the vROps Preupgrade Assessment tool
  • Ensure that vROps admin or root account password has not expired. For details, please refer KB article 75195
  • Please go through KB article 76339, in case you happen to encounter the issue detailed in this KB during the upgrade process.
  • Ensure that there is enough disk space available for /dev/sda partition. For details, please refer KB article 75298
  • Take a backup and snapshot of the vROps instance
  • Export and save all the custom Views, Dashboards and Supermetrics

Procedure to run the vROps Upgrade Assessment tool

  • Login to the master vROps node admin console page https://<master vROps node IP or fqdn>/admin and click on software update
  • Click on install a software update and upload the pre-upgrade assessment pak file
  • Once the pak file is completely uploaded, in the next step, install the software update

  • Once the preupgrade assessment pak file is completely installed, click on support in the left panel and download the support bundle
  • Download the support bundle into appropriate location and navigate to the index file as shown below
  • Open the index HTML file in browser (preferably Chrome) and go through the ‘System validation checks’ tab and ‘Removed and Discontinued Metrics’ tab.
  • Before you proceed with the upgrade, all your system validation checks should be green ticked.
  • Click on Removed/Discontinued Metrics to check if there are any metrics, which may not be supported in vROps 8.1. For instance, in this case, the summary|oversized metric is highlighted as one of the impacted metrics.
  • Navigate to the below link and check if there is any replacement metric available for the impacted metric.

We are done with all the prerequisites including the upgrade assessment tool.

Let us start with the upgrade now.

Upgrade Procedure

  • Login to the master node of the vROps cluster using the admin console url – https://<vrops master node ip or fqdn>/admin and take the cluster offline.
  • In the left panel, click on software update and click on Install a software update
  • Upload the vROps 8.1 update pack file and click on install the PAK file even if it is already installed
  • Should you choose to select ‘Reset Default Content’, read and acknowledge the below warning
  • Allow the pak file to upload completely. Once the pak file is uploaded, the below page appears where there is a warning that during the upgrade process vROps cluster will be restarted.
  • In the next few steps, navigate through the license agreement, update information page and finally click on INSTALL to install the uploaded pak file
  • Allow the installation process to complete. This may take a while, so you may want to enjoy a cup of coffee until the installation process completes 🙂
  • Cluster state would go offline during the installation process
  • Once the upgrade completes, the below message will appear in the admin console
  • After the upgrade completes, login to vROps console and verify the version
  • So, here is the welcome page of the brand new vROps 8.1 instance

That’s it for this blog.

I hope you found this blog useful. Please feel free to provide your feedback.

Migration from VMware NSX for vSphere to NSX-T

Migration from VMware NSX for vSphere to NSX-T

Migration to VMware NSX-T Data Center (NSX-T) is top of mind for customers who are on NSX for vSphere (NSX-V). Broadly speaking, there are two main methods to migrate from NSX for vSphere to NSX-T Data Center: In Parallel Migration and In Place Migration. This blog post is a high-level overview of the above two The post Migration from VMware NSX for vSphere to NSX-T appeared first on Network Virtualization.


VMware Social Media Advocacy