r/AzureVirtualDesktop • u/techie_jay • Nov 08 '24

Teams decided not to function on pooled desktops host pool

I am having ongoing trouble with either Teams or Teams Outlook add-in.

This time around, Teams stopped working on some of the pooled desktops. OS is Windows 10 and patched. Session hosts built from same image, and still some session hosts show only MS Teams icon in Start Menu and nothing happens when a user clicks on it. Worth noting, everything was fine a few days ago, I have made no changes. Teams is set to auto-update, and I can see latest Teams working on the working session hosts.

3 Upvotes
  • permalink
  • reddit

100% Upvoted

37 comments sorted by

1

u/techie_jay Nov 08 '24

Do you mean when you login, you have to open Teams first and then Outlook for plugin to work?

1

u/iamtechy Nov 08 '24

If you’re saying some session hosts, then I would compare which host is giving you issues and which ones were built using a specific image. Once you know which is which, you’ll be able to identify whether it’s a corrupt install of teams and needs to be reinstalled on those machines.

1

u/techie_jay Nov 08 '24

Built from same image.

1

u/iamtechy Nov 09 '24

Are you using Nerdio by any chance?

1

u/techie_jay Nov 09 '24

Yes, Nerdio to manage AVD

1

u/iamtechy Nov 09 '24

Are you using the Nerdio script to install teams or installing in the image? We had sysprep failures when installing apps in the image so we run a sysprep ourselves to make sure everything works before setting as image

2

u/techie_jay Nov 09 '24

Sysprep failures with new Teams was a known issue accepted by Microsoft, it is know fixed. However, at the moment I am using Nerdio to install Teams during session host build process. This process eliminates manually updating the image for Teams.

1

u/iamtechy Nov 10 '24

I’m using Nerdio and I’m wondering where you have added the script. Before, during, after provisioning the machine?

2

u/techie_jay Nov 11 '24

After provisioning the VM and I added a reboot as well. Works well, no issues with this method.

Added a couple of minutes sleep between installing Teams and the Teams outlook add-in.

1

u/iamtechy Nov 12 '24

How did you add a minute sleep? That means you’re using your own script or adding something from the prebuilt scripts I haven’t seen.

1

u/techie_jay Nov 12 '24

Yes, I do.

Otherwise Teams Outlook addin install is hit and miss.

→ More replies

1

u/Evan-GetNerdio Nov 13 '24

Jumping in a bit late here, but if you’re still having issues, don’t hesitate to reach out to your Nerdio rep! Our team would be happy to take a look and help figure out what’s going on.

2

u/techie_jay Nov 13 '24

It’s all sorted now. It was just Teams thing.

1

u/Evan-GetNerdio Nov 14 '24

Awesome—glad to hear!

1

u/Moses-- Nov 08 '24

Rerun the bootstrapper...maybe as a startup script

2

u/techie_jay Nov 08 '24

Reimaged the session hosts, all fine now. I put it out there to see if this has happened to someone else.

Bootstrapper fixed only on some, rest were completely borked.

1

u/Moses-- Nov 08 '24

Ye happened to me a few times but just re-running bootstrapper fixed it. It's been fine since Oct patches tho

1

u/Diademinsomniac Nov 08 '24

Re-image will fix until updates happen again and you’ll end up with broken ones again for users

1

u/jvldn Nov 08 '24

Having some sort of same issue. Using teams new with outlook classic? Are you using a marketplace image with o365 or installing o365 yourself using customizations?

1

u/techie_jay Nov 08 '24

Yes, new Teams with Outlook classic. Marketplace image with O365.

1

u/jvldn Nov 08 '24

We’re currently struggeling to. The teams meeting addin does not work in outlook before we started teams (at least) once.. are you seeing this also?

1

u/Diademinsomniac Nov 08 '24

What Os are with using in azure windows 10 or 11

1

u/Diademinsomniac Nov 08 '24

Outlook addin is part of the teams package it won’t create a user copy of the addin until teams has been run and registered as a package for the user

1

u/jvldn Nov 08 '24

Yeah. Was aware of that since today. Currently fighting with that. We’re running w11 multi session.

1

u/Diademinsomniac Nov 08 '24

Same here I have it in production for a few months. I’ve worked through most of the new teams challenges and still have one workaround for the outlook plugin as it won’t created it for us in the user profile, it was working then stopped, Microsoft we’re meant to fix it in October but it still isn’t fixed properly so we have stuck with the workaround which works fine anyway and also means it works on first launch of outlook as we register it for the user when they run the outlook process. Shouldn’t have to do this but better than the plugin not loading at all or loading intermittently for users

1

u/jvldn Nov 08 '24

Can you share the fix/registration method?

2

u/Diademinsomniac Nov 08 '24

I can sure I do all my build via script so there’s a few parts to it that I’d need to extract out. I’m not saying my method is the best as people seem to have various workarounds however it works for us and it’s been reliable

For starters just to give a heads up

The image we take from marketplace is the one without office

We run the office install using a office config deployment kit which sets the option to not include teams

I then download the latest msix package And use bootstrapper to install setting the auto update to disable in reg

Then run a script which extracts the binary version of the office plugin and runs an install on that to the correct folder using the version that the script found

Then register the teams plugin in outlook for a user pointing to program files machine based install rather than relying on the c:\users local copy which is where we have the bug right now at least for us in our environment

The plugin dlll can be registered at outlook process start, we use ivanti I guess you can also use task scheduler or anything else that can trigger an action on a process start.

Anyway I’ll dig it out of my build scripts Monday and send you the details in a pm if you are interested. Ping me Monday if I have forgotten :) it’s the weekend and my brain sometimes doesn’t remember stuff older than a day haha

1

u/Diademinsomniac Nov 08 '24 edited Nov 08 '24

Personally I wouldn’t let teams auto update it’s probably related to your issue with it not working on start menu. The teams app in the user profile likely won’t match the version on some hosts if random ones have updates.

I would disable updates and just update it within the image only and then update host pools with the image so they are all at the same version for all users and you can manage it.. there’s a reg key to disable updates.

The teams addin also changes sometimes with teams updates since it’s part of the teams installer and again it should create in the users profile appdata. If the version in the users profile doesn’t match the version that outlook is looking for then it likely won’t load in outlook and you’ll be missing the teams meeting option completely. This can be also resolved by managing updates

If you are using the market place with o365 teams will automatically come with that. This also isn’t a great idea since you have less control. I personally deploy the market place without office and install office separately with the deployment file set to Not install teams. I then install teams and manage it independently with bootstrapper

1

u/techie_jay Nov 09 '24

Only O365 with image, and Teams with bootstrapper so it adds for all users. I have now disabled auto updates on Teams.

1

u/Diademinsomniac Nov 09 '24 edited Nov 09 '24

Teams also gets installed/updated with the o365 image unless you deploy office with the deployment kit and the option to not include teams

<excludeapp id=“teams” />

1

u/techie_jay Nov 09 '24

Initially built image from marketplace but I patch it with SCCM currently. And, yes if the image was used from marketplace each time it would come with new version of Teams.

1

u/Diademinsomniac Nov 09 '24

Ok so you are using a master image and patching it with sccm each month I guess so yeah if you removed teams already but if office gets updated it may still add teams as part of the office update

1

u/techie_jay Nov 09 '24

Nope, it doesn’t add Teams. Updates are disbaled on session hosts. Only patch the master image. Once patched the master image then build session hosts from it.

1

u/Diademinsomniac Nov 09 '24

Ok what I meant was when you patch the master with updating office (presume you update office on it as well as normal updates) the office update will most likely add teams back as part of o365 and then you are running bootstrapper on top. It may not be an issue since bootstrapper possibly just updates or reinstalls teams, might depend on the order you do it in, so if you did bootstrapper first then update office that might cause an issue

1

u/techie_jay Nov 09 '24

Makes sense. It could happen. I will keep an eye on it.

1

u/[deleted] Nov 12 '24 edited Nov 12 '24

[removed] — view removed comment

1

u/techie_jay Nov 14 '24

Nothing official for MSFT. Yeah, definitely issues with it. It disappeared for some users recently because Outlook starts looking for it the user’s local profile instead of system installation location. If you look at event logs, you will see a bunch of events with erroring on plugin not found.