Migration to "New" Teams from "Classic" Teams

Classic Teams in a VDI environment is due to go end of support on June 30th this year. What is the recommended approach to move Windows 11 shared pools to "New" Teams? Currently i deploy the following Scripted Actions on the desktop re-image scheduled task, is this the recommended approach or should we be doing anything different?

  • Install Microsoft 365 Office Apps (Individual with restart)
  • Install Microsoft Teams (Individual with restart)

Comments (4 comments)

Kevin Halstead

At time of writing the new Teams is supported in AVD but FSLogix is still in preview. FSLogix needs to be updated before even attempting the new Teams, I'd wait until FSLogix goes GA before attempting to migrate. I guess some scripts will be along shortly to assist.

Dave Stephenson

I know we've had issues with "New Teams" on our Windows 11 host pools.
What Kevin Halstead is saying makes sense. 
Just for a point a reference, here is a blog post that talks about the issue. 
Latest FSLogix and New Teams - how to get that working reliably - Microsoft Community Hub

Peter Yasuda

We've been running New Teams in our Windows 11 host pool with FSLogix 2210 hotfix 2. There are some quirks and some features missing, but the performance improvement makes it worthwhile. My Teams version in AVD is 24004.1309.2689.2246, 2/27/2024. We're running the Install Microsoft Teams (New) Scripted action, but New Teams seems to update itself anyway. The Teams version history, https://learn.microsoft.com/en-us/officeupdates/teams-app-versioning, makes it look like the only VDI version is the old, Electron, version. Are you using these FSLogix Registry Options Redirections? They seem to help. 

<?xml version="1.0" encoding="UTF-8"?><FrxProfileFolderRedirection>
<Exclude Copy="0">AppData\Local\SquirrelTemp</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Teams\Current\Locales</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Teams\Packages\SquirrelTemp</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Teams\current\resources\locales</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Teams\Current\Locales</Exclude>
<Exclude Copy="0">AppData\Roaming\Microsoft\Teams\Service Worker\CacheStorage</Exclude>
<Exclude Copy="0">AppData\Roaming\Microsoft\Teams\Application Cache</Exclude>
<Exclude Copy="0">AppData\Roaming\Microsoft\Teams\Cache</Exclude>
<Exclude Copy="0">AppData\Roaming\Microsoft Teams\Logs</Exclude>
<Exclude Copy="0">AppData\Roaming\Microsoft\Teams\media-stack</Exclude>

Kit Fletcher

Is the existing "New Teams Individual" scripted action designed for use on an image, or linked to VM's to run at start-up?


Please sign in to leave a comment.