Teams on RDS - Users Can't Login

Question

question

JeffSnyder-0562 asked Oct 15, '20 DalipTicku-1739 answered May 10, '22

Teams on RDS - Users Can't Login

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://docs.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!

office-teams-windows-itpro remote-desktop-services

thumbnail-image002.png (53.2 KiB)

· 1

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

ColinS-5317 · Oct 20, 2020 at 03:10 PM

I've had exactly the same issue. So far the only workaround has been to uninstall Teams for the selected user (%localappdata%\Microsoft\teams\update.exe --uninstall). They then log out and in and the machine-wide installer gives them a new installation that works.

Only one user affected currently. First occurrence 7 October. Reoccurred for the same user today.

0 ·

Answer 1 · 2020-10-16T07:14:46.767Z

SharonZhao-MSFT answered Oct 16, '20 SharonZhao-MSFT commented Oct 27, '20

@JeffSnyder-0562,

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.

· 2

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

SharonZhao-MSFT · Oct 22, 2020 at 09:42 AM

@JeffSnyder-0562,
Do you have any update on this topic?
Do you try the workaround by ColinS?

0 ·

SharonZhao-MSFT · Oct 27, 2020 at 09:44 AM

@JeffSnyder-0562,
Haven't received your update for a long time, any update now?
If the above suggestion helps, please be free to mark it as answer for helping more people.

0 ·

Answer 2 · 2020-11-26T09:22:03.293Z

JanDirkLehde-0316 answered Nov 26, '20 JanDirkLehde-0316 edited Nov 26, '20

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

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Answer 3 · 2020-11-26T10:53:42.627Z

ColinS-5317 answered Nov 26, '20 ColinS-5317 commented Jan 18, '21

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.

· 3

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

SharonZhao-MSFT · Nov 27, 2020 at 01:53 AM

@JeffSnyder-0562, @JanDirkLehde-0316
You could try this solution provided by @ColinS-5317.
If there is any update, please feel free to drop us a note.
Have a nice day.

0 ·

JanDirkLehde-0316 · Nov 30, 2020 at 01:18 PM

Thanks for this solution. I deployed it this way on our RDS farm and set it up for a few test users. Will give feedback soon.

0 ·

ColinS-5317 · Jan 18, 2021 at 08:29 AM

This didn't work. The issue reoccurred.

0 ·

Answer 4 · 2020-12-01T00:06:13.037Z

ScottGiles-7262 answered Dec 1, '20 AlanW-5659 commented Jan 21, '21

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

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

ColinS-5317 · Jan 18, 2021 at 08:35 AM

Thanks. This works for me. I made a script that I direct staff to when they have this issue:

taskkill /f /im teams.exe
del /s %appdata%\Microsoft\Teams\desktop-config.json
%localappdata%\Microsoft\Teams\Update.exe --processStart "Teams.exe"
"C:\Program Files (x86)\Microsoft\Teams\current\Teams.exe"

It calls Teams both ways at the end to cover both the per-user and per-computer installations. It could be far more fancy with testing paths, etc but this gets our staff back in action.

I opened a call with MS365. Hilariously I was first directed to this thread as a solution. Since this problem only happens on RDS they could not help stating that it is an RDS environment issue rather than a Teams issue.

1 ·

AlanW-5659 · Jan 21, 2021 at 09:47 PM

Thanks for this - is this a permanent fix once performed or does it need to be done before every re-launch of Teams at each login in .. i.e. use the script listed below ?

Thanks, we just re-deployed 4 RDC servers on AWS running Server 2019 switching from an older in-house setup and this has been a nightmare ..

0 ·

Answer 5 · 2021-01-14T22:49:21.09Z

DalipTicku-1739 answered Jan 14, '21 GDub-2250 commented Oct 22, '21

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"

· 3

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

AndrewWright · Jan 18, 2021 at 11:21 AM

We have been suffereing with an issue where Outlook constanttly was asking for a password within a Citrix Environment, we believed the issue was caused by the AAD.BrokerPlugin but could not work out why it affected only users using MFA, this could be a temporary fix using just the last part of @DalipTicku-1739 script.

Thanks for posting.

Andrew

0 ·

MicheleVanderheidenMCSA-8626 · Jan 18, 2021 at 05:14 PM

We have been seeing this also, We have Citrix and running Server 2019 with Office 2019 Click to Run with Teams latest version.
Basically have been working with Microsoft and they don't seem to know what the problem is but Citrix has told us that it has to do with Authentication. We have tried several things per Microsoft and nothing has worked. They came back last week with the problem having to do with Volume license on our Office 2019. Since it doesn't sync the account when when they setup office for the first time. Once you log out and back in it will sync SharePoint Sites and One Drive but as soon as you sign out and back in and go back to the Office account it has a Fix me error every time. MS Team issue started with Server 2019, as it works fine in Server 2016. So what has changed.

0 ·

GDub-2250 · Oct 22, 2021 at 05:27 PM

You rock @DalipTicku-1739 !

This is what finally worked for me, after trying clearing the %appdata%\Microsoft\Teams did not help, etc

Thanks very much DalipTicku-1739, this got my Teams to launch again. Before it would just hang at the "Loading Microsoft Teams..." forever.

I have recommended our Citrix / AD admins to make this .bat (which I've appropriately named "FixTeams.bat" because that's exactly what it does!), and we will make sure it is made available to all of our VDI users. Since Teams startup issues appear to be a problem with Citrix / RDS environments, I am hopeful this will be an immediate fix for anyone who runs into the "hanging" issue. It doesn't happen every login, it was sporadic. So now, our support team can simply point users to execute the "globally available" .bat script to fix this, if needed.

Thank you very much @DalipTicku-1739 for sharing this batch script. It worked perfectly, on first try it fixed the issue in my VDI session.

Garrett B.

0 ·

Answer 6 · 2021-01-21T21:56:42.98Z

DalipTicku-1739 answered Jan 21, '21

@AlanW-5659 script has to run only when user has an issue.

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Answer 7 · 2021-01-24T12:27:16.96Z

PatrickJoosen-8454 answered Jan 24, '21 PatrickJoosen-8454 edited Jan 24, '21

We have the same problem here. RDS 2019 farm with 365 pro plus. The fix from @AlanW-5659 is working. I hope there will be a final solution.
we had trouble remembering the passwords in Outlook we fixed this with the folliwing keys.
[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity "DisableADALatopWAMOverride"=dword:00000001
[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity "DisableAADWAM"=dword:00000001

maybe this has to do with this.

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Answer 8 · 2021-02-01T15:59:24.67Z

SmeddeuIT-5547 answered Feb 1, '21

Nothing described solutions above helped. Any other suggestions?
Really don't understand why Microsoft isn't recognizing this issue.

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Answer 9 · 2021-02-04T16:23:32.803Z

AJAL answered Feb 4, '21 DaleTaylor-3209 edited Apr 22, '21

Hi there. Same Issue here, on RDS2019 with FSLogix 2.9.7349.30108, MS Teams Machine Wide Installer and Microsoft 365 Apps for Enterprise.
In my case, we have sometimes this issue here not only with MS Teams:
https://docs.microsoft.com/en-us/answers/questions/204147/windows-server-2019-rds-start-amp-search-does-not.html

· 1

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DaleTaylor-3209 · Apr 22, 2021 at 01:00 AM

Hey,

Not sure if you're still having this issue - I've answered this in the main topic, does this solve it for you? The common thread seems to be FSLogix.

Solution:

Get the user to sign out of their account in Settings > Accounts > Access work or school
Apply the registry fix from Cozzy-0379 above:

Create registry entry to prevent users on RDS server from performing workplace AAD joins: HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin, “BlockAADWorkplaceJoin”=dword:00000001

0 ·

Answer 10 · 2021-03-04T01:03:46.157Z

Cozzy-0379 answered Mar 4, '21

I was getting this issue with some of our clients staff. Deleting the AppData\Roaming\Teams folder would work temporarily.

Steps I've done to resolve this more permanently (so far):

Create registry entry to prevent users on RDS server from performing workplace AAD joins: HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin, “BlockAADWorkplaceJoin”=dword:00000001
Delete/Rename the following folders on the users profile:

C:\Users\<username>\AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy
C:\Users\<username>\AppData\Roaming\Microsoft\Teams

Upon completing these and re-logging into the user account they are prompted to login again to Teams with their username/password and any MFA in place. After this I can log the users out and back in of teams at will.

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

question