Subject: Re: Location of install directory for users ( - do you think it is possible to open a User Voice for a feature request to install in Program Files? That said, I would recommend to open a separate UV for shared device (aka, VDI, RDS, etc.). If we open a separate UV around that, we are breaking down the feedback around our deployment. I the specific of issue with Program Files is part of our deployment story and as such, this falls already into the IT Admin support deployment with MSI Installer. For instance there was a user that ran into registry issues/permission problems because of this "deployment strategy".īut at this point I'm moving on from Teams ever being a viable option, so feel free to just ignore this customer. There are threads in the Microsoft Forums about this very topic and how your "allowing end users to update apps without Admin rights" not only is a security issue, but that it also doesn't even work correctly. Staged and thoroughly tested updates that LIMIT bugs.Īlso, I've been pushing against this practice for a few years now. Maybe align more with all the rest of Microsoft Office products. Perhaps you should rethink your "deliver updates and fixes as quickly as possible" strategy. If the group at Teams doesn't see that as a problem then I guess I don't see their product having a place in my environments. Your "solution" for Teams installation simply doesn't work in a multitude of environments. It also conflicts with any RDS or VDI environment which is a MAJOR ISSUE. It also tries to VIOLATE the very security measures put in place to protect my end users. To make matters worse you can't even whitelists the applications through other means like Certificate or Hash. Installing to AppData conflicts with Security Policies. Reply to this email directly, view it on GitHub, or mute the thread.įine, then know that Teams will NEVER be used by a large number of Corporate entities. You are receiving this because you were assigned. Sorry - getting used to this new comment system Subject: Re: Location of install directory for users ( #101) To: MicrosoftDocs/OfficeDocs-SkypeForBusiness No apologies necessary! I just wanted everyone to know that I’m reaching out to the owners of install and setup to get some answers for you! GitHub Login: Microsoft Alias: ninadara.Content Source: Teams/msi-deployment.md.Content: Install Microsoft Teams using MSI.It is required for ➟ GitHub issue linking. In general I would like to handle Teams application like any other application in a enterprise environment, install to c:\program files (x86), and the patch it the way we patch all other applications. This would not be the case if the install was in %localappdata%\Microsoft\Teams. Since domain users is a member of this group, it means that all users from the domain can overwrite update.exe in the Teams folder and replace it with a “bad” file, not good from a security perspective. When I check the user rights for C:\ProgramData\kfl\Microsoft\Teams I see that local users group has write access to the folder. Under install I see the install directory as C:\ProgramData\kfl\Microsoft\Teams, install updated but not documentation? In your documentation the install directory is referred to as %localappdata%\Microsoft\Teams,
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |