Hi guys, we recently rolled out a newer CU of the ...
# citrix-vad
f
Hi guys, we recently rolled out a newer CU of the Workspace App Client with the MicrosoftTeamsVDIPlugin parameter, to ensure a working moveother to Slimcore. I noticed that for most of the Clients it is still not working, the plugin is showing in appwiz.cpl and the following Appx-packages are found when running "Get-AppxPackage -AllUsers | ? {$_.Name -match "Slim|Teams"}": Microsoft.Teams.SlimCoreVdiFwk.win-x64.2026.12 Microsoft.Teams.SlimCoreVdiHost.win-x64 Microsoft.Teams.SlimCoreVdiFwk.win-x64.2026.22 UDP is also enabled aswell as all the Virutal Channels allower for MSTeams, we also use the latest Teams-version. After further troubleshooting I found in the ProcessExplorer, that the .dll for the MsTeamsPluginCitrix.dll isn't being loaded whatsoever, after further checking i noticed that the .dll is missing ENTIRELY. Even after deploying the standalone installation of the MSTeamPlugin the .dll is just not being created at all. On my client for a reference it is there and working fine, however i installed the Workspace App manually in the past, so I wouldn't use this as a reference. Any ideas - or did somebody face this in the past?
b
Which AV do you have on the endpoint?
👍 1
c
2507 CU2 CWA? what are your install parameters?
s
i remember having similar issues with no .dll present a year or so ago on some devices. If you uninstall the "Microsoft Teams VDI Citrix Plugin" and then install the MSI for it, does it exist then?
f
We are using Windows Defender, however I don't see any blocks in the Event Viewer We are using CWA 26.3.1.194 (2603.1) -> i meant the Current Release / not Cumulative, my bad. Uninstalling the Plugin and installing over MSI didn't do the trick. These are our install parameters: /cleaninstall /silent /noreboot InstallEPAClient=N Installzoomplugin=N /includeSSON /installMSTeamsPlugin ENABLE_SSON=Yes AutoUpdateCheck=Disabled EnableCEIP=False ADDLOCAL=ReceiverInside,ICA_Client,USB,DesktopViewer,AM,SSON,SelfService,WebHelper STORE0=XXX
On my client for example it is working fine, with the same GPOs/Exclusions etc.
I deployed the .dll manually now, in the post-install... hopefully this will get better with a newer release of the Workspace App