The command line you need to install teams is:
I wanted to have a look at this executable and see how it installed. Specific command line to run in order to install Teams as a VDI friendly
Which includes download links to the 圆4 and x86 versions of teams and a Microsoft have recently released this article Sorry SBC people you’ll have to have wait a bit longer I think. Microsoft have released a version of Teams that is a machine based install which does not install the application into a profile location but with in the correct C:\program files\ location with the caveat that it available for VDI instances only. Microsoft are now starting to do something about it. Is a badly written application for any kind of non-perisitent solution andĮveryone has been commenting on the situation for some time. of users of storage space that could be put to better use.ĭespite the great FSLogix option there’s no denying that Teams however the problem will still be the same that while Teams is containerised within FSLogix that is still 500mb x No. This obviously covers pretty much about everybody. This is one of the reasons why Microsoft purchased FSLogix then provided effectively free licences for anyone who purchases RDS,VDA, E3 and above O365 among others. To each profile (no thank) or users have to accept that on each logon to a nonpersistentįresh desktop the Teams installer will execute providing a non ideal userĮxperience while the CPU is busy performing the installation actions and whateverĮlse it has to worry about during a logon.Ī great solution to this is FSLogix and Office365 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. Installation files within your profile management solution adding at least 500mb’s You either have to persist the default locations for the If you consider a typical non-persistent VDI environment which includes some kind of profile solution, Citrix UPM, VMware’s persona manager etc etc you get some highly undesirable effects. When a user then logs into a their VDI instance the package is extracted and installed directly into the users profile (around 500mb natively).įor physical devices this doesn’t cause too much of a hassle but for VDI implementations this causes a massive headache. By default, running the installer for Microsoft Teams doesn’t actually install the application but it extracts a package and a json file into the c:\program files directory. However teams also has an unpleasant after taste for SBC/VDI admins (its not the only app that does mind you) in the way that it is installed. Teams is actually a really good enterprise messaging and collaboration tool and as its in many O365 subscriptions etc then it’s a no-brainer to use it.