Proper MSI Installer for VDI
The recent MSI installer isn't really what people are asking for. It doesn't actually install to program files. It just puts an installer in program files which then installs to the users app data. This doesn't work for me at all.
In a non-persistent VDI environment the application has to install on every login (unless I roam appdata/local which I don't want to do). This isn't the end of the world as it's fairly quick but the problem comes when you also use Yammer. Yammer has the same weird install method and when both teams and yammer try to install they cause a process conflict so only one of them actually installs.
Can we have some proper deployment methods like the rest of Office please? Or at the very least a way of deploying Teams and Yammer together?
Rick
shared this idea
12 comments
-
Joe Robinson
commented
As an administrator, it frustrates me that Microsoft standardizes the installation process for windows, then goes rogue with their own installers. A proper installation would not only benefit VDI, but also companies that follow Microsoft's own security advice...
Who in their right mind lets any random user run an executable out of their profile, regardless of how it got there!
-
Tom Stack
commented
The bigger issue I have is if the stupid user account based install gets borked its much more difficult to fix since you cant really uninstall/reinstall Give us a standard install to program files installer thanks.
-
Anonymous
commented
Application in profiles is ******* non presisent vdi machine. Please make per machine teams install
-
Dale
commented
Obviously this is one of the reasons why you bought FSLogix, but it doesn't mean you shouldn't fix this hideous deployment method for teams.
-
Johan Lysén
commented
Why not As part of Office ?
-
Chris Smith commented
Will this be addressed with Teams being deployed alongside the Office 365 ProPlus package?
-
Anonymous
commented
Just Do it. Ridiculous that you have closed the first user voice and implemented such a ****** solution.
-
Adam Fowler
commented
The previous user voice being closed is definitely wrong - we want an end result of the program being in Program Files, not the user's profile. OneDrive for Business is finally moving towards this way, and Teams needs to be there too.
There's even gaps where we can't deploy a firewall rule, and Teams will alert on this https://docs.microsoft.com/en-us/microsoftteams/get-clients
-
AndresP
commented
current (4.4.2019 x64) MSi installe is a joke. I just copies the same user based executable to program files and sets windows to autolaunch it for every user - still installing in user profile space. Not wort time to experiment with it.
Whats wrong with You?
It is still not usable in enterprise and in Terminal and not in roaming profile . -
Anonymous
commented
Until we have this, we will not deploy teams and hang on to "legacy" Skype for as long as possible (should apply to OS X too). We have 8,500 devices. 4500 of these are shared by 17,000 users who get a fresh profile every time they login! There needs to be a device based installation!
-
Brian
commented
Ideally it installs to C:\Program Files\Microsoft Teams and installs an updater service and keeps its user-specific stuff in %appdata% like the rest of windows.
Windows Defender and Office O365 seem to have no trouble at all updating themselves and interacting with Users or other non-admin accounts.
-
Koen
commented
As the previous MSI uservoice is closed without addressing the main feature request (per machine basis installer) I support continuing in this uservoice.