New Teams for VDI with Office 365

[Darryl Sakach]

I am having an issue getting the New Teams for VDI working. It works fine without the Office 365 App Layer, but once I add the O365 App Layer to the image it fails to open.

 

I have:

1. Set the WEbSocketService ProcessWhitelist to include msedgewebview2.exe

2. Updated to the FSLogix 2.9.8716.30241 (2210 Hotfix 3) (no exclusions in Redirections.xml related to Teams or Packages locations).

3. Installed New Teams MSIX x64 in the Server 2019 OS Layer via dism command

4. Set Teams registry to not autoupdate.

 

The errors I get once the O365 layer is added are:

 

Faulting application name: ms-teams.exe, version: 23320.3021.2567.4799, time stamp: 0x65719f33
Faulting module name: ucrtbase.dll, version: 10.0.17763.1490, time stamp: 0x48ac8393
Exception code: 0xc0000409
Fault offset: 0x000000000006e77e
Faulting process id: 0x2c44
Faulting application start time: 0x01da562b8f46c9ce
Faulting application path: C:\Program Files\WindowsApps\MSTeams_23320.3021.2567.4799_x64__8wekyb3d8bbwe\ms-teams.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report Id: d9040988-817d-485b-a15e-4a3cfb0d365a
Faulting package full name: MSTeams_23320.3021.2567.4799_x64__8wekyb3d8bbwe
Faulting package-relative application ID: MSTeams

And:

Failure to instantiate storage folder C:\Users\xxxxx\AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache for package MSTeams_8wekyb3d8bbwe with Error Code: -2147024809

 

[Martin Kramps1709161707]

hello seems to be a known issue. i think not a citrix issue. 

 

"

Microsoft is pleased to announce the availability of FSLogix 2210 hotfix 3 Preview (2.9.8716.30241).

 

This is a PREVIEW version, and we recommend first running in your non-production environments to fully test and understand the new updates and fix.

 

We've updated several new articles in our documentation and updated the release notes page.

 

Release Notes:

Update: When new Teams is detected, the AppX package is registered for the user during sign-in.

Update: During user sign-out, Teams user data/cache located in %LocalAppData%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache will be saved in the container.

Fix: Resolved an issue where a virtual machine would reboot unexpectedly as a result of bug check (various stop codes) when a user's redirects were removed before sign-out

[UPDATE] January 9th, 2024:

 

First of all, I want to say "THANK YOU" to all of those who've been testing and validating this hotfix preview release. Based on the testing and feedback I'd like to report on the current status:

 

All:

Potential anti-virus conflicts. Teams 2.1 paths have changed, and some anti-virus products have prevented the Teams executables from launching correctly.  Confirm with your vendor if any changes are needed to be compatible with Teams 2.1.

Windows 10 and 11 (Enterprise and Multi-session):

Operating systems have the correct API(s) for proper discovery and registration for UWP / AppX packages.

Profile only, Profile and ODFC, and ODFC only configurations working as intended.

Preservation of Teams user data in %LocalAppData%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache working as intended.

Windows Server 2022:

[Unable to reproduce] Teams 2.1 fails to launch / start with a message, "msteams_autostarter.exe 'The parameter is incorrect'" (Looking for customers to help investigate and reproduce).

Windows Server 2019:

[Confirmed] Missing API for UWP / AppX packages preventing discovery and registration (under investigation).

[Unable to reproduce] Failure to instantiate storage folder C:\Users\%username%\AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache for package MSTeams_8wekyb3d8bbwe with Error Code: -2147024809 (Looking for customers to help investigate and reproduce).

Once we can confirm we've addressed the issue above, we will plan for an updated release for hotfix 3 (updated version).

 

"

 

 

[Daniel Dilling1709156725]

I have the issue aswell and tested a lot. Following the eventviewer entry:

Faulting application name: ms-teams.exe, version: 23335.232.2637.4844, time stamp: 0x65a8bdc4
Faulting module name: ucrtbase.dll, version: 10.0.17763.1490, time stamp: 0x48ac8393
Exception code: 0xc0000409
Fault offset: 0x000000000006e77e
Faulting process id: 0x2858
Faulting application start time: 0x01da5e60beec5600
Faulting application path: C:\Program Files\WindowsApps\MSTeams_23335.232.2637.4844_x64__8wekyb3d8bbwe\ms-teams.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report Id: 88e2a507-7950-4a1f-a665-fa4175ae3e52
Faulting package full name: MSTeams_23335.232.2637.4844_x64__8wekyb3d8bbwe
Faulting package-relative application ID: MSTeams

 

--

 

Server2019

CVAD2311

FSLogix2210 Hotfix3 Preview

Allowed sideloading apps before rolling out new Teams with all information delivered by Microsoft over DISM command. 

Also tried to deploy the certificate delivered in the msteams.msix before rolling out the appx.

Entered the regkey for CITRIX in the websocketservice processwhitelist regvalue.

Entered the antivirus exclusions.

 

--

 

I also tried different version of all components, also preview versions, without any success.

--

 

For any reason, new teams only runs on server2019 terminal server, with onedrive not being installed. so if you deploy office and exclude onedrive, you will have the effect, that the new teams will work. if you install onedrive afterwards, the new teams won't work anymore.

The best situation i could reach with new teams and onedrive being installed together is that after a server restart, onedrive and new teams start in the user session and both is usable until you close new teams. you won't be able to start new teams afterwards until you restart the server again, which is no solution in a terminal server environment.

 

hope there will be some fixes in any cumu updates, msteams.msix, fslogix versions and so on, to fix that. 

 

 

[Darryl Sakach]

I published the New MS Teams OS Layer with O365, but without the AV layer. Everything works. We are working on applying the recommended AV exclusions.