This is data related to their Teams sign-in profile and is stored in %LOCALAPPDATA%l\Packages\MSTeams_8wekyb3d8bbwe However, similar to classic teams, new teams has some data that lives in the local user profile (where the backgrounds and other cached data are stored). We can see the install path pointing to C:\Program Files\WindowsApps. Let’s take a quick look at the app details using get-appxpackage in PowerShell: It’s more like a Microsoft Store application than a traditional MSI/EXE installer. Without getting too into the weeds, the new Teams app differs from the classic app in that it’s an MSIX package. I will be using the same method using blob storage that I used in this post, so I will skip over the beginning portion. There is one extra pre-req for new teams, but the rest is mostly the same, other than changing some paths. If you are still using classic teams, see my previous post here. This post focuses on adding backgrounds for New Teams. ![]() Using this method allows you to deploy custom backgrounds to your users without a Teams Premium license. I took a look at where backgrounds are stored in the new teams, and how we can deploy backgrounds with remediations. As I’ve been testing the new teams, I realized that custom backgrounds that were manually added, or added via remediations, do not transfer over to the New Teams. There are several reasons to make the switch, the biggest reason likely being the performance benefits. IPhone - Select the image you would like to use as a wallpaper below.With the New Teams app being GA, organizations will eventually move from “Teams Classic” to the “New Teams” app.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |