Teams msi installer for vdi –
Teams for Virtualized Desktop Infrastructure – Microsoft Teams | Microsoft Docs.Teams for Virtualized Desktop Infrastructure – Microsoft Teams | Microsoft Docs
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. Related Posts. Citrix StoreFront 3. Droplet Computing October 20, October 20, dale scriven. Leave a Reply Cancel reply. Loading Comments Email Required Name Required Website.
Teams msi installer for vdi. Optimization for Microsoft Teams
MSI files give administrators flexibility and customization options when installing software. The Teams MSI installer is no exception. You can deploy the Teams desktop app using a per-machine or per-user installation. To install Microsoft Teams in your Azure Virtual Desktop. Microsoft released a windows installer for Teams that is placed in Program Files, but this is theoretically targeted only for VDI (Virtualized Desktop.