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
We have noticed there is now an MSI installer. However this behaves like the exe installer. A per user install in %appdata% is still performed. In our opinion this issue is not yet resolved. Please do not change the status of this uservoice to resolved with the current MSI installer
AdminSam (Admin, Microsoft Teams) commented
MSI installer is now resolved and confirmed to be signed. https://docs.microsoft.com/en-us/MicrosoftTeams/msi-deployment
Signing date: 3:44 PM 4/10/2018
Publisher: Microsoft Corporation
Bart M commented
Can you give us an update?
Slack Fan commented
Why are the MSIs not updated? (184.108.40.20666 vs. 220.127.116.1155)
And when will we get an enterprise ready package?
Chris White commented
Teams.exe prompts for windows firewall when making calls. Adding rules to windows firewall requires elevation. Therefore creating a user based installer of software that has features which require elevation is pretty bad is it not?
In our environment Windows firewall is managed by group policy. I have tried creating firewall rules to %USERPROFILE%\AppData\Local\Microsoft\Teams\Current\Teams.exe and also to C:\Users\%USERNAME%\AppData\Local\Microsoft\Teams\Current\Teams.exe. Both of these do not appear to work and the prompt saying C:\Users\joebloggs\AppData\Local\Microsoft\Teams\Current\Teams.exe still pops up.
Can we have an installer that installs the product into the propper directory for installed programs C:\Program Files or C:\Program Files (x86). This way we can create firewall rules in our environment that will work and create a more seamless hassle free environment for our users.
Teams.exe under C:\Program Files (x86) disappear after the first user loaded Teams. Meaning, all the new subsequent users of the machine will not benefit.
Yammer machine-wide + Teams machine-wide MSI installers = broken. They both rely on Squirrel, both function identically, and running simultaneously is stopping both from installing at all. Please fix!
Hold on a second... I've just seen the requirements on this...
"32GB of disk space for each user profile (recommended)"
Are you serious?!?!?!
On another note, nice to see MS are paying attention to the thread...
Please create enterprise-ready MSI install package: i.e. per-machine install to Program Files and remember to digitally sign to package. Current msi can't be used.
Last weeks update to Teams had changes that triggered applocker to block it. Ridiculous that MSFT can't provide software that can be deployed to managed Windows 10 machines
Steve Whitcher commented
I hate to say it, but I'm with Gareth. While I appreciate that you've made an MSI installer available, it seems that you completely dodged addressing the real issue(s). We don't want a pseudo web app that installs a separate copy of itself for each user, has to be updated for each user, etc. We want a proper business class application. There are 2 ways to do this. It either needs to be:
1) A Win32 app that follows the proper standards, such as installing itself in the program files directory and using that single installed instance for all users, with updates coming through the same channels as other office apps, or
2) A Windows Store / UWP app. Windows store apps still have their downsides compared to traditional Win32 apps, but there are a lot of good things about them as well.
I still don't understand why Teams was developed as anything but a UWP app in the first place, considering how hard Microsoft has been pushing for 3rd party devs to switch to UWP. With store apps getting regular updates automatically and being installed on a per user basis, it seems like this would have been a perfect fit for what the Teams devs wanted. It also would have meant that the app could be available from the start for Surface Hub without requiring a lot of extra effort.
Workaround is to create an AppLocker "Publisher" rule for UPDATE.EXE and TEAMS.EXE. Hopefully that is all that will be required
Before you update us to report that an MSI is now available, please turn around and start again.
Yes, an MSI is available, https://docs.microsoft.com/en-us/MicrosoftTeams/msi-deployment. However this is such a poor effort in that all you have done is wrap the download in an MSI and executing it at login of the user.
That still will not work when AppLocker is around as you are still stuffing data in LOCALAPPDATA. There is no way we will be configuring AppLocker to allow execution of anything from there!
Oh, and the MSI isn't even signed!
I could have written this poor effort of an MSI in a batch script. Teams will not properly fit in to an enterprise until you have installed it in to "Program Files"! Essentially somewhere that the user cannot write to.
Matt R commented
Looks like we are all in the same boat... Under increasing pressure to deploy this and replace Hipchat. Unless the 'coming months' is the month coming next I don't think I'll be able to go forward with this. Would love a ballpark timescale :)
It is ridiculous that a product to be used by Enterprise companies does not already have an Enterprise deployment mechanism!
This should have been in-place from day 0! Before it left for Development for alpha release even! Such basic functionality that has not even been considered. We use AppLocker and we can't7 deploy Teams without having to bodge a load of rules and making the systems insecure!
Andrew P commented
Thanks for the update. Like many I'm coming under increasing pressure to deploy this application in my mixed Citrix environment. I'm holding off as I don't want to invest in figuring out a messy user profile deployment (Citrix UPM and AppLocker), then having to undo it and use a proper deployment later. Please move this along as quickly as you can.
Stuart Bailie commented
It has been near four months since the last admin comment and over a year since the initial thread was started. If Warren and Suphatra could be so honest as saying "We will not be moving forward with this" that would be great. Even a "We are moving forward with this and we will update you in a year" that would also be great. Just something aside from the quiet, what was that word, contempt for the rest of us here. This is a well populated thread and gets comments quite frequently and yet Microsoft seems to feel that updates ever three or four months is a good idea.
There are lots of things I would like to see addressed but if this is how user voice works I don't see much point in talking about it. I'll follow Anonymous' comment and start to look into Slack or other alternatives.
Paul Cook commented
Is there any update on this? This issue is still preventing us from rolling out the desktop client to our users.
Pavel Večeř commented
Hello, any ETA for this?