Improve Install options - Install for all users and install location

Hi there,

I would like to be able to install for all users of a PC via and MSI, the current installer installs into the users Appdata which means each user has to install manually.

I would like to see a "proper" installer than loads it to Program Files for all users

668 votes

Your name

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

UserVoice password

Forgot password?

Create a password

Signed in as (Sign out)

We’ll send you updates on this idea

Martin DUggan shared this idea · Dec 9, 2016 · Flag idea as inappropriate… · Admin →

completed ·

Warren responded · Jul 6, 2018

Good news, this feature request has been completed.

You can find details on MSI installation instructions at: https://docs.microsoft.com/en-us/microsoftteams/msi-deployment

You can find details on SCCM instructions at: https://docs.microsoft.com/en-us/sccm/core/understand/introduction

Thank you all for the feedback and support.
-Warren

Show previous admin responses (4)

working on it ·

Warren responded · Mar 8, 2018

Sorry for the long delay! We are still hard at work on this.

The SCCM/MSI install will be available in the coming months! No exact release date to share, but it is making some great progress.

Documentation will also be provided when this is ready.

Our updates should be much more regular on this topic moving forward.

Thank you for all the feedback.
-Warren

working on it ·

Warren responded · Nov 20, 2017

Thanks for your feedback. I talked to the engineering team about your ask for a SCCM installation option. We understand the concern with having to deploy each user on a machine via the exe file. Therefore, a MSI pack is in the works which will handle installation. This MSI will allow easier distribution of Teams and will smartly install for new users upon first login into a machine that has Teams already installed. This should allow for a much easier installation process for IT admins. Network usage is also being reviewed to ensure how to prevent network stability issues when deploying to or updating many machines.

Thanks again for your input and your time. We’re listening, so please keep sharing your great ideas. -Warren

needs your feedback ·

Suphatra responded · Jul 17, 2017

Hi, thanks for your idea! I have a few follow up questions — would you mind sharing in the comments below?

1. Do you want install privileges so that you can load the program for all users?
2. Or do you want a central repository which all users can access and deploy programs?
3. Do you want the access given to specific users only for the installer to deploy programs?

Cheers,
Suphatra
Microsoft Teams

under review ·

Suphatra responded · Feb 8, 2017

Thanks for submitting this! We’re looking into this.

180 comments

Comments are closed

Michael Gorn commented · June 29, 2018 9:23 AM · Flag as inappropriate

updates?
Anonymous commented · June 22, 2018 11:36 AM · Flag as inappropriate

Any updates? Its been 3 months....
Nahum Ella commented · June 20, 2018 5:56 AM · Flag as inappropriate

Please add a switch to the installation that prevents Teams starting at logon.
For the MSI, lets say something like this:
msiexec /i "Teams_windows.msi" START_AT_LOGON=FALSE /qn /norestart
Rick commented · June 19, 2018 6:02 AM · Flag as inappropriate

A proper MSI going to program files would be nice but in the meantime can we at least have a way of stopping the yammer and teams MSIs from conflicting please?
Tom S commented · June 15, 2018 8:48 AM · Flag as inappropriate

Need a true MSI that installs per machine not per user.
Anonymous commented · June 11, 2018 9:22 PM · Flag as inappropriate

Can you define coming months? It's been 3 months since the last update.
Katy commented · June 7, 2018 1:36 PM · Flag as inappropriate

This does not work in an educational environment where apps need to be deployed to a location other than appdata
Jason Gould commented · June 5, 2018 6:36 AM · Flag as inappropriate

Microsoft still failing miserably here to offer proper business focused products. Installer should be to %ProgramFiles% not %AppData%. Learn to LISTEN!
Andrew Williams commented · June 1, 2018 7:01 AM · Flag as inappropriate

Attempting to package Teams in a VDI environment has been... entertaining. Finally managed to get a working appstack that launches it on startup and our antivirus software reported it as a potential trojan!
Anonymous commented · May 30, 2018 9:57 PM · Flag as inappropriate

I tried to deploy this today for our office and discovered the mess that is Microsoft Teams. Please provide an MSI package that installs into program files and stores user data in %appdata%.
Lucas Kuiper commented · May 16, 2018 1:09 AM · Flag as inappropriate

This MSI is still of no use in Enterprise environments. It doesn't do a proper install in program Files for All users. For installation in non-persistent VDI environment it is useless.
Anonymous commented · May 10, 2018 10:36 PM · Flag as inappropriate

This would be an awesome feature to have! SCCM can't reliably detect the installation and flags it as failed. an proper MSI would be perfect!

btw keep up the great work!
Chris commented · May 8, 2018 1:44 PM · Flag as inappropriate

So any update on this? Need it for SCCM
Paul commented · May 2, 2018 3:22 AM · Flag as inappropriate

Just been doing some testing in my environment seems that Yammer and Teams MSI installer do not work side by side. The installers create two start up processes however the two start up processes require the same resources and fall over.

All this seems to suggest that you are planning to kill either Teams or Yammer or that you haven't tested them together!
Anonymous commented · May 1, 2018 8:36 AM · Flag as inappropriate

Also running non-persistent virtual desktop environment. Come on MS, fix this garbage.
Ben Giacaman commented · April 25, 2018 5:44 AM · Flag as inappropriate

C'mon Microsoft! We need to deploy this to several thousands computers, but we can't install on the user AppData folder. Please make the MSI install Teams for the entire computer in the %ProgramFiles% directory, and have the data (settings, etc) for each user stored in their own %AppData% directory. No need to actually run the executable from this directory! Get your act together! Think Enterprise-level..
Jose segura commented · April 20, 2018 7:04 PM · Flag as inappropriate

Please let us know if there are any updates on the installer options for SCCM. We need to deploy Teams to several thousand computers and need an installer that allows us to install the application for all users on the computer. Thank you
Anonymous commented · April 20, 2018 12:58 AM · Flag as inappropriate

As an educational user. We cannot install things into AppData with roaming profiles... This should have been resolved before releasing teams for education.
Brad commented · April 16, 2018 6:23 AM · Flag as inappropriate

Who comes up with these rubbish responses? Are they written by a politician... not once have you covered the initial request.

Stop ******* on about how much "great progress" is being made with the MSI installer. If it doesn't remove the requirement to install into the users AppData then it is not a solution.

Why is this so difficult?
Jeroen commented · April 16, 2018 2:28 AM · Flag as inappropriate

An Enterprise Ready installer with installation in the program files folder is required. We will NOT allow any processes running from within the user profile (Applocker block!) even if this means Teams can not be used.