Microsoft Teams
A Microsoft customizable chat-based workspace.
10,102 questions
Teams Meeting Add-in not installing on Windows server 2022 Remote desktop server
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(265.6, 71%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBD%3C/text%3E%3C/svg%3E)
Bram Drijvers | OBI - ICT voor het MKB
0
Reputation points
I am having issues with the Teams meeting add-in for multiple users on 3 different Remote desktop servers.
Teams is installed using the machine wide installer but for some users the Teams meeting add-in is not being installed.
The tma_addin_msi.txt file is not being created.
The users have a FSLogix profile and FSLogix is updated to the latest version.
The Teams version on the Remote desktop servers is: 24231.512.3106.6573 The Teams meeting Add-in is installed on the server and the version is: 1.24.23304
The MSTeamsUpdate file is showing the following error:
2024-09-26T07:04:31.816109+02:00 0x00002038 <INFO> SingleThreadedWorkerWin: Waiting for Work on worker thread : TelemetryServiceWorker
2024-09-26T07:04:31.862983+02:00 0x00003aa0 <INFO> TelemetryService: Sampling rules from previous session recovered
2024-09-26T07:04:31.862983+02:00 0x00003aa0 <INFO> TelemetryService: InitOfficeDiagnosticLevel to OfficeDiagnosticLevel::Unset
2024-09-26T07:04:31.862983+02:00 0x00003aa0 <INFO> TelemetryService: forcing diagnostic level OfficeDiagnosticLevel::NSD
2024-09-26T07:04:31.862983+02:00 0x00003aa0 <INFO> vdi::VDIProvider: : VDIMode: 0000
2024-09-26T07:04:31.878607+02:00 0x00003aa0 <INFO> TelemetryService: No primary user detected during a SetUserTenantId Call, setting 7d1be701-3aa2-4758-a7a1-e06180540555 as default tenant
2024-09-26T07:04:31.878607+02:00 0x00003aa0 <INFO> TelemetryService: No primary user detected during a SetUserId Call, setting 7f5d6974-c014-4a33-b693-f74d13cce5a3 as UserInfo_Id
2024-09-26T07:04:31.878607+02:00 0x00003aa0 <INFO> TelemetryService: Restored sampling rules from previous session
2024-09-26T07:04:31.897751+02:00 0x00003aa0 <INFO> EcsSettings: Full build path /BuildSettings/WebView2Canary/x64/latestVersion
2024-09-26T07:04:31.897751+02:00 0x00003aa0 <INFO> EcsFetchCompletion: Ecs settings are already up to date
2024-09-26T07:04:31.897751+02:00 0x00003aa0 <INFO> UpdaterMain: Wait for ECS check result:0
2024-09-26T07:04:31.897751+02:00 0x00003aa0 <INFO> BackgroundTaskBase: Registered TeamsTfwAsyncUpdaterTask background task successfully
2024-09-26T07:04:31.897751+02:00 0x00003aa0 <INFO> BackgroundTaskBase: Registered TeamsTfwEcsTask background task successfully
2024-09-26T07:04:31.941530+02:00 0x00003aa0 <INFO> settings::AppSettings: Main window state value: 1
2024-09-26T07:04:31.941530+02:00 0x00003aa0 <INFO> settings::AppSettings: Main window state before restart value: 256
2024-09-26T07:04:31.957156+02:00 0x00003aa0 <INFO> EcsSettings: Full build path /BuildSettings/WebView2Canary/x64/buildLink
2024-09-26T07:04:31.957156+02:00 0x00003aa0 <INFO> EcsSettings: Full build path /BuildSettings/WebView2Canary/x64/latestVersion
2024-09-26T07:04:31.957156+02:00 0x00003aa0 <ERR> DeploymentProviderMSIX: Already up to date
2024-09-26T07:04:31.957156+02:00 0x00003aa0 <ERR> WIL: ms-teamsupdate.exe!00007FF6996D2EE4: LogHr(1) tid(3aa0) 800704C7 De bewerking is geannuleerd door de gebruiker.
2024-09-26T07:04:31.957156+02:00 0x00003aa0 <ERR> WIL: ms-teamsupdate.exe!00007FF699865296: ReturnHr(1) tid(3aa0) 800704C7 De bewerking is geannuleerd door de gebruiker.
Msg:[winrt::hresult_error: De bewerking is geannuleerd door de gebruiker.]
2024-09-26T07:04:31.957156+02:00 0x00003aa0 <INFO> UpdateInstaller: InstallUpdateInternal: Download failed with error: -2,147,023,673, extended error: 0, error message:
2024-09-26T07:04:31.957156+02:00 0x00003aa0 <INFO> UpdateInstaller: InstallUpdateInternal download result: -2,147,023,673, cancel reason: None
2024-09-26T07:04:31.957156+02:00 0x00003aa0 <INFO> UpdateStateStoreWinRTAppData: previous app session:7bed8e75-9ece-4ffd-b8f0-5c57f472447c current app session:7bed8e75-9ece-4ffd-b8f0-5c57f472447c target version:24231.512.3106.6573
2024-09-26T07:04:31.957156+02:00 0x00003aa0 <INFO> UpdateStateStoreWinRTAppData: Current total update failure count:0
2024-09-26T07:04:31.957156+02:00 0x00003aa0 <INFO> UpdateStateStoreWinRTAppData: Erasing update attempt
2024-09-26T07:04:31.957156+02:00 0x00003aa0 <INFO> UpdateStateStoreWinRTAppData: Storing update attempt for app session:7bed8e75-9ece-4ffd-b8f0-5c57f472447c,target version:24231.512.3106.6573
2024-09-26T07:04:31.957156+02:00 0x00003aa0 <INFO> TeamsMeetingMsiAddin: Meeting Addin MSI msexec command: TEAMSFLAVOR=T2.1 MSIINSTALLPERUSER=1 ALLUSERS=2 REBOOT=ReallySuppress InstallerVersion=v3
2024-09-26T07:04:31.957156+02:00 0x00003aa0 <INFO> TeamsMeetingMsiAddin: MsiGetProductInfo returned code 1,608
2024-09-26T07:04:31.957156+02:00 0x00003aa0 <INFO> TeamsMeetingMsiAddin: Trying to remove residual registry key from previous partial uninstall
2024-09-26T07:04:31.957156+02:00 0x00003aa0 <ERR> Scenario: shell_install_msi_addin [stop,failure] InstanceId:ec600cac-795f-40b6-8fb3-592bec41c47e,Scenario.Mode:3,Scenario.Name:shell_install_msi_addin,Scenario.Status:failure,Scenario.Step:stop,Scenario.Steps:[{"Scenario.Status":"failure","Scenario.Step":"stop","delta":5,"elapsed":93,"elapsedSinceProcessStart":246,"previousStep":"start","sequence":1,"stepDelta":5}],Scenario.****:[{"UpdateCheckReason":"MainAppUpdateCheck","errorCode":1608,"reason":"MsiGetProductInfo","teamsFlavor":"T2.1"}],UpdateCheckReason:MainAppUpdateCheck,delta:5,elapsed:93,elapsedSinceProcessStart:246,errorCode:1608,eventpdclevel:3,previousStep:start,reason:MsiGetProductInfo,sequence:1,stepDelta:5,teamsFlavor:T2.1
2024-09-26T07:04:31.988404+02:00 0x00003aa0 <INFO> settings::AppSettings: Main window state value: 1
2024-09-26T07:04:31.988404+02:00 0x00003aa0 <INFO> settings::AppSettings: Main window state before restart value: 256
2024-09-26T07:04:33.102653+02:00 0x00003aa0 <INFO> TelemetryService: Telemetry service stopped
Microsoft Teams
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
13,070 questions
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(172.8, 5%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERS%3C/text%3E%3C/svg%3E)
Robin Sheng-MSFT 3,050 Reputation points Microsoft Vendor2024-09-27T05:12:56.9433333+00:00 Hi @Bram Drijvers | OBI - ICT voor het MKB
According to your case description, your Teams meeting add-in has an error on the remote desktop server. Please try the following steps to troubleshoot the Teams meeting add-in problem on the remote desktop server:
Reinstall the Teams meeting add-in: Uninstall the Teams meeting add-in from the server. Reinstall it using the msiexec /i command.
msiexec.exe /i "C:\Program Files\WindowsApps\MSTeams_X.X.X.X_x64__8wekyb3d8bbwe\MicrosoftTeamsMeetingAddinInstaller.msi" ALLUSERS=1 /qn /norestart TARGETDIR="C:\Program Files (x86)\Microsoft\TeamsMeetingAdd-in\<version>\"Verify FSLogix configuration: Make sure FSLogix is correctly configured to handle Teams cache and profile data. Sometimes, problems with the FSLogix configuration file may prevent the add-in from loading correctly.
Check registry keys: Residual registry keys from previous installations may cause problems. You can try to delete any residual keys manually or using a cleanup tool.
Update Teams and Office: Make sure both Microsoft Teams and Office are updated to the latest version.
For more detailed information, refer to Upgrade to the new Teams for Virtualized Desktop Infrastructure (VDI) or Verify registry settings.
Thank you for your understanding and patience!
Sign in to comment
Sign in to answer