HI Mathew-8525
Never experienced that once i have ran the script.
Regards
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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!
HI Mathew-8525
Never experienced that once i have ran the script.
Regards
I have ran the following on RDSH Server 2019 in a Farm and it seems to have fixed the problem with users not being able to login and use Teams.
But some users can login to the RDSH and Teams opens up fine and then part way through the day Teams asks them to login again.
Is this normal asking to login again once its been logged in for most of the day?
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"
I've been looking for a solution for a while for this. In our environment, this was caused by users selecting "Stay signed in to all your apps" on first login with Teams. Since the workstations are non-persistent, but the profile moves to each workstation, this caused 80070003 errors in Teams.
All solutions seemed to only be temporary - deleting app data would solve the issue, only for it to immediately return on next login. Teams is installed machine-wide, etc.
Solution:
Create registry entry to prevent users on RDS server from performing workplace AAD joins: HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin, “BlockAADWorkplaceJoin”=dword:00000001
Step 1 works independently of step 2. Step 2 is just preventative. This is also a bit less destructive than wiping the whole profile. Users can also prevent this by clicking "No, sign in to this app only" when launching Teams for this time.
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):
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.
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://learn.microsoft.com/en-us/answers/questions/204147/windows-server-2019-rds-start-amp-search-does-not.html