Forum Discussion

timrear's avatar
timrear
Copper Contributor
Feb 01, 2024

Teams (new) not starting in RDP User Session

Hey folks,

i hope you are doing well!

We have just installed Teams New on several Windows Server 2019 RDP Servers using the folowing way (maybe it helps some guys as i was searching for a longer time!):

 

 

reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModelUnlock" /t REG_DWORD /f /v "AllowAllTrustedApps" /d "1"​

 

 

  • activate Windows Developer mode:

 

 

reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModelUnlock" /t REG_DWORD /f /v "AllowDevelopmentWithoutDevLicense" /d "1"​

 

 

  • Install teams (only dism supported on 2019)

 

 

Dism /Online /Add-ProvisionedAppxPackage /PackagePath:"PFADZUR\MSTeams-x64.msix" /SkipLicense​

 

 

This works successfully in several environments.

BUT: As soon as the gpo "delete cached copies of roaming profiles" (sorry i am not sure if this is 100% correct translated) is activated, the user cant even start teams new client - nothing happens.

We reproduced this issue several times. after deactivating this gpo, teams new client starts without problems.

Do you have any idea how to get rid of this problem? We cant deactivate this funktion as we use a lot of servers in Session Farm and need to save hundrends of GB this way.

Thanks a lot for your help!

  • Seems like i have just found the solution by myself - i was searching for days now 😞

    Computer Configuration -->Administrative Templates --> Windows Components --> App Package Deployment --> Allow deployment operations in special profiles: Enabled
  • timrear's avatar
    timrear
    Copper Contributor
    Seems like i have just found the solution by myself - i was searching for days now 😞

    Computer Configuration -->Administrative Templates --> Windows Components --> App Package Deployment --> Allow deployment operations in special profiles: Enabled
    • Corbett_Enders's avatar
      Corbett_Enders
      Copper Contributor
      Thank you for posting this! We are just testing new Teams on RDS Server 2022 and ran into the same problem.

Resources