I'm looking to install New Teams 2.0 this month on Windows Server 2022. Does it make any relevant difference, if I install New Teams:

.\teamsbootstrapper.exe -p

VS

.\teamsbootstrapper.exe -p -o "c:\path\to\teams.msix"

On a monthly replace master image? I would choose the first option, as it would simplify the script a lot.

As I understand it, the last option requires you to download the msix manually, while the first option will download it for you

Yes exactly. Would be easy to solve with Evergreen. But is it something I would have to solve in the first place?

The Teamsbootstrapper will only install the latest rolled up version. You have to update Teams via launching it. I have a guide and powershell that will install and patch it. https://www.jeffriechers.com/wiki/teams-2-1-with-fslogix-setup-guide/

We replace our master images monthly. Does your argument still apply?

Yes, because they will have sub-updates outside the bootstrapper. So run that with the -p, then just launch teams after the install and it will kick off the update. You will need to launch and close it twice to get it fully cutover. Then install the Outlook Teams plug-in with the allusers switch after all the updates are done. Again, something my script can do for you if you like automation, feel free to steal from it.

If I would use

.\teamsbootstrapper.exe -p -o "c:\path\to\teams.msix"

instead, would that handle the sub-updates? I must admit I'm super confused.

Only if that teams.msix is the latest version. They don't always roll up all the latest patches into the msix it downloads. They let sub versions just update as part of the software. And they sometimes release them multiple times a month.

Mh I'm still not convinced, that this should matter to me. With

.\teamsbootstrapper.exe -p

I installed the version the MS publishes at the moment of install. Then I disable auto updates. 4 weeks later I repeat the process. Would the hastle to work with start-process, start-sleep, stop-process be worth that? The reason I say that is, because I hate to use start-sleep in an image build process.

Yup. Hopefully the New New Teams has a better update process.

I don't want to use sleeps in my script, what a PITA

Yup. Use Dism to get it installed, then launch it to patch.

I already wrote a PoC for the setup, was asking for the update. Thank you. So I could adapt the concept.

Need to make sure that the disable updates is NOT set for the user running the script, or the maintenance machine. I have had it work just opening to the login window.

Yes, I already expected that, so I commented the line in my script, that disabled the updates.

@Jeff Riechers thanks and i've been using your script and it's great. when you get ready to update your master, are you uninstalling teams, add-in and webview before running your script each time for updates?

@Matt Nation Does it work for you, that the script installs the mini in between updates through sleeps without logging in?

I uninstall the add-in as sometimes updates will install it under the user environment, instead of the whole system. One thing I need to add is a check in the script to see if the the ms-teams.exe is in your profile, if not then have it stop and prompt you to launch it once. But you should not have to login, it will update itself while sitting at the login screen. Just make sure that the registry entries are NOT in place to block updates on your update machine.

thanks @Jeff Riechers So on a master/golden image, do not set the keys to prevent the automagic updates?

I will set those either on an OU with the non-persistent machines, or will use a sealing script to prepare the machine and set the value then. If you use the script route, just add a similar script to remove that setting before running updates.