Nov 24 2016 03:27 AM
Nov 24 2016 03:27 AM
I've installed the Teams client on my computer (as a local admin) and the client installs in the 'Appdata/local' part of my profile? is this correct? It doesn't install into into Program Files or someone else in the OS?
Sep 28 2017 07:00 AM
That is correct. The installer of the client uses Squirrel as the installation framework which by default installs to AppData\Local. It's the root concept of Squirrel to allow regular users to install applications and automatically keep them up to date.
I don't like this concept at all and would prefer the app to install to Program Files and require admin privileges to install and update. In my opinion AppData is meant to store data and no executables. I usually use software restriction policies to block all executable in user writable folders. Most modern malicious software especially ransomware does not need administrator privileges to harm your data and as the malicious application is just written to a user writeable folder they should not be executable from this folder.
Sep 29 2017 03:21 AM
I totally agree with you here. In a controlled enterprise environment, one of the strongest safety controls for avoiding malware is whitelisting executables that are allowed to run.
As such, allowing local user software updates is totally against useful policy and will fail.
In addition, this adds significant complexity and size to user data backups as we wouldn't be expecting executables to exist in this "data" area
Microsoft need to tell us how we will manage their "new" EU tools such as Teams and Yammer desktop apps using enterprise deployment and management tools.
We really don't need a different and poorly managed new installation type, the ones we have are bad enough and this just makes things worse not better.
Jan 21 2019 09:11 PM
Hey mate know this is an old thread but I'm using Applocker myself and it is blocking the team setup for new users when they log in, as a workaround I have to copy the Teams folder in AppData manually. I'm trying to figure out what permissions it needs to do this automatically.
Just wondering if you came across a fix?