Why does Teams default to (and encourage) a per-user installation?

%3CLINGO-SUB%20id%3D%22lingo-sub-1503135%22%20slang%3D%22en-US%22%3EWhy%20does%20Teams%20default%20to%20(and%20encourage)%20a%20per-user%20installation%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1503135%22%20slang%3D%22en-US%22%3E%3CP%3ETeams%20is%20being%20heavily%20promoted%20for%20use%20in%20a%20corporate%2Fbusiness%20environment.%26nbsp%3B%20However%2C%20the%20various%20installers%20always%20default%20to%20a%20%22per%20user%22%20mode%2C%20and%20it%20feels%20like%20the%20per%20user%20app%20is%20being%20forced%20on%20us.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-%20This%20includes%20the%20Teams%20version%20that%20is%20delivered%20with%20the%20Office%20365%20ProPlus%20C2R%20install.%26nbsp%3B%20The%20rest%20of%20the%20office%20suite%20installs%20per-computer%2C%20but%20Teams%20installs%20per%20user...%3C%2FP%3E%3CP%3E-%20If%20we%20direct%20staff%20and%20customers%20to%20use%20the%20web%20version%2C%20the%20first%20time%20they%20log%20in%20they%20get%20prompted%20to%20install%20the%20windows%20app%2C%20which%20does%20the%20same%20thing.%26nbsp%3B%20We%20can't%20suppress%20the%20prompts%20for%20them%20to%20install%20the%20%22per%20user%22%20app.%3C%2FP%3E%3CP%3E-%20An%20MSI%20installer%20for%20Teams%20can%20be%20run%20machine-wide%20and%20set%20in%20an%20%22all%20users%22%20mode%20to%20install%20per%20computer%2C%20but%20this%20is%20only%20supported%20for%20use%20in%20VDI%20environments.%26nbsp%3B%20Why%20is%20that%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20understand%20that%20Teams%20development%20is%20very%20active%20and%20updates%20are%20rolled%20out%20very%20frequently%20but%20in%20my%20mind%20this%20ends%20up%20creating%20a%20nightmare%20for%20system%20admins.%26nbsp%3B%20We%20need%20to%20be%20able%20to%20control%20how%20software%20is%20deployed%2C%20managed%2C%20and%20updated.%26nbsp%3B%20We're%20being%20forced%20to%20use%20third-party%20software%20products%20to%20manage%20the%20way%20that%20Teams%20runs%20in%20our%20environment%2C%20or%20we%20have%20to%20revert%20to%20unsupported%20methods.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1503135%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdministrator%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESettings%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
New Contributor

Teams is being heavily promoted for use in a corporate/business environment.  However, the various installers always default to a "per user" mode, and it feels like the per user app is being forced on us.

 

- This includes the Teams version that is delivered with the Office 365 ProPlus C2R install.  The rest of the office suite installs per-computer, but Teams installs per user...

- If we direct staff and customers to use the web version, the first time they log in they get prompted to install the windows app, which does the same thing.  We can't suppress the prompts for them to install the "per user" app.

- An MSI installer for Teams can be run machine-wide and set in an "all users" mode to install per computer, but this is only supported for use in VDI environments.  Why is that?

 

I understand that Teams development is very active and updates are rolled out very frequently but in my mind this ends up creating a nightmare for system admins.  We need to be able to control how software is deployed, managed, and updated.  We're being forced to use third-party software products to manage the way that Teams runs in our environment, or we have to revert to unsupported methods.

1 Reply
Highlighted

@jrondo4

 

Teams is a client, rather than a standalone application. That client needs to keep in sync with the central shared service that it's talking to, so Microsoft currently have it update every 2 weeks (sometimes less). This allows the pace of continuous development and feature release of the product. I'm sure you'll probably acknowledge that when 'enterprise' scale testing and deployment processes get involved they slow things down, e.g. choosing Semi-Annual office app updates. This old model used to be how Skype for Business worked, and it became hugely slow for new capabilities like VBSS to get to widespread deployment, years rather than weeks. It's just not viable for a modern product in a competitive market.

 

I think it's fair comment that storing applications under %userdata% isn't good practice, and other frequent self-updating apps like OneDrive, Chrome etc. manage to do it in Program Files by installing an agent as an admin to overcome locked down user accounts. There was originally a plan that Teams would eventually become a UWP app deployed and update through the Windows Store, but when the strategy around Edge changed to Chromium that took a backseat. I work for a company with 500K Teams users, it's not ideal, but really it doesn't cause much issue to get it to just look after itself.