This feature request is still working its way through the backlog queue.
Seriously - is anybody on the Teams team (ahem) working? Between this BASIC FUNCTIONALITY and the absolute GARBAGE .msi, it appears MS is *trying* to make this fail. Get to work on things that matter.
Great performance and user experience remain a topmost priority for us. Application launch time has seen improvements in the recent build. We will continue making improvements across the product including channel to chat switching and overall resource consumption.
"More improvements are on the way." - Alex, July 3, 2019
About when? Is this steaming pile of hot garbage going to be fixed before or after Microsoft kills Skype for Business? Between this and the absolute trash "installer" issue (seriously, who in their right mind thought that was a good idea for a corporate product, particularly something that would *probably* be used in a VDI environment, and where users are *most likely* prevented from installing in %appdata%...), we're wondering if perhaps there isn't another vendor that would like our money.
You've been "working on it" since May 1, 2019, and this topic was created in July of 2018. Get with it. Our users don't install apps, period - not in %appdata% or anywhere else. And having 50-100 copies of an executable running around in a VDI environment is mind-numbingly stupid. Admit that the already-supplied .msi "solution" is garbage and FIX IT CORRECTLY!
5 votesDavid shared this idea ·
It is beyond stupid to not provide this! Allow regular users to install apps in user-writable app-data? Has MS been aware of this new ransomware thing? If they want enterprise adoption, get with it.