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 message) working reliably between Windows 10 desktops using FSLogix (for hotdesking requirements).
I used the following article to deploy the new Teams to a set of test desktops running Windows 10 22H2 x64 and FSLogix 2.9.8612.60056
https://learn.microsoft.com/en-us/microsoftteams/new-teams-bulk-install-client
I logged in as a test user, started the New Teams from the Start Menu (got a GPO stopping it auto-starting) and it sets itself up correctly.
It them reports that there is a newer version and I upgrade it to 23306.3308.2524.1744
After that, the upgrade message no longer appears
I then log off, and log onto another test desktop.
Again starting New Teams from the start menu and it appears to go through the same initialisation / configuration routing, but reports the new version (23306.3308.2524.1744), and also says that there is an upgrade available.
If I perform the upgrade, it downgrades the version to the version that was originally installed on that desktop, not the new version that was upgraded to the the other desktop.
Is this a bug in Teams or an issue with FSLogix/misconfiguration in redirections.xml?
Has anyone successfully deployed the New Teams with FSLogix?
One excellent point with the new Teams is that the horrendous bloating of the profiles are a thing of the past now.
Regards
Ken Z
- FSLogix 2210 hotfix 3 is GA!
- Stefan_StekhuizenCopper Contributor
Hi,
We're experiencing the same issue.
All the user settings and configurations are now stored in: C:\Users\alland\AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams
But FSLogix excludes most folders in Packages\MSTeams_8wekyb3d8bbwe\. - Mr_KeithyCopper Contributor
Hi Ken_Z I have been waiting for the new VDI version of the teams client which has now launched, but at the bottom of the page MS are saying there is problem with FSLogix and it is not yet supported. I run a Citrix environment using FSLogix, its annoying as we could do with the new client as we are also working on a Cross tenant sync project which the new Teams client works nicely with. There exact wording on the site is;
"Note!
Currently, the new Teams client in VDI is not compatible with FSLogix Profile containers and ODFC containers. Microsoft is working on a solution and plan to remove these limitations soon."
You can see it here if you scroll down near the bottom.
New Microsoft Teams for Virtualized Desktop Infrastructure (VDI) - Microsoft Teams | Microsoft Learn
I suspect its the same with the normal client too, but not 100% sure.
Keith
- Ken_ZBrass ContributorHi Keith
there is a new version of FSLogix (hotfix 3 - 2.9.8716) but it's in preview. I'm testing that at the moment and it seems to be working with the new Teams.
https://learn.microsoft.com/en-us/fslogix/overview-release-notes#fslogix-2210-hotfix-3-preview-29871630241
Regards
Ken Z
- Chin-SCopper ContributorI have a working work-around:
When users log in, the following mandatory script is run. This installs the new-Teams with the user's credentials, it looks like something is written in the userprofile as well:
=======
c:
cd \Program Files\Microsoft Teams Installer\
teamsbootstrapper.exe -p -o "C:\Program Files\Microsoft Teams Installer\MSTeams-x64.msix"
=======
If the return-code is 'true' (that means the installation is succesfull) users can then start new-Teams via START -> Microsoft Teams (Work or School). - Luis2080Copper Contributor
Ken_Z not sure if everyone has seen this update but seems like Microsoft and Citrix are working on updates to make things better. We shall see how things look in June.
https://support.citrix.com/article/CTX585013/microsoft-teams-21-supported-for-vdidaas
- Tan_V555Copper Contributor
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\RunHKLM\Software\Microsoft\Windows\Current Version\Run- Delete the Classic Teams folder if existsC:\ProgramData\Microsoft\Teams2. 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 offecho Registering the New Team assembly...Powershell -ExecutionPolicy Bypass -File C:\Users\Public\RegNewTeams\regnewteams.ps12. regnewteams.ps1: open notepad, paste in the line below and save the file as "regnewteams.ps1"Add-AppxPackage -MainPackage "MSTeams_8wekyb3d8bbwe" -RegisterByFamilyName- Tan_V555Copper Contributor
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.
- Ken_ZBrass ContributorLuis (and anyone else)
to stop new Teams from auto-starting, see this article
https://www.reddit.com/r/MicrosoftTeams/comments/174mpaq/disable_auto_start_for_new_teams/
In that regkey is a reg-value called "State". Set it to a value of 1
tested and working with the latest new teams on Windows 10
regards
Ken Z - Ken_ZBrass ContributorHi
Yes i can. Give me 24 hours to get this for you.- TCon06Copper Contributor
I'd like to see this also. But my issue is the new Teams is auto starting in VDI with latest FSLogix build after the first startup. Can you also share your exclusions for teams in fslogix?
- Jason_ParkerMicrosoftFSLogix 2210 hotfix 3 is GA!
- matthew777Copper Contributor
Jason_Parker I installed it, and new Teams is there and logs in fine from session host to session host. It doesn't seem to save all the settings though. For example, my color scheme keeps reverting after I change it. Anything else I need to do other than just install that version?
- Chin-SCopper Contributor
Jason_Parker Hi, I have the latest FSLogix installed in the master-image but when I login to a Citrix-session, the new-Teams won't start. Only when I remove my profile from FSLogix and login with a clean profile (no profile) it rebuilds the profile from scratch and then the new Teams is able to start up.
I really have no clues anymore on how/what to configure. I even have used the GPO FSLogix [ see attached screenshot ] but that doesn't seem to work either:
- KristofferAndersenCopper ContributorSame thing happend to me. Deleted my profile and after that it worked fine. Need to find a solution for existing profiles.
- jimamjCopper Contributor
I have New Teams installed on Win10 VDI's using FSLogix. It launches and functions, but I have several users who want Teams to auto-start, but it won't unless put in the start menu folder. This is acceptable as a work around, but those same users can't launch meetings from Outlook. They are taken to a web page asking to join from web or app. Choosing web launches the web app, and choosing app does nothing. They can launch meetings fine from the calendar in New Teams. I have tried clearing profiles etc. This has happened on a brand new profile as well. Anyone experience this?
- Ken_ZBrass Contributor
Hi jimamj
My understanding is that as New Teams is a modern app (AppX package), this will not auto-start as such, and needs to be "poked" to start up the very first time. Subsequent logins, it should auto-start, unless it is being prevented from doing this.
(Can't remember exactly where i read this, but it was recently and from an official Microsoft article)
Regards
Ken Z