Anyone seen this behaviour with MS teams 2.1 and Teams outlook add in. The ms teams outlook Com add-in says it is enabled but i dont see it in Outlook. MS teams is listed in meeting providers under calendar options

Did you check/set the registry keys?

New-Item -Path "HKLM:\Software\Microsoft\Office\Outlook\Addins" -Name "TeamsAddin.FastConnect" -Force -ErrorAction Ignore | Out-Null

New-ItemProperty -Path "HKLM:\Software\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect" -Type "DWord" -Name "LoadBehavior" -Value 3 -force | Out-Null

New-ItemProperty -Path "HKLM:\Software\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect" -Type "String" -Name "Description" -Value "Microsoft Teams Meeting Add-in for Microsoft Office" -force | Out-Null

New-ItemProperty -Path "HKLM:\Software\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect" -Type "String" -Name "FriendlyName" -Value "Microsoft Teams Meeting Add-in for Microsoft Office" -force | Out-Null

Looks like all i had to do was open ms teams 2.1 before opening outlook 🤦🏻‍♀️

Also if you have issues with it pointing to the user location instead of the program files location, do the following.

Also for the load behavior and forcing it to set to 3. If the Teams Plugin path is incorrect for whatever reason, Forcing it to 3 does nothing, it will revert back to 2 every time cause it can't load the path due to the path being incorrect. Which the Keys above will fix it and the forcing to 3 will do it's job.

i spoke too soon cant get it working at all. This is a brand new server 2022 PVS image i used Jeff's powershell script to install ms teams 2.1 no error's during execution. The load behaviour registry keys Dennis mentioned for MS teams outlook add-in are set in HKLM. I launch Outlook as an seamless published application to a VDA using the new 2022 PVS image and i dont see the MS Teams add in when i go into calendar. I check the com add-ins and it is listed and started and path is correct "C:\Program Files (x86)\Microsoft\TeamsMeetingAddin\1.24.23304.0\x64" opening MS teams v2.1 as a seamless application froom (C:\Program Files\WindowsApps\MSTeams_24231.512.3106.6573_x64__8wekyb3d8bbwe) before or after Outlook launch makes no difference. The reg keys jeff mentions i dont see the only ones i see are HKCU\Software\Microsoft\office\Outlook\Addins\TeamsAddin.FastConnect which i have tried deleting to no avail

Does it work from the desktop, or do you see the same thing.

will check published desktop now

Just tested with a customer that we updated to the latest teams and outlook did not see the plugin, until they launched teams first, then opened outlook at everything was there, and it stayed persistent.

stumped as i dont see that behaviour i open ms teams first then outlook and the "New teams meeting" button is missing from within calendar. The add-in looks like it is enabled and event logs suggest the add-in is loaded Log Name: Application Source: Outlook Date: 25/09/2024 154600 Event ID: 45 name: Microsoft Teams Meeting Add-in for Microsoft Office Description: Microsoft Teams Meeting Add-in for Microsoft Office ProgID: TeamsAddin.FastConnect GUID: {19A6E644-14E6-4A60-B8D7-DD20610A871D} Load Behavior: 3 HKLM: 1 Location: C:\Program Files (x86)\Microsoft\TeamsMeetingAddin\1.24.23304.0\x64\Microsoft.Teams.AddinLoader.dll Boot Time (Milliseconds): 3187

Do you have all the Appx deployment policies set in GPO? Doing full profile, or just office? And have the exclusions setup for teams 2 instead of teams 1?

@c4rm0 why are you having some much issues. Teams is easy man... come on. LMAO jk

i hate it with a passion i purposely didnt touch it for months as expected the issues to be ironed out

It's challenging for sure, but the docs are way better now than before.

appx polices are set its fslogix profile/ODFC i will take a look at the exclusions sure i added them to the redirections.xml but will double check

The is a TMA logs location, Can't remember, but the docs will tell you where it's at.

with both profile and odfc it could be running into a redirecting on redirecting issue. Try using just profiles, not both.

this one @Ray Davis ?Installation logs for TMA MSI are stored here: _AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\Logs \tma_addin_msi.txt_

As a Test, Remove it all. Just do the base install .\bootstrapper -p Don't install the plugin via machine wide. Then test to see if the "auto load" per user kicks in. It should, and if it does then it's something else then.

yeah am gonna remove it and start again ./teamsbootstrapper -x i use that to remove it all ?

What happens when you just do a base install via -p is Teams will auto load the plugin by default. Nothing something we want though, but as a test. yea -x is fine, then run the get-appxpackage to make sure it's really gone. Uninstall the MSI as well. Ensure the whole teams foles is gone in windowapps

so uninstalled completley ./teamsbootstrapper -x and removed the teams meeting addin via add/remove programs and cleaned up the teams and meeting addin folders and reinstalled with jeffs's script and same issue so removed again and tried the manual way via microsoft page and again the same issue !!! . While testing i noticed if i run the ms-teams.exe from c:\Program Files\WindowsApps\MSTeams_24231.512.3106.6573_x64__8wekyb3d8bbwe\ as a published seamless citrix app or from a rdp session (Jeff's script grants users read+ execute perms to this folder) thats when teams meeting add-in doesnt show up in outlook no matter the order of launch with teams/outlook. I found if i run the Microsoft teams icon from the start menu on the rdp session then the teams outlook add in is working when you open Outlook. So I have published MS teams in citrix by browsing to the start menu of the machine and it published MS teams using UWAlauncher and so far it appears to be working fine

Did you install the add-in as part of the script install? In my test environment users did have to open teams first, then outlook and the add-in would work correctly.

yeah i ran your script and didnt skip anything and i didnt see any errors in powershell or log. Microsoft install way i ran .\teamsbootstrapper.exe -p -o "\unc\path\to\teams.msix and then opened MS teams app > uninstalled user installed Teams meeting add-in in add/remove progs > then ran Get-AppXPackage -Name "*msteams*" | Select-Object -ExpandProperty Version > Get-AppLockerFileInformation -Path "C:\PROGRAM FILES\WINDOWSAPPS\MSTEAMS_24026.1000.2656.1710_X64__8WEKYB3D8BBWE\MICROSOFTTEAMSMEETINGADDININSTALLER.MSI" | Select -ExpandProperty Publisher | select BinaryVersion > then msiexec.exe /i "C:\Program Files\WindowsApps\MSTeams_23320.3021.2567.4799_x64__8wekyb3d8bbwe\MicrosoftTeamsMeetingAddinInstaller.msi" ALLUSERS=1 /qn /norestart TARGETDIR="C:\Program Files (x86)\Microsoft\TeamsMeetingAdd-in\1.24.2203.0\" obviously changing the versions numbers in above commands as per MS article

Launching from WindowsApps really only works for the update mechanism. But for doing a published app it is best to go from the profile. But sometimes that profile launch location doesn't show up until after they launch it once, which requires running it from the start menu. Still working to find a better guaranteed launch position for users with nothing in their profile.