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
[Deleted User] commented
It's impossible to deploy the desktop app in an enterprise environment unless security policies are relaxed. For some this is just not acceptable. This trend of installing software to appdata is fine as long as you provide enterprise organisations with an alternative. Please give us an msi that installs to Program Files.
Any update on this?
Teams Sux commented
What is this junk? Your marketing team is advertising the s**t out of this product but I have to shut any discussion down about using it in our business as we cannot manage deployments.
The post is a few months old, I was hoping Microsoft would have pulled the plug out of their proverbial rear and had an msi that installs locally to machine rather than user profile by now.
This is probably the jankiest package I have ever created. I installed it manually then copied the install folder out of the appdata folder and exported the registry keys and shortcut icon. I built a package which literally dumps the install folder to the user's appdata folder and imports the registry entries and dumps the shortcut into the correct place.
Once done it still goes through the self update process and it's available for that user only. If they go to another machine the shortcut and possibly registry keys won't be there so they may have to go through the install process again? we might be able to use AD GPO to install as user if we can't get sccm to slap it down. If you can't package it you can script it as well. Pretty much copy folder to (%LocalAppData%) correct place in appdata. Make sure the exported registry file is amended to have the unique user path replaced with %LocalappData%, otherwise it will only work for the user you originally installed it for. We're still testing this, will )post back how it goes.
Windows Registry Editor Version 5.00
"QuietUninstallString"="\"C:\\%LocalAppData%\\Microsoft\\Teams\\Update.exe\" --uninstall -s"
+1 for non-user-dependent installation.
Also, an installer switch added to control the "auto-start application" and "open application in background" settings would be helpful
Another "Seconded" for non-user-dependent installation. We primarily use Citrix non-persistent desktops, and applications like this are a pain to support even if we can make workarounds.
If you wish to make Teams an enterprise level offering on a par with - or part of - Office, then please give it the same flexibility for installation and for management.
Not going to use this rubbish until we can install into program files. Installation to person AppData is blocked on our network for obvious reasons.
Any update? it becomes very urgent for us please
Bobby Hilvert commented
Throwing in my hat that this. Not compatible with Horizon View (VDI) app volumes.
Jason Gould commented
The "working on it" answer isn't addressing the issue. An MSI is nice, but the REAL issue that everyone has been pointing out to Microsoft about Teams (and OneDrive) is the persistence on installing in the users profile (AppData). This needs to go into Program Files like normal software.
I've read the "reasoning" for AppData; allowing users to install without Admin credentials or prompts. But that is completely counter to what any Business or School would EVER want. I don't WANT my users being able to install anything they desire, that's how VERY bad things happen. We've gone through great lengths to guard our systems and what goes on them. I don't want Microsoft promoting the opposite of that.
Luke Pollard commented
Another IT Manager here, we've deployed User Experience Virtualisation rather than roaming profiles, a feature that was encouraged in Windows 10. I have been unable to get teams to work correctly in UE-V and need it to be installed in C:\program files.
Can you tell us how long this is going to take before we can deploy to the machine and not to each user?
Ward Germonpré commented
Citrix PVS shop here. We use Citrix profile manager to roam 150 profiles across 12 session delivery controllers. On my local machine the Teams folder is 545MB and I haven't really done anything with Teams yet, this is going to be a problem if that folder is moved around and Teams does its caching there. I really would like Teams to install like any ordinary Office application. Can you elaborate on how Teams implements search? On citrix we've been bitten once with the roaming OST files issue preventing deep search of mailboxes (there is 3rd party solution that employs personal virtual disks for ost storage that CAN be indexed), so we're twice shy of Teams.
Also mind that we use on premise Skype4Business so .... Teams is our roadmap. I would REALLY appreciate you confirming Teams for Citrix PVS/MCS shops, thanks.
Stuart Bailie commented
It has been over a year since this problem was brought up and in that time only two admin responses have been logged. In a similar timeframe there has been almost a comment every three days.
Michael Rosa commented
Is there any news on this ? It would be very helpful
Andrew Whewell commented
We are currently experiencing issues with installing this to a VDI environment... we have managed to successfully install it via group policy to the first desktop a user logs into, however it will not install again to another desktop if they move to it. That means they still have their Roaming data, but no actual application to use it with.
Is there any update on when a more centralised solution will be made available to allow companies to make use of the app on multiple desktops?
Need an installer which install to c:\program files so that we can deploy Teams on our rds farm
Need to work on my Xenapp environment.
Dadi Mar Sigurdsson commented
Any news on this?
internal admin requiring that this installer has the ability to be deployed to C:\Program Files. Completely unusable on our enterprise vdi as is