Share via

Login loop MS Teams on RDS

RWI 96 Reputation points
2020-11-16T15:11:48.663+00:00

Symptoms:
A couple of users (3 out of 50) on our RDS farm experience the same issue. When the user starts Microsoft Teams (Desktop application) he or she is presented with a loginscreen. After entering the credentials some time passes and the loginscreen is presented again withoud an error. These users can therefore not use MS Teams.

Environment:
The users make use of an Remote Desktop environment with two Session Hosts and a single Connection Broker. Profiles are provides by FSLogix on a Scale-Out File Cluster.

Test results:

  • Users are able to login to the web version of Teams without any problems.
  • When the %appdata\Microsoft\Teams folder is manually emptied, the user is able to login without any problem for one time only. When the user logs off or closes the application and starts the application again, the same issue returns.
  • The same issue occurs when a user is given a new profile. First time login succeeds, but subsequent logins fail.
  • The issues occurs on both Session Hosts. However it does not occur when the user logs in to the MS Teams desktop application on a laptop.

What I`ve tried so far:

  • Added these url`s to the trusted site zone via GPO:
    [.]microsoft.com
    [    .]microsoftonline.com
    [.]teams.skype.com
    [    .]teams.microsoft.com
    [.]sfbassets.com
    [    .]skypeforbusiness.com
  • Cleared the browser cache.
  • Cleared saved credentials from Credential Manager.
  • Tried entering a wrong user name: Login screen returns with the original username.
  • Created test server by cloning a Session Hosts and adding it to a new Test Session Collection. Same symptoms.
  • Updated FSLogix on the test server.
  • Updated Teams installer on test server.

Any thoughts are much appreciated!

Microsoft Teams
Microsoft Teams
A Microsoft customizable chat-based workspace.
10,139 questions
Remote Desktop
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
4,563 questions
0 comments
Accepted answer
  1. RWI 96 Reputation points
    2020-11-25T13:44:35.17+00:00

    Apparently this issue was caused by the Teams client not correctly updating itself.
    The Machine-Wide installer version was used to install on the RDS environment quite some time ago.

    More info:
    https://learn.microsoft.com/en-us/microsoftteams/msi-deployment#clean-up-and-redeployment-procedure

    0 comments

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Eleven Yu (Shanghai Wicresoft Co,.Ltd.) 10,756 Reputation points Microsoft Vendor
    2020-11-17T04:13:40.563+00:00

    Hi,

    We think this issue should be more related to Teams as there seems no problem with RDS. But we suggest you could first proceed below actions for troubleshooting.

    1. Run command "gpresult /h gpresult.html" on both problematic user'PC and working user's, the file will be saved under C drive.
    2. Download process monitor and install it on both clients (probelmatic and working) and session host servers the clients connect to.
      https://learn.microsoft.com/en-us/sysinternals/downloads/procmon
      Start the process monitor from both sides (clients and servers)
      Open Teams (desktop application) and reproduce the issue. Wait for some time, stop and save the procmon trace.
      Also collect traces from the working users for comparison.

    Thanks,
    Eleven

    ----------

    If the Answer is helpful, please click "Accept Answer" and upvote it. Thanks.

    0 comments
  2. RWI 96 Reputation points
    2020-11-17T15:29:51.79+00:00

    Hi Eleven,

    Thank you for your quick reply.

    I`ve generated the requested logfiles. How do we go about interpreting them?

    Regards,

    Richard

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.