Improve Install options - Install for all users and install location
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
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.
181 commentsComments are closed
Michael Gorn commented
Any updates? Its been 3 months....
Nahum Ella commented
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
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
Need a true MSI that installs per machine not per user.
Can you define coming months? It's been 3 months since the last update.
This does not work in an educational environment where apps need to be deployed to a location other than appdata
Jason Gould commented
Microsoft still failing miserably here to offer proper business focused products. Installer should be to %ProgramFiles% not %AppData%. Learn to LISTEN!
Andrew Williams commented
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!
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
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.
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!
So any update on this? Need it for SCCM
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!
Also running non-persistent virtual desktop environment. Come on MS, fix this garbage.
Ben Giacaman commented
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
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
As an educational user. We cannot install things into AppData with roaming profiles... This should have been resolved before releasing teams for education.
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?
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.