Forum Discussion
New Teams / Meeting addin missing on Windows Server 2019 RDSH / Autostart Issue
Dear Community, dear Microsoft Pros, We are currently struggling with getting the New Teams running smoothly on our RDSHs. It was already a painful experience to remove the old Teams and inst...
Hi Dirk,
thanks for the note! We're currently examining which user impact the setting "DisableUserInstalls" would have, as we don't allow it currently.
We took a deep dive into system flows and found out, the startup problems with the new Teams Client were triggered by the User Profile Disks. The required Registry entries were wiped completely during sign out and the new Teams seems to be installed again (along with the registry entries) from the windowsapps folder during sign-in.
We cross-tested this on a remoteapp server that is running in our infrastructure without UPDs but the same policies, and the new Teams is running there as it should (but without the Meeting Addin, due to DisableUserInstalls).
We came to the point that we should upgrade the servers to Windows Server 2022 first, possibly followed by setting up FSLogix, because we think that Microsoft will do nothing about this.
thanks for the note! We're currently examining which user impact the setting "DisableUserInstalls" would have, as we don't allow it currently.
We took a deep dive into system flows and found out, the startup problems with the new Teams Client were triggered by the User Profile Disks. The required Registry entries were wiped completely during sign out and the new Teams seems to be installed again (along with the registry entries) from the windowsapps folder during sign-in.
We cross-tested this on a remoteapp server that is running in our infrastructure without UPDs but the same policies, and the new Teams is running there as it should (but without the Meeting Addin, due to DisableUserInstalls).
We came to the point that we should upgrade the servers to Windows Server 2022 first, possibly followed by setting up FSLogix, because we think that Microsoft will do nothing about this.
Hi calaneo,
so, you don't use FSLogix right now?
Please note:
Folder Redirection or Roaming User Profiles aren't supported with the new Teams client in VDI environments since they can't roam folders in AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams.
Customers can continue to use Folder Redirection or Roaming User Profiles with a complementary product, such as FSLogix, Citrix Profile Manager, and VMware DEM, that can roam the Appdata\Local folders above.
Maybe that's your problem?
so, you don't use FSLogix right now?
Please note:
Folder Redirection or Roaming User Profiles aren't supported with the new Teams client in VDI environments since they can't roam folders in AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams.
Customers can continue to use Folder Redirection or Roaming User Profiles with a complementary product, such as FSLogix, Citrix Profile Manager, and VMware DEM, that can roam the Appdata\Local folders above.
Maybe that's your problem?
- Yes, this formulation is pretty much spot on. Currently we are using standard UPDs. That's why we want to switch to FSLogix soon. Thank you for the hint!