Hi, Teams 24215.1007.3082.1590 appears to break Ou...
# citrix-vadf
François-Xavier Rigaud
09/11/2024, 1:51 PMHi, Teams 24215.1007.3082.1590 appears to break Outlook Teams Meeting Add-In.
It wrongly try to load the DLL from the user profile despite having it installed machine-wide.
Is anyone else affected by this?
🤦♂️ 3
🤦 1
b
Balint Oberrauch
09/11/2024, 1:52 PMNot another issue - I hate teams 😢
😅 2
😮 1
😢 1
t
Tom Berntsen
09/11/2024, 1:57 PMYeah, just checked our test servers, the meeting add-in is gone for the users. Perfect timing as we are in the final leg before rolling it out to all users.
r
Ryan Gallier
09/11/2024, 1:59 PM@Marco Hofmann ^---
❤️ 1
j
Julian Jakob
09/12/2024, 10:37 AMSame here, any confirmations from MS?
m
Marco Zimmermann
09/12/2024, 1:53 PMOne of my customers was in contact with MSFT. Answer in short: Known Issue in Outlook Classic, solution: Use NEW Outlook :D
🤦 1
😡 1
Marco Zimmermann
09/12/2024, 2:02 PMin his case outlook was looking for this dll:
Microsoft\TeamsMeetingAddin\1.24.19202\x86\Microsoft.Teams.AddinLoader.dll
but the correct location was ..\1.24.19202*.0*\..
If thats really the same problem here it could be easily resolved by an FSLOGIX redirection policy filtered to outlook.exe
j
Jeff Riechers
09/12/2024, 2:34 PM24231 is broken as well.
f
François-Xavier Rigaud
09/20/2024, 11:40 AMVersion 24231.512.3106.6573 seems to work. Can anyone else confirm?
m
Marco Hofmann
10/14/2024, 8:56 AMAre there any news on this front? With this months images, we still seem to face the same problem.
In our October images we have Teams 24243.1309.3132.617 and Meeting Add-In 1.24.25503
cc @Stephan Sprathoff
f
François-Xavier Rigaud
10/14/2024, 12:19 PM@Marco Hofmann Hello, for our part, starting from 24231.512.3106.6573 this issue was not seen anymore.
s
Stephan Sprathoff
10/14/2024, 12:34 PMThe TARGETDIR variable was missing in our installation-script... after including it the add in works (was just a quick test, but this has to be the cause of the problem). 🙄🥵
8 Views