Forum Discussion
Latest FSLogix and New Teams - how to get that working reliably
Hi Everyone I've spending a long time earlier this year getting Teams and Office working reliably with FSLogix, I'm now trying to get the new Teams (23306.3308.2524.1744 as of posting this messag...
- FSLogix 2210 hotfix 3 is GA!
This was how I updated my golden image for VMware Horizon View. New Teams works well in VDI pool sessions with this setup.
1. Uninstall Classic Teams.
- Delete auto-start entries in Windows' registry:
HKCU\Software\Microsoft\Windows\Current Version\Run
HKLM\Software\Microsoft\Windows\Current Version\Run
- Delete the Classic Teams folder if exists
C:\ProgramData\Microsoft\Teams
2. Updated to the latest version of FSLogix (currently 2.9.8884.27471). Reboot.
3. Install New Teams (following in Microsoft's instructions).
4. Run Powershell script to remove unwanted Windows store apps manually (optional).
5. Delete all Teams shortcuts in Start Menu.
6. Copy the RegNewTeams folder to "C:\Users\Public" folder (login script will call the regnewteams.bat from this location. Alternately, you can add "regnewteams.bat" to the Startup folder of the VM)
7. Run VMware OSOT
- Before running Optimization, enable the option to keep Windows Store Apps in OSTS's settings.
- Afer Optimization, run Finalize.
8. Release IP address and shut down.
9. Take a snapshot of the VM.
=======================================
Contents of RegNewTeams folder include 2 files:
1. regnewteams.bat: open notepad, paste in the commands below and save the file as "regnewteams.bat"
@echo off
echo Registering the New Team assembly...
Powershell -ExecutionPolicy Bypass -File C:\Users\Public\RegNewTeams\regnewteams.ps1
2. regnewteams.ps1: open notepad, paste in the line below and save the file as "regnewteams.ps1"
Add-AppxPackage -MainPackage "MSTeams_8wekyb3d8bbwe" -RegisterByFamilyName
Hi Tan_V555
Thanks for the tips, the script seems to solve the issue when New Teams doesn't launch.
About the script you add, do you launch it on each logon or only once?
BR
ThierryLk My VDI environment is non-persistent (the VM is destroyed each time a user signs off, and a new VM is assigned when a user signs in), so I have the script called at every logon. However, when I tested, even with a persistent environment, the script just errored out and quit on subsequent runs if the New Teams had been registered before; the New Teams app still worked as normal.
- Thanks. I am in a fairly similar environment but in my case the posts are deleted with each update or automatic refresh (and users normally keep the same post name).
Not all users seem to be concerned by the bug (some have the shortcut in the Start menu but don’t launch, others don’t have the shortcut at all).
If a user never had a FSLogix profile before I never run into the problem, it’s only on existing profiles that had the old version of Teams.
I will see if I add the script in the startup or if I just leave the script to users "if necessary", I prefer to avoid too many scripts when opening sessions.
