Do you guys do the .\teamsbootstrapper.exe -p or the whole path to the MSIX (.\teamsbootstrapper.exe -p -o "c:\path\to\teams.msix) install for new Teams? Both seem to do the same, but I was curious on feedback?

.\teamsbootstrapper.exe -p will pull down the MSIX "online" and install it. It takes a little longer, as it has to go pull it down. Or you can specify the MSIX location for bulk install "offline." which you point it to the UNC path if needed. Both are the same as what I see here. However, it was brought up that it will not download the latest version when you do it either way. Meaning you download what you think is the latest, and install it. Then open it up, and it will show an older version, for example. You download and install it with whatever desired install you want. Then, you have to let it sit for a minute or 2. Exit teams will then reopen it, and it will update itself. That is very odd behavior that I have seen just now. I went through and double-checked this. I pulled down the teamsbootstrapper.exe and installed it via—p. The version it installed was 24033.813.2779.520. Then, I closed Teams altogether and opened it as a backup. It took about 10 seconds to open, and then I noticed it had the latest version. 24060.2623.2790.8046. Did the same procedure with the msix (.\teamsbootstrapper.exe -p -o "c:\path\to\teams.msix) path and got the same results. This was on a golden image. I'm not sure if it was designed that way or if MS messed up the download link. Curious if others are seeing this as well.

Did you download the latest bootstrapper? I have seen you need to have the latest to get the latest Teams.

Yep. You download and install it. Even if you install the latest bootstrapper( download it and Install), it will still show an older version. I went through it last night and this morning to verify. It may change in the near future, but as of now, you have installed it, closed teams, opened it up, and it will update. Then, I put the autodisable back on the Golden image to keep it from updating for this scenario or situation.

Interesting, I will have to look into that, and maybe modify my patching script. Thanks for the info.

Yea, check it out and see if you get the same thing. I am really curious here myself.

Can confirm. One more bug for the Teams team.

Okay cool Thanks man for checking

Luckily I had a maintenance image up as we are pulling out 1.x. So I downloaded a fresh bootstrapper and ran a -x to get rid of the app then did the install with just -p. I then downloaded the latest msix and did the -p -o. Both times they came down to the same image. So it looks like they only do a rollup to a certain version level, and then everything else comes down as updates.

Okay, thanks for the update. The problem is that on W10, the location is restricted by default to this location. WindowsApps ( hidden Folder) "C:\ProgramFiles\WindowsApps\MSTeams_24074.2321.2810.3500_x64__8wekyb3d8bbwe" On W11, it seems to be open via GUI. Now, I can navigate to it via CLI with W10, but not via GUI. Seen this in other customers setup as well.

wow, this new version has lot's of loopholes 😞

It will get ironed out in time. it's how things are at times. Just roll with it and come up with workarounds

Sorry it took so long. This was a long rabbit hole to go down. I have created a new powershell script specifically for Teams 2 that will install Teams from the bootstrapper, execute an update, and then install the Teams Add-in automatically. If Teams 2 is already installed it will execute an update of Teams, and if there is an updated Teams Add-in for Outlook it will install that. Want to take it for a test spin and let me know what needs to be fixed on it? https://www.jeffriechers.com/wiki/teams-2-1-with-fslogix-setup-guide/

@Jeff Riechers very nice man. Definitely will check this out.

Just remember, I am not a coder, so no laughing at my syntax. 😉

Oh na man, same here. I build it to work. I could care less how it works or if it’s dev worthy lol. My current one is probably messy to.

After rolling some testing I am seeing my code isn't updating right. I have a whole new update process I am testing now and will share it when I get it done.