Forum Discussion
Dharani_Raj
Jan 29, 2025Copper Contributor
Teams addin missing in Classic outlook in Azure virtual desktop
Hello Everyone! We have both classic and new teams installed in our AVD environment, Win11 Multisession. Since we have updated our AVD machines with the new image, we noticed that it does not have t...
- Feb 12, 2025
Hi Axel,
Thank you for your response! It looks like I came to your response a little late. I already found the solution with this link, which has the script that you can directly deploy to install the addin.
New Microsoft Teams for Virtualized Desktop Infrastructure (VDI) - Microsoft Teams | Microsoft Learn
With the latest Teams versions, they got rid of those registries and made it simpler with one. The above link will give you more information.
But I'm very happy to get so many helps on this topic. Thank you, Axel and everyone. I truly appreciate all your help. <3
If (-not ([Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole] 'Administrator') ){ Write-Error "Need to run as administrator. Exiting.." exit 1 } # Get Version of currently installed new Teams Package if (-not ($NewTeamsPackageVersion = (Get-AppxPackage -Name MSTeams).Version)) { Write-Host "New Teams Package not found. Please install new Teams from https://aka.ms/GetTeams ." exit 1 } Write-Host "Found new Teams Version: $NewTeamsPackageVersion" # Get Teams Meeting Addin Version $TMAPath = "{0}\WINDOWSAPPS\MSTEAMS_{1}_X64__8WEKYB3D8BBWE\MICROSOFTTEAMSMEETINGADDININSTALLER.MSI" -f $env:programfiles,$NewTeamsPackageVersion if (-not ($TMAVersion = (Get-AppLockerFileInformation -Path $TMAPath | Select-Object -ExpandProperty Publisher).BinaryVersion)) { Write-Host "Teams Meeting Addin not found in $TMAPath." exit 1 } Write-Host "Found Teams Meeting Addin Version: $TMAVersion" # Install parameters $TargetDir = "{0}\Microsoft\TeamsMeetingAddin\{1}\" -f ${env:ProgramFiles(x86)},$TMAVersion $params = '/i "{0}" TARGETDIR="{1}" /qn ALLUSERS=1' -f $TMAPath, $TargetDir # Start the install process write-host "executing msiexec.exe $params" Start-Process msiexec.exe -ArgumentList $params write-host "Please confirm install result in Windows Eventlog"
AxelGlzs31
Feb 06, 2025Copper Contributor
Hello,
I had the same issue, and here’s how I fixed it:
On your master image:
1. Create the following registry keys:
New-Item -Path “HKLM:\Software\Microsoft\Office\Outlook\Addins” -Name “TeamsAddin.FastConnect” -Force -ErrorAction Ignore
New-ItemProperty -Path “HKLM:\Software\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect” -Type “DWord” -Name “LoadBehavior” -Value 3 -force
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
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
2. Reinstall the ‘Teams Meeting Add-in’ in “C:\Program Files (x86)\Microsoft\TeamsMeetingAddin\”
You can find the program in “C:\Program Files\WindowsApps\MSTeams_24277.3507.3205.5228_x64__8wekyb3d8bbwe”
3. Execute this PowerShell script via GPO:
# Define the necessary file paths.
$regsvr32Path = "C:\Windows\System32\regsvr32.exe"
$dllPath = "C:\Program Files (x86)\Microsoft\TeamsMeetingAddin\1.24.25702.0\x64\Microsoft.Teams.AddinLoader.dll"
# Run the command to register the DLL.
Start-Process -FilePath $regsvr32Path -ArgumentList "/n /s /i:user `"$dllPath`"" -NoNewWindow -Wait
Write-Output "DLL successfully registered."
- Dharani_RajFeb 12, 2025Copper Contributor
Hi Axel,
Thank you for your response! It looks like I came to your response a little late. I already found the solution with this link, which has the script that you can directly deploy to install the addin.
New Microsoft Teams for Virtualized Desktop Infrastructure (VDI) - Microsoft Teams | Microsoft Learn
With the latest Teams versions, they got rid of those registries and made it simpler with one. The above link will give you more information.
But I'm very happy to get so many helps on this topic. Thank you, Axel and everyone. I truly appreciate all your help. <3
If (-not ([Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole] 'Administrator') ){ Write-Error "Need to run as administrator. Exiting.." exit 1 } # Get Version of currently installed new Teams Package if (-not ($NewTeamsPackageVersion = (Get-AppxPackage -Name MSTeams).Version)) { Write-Host "New Teams Package not found. Please install new Teams from https://aka.ms/GetTeams ." exit 1 } Write-Host "Found new Teams Version: $NewTeamsPackageVersion" # Get Teams Meeting Addin Version $TMAPath = "{0}\WINDOWSAPPS\MSTEAMS_{1}_X64__8WEKYB3D8BBWE\MICROSOFTTEAMSMEETINGADDININSTALLER.MSI" -f $env:programfiles,$NewTeamsPackageVersion if (-not ($TMAVersion = (Get-AppLockerFileInformation -Path $TMAPath | Select-Object -ExpandProperty Publisher).BinaryVersion)) { Write-Host "Teams Meeting Addin not found in $TMAPath." exit 1 } Write-Host "Found Teams Meeting Addin Version: $TMAVersion" # Install parameters $TargetDir = "{0}\Microsoft\TeamsMeetingAddin\{1}\" -f ${env:ProgramFiles(x86)},$TMAVersion $params = '/i "{0}" TARGETDIR="{1}" /qn ALLUSERS=1' -f $TMAPath, $TargetDir # Start the install process write-host "executing msiexec.exe $params" Start-Process msiexec.exe -ArgumentList $params write-host "Please confirm install result in Windows Eventlog"
- Chris_toffer0707Feb 15, 2025Iron Contributor
I had to insert a few lines of code to make sure the addin was uninstalled first, because in my case I was using a golden image VM, and the current user running the script as admin, already had the addin installed.
try { $params = '/qn /x "{0}"' -f $TMAPath Start-Process msiexec.exe -ArgumentList $params } catch{ write-host "Error uninstalling Teams Meeting Addin. Most likely it is not installed in current users context." }
I know it is not very pretty but it works.
But now it works and deployment of session hosts works with the Teams Meeting add-in present to users.
- Dharani_RajFeb 24, 2025Copper Contributor
Thank you, Chris, for your response! We are not using a custom image / golden image. So it's a live environment with MS gallery image. But I'll make a note of your script for any future requirements. Appreciate it :)