These reg keys are obviously associated with the two big VDI vendors however if you are using another vendor again you may be out of luck for now. If a VDI agent is not installed then the installer looks for these keys only and then fails the install however if the VDA is installed it also looks for quite a few other keys so at the moment its not a case of creating a single key to fool the installer. The change to MSI package are certainly welcome and a good initial step in providing a machine based install for Microsoft Teams which hopefully will also migrate across to the other apps that are guilty of the same behaviour cough OneDrive.

I personally would like it be a choice for the customer whether they want to go to the standard version of teams ensuring that they stay up to date with the latest versions automatically across their estate or take a steadier approach by using the machine based install versions without the VDI technology search behaviour which would require more administrative effort for IT teams but a further degree of control that most companies find comforting.

A couple of things worth noting is that like its non machine based install counterpart Teams is not yet optimised for VDI voice and video capabilities, such as the HDX realtime pack so Microsoft recommend disabling the calling feature within teams.

The machine based installed is also not automatically updated so IT teams will need to manage the update procedure as they would for any other application. The default behavior of the MSI is to install the Teams app as soon as a user signs in and then automatically start Teams.

If you don’t want Teams to start automatically for users after it’s installed, you can use Group Policy to set a policy setting or disable auto launch for the MSI installer. Enable the Prevent Microsoft Teams from starting automatically after installation Group Policy setting.

This is the recommended method because you can turn off or turn on the policy setting according to your organization’s needs. When you enable this policy setting before Teams is installed, Teams doesn’t start automatically when users log in to Windows. After a user signs in to Teams for the first time, Teams starts automatically the next time the user logs in.

To learn more, see Use Group Policy to prevent Teams from starting automatically after installation. If you’ve already deployed Teams and want to set this policy to disable Teams autostart, first set the Group Policy setting to the value you want, and then run the Teams autostart reset script on a per-user basis.

Teams won’t start until the user manually starts Teams. After the user manually starts Teams, Teams automatically starts whenever the user logs in. All users can then uninstall Teams if they have admin credentials on the computer. If you run the MSI manually, be sure to run it with elevated permissions. Even if you run it as an administrator, without running it with elevated permissions, the installer won’t be able to configure the option to disable auto start.

Take control To take control while another person is sharing, simply:. Select Request control, from the sharing toolbar prompting the presenter to approve or deny the request. Once a user has control, they can make selections, edits, and other modifications to the shared screen.

To return screen ownership to the presenter, select select Release control. This feature is available in desktop sharing scenarios but is not supported in individual window sharing. It will soon be available to Azure Virtual Desktop. Teams users on VDI can now use real-time captions to improve meeting accessibility for participants with hearing impairments, varying levels of language proficiency, or those who may be attending from noisy environments.

Users can also adjust the language captured for improved the accuracy of the captioning. During a scheduled Teams meeting, users can start a live transcription of the proceedings. The text appears alongside the meeting video or audio in real time, including the speaker’s name unless they chose to hide it and a time stamp.

Once enabled, any participant can opt to see, save, and download the transcription. Learn more about using live captions in a Teams meeting.

Learn more about using live transcription in a Teams meeting. Learn more about spotlighting video in a Teams meeting. Teams background blur and effects is generally available on Azure Virtual Desktop and Windows Before or during a video meeting or call, users can change the appearance of their background with a blur effect or Teams virtual background template. Keep watching this blog for new ways to meet, chat, call, and collaborate. You must be a registered user to add a comment.

If you’ve already registered, sign in. Otherwise, register and sign in. Products 68 Special Topics 42 Video Hub Most Active Hubs Microsoft Teams.

With per-user installation, automatic updates is enabled. For most VDI deployments, we recommend you deploy Teams using per-machine installation. To update to the latest Teams version, start with the uninstall procedure followed by latest Teams version deployment. This makes complete sense for a VDI environment. They found a series of laptops that would not update to the latest Teams client no matter what they did.

The only recourse was to uninstall and reinstall the client. This credit goes to one our engineers, Jeremy Coleman, who did all of the hard work of tracking down what was happening. That entry may also have a value of 1, either case indicates you are in VDI mode. If it does not exist or has the value of 0, you are not in VDI mode. To get to the diagnostic logs, you can follow the steps laid out in the Microsoft Docs.

Deploy Microsoft Teams with Microsoft Apps – Deploy Office | Microsoft Docs.Use Microsoft Teams on Azure Virtual Desktop – Azure | Microsoft Learn

When a user then logs into a their VDI instance the package is extracted and installed directly into the users profile around mb natively. A great solution to this is FSLogix and Office or profile containers to containerise the installer reducing the user impact by persisting the data natively within an OS as far as Windows is concerned.

This obviously covers pretty much about everybody. It appears that Microsoft are now starting to do something about it. Microsoft have recently released this article which includes download links to the x64 and x86 versions of teams and a specific command line to run in order to install Teams as a VDI friendly product. I wanted to have a look at this executable and see how it installed.

In order to find out a bit more about the teams installer I broke open process monitor and ran the command line without having preinstalled any typical VDI agent packages into a windows 10 instance.

Looking into the process monitor logs it appears that the teams installer looks for specific VDI agent based registry locations to determine whether it will install or not. These reg keys are obviously associated with the two big VDI vendors however if you are using another vendor again you may be out of luck for now. If a VDI agent is not installed then the installer looks for these keys only and then fails the install however if the VDA is installed it also looks for quite a few other keys so at the moment its not a case of creating a single key to fool the installer.

The change to MSI package are certainly welcome and a good initial step in providing a machine based install for Microsoft Teams which hopefully will also migrate across to the other apps that are guilty of the same behaviour cough OneDrive. I personally would like it be a choice for the customer whether they want to go to the standard version of teams ensuring that they stay up to date with the latest versions automatically across their estate or take a steadier approach by using the machine based install versions without the VDI technology search behaviour which would require more administrative effort for IT teams but a further degree of control that most companies find comforting.

A couple of things worth noting is that like its non machine based install counterpart Teams is not yet optimised for VDI voice and video capabilities, such as the HDX realtime pack so Microsoft recommend disabling the calling feature within teams.

The machine based installed is also not automatically updated so IT teams will need to manage the update procedure as they would for any other application. Hi Dale, nice post. Thanks for the info on the registry entries. I used that to trick the machine wide installer to install onto a RDS server. Author: Dale Scriven Share this: Tweet. Like this: Like Loading Dale Scriven. Lakeside Systrack — excluding applications from being captured. Migrating Outlook autocorrect to a new profile August 26, Dale Scriven.

Leave a Reply Cancel reply. Loading Comments Email Required Name Required Website.