![]() We can see ms-teams.exe doing this in procmon during the process of adding a background manually: So, Teams is grabbing your image, and then assigning it a UUID.jpeg name, adding a UUID_thumb.jpeg file, and that gets added to the %LOCALAPPDATA\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\Backgrounds\Uploads directory. If you simply drag and drop images into this directory without this naming convention, New Teams will not recognize them. ![]() New Teams assigns a UUID to the image as the name, and also creates a smaller image for the thumbnail. Just to make sure this was the case, I added another image to confirm. My original test image was named “ozzy.jpeg”, but after adding the new image, it was renamed to 2dcf91dd-0b21-4266-bd5e-eb3dca976b9e.jpeg. You can do this from a meeting or the meeting lobby by selecting VIdeo Effects > backgrounds > Add New: I discovered this by manually adding a new image through the Teams App. ![]() New Teams uses the directory %LOCALAPPDATA%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\Backgrounds\Uploads. To review, with Classic Teams, we simply add images to that directory and Teams will automatically generate a thumbnail of the image, like in the image below: Classic Teams uses the directory %appdata%\Microsoft\Teams\Backgrounds\Uploads. As I mentioned, if you’re organization is using New Teams side-by-side with Teams Classic, your backgrounds do NOT transfer over to the new teams unless you have Teams Premium licensing and are deploying backgrounds using the Teams admin center. Now that we have some basics down on some of the differences between installation and installation paths, let’s see how we can start adding custom backgrounds to the new teams. If you’re using the Machine-Wide installer, it will be located at C:\Program Files (x86)\Teams Installer, but each user on the device still has Teams installed to their local profile on first sign-in. If we wanted to look at Teams Classic, we use get-package (since it’s not an MSIX) and can see that for each user, it’s installed to their profile. 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. 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 |