How can we make Microsoft Teams better?

← Public

Improve Install options - Install for all users and install location

Raising this again as Microsoft closed the previous request, saying it was complete even though it was not. (link below)

Teams should install to the program files directory, not the users AppData.

And NO, the answer is not to put a copy of the MSI in Pogram Files and deploy to the users AppData when they login.

https://microsoftteams.uservoice.com/forums/555103-public/suggestions/17380159-improve-install-options-install-for-all-users-an

489 votes
Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Anonymous shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

77 comments

Attach a File
Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Brian commented  ·   ·  Flag as inappropriate

    Please just use the O365 C2R / Standalone Setup set and stop with the open source, security and enterprise nightmare updater. This would put it in C:\Program Files\ where it belongs, not in App Data where everyone should never let executable code run and it also makes it a total nightmare to manage and report on version updates. There is more than one reason for this - we have security policies to follow and validate and verify that software is indeed at the correct version - when its installed per user it could have 30 different versions of the software, and has to install 30 times when each user logs in, and it is not efficient or effective. It also makes troubleshooting and central management nearly impossible.

  • Anonymous commented  ·   ·  Flag as inappropriate

    We would love to use Teams on computers in a training lab, but installing to each user's APPDATA folder is a terrible means to accomplish this. It's not a useful tool if all of my users lose access to it if they need to use a different machine.

  • Asmus Georgi commented  ·   ·  Flag as inappropriate

    I agree. At least for enterprise/institutional environments, please allow installation of Teams for all users, in Program Files. Use functionality such as is employed by Windows, Office, or Google Chrome and other software, for updates in such a scenario.

    You now allow installation for all users in a VDI environment, but provide no update mechanism in that case, and you block the alluser install in non-VDI cases.

    This is all very frustrating, and will limit adoption of Teams. We have decided not to deploy it in new university labs and VMs that we are setting up, despite heavily using Teams otherwise and being quite happy.

  • Anthony commented  ·   ·  Flag as inappropriate

    Please change the install directory to program files instead of dumping it APPDATA.

    Cheers
    Anthony

  • John Babbitt commented  ·   ·  Flag as inappropriate

    Microsoft finally made it enterprise-friendly. I have the full Remote Desktop Server package (RDG, RDCB, RDSH), including User Profile Disk (UPD) and Software Restriction Policies (SRP) yet I got this to work today with the enterprise-friendly installation. You can read about it at https://docs.microsoft.com/en-us/microsoftteams/teams-for-vdi. There are a few items to tweak, though:

    1. Installation will fail unless you create a registry key, if one doesn't already exists, for either:
    a. HKLM\SOFTWARE\VMware, Inc.\VMware VDM\Agent, or
    b. HKLM\Software\Citrix\PortICA

    If you do not want to auto-start this for everyone (I had another group that doesn't use it at all and it annoys them every time they log in):

    2. After installation, delete the registry value Teams from HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Run. Do not delete the other two TeamsMachineUninstaller* values.

    3. If the user wants it to auto-start (unfortunately, Teams didn't have its own auto-start option), do these:
    a. Right-click Start Menu (Windows logo key) and select "Run".
    b. Enter "shell:startup" and press Enter. This opens up you your Startup folder.
    c. Click Start Menu, scroll down to Microsoft Corporation, drag Teams to your Startup folder.

    Enjoy!

  • Rich Mawdsley commented  ·   ·  Flag as inappropriate

    Utterly ridiculous that this still hasnt been sorted. As per other comments, this has now been done with Onedrive, that team has seen the light and made a PROPER machine install which before you say it Mr Teams admin, SELF UPDATES. So you no longer have that excuse.

    Just make it properly and you'd get such a HUGE uptick in users by enterprises across the world who hate this current method.

  • Rick Cobb commented  ·   ·  Flag as inappropriate

    Microsoft... please stop this insanity! Install your applications in "Program Files" and give us control of global settings in the registry! You (MS) are the one who created these protocols. Enterprise admins have lived by these protocols for years very successfully. Get control over your application developers and stop breaking your own rules!

  • CP commented  ·   ·  Flag as inappropriate

    How is this still only getting 400 votes?

    Is there not a lot of VMware Horizon View + UEM admin that uses Teams in their environment?

    @Microsoft,
    I guess as a workaround we just need to tell our people to use Teams only on either web or mobile app, huh?

  • Cam commented  ·   ·  Flag as inappropriate

    @James, the Office 365 ProPlus installs it in the exact same manner as the MSI (again, useless)

    Found under "Additional Info":
    "Teams is installed with Office 365 ProPlus in the same way that Teams is installed if you use the MSI-based installer for Teams. For each new user that signs into the device, the Teams installer runs and the Teams application is installed in the user's AppData folder."

  • Cam commented  ·   ·  Flag as inappropriate

    We've been trying to roll out Teams for months, but with Teams needing admin rights to create a firewall rule to the AppData folder, it's impossible.
    I've tried numerous scripts myself and others online have made, but this AppData location jams up everything.

← Previous 1 3 4

Forum Home

Reference Information for Teams

Public: IT Pro - Controls and Knobs

Categories

Feedback and Knowledge Base

(thinking…)

More Teams Information



You are about to visit the UserVoice site for Microsoft Teams

We have partnered with UserVoice, a 3rd party service providing public discussion forums for product-specific feedback.

By clicking "Continue to UserVoice" you agree to UserVoice's Privacy Policy and Terms of Use.