New Teams and Sysprep

I noticed the same thing.
I'm wondering if Microsoft "designed" New Teams that way because it's so much faster, they assumed we wouldn't put it in an image?🤔
The "easy" fix is to put that scripted action as part of the VM Deployment settings of the Host Pool Properties, but that just means that you need to way another 2-5 minutes per host for it to install everytime you deploy/reimage a host. 😟

That was going to be my solution as well. Do you use the Optimization script during deployment. I haven't tested with that off to verify it's not removing Teams from the image during deployment.

I can't say we have used any of the Optimization Scripts.
We use the Azure Windows 11 images so none of the optimization scripts are designed to work for that edition.

It's possible that it could be causing a problem, but I'm guessing not.

Thanks!

This may be your "issue" Randy, but the New Teams is an MSIX/APPX package (windows store app style) so it unpacks itself to the C:\ProgramFiles\WindowsApps directory then presents itself in the start menu to users.  Users should then be able to go open it from the start menu and sign in.  

I haven't put New Teams in any of my images yet but is on my list to do very soon since we only have till July 1st to switch completely.  

Hey Everyone,

   Chuck here from Nerdio.  We have seen some other reports of the New Teams installer not surviving sysprep and we have been following this thread:
https://techcommunity.microsoft.com/t5/azure-virtual-desktop/new-teams-update-issues/m-p/4095837

Currently it appears that New Teams does not play nice with the /mode:VM for sysprep and we would advise that New Teams is installed upon host creation and NOT on your desktop images.  This can be done quite easily via scripted actions in Nerdio. Here's those steps:
- Assign the New Teams scripted action to your accounts in Nerdio (MSP Level in NMM>Scripted Actions)

- Configure your hostpool properties to run the scripted action during host creation like this screenshot below:

Going forward, you'll now see each host created/re-image in the pool have Teams (New) installed via this scripted action.  Hopefully this helps!!!

Thanks Chuck, that does help!  

Thanks Chuck! I found that info in this other thread I didn't find earlier. https://nmehelp.getnerdio.com/hc/en-us/community/posts/23918750567821-Add-a-script-for-updating-installing-New-Teams

Some recent information that we've received from the FSLogix team regarding New Teams is that hotfix 3 is only optimizations for Windows 11. Windows 10 and server OSs are not optimized in that hotfix. If your host pool is running Windows 10, you might be better off sticking with classic Teams for now until hotfix 4 comes out, which should include optimizations for Windows 10 and Server.

I'll have to watch for that.
Microsoft started forcing auto-update to New Teams on VMs where the user is an admin. This affected 1 client with single-user AVD hosts due to an app requirement, and our golden image VMs. The only place I've found to disable the update is in Teams admin for the whole tenant. We don't want to block new Teams anywhere but AVD, so we're working around the issue by reinstalling classic Teams before starting the sysprep process.

Hi Randy, where can I download the Install Script for MS Teams? Thanks in advance.

DenDee Import it from Nerdio's GitHub

Thank you Randy, I just want to ask where will I install the FSLogix? Is it in the Golden image? or the host pools? TIA

Your fslogix profile will determine which version of fslogix will get installed by Nerdio when a VM is created. If it's set to "latest" then Nerdio will install the latest version that is included with whatever version of NMM you're running.

Important to note is that if you change those settings, then you will need to reimage that session host to get the newer version.

DenDee I leave FSLogix off the golden image and let Nerdio install it during host deployment. 

Is it recommended to install the new version of Teams in the base image or is everyone still deploying it after the host is created?

The Teams app still doesn't survive the sysprep process, so running the install script during a host deployment still works best....BUT we started having issues with the script installing the Teams add-in for Outlook. I've had to manually run the add-in installer on the golden images. The add-in survives sysprep.

Even with KB5039299 installed ?  as per  New Teams Update Issues - Microsoft Community Hub

I wasn't aware of that update. I'll have to test it out.

I tested it with Win 10 22h2 and Win 11 23h2 and it didn't survive the sysprep for me with either one.
However, I didn't explicitly check for KB5039299 so maybe that still has some hope?

KB5039299 is a preview update, so not something we'll be using in production environments.

I've been having this issue (Teams gone after Set As Image is ran) sporadically over the past several months. Just came acorss this thread and tried adding the Teams script to VM Deployment as described. I made those changes yesterday, then ran a scheduled re-image over night. Today, still no Teams app for end users. Any suggestions? How are you successfully getting the new Teams app into end-user AVD's? Thanks.

David Graham  The Nerdio provided Scripted Action named “Install Microsoft Teams (New)” should be sufficient, I have been using it for all my Host Pools for quite a while.  Ensure you set the scripted action to run “when host VM is created” in the “VM Deployemnt” settings.  

Otherwise you might look at the event viewer application logs on the newly created session host for any msi errors related to the team install.  there may be something blocking the install or stopping it when the script tries to run.  

Thank you Phil Long - I appreciate your response. See attached for the VM Deployment script setting I made yesterday. As I mentioned, a re-image of the Host Pool was made last night, but still no Teams in user sessions. This deployment is very simple: 1 Host and 1 Desktop Image, only 8 users. This is preaching to the choir, but it's been extremely frustrating over the past several months to not know if Teams would be there for users after a re-image. We re-image monthly as we run updates, etc. on the Desktop Image. We have been running the “Install Microsoft Teams (NEW)” script when starting the Desktop Image. That seemed to give better results, but it wasn't foolproof. We'll stop doing that now, in light of the new VM Deployment script setting.

Question - now that I've made this change to run the “Install Microsoft Teams (NEW)” script when the VM is created, should I uninstall Microsoft Teams from the Desktop Image? To do this, I would right-click on the app in the Start Menu and choose Uninstall.

I'm going to look more closely at the new session Host VM now to check for install errors, etc. Thanks.

FYI to close the loop on my comments in this thread … after continuing to have issues getting Teams to be present for end users, I reached out to Nerdio support. They confirmed that uninstalling the Teams app from the Image and then using the install script in the VM Deployment settings is the recommended thing to do at this point. When that still was failing for me, they provided me with a new Teams install script that will be pushed out with NMM 6.4. The new script worked successfully.

Hello again all, i wanted to throw this question out there and see if anyone else has been experiencing anything similar with Teams.  

On a session host, teams gets installed “properly” during the deployment process but after a few days the teams app goes missing?  Im not sure if there is a user that is doing “something” that uninstalls it but its completely missing from windows apps directory and i have to reinstall it.  So far i only see this with 1 client that I recently moved to windows11 session hosts and it happens on different session hosts and so far seems pretty random.  

The session hosts are note getting powered off/deallocated at night but do reboot from inside the OS.  I dont have any other scripted actions set to happen except for on VM creation.  I dont think there is an update to the teams app causing the issue cause these session hosts get reimaged fairly often so it should be up to date.  

I will be looking through some logs and doing testing and will update if i find anything concrete. 

Hi, we are doing a new deployment and would like to use the method advised above (no teams on desktop image and deploy via script during host creation). Above it shows a slightly different script then what I have available in the portal.

Above shows 

While I only have this one. Am I missing something?

Looks like my Github repository is connected