Show of hands who are running 32bit office with Team 2 and have the outlook plugin working 100%? No profile management, and all local. Fresh image. Tried neverred, tried custom scripts I made, tried manual way. Just won't load for 32 bit office. Tried MSIX32 install way. Switch to 64 Office, bam it comes in. Tried the 32-bit plugin only, which from following MS article here. It looks to be adding both and register the dlls. Anybody seen this yet? Just wanted to check and see if others see this or it's something I'm doing wrong then?

I didnt think 32bit office even existed anymore 🙂

We're using Office 32bit, here's our install script for Teams and the add-in.

Start-Process "C:\Temp\teamsbootstrapper.exe" -ArgumentList "-p -o `"C:\Temp\MSTeams-x64.msix`"" -Wait
$VERSION=(Get-AppxPackage | where {$_.Name -eq 'MSTeams'}).Version
$DisplayName = (Get-AppxPackage | where {$_.Name -eq 'MSTeams'}).Name
Add-Content -Value "Mise à jour $($DisplayName) v. $($VERSION)" -Path 'C:\Temp\CHANGELOG.md' -Encoding UTF8
REG ADD "\\$($env:COMPUTERNAME)\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Teams" /v disableAutoUpdate /t REG_DWORD /d 1 /f
REG ADD "\\$($env:COMPUTERNAME)\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Teams" /v DisableFallback /t REG_DWORD /d 2 /f
REG ADD "\\$($env:COMPUTERNAME)\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Citrix\WebSocketService" /v ProcessWhitelist /t REG_MULTI_SZ /d 'msedgewebview2.exe' /f
$UninstallTeamsAddin = (Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -eq 'Microsoft Teams Meeting Add-in for Microsoft Office'}).UninstallString
$UninstallTeamsAddin = $UninstallTeamsAddin -Replace("MsiExec.exe /I","")
Start-Process -FilePath msiexec.exe -ArgumentList "/X $UninstallTeamsAddin /qn" -Wait
Start-Process msiexec.exe -ArgumentList "/i `"$((Get-ChildItem -Path 'C:\Program Files\WindowsApps' -Filter 'MSTeams*').FullName)\MicrosoftTeamsMeetingAddinInstaller.msi`" Reboot=ReallySuppress ALLUSERS=1 TARGETDIR=`"C:\Program Files (x86)\Microsoft\TeamsMeetingAddin`" /qn" -Wait
$VERSION=(Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -eq 'Microsoft Teams Meeting Add-in for Microsoft Office'}).DisplayVersion
$DisplayName = (Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -eq 'Microsoft Teams Meeting Add-in for Microsoft Office'}).DisplayName
Add-Content -Value "Mise à jour $($DisplayName) v. $($VERSION)" -Path 'C:\Temp\CHANGELOG.md' -Encoding UTF8
REG ADD "\\$($env:COMPUTERNAME)\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect" /v Description /t REG_SZ /d 'Microsoft Teams Meeting Add-in for Microsoft Office' /f
REG ADD "\\$($env:COMPUTERNAME)\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect" /v FriendlyName /t REG_SZ /d 'Microsoft Teams Meeting Add-in for Microsoft Office' /f
REG ADD "\\$($env:COMPUTERNAME)\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect" /v LoadBehavior /t REG_DWORD /d 3 /f

We're still in the early stages of testing, so to say it works 100% would be a bit presumptuous. But it definitely loads correctly.

This I got working but I had to enable load behavior in the users hive. Maybe try that.

Thanks, guys, I did all this. But going to try once more.

Why are you still running 32 bit office? Unless you have some old Excel plugins that are only written for 32 bit I haven't seen any issues moving up to 64 bit.

is that a serious question?

A lot of them, haven't seen any of them tied to 32 bit. Is there an app integration for a particular EMR?

Understood, man, I thought you were yanking my chain lol. but I can't tell a customer to go upgrade the office from 32bit to 64bit with all the plugins they have now in place just to make Teams 2 work in Outlook, it's not an option for me and for some customers. I can suggest it, but as you know, customers have to go through a whole process of changing offices, validation, and testing with existing things. Now I have used Office 64bit for years myself. Now, some can, but when you have large enterprise customers, Change is very hard when you have many plugins that work 100% with 32bit. It's really not something I can make them change, I can suggest it, but at the end of the day. The customers are going to hit the docs and say hey it says it works with 32bit. So it's not that I am running it; it's around providing a seamless transition to new Teams to retrofit what they have now. Now, if Microsoft came back and said hey, 32bit Office or Outlook, in this case, is EOL, and Teams 2 is only supported with 64bit, then that is a different story. At the end of the day, as a Consultant, you have to be able to pivot with many versions of OS, W10, W11, 2019, 2022, 64bit, or 32bit apps. This means that I have to ensure CPM Containers, FSLogix Containers, CPM files, Invanti UEM(personalization) , and WEM (CPM side) all work well. So when I conduct testing it's all or nothing. I have to be able to back things up.

I hear ya. Was just looking to see if there was another 32 vs 64 bit compatibility issue I was missing.