Pushing Teams Background images through Intune

Microsoft announced that you can finally use custom background images during Teams meetings. Our customers directly contacted us how to upload those images. Some of them already created their own custom branding background image and wanted to distribute this towards their end users. The procedure for uploading your custom background images can be to technical for some end users. Therefore I’ve created following procedure to deploy those custom images towards end-users devices using Microsoft Endpoint Manager.

Prepare the Win32 Apps

The first thing you need to do is to create 3 folder. The first folder is to store your cmd command to create the folder structure, the second folder contains the images and the cmd command to copy the images and the third folder is to store the intunewin files.

First lets take a look at the copyfiles folder this contains my background image and the script to copy the files. The command I used to copy the files is mentioned below:

copy /Y .\Backgroundimage.jpg %APPDATA%\Microsoft\Teams\Backgrounds\Uploads\

The second folder is the folder that contains the script to create the folder structure for custom background images. It can be possible that some users doesn’t have the folder structure yet. Some of them received it already by using the latest version of Teams. The script I used to create the folder structure is mentioned below, it just simple navigates to the appdata folder of the user and create 2 folders Backgrounds and Uploads (Note: the custom background images needs to be deployed to this folder):

cd "%APPDATA%\Microsoft\Teams"
mkdir Backgrounds
cd ./Backgrounds
mkdir Uploads

Now you need to create your IntuneWin files this can be done by using the Win 32 Content Prep Tool. This tool can be downloaded here. If you downloaded the tool open a command prompt and navigate to the folder that contains the IntuneWinAppUtil.exe file. You need to specify the folder where you stored your cmd file, specify your script file name and specify the folder where you want the intunewin files to be stored (3th folder you’ve created). You need to do this for your folderstructure task and for your copy task.

As a result your IntuneWin files are created:

Configuration in Microsoft Endpoint Manager

The first task we need to do is to create the createfolderstructure Win32 App. Go to the portal and create a new app:

Select Windows app (Win32):

Click on select app package file and upload your IntuneWin file to create a folder structure

Fill in the basic settings like Name, Description and Publisher:

Please use the name of your cmd file as the install command. We didn’t create an uninstall command so I used the same cmd file. Select “User” as the install behavior we want that the folder is created in the users APPDATA.

Select the operating system architecture and the minimum OS version:

The next step is to create the detection rules, this validates if the script created the folder structure correctly. Use the settings below to configure the detection rules:

There are no dependencies for this app. Please proceed to the assignment section. Select the group where the app needs to be deployed. After the assignment create the application.

The next step is to create a Win32 App for copying the images to the correct folder. Create a new Win 32 App and upload the necessary intunewin file.

Fill in the App information:

Please specify the install and uninstall command:

Choose the OS requirements:

Configure the detection rules. As file or folder specify a file name that is included in your script:

You need to configure a dependency, the folder structure needs to be completed before you perform the copy of your backgroundimages.

Assign this task to the same group as your previous app and create the application.

End User Experience

If the tasks are performed users will be able to use the custom background images.

Published by jordyblommaert

My passion is the cloud

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: