Teams on RDS - Users Can't Login

Jeff Snyder 31 Reputation points
2020-10-15T15:13:48.697+00:00

On our RDS server, we have an issue where upon login to the RDS machine a user is not able to login to Teams and gets Error Code: " 80070003 There's a more permanent way to sign in to Microsoft Teams. If you're having trouble completing the process, talk to your IT Admin. "

We have followed the walkthrough at the following link and it has not solved the issue. https://learn.microsoft.com/en-us/deployoffice/deploy-microsoft-365-apps-remote-desktop-services

We are trying to prevent the need to move to Zoom at all costs but this is causing productivity issues and we are at a stand still with Microsoft support.

Any advice that could be offered would be greatly appreciated!

32637-thumbnail-image002.png

Microsoft Teams
Microsoft Teams
A Microsoft customizable chat-based workspace.
8,621 questions
Remote Desktop
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
4,133 questions
{count} votes

13 answers

Sort by: Most helpful
  1. ColinS 16 Reputation points
    2020-11-26T10:53:42.627+00:00

    I have a solution that is working for me so far with over two weeks in production. Taken from https://christiaanbrinkhoff.com/2020/05/29/learn-how-to-install-and-configure-microsoft-teams-with-av-redirection-media-optimizations-on-windows-virtual-desktop/

    The key is to install Microsoft Teams per-machine on RDS rather than per user. The key steps are:

    First we must create the following registry key in the image

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Teams\IsWVDEnvironment]
    Type: REG_DWORD Value: 1
    Download Teams and run the command below to install Teams per-machine

    Note: To use the WebRTC AV redirection client, you must use Teams version 1.3.00.4461 or later – the 64-bit version is highly recommended.

    msiexec /i c:\install\Teams_windows_x64.msi /l*v c:\install\Teams.log ALLUSERS=1 ALLUSER=1

    If everything ran perfectly you will see Teams showing up in the Program Files directory.

    2 people found this answer helpful.

  2. Scott Giles 11 Reputation points
    2020-12-01T00:06:13.037+00:00

    I have a work-around I developed that resolves the issue with everyone we tested with on our side.

    Basically you just have to close Teams and rename or delete this file:
    %appdata%\Microsoft\Teams\desktop-config.json

    After that, they started Teams back up and it was working normally for all our users.

    2 people found this answer helpful.

  3. Sharon Zhao-MSFT 25,121 Reputation points Microsoft Vendor
    2020-10-16T07:14:46.767+00:00

    @Jeff Snyder ,

    Does anyone else have the same issue?

    To exclude the account itself, you could try to sign in Teams web client(https://teams.microsoft.com) in InPrivate mode and check the result.

    Then, perform a clean boot to exclude whether a background program is interfering with Teams.

    Moreover, make sure Teams client is the latest version. If there is any update requirement on the machine, please install the package in time.


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

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


  4. Jan-Dirk Lehde 1 Reputation point
    2020-11-26T09:22:03.293+00:00

    We have the same problem for all users on RDS 2019 Server Farm with 2 Session hosts. It reoccurs almost daily.
    The User has to delete %appdata%\Microsoft\Teams content to get Teams working again

    Errors in the Teams log file:

    -- error -- (Account)ProviderError.s:5;e:80070003; 
     -- error -- Falling back to ADAL. Failing WAM scenario.
    -- error -- getInstallOrUpdateTime failed 
    -- error -- Error occurred while saving env_config.json 
    -- error -- There are 2 open windows after main window closed, force closing all windows 
    
    0 comments No comments

  5. Dalip Ticku 1 Reputation point
    2021-01-14T22:49:21.09+00:00

    we have citrix env and also teams is installed using per machine install. We are still having this issue.
    at present i have created a batch file which a user runs if cannot login to teams.

    Create this batch file and run

    attrib -h -r -s %appdata%\Microsoft\Teams /s /d
    rd /s %appdata%\Microsoft\Teams /q
    attrib -h -r -s C:\Users\%username%\AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_* /s /d

    FOR /D %%i IN (C:\Users\%username%\AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_*) DO RD /q /S "%%i"