New Teams and Sysprep

I'm installing New Teams to my golden image using the Nerdio install script, then capturing. The reimaged test AVD host doesn't show Teams installed. 

If I run the script directly on the test AVD host, new Teams shows installed and the start menu shortcut appears.

Anyone else seeing this behavior? 

0

Comments (10 comments)

Avatar
Dave Stephenson

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. 😟

1
Avatar
Randy Lehman

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.

1
Avatar
Dave Stephenson

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.

0
Avatar
Randy Lehman

Thanks!

0
Avatar
Phil Long

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.  

0
Avatar
Nerdio Virtuoso

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!!!

 

1
Avatar
Phil Long

Thanks Chuck, that does help!  

1
Avatar
Randy Lehman

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

1
Avatar
Marcos Artiaga

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.

0
Avatar
Randy Lehman

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.

0

Please sign in to leave a comment.