Good morning. Been having an issue with teams addi...
# citrix-vada
Artiom Kocharov
03/20/2025, 7:43 AMGood morning. Been having an issue with teams addin past days which is almost solved. It has been very tricky since I always clicked on "No, this app only" on this prompt after installing teams and teams addin which results in outlook crashing when trying to open the teams addin. Anyone know why the teams addin with the new teams crashes in outlook when this is configured as "No, this app only" ? If I click on yes, all apps it works perfectly. I would like to configure a GPO so that this prompt doesn't appear for the users. If they happen to click on "no, this app only" their teams addin will not work. I found a registry key named autoWorkplaceJoin 1 under Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin but the prompt is still appearing. I can add that the prompt appears during the first time when configuring outlook.
👀 2
j
Jeff Riechers
03/20/2025, 10:38 AMCouple of things that need to be done.
Jeff Riechers
03/20/2025, 10:39 AM1. Your non-persistent maintenance machine needs to have a dsregcmd /leave command executed during sealing to ensure proper image connection
2. Your non-persistent maintenance machine needs the \Microsoft\Windows\Workplace Join\Automatic-Device-Join scheduled task modified. Add an At Startup Trigger. This will register the machine at it’s startup to Azure AD, and the user account will register with the existing At log on trigger.
3. Teams and the meeting add-in need to be installed with the all users method. I have that documented in my script here.
👍 1
Jeff Riechers
03/20/2025, 10:39 AMJeff Riechers
03/20/2025, 10:40 AMIf you are using published apps, make sure shellbridge is enabled.
a
Artiom Kocharov
03/20/2025, 11:58 AMHello Jeff, thanks for the reply. Problem is that this customer doesn't want to register the VDAs in Azure AD. Is there some other way?
j
Jeff Riechers
03/20/2025, 11:58 AMWhy would they not want to? That is what makes all the MS products work smoothly and silently.
a
Artiom Kocharov
03/20/2025, 12:00 PMI agree with you but it seems that they don't understand this. I will try your steps in my test environment then suggest the same to the customer
j
Jeff Riechers
03/20/2025, 12:01 PMI have taken to telling customers, no. If you want this to work, you need to do this. The only way it doesn't work is if they are using a different federation on top of Azure AD, like Okta. Okta has a client you install in the VDA to do all that SSO for you.
✅ 1
a
Artiom Kocharov
03/20/2025, 12:02 PMThey are not using Okta. Can I run that script which installs the teams from line "echo Installing New Teams…" without modifying it?
Artiom Kocharov
03/20/2025, 12:02 PMto install teams and the addin properly
j
Jeff Riechers
03/20/2025, 12:03 PMIt's best to remove the plugin and teams first, then run the powershell as it starts it from scratch and guarantees everything is in place.
a
Artiom Kocharov
03/20/2025, 12:05 PMthis is a fresh MCS image so no teams installed
Artiom Kocharov
03/20/2025, 12:05 PMI am finished with step 1 and 2
Artiom Kocharov
03/20/2025, 12:10 PMmy bad, I am able to run the script
Artiom Kocharov
03/20/2025, 12:10 PMwill do it in a moment and see if this makes a diff. I was actually already running this script from before. Only difference now is that I have that scheduled task configured, so step 1 and step 2 is something new to me
n
Nick Pylarinos
03/21/2025, 2:51 AM@Jeff Riechers just wondering - do you have more info on the OKTA Plugin for the VDA your referring to?
2 Views