Just wondering if anyone else has seen this with t...
# microsoft-fslogixp
Phil Savage
03/15/2024, 3:30 AMJust wondering if anyone else has seen this with the New Teams Client being deployed to VDI's??
1. If a user manually installs the new teams client FSLogix HF3 will not detect the new client. (Error Message: MSTeams installation error: Windows cannot perform the RegisterByPackageFamilyName operation because it could not find MSTeams_8wekyb3d8bbwe in the repository)
2. If you do a force/admin install using the teamsbootstrapper.exe -p -o method FSLogix HF3 will detect MSTeams is installed!
3. When a user does the install the following regkey is seen: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore\Applications\*MicrosoftTeams_24033.1005.2701.7380_x64__8wekyb3d8bbwe*
4. using the Bootstrapper means the following Registry key is written: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore\Applications\*MSTeams_24033.811.2738.2546_x64__8wekyb3d8bbwe*
In other words the manual installer installs the new teams client to a different directory than the bootstrapper method, and FSLogix is expecting the New Teams Client appx registration to be MSTeams... and not MicrosoftTeams
I am going to raise a case withy MS About this, because when they flick the switch for VDI's in june 1. (above) is the outcome, There will be an extremely poor user experience, as we have felt (luckily with only 65 Users so far)
s
Selimir
03/15/2024, 6:20 AM@Jason Parker
r
Ray Davis
03/18/2024, 12:09 AMI wonder as a test if you update the registry in your findings if that kicks over and Fslogix can pick it up?
p
Phil Savage
03/18/2024, 3:04 AMUpdate:
The "MicrosoftTeams_8wekyb3d8bbwe" package family is I believe related to the Windows 11 inbox version. I need to do more testing around the behaviour of using the teamsbootstrapper install method vs the manual install by the user. But in anycase "MicrosoftTeams_8wekyb3d8bbwe" is not supported by FSLogix HF3 by my troubleshooting.
Irrespective of all these issues I am trying to weed my way through, I have a grave concern the new Teams Client is no longer evergreen on Stateless/Non-Persistent VDI's as the new Teams Client is an MSIX package that installs into C:\Program Files\WindowsApps\... which is obviously not roamable in the user profile via FSLogix like the "classic" version was. (Massive step backwards it seems!)
Phil Savage
03/18/2024, 3:58 AMUpdate 2:
If a User Installs the MSIX package from the download location it is installed under the user context. As such the new teams Client will be removed upon restart of the virtual machine. This is a known issue for us and to get around it, we force Appx/MSIX packages to be deployed to the system from the company portal, and not the user context.
This is just another variation of the whole AppX/MSIX compatibility issue with FSLogix.
If Microsoft flick the switch in June for all Virtual Machines, I suspect there will be alot of issues, or at the very least the New teams client being re-installed every day for Virtual machine users with FSLogix
r
Ray Davis
03/21/2024, 11:29 AMSince you allow users to install new Teams on the VDI with no -p, I have not tested this. But the AppX Roam feature in FSLogix may help?
2 Views