Forum Discussion
Push files to Teams Custom Background Upload folder - Get the New Teams version
ChristianBergstrom thank you for the advice.
Here is my update with findings:
- our laptops and VDIs all received Teams version 1.3.00.12058 on various dates early May (ranging from 5/4 to 5/8 on the small group I sampled).
- Those that have that version do have the feature of Select Custom Background.
- Our problem was that we wanted to push (from Azure Intune to all company laptops) some company-branded background images to the designated folder for Teams: %AppData%\Microsoft\Teams\Backgrounds\Uploads. But that folder did not exist for everyone, only for some. We then concluded (wrongly) that some users did not have the feature.
- Turns out, the feature exists for everyone, but it only creates the Backgrounds folder and the Uploads folder in it upon first use of the Show Background Effects feature from the 3dot (...) menu in the meeting. When clicking any of the backgrounds offered by Teams (just click, not even need to actually use it) that background image PNG file is then placed in the Backgrounds folder.
- Therefore we are changing our script to also create the folder structure first, in case it does not exist yet (if the user did not try this feature yet), and only then copy the files in there. This way it will not fail on not finding the folder. Furthermore, when the user ever wants to use it, it will be there ready and waiting for them.
- For all this to work, naturally Teams has to be on it's latest version (or at least the one that supports it). Click the user icon on the Teams window top right (with your initials or picture), and choose Check For Updates to get the latest Teams version. It might take a bit, minutes or an hour to go, I am not sure. If you don't initiate it yourself, Microsoft documents that the Teams desktop app does that automatically every few hours, and even the admin doesn't have control of that.
So now we understand it was not about O365 versions and upgrade paths.
ChristianBergstrom - your blessing/validation of the findings will help the crowds here, I'm sure.
Regards, David.
ChristianBergstrom thank you for your reply.
We have two scenarios of the missing Change Background feature.
First, some of our laptops are missing it. They Do have the Blur Background feature (so I guess it's not an issue of missing CPU AVX2 feasure set, I saw other publications from you on that). Also they are on version 1.3.00.12058 which is the latest.
Second, all VDIs we sampled are missing it. They all Do have the Blur Background feature. We use Azure VMs accessed via Citrix as our VDIs. Also using the same latest Teams version 1.3.00.12058.
So now I understand we probably have the latest version, and also read that in the link you provided. Therefore looking for what condition is preventing some Teams clients from offering the feature. It's not the CPU AVX2 feature set, all our laptops are top of the line i5/i7 and 1-2 years old.
Thoughts?
Thank you very much,
Regards, David.
ChristianBergstrom thank you for the advice.
Here is my update with findings:
- our laptops and VDIs all received Teams version 1.3.00.12058 on various dates early May (ranging from 5/4 to 5/8 on the small group I sampled).
- Those that have that version do have the feature of Select Custom Background.
- Our problem was that we wanted to push (from Azure Intune to all company laptops) some company-branded background images to the designated folder for Teams: %AppData%\Microsoft\Teams\Backgrounds\Uploads. But that folder did not exist for everyone, only for some. We then concluded (wrongly) that some users did not have the feature.
- Turns out, the feature exists for everyone, but it only creates the Backgrounds folder and the Uploads folder in it upon first use of the Show Background Effects feature from the 3dot (...) menu in the meeting. When clicking any of the backgrounds offered by Teams (just click, not even need to actually use it) that background image PNG file is then placed in the Backgrounds folder.
- Therefore we are changing our script to also create the folder structure first, in case it does not exist yet (if the user did not try this feature yet), and only then copy the files in there. This way it will not fail on not finding the folder. Furthermore, when the user ever wants to use it, it will be there ready and waiting for them.
- For all this to work, naturally Teams has to be on it's latest version (or at least the one that supports it). Click the user icon on the Teams window top right (with your initials or picture), and choose Check For Updates to get the latest Teams version. It might take a bit, minutes or an hour to go, I am not sure. If you don't initiate it yourself, Microsoft documents that the Teams desktop app does that automatically every few hours, and even the admin doesn't have control of that.
So now we understand it was not about O365 versions and upgrade paths.
ChristianBergstrom - your blessing/validation of the findings will help the crowds here, I'm sure.
Regards, David.
David_Dudi_Yacouel Thanks for the update, I did mention the creation of the folder in a previous reply to you 😉 But great that you now have verified it as well. Good luck with the process!
ChristianBergstrom yes you definitely mentioned that, so we went and verified and used it. My last post serves as a summary so far, for future use. Thanks for staying close on this!