DFMIT Posted July 12 Share Posted July 12 I have the new teams installed and when a user logs into an instant clone non-persistent desktop, teams will open but at the top it will have a red bar with a sign in error, if you click sign in button at the top right, it will then prompt for MFA and everything will work. Has anyone else had this and were you able to resolve it. I am using FSLOGIX office container to hold teams data. I also have a DEM profile setup to retain some of the settings that the office container does not, such as auto start teams on windows login. Link to comment Share on other sites More sharing options...
Dominik Posted July 12 Share Posted July 12 Hello, as far as remember I use this DEM settings to get Teams settings, include logon information. You can test on yours ENV. Most important is folders, because in this place some information about logon are stored: <LocalAppData>\Microsoft\Vault <AppData>\Microsoft\Vault DEM settings: [IncludeRegistryTrees] HKCU\Software\Microsoft\Office\Teams [IncludeFolderTrees] <LocalAppData>\Microsoft\Credentials <LocalAppData>\Microsoft\Teams <LocalAppData>\Microsoft\TeamsMeetingAddin <LocalAppData>\Microsoft\TeamsPresenceAddin <LocalAppData>\SquirrelTemp <LocalAppData>\Microsoft\IdentityCache <LocalAppData>\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy <AppData>\Microsoft\Teams <AppData>\Microsoft Teams <AppData>\Teams <AppData>\Microsoft\Protect <LocalAppData>\Microsoft\Vault <AppData>\Microsoft\Vault [ExcludeFolderTrees] <AppData>\Teams\logs <AppData>\Microsoft\Teams\media-stack <AppData>\Microsoft\Teams\Service Worker <AppData>\Microsoft\Teams\Application Cache <AppData>\Microsoft\Teams\Cache <AppData>\Microsoft\Teams\tmp <LocalAppData>\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\TempState <LocalAppData>\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\AC\Temp [ExcludeFiles] <AppData>\Microsoft\Teams\logs.txt <AppData>\Microsoft\Teams\lockfile Dominik Jakubowski EUC Expert | vExpert ⭐️⭐️⭐️ VDI Ninja https://vdesktop.ninja Link to comment Share on other sites More sharing options...
DFMIT Posted July 12 Author Share Posted July 12 I am seeing the issue on the New Teams 2.1 not the classic teams. Link to comment Share on other sites More sharing options...
Zeno Posted August 21 Share Posted August 21 Hello DFMIT, Did you solve this problem? I have the same setup(New Teams 2.1 on non-persistent Win 11 23H2, ODFC, DEM) and I am facing the same issue. Link to comment Share on other sites More sharing options...
DFMIT Posted August 22 Author Share Posted August 22 I still do not have a resolution so I have kept teams classic in our production environment. Link to comment Share on other sites More sharing options...
BenTrojahn Posted August 22 Share Posted August 22 (edited) For us, this issue only happens on some 0365 with admin roles WHERE mfa was required. The clue was that the issue happens in the full Outlook client where we not have expected an MFA prompt on prem. Remove that role or MFA requirement and the issue went away. All O365 apps now login automatically. Edited August 22 by BenTrojahn Link to comment Share on other sites More sharing options...
Administrators Holly Lehman Posted August 26 Administrators Share Posted August 26 @DFMIT based on this thread, did the reply from @BenTrojahn solve your issue, or are you still keeping with the classic Teams environment? Link to comment Share on other sites More sharing options...
Zeno Posted August 28 Share Posted August 28 (edited) On 8/26/2024 at 5:31 PM, Holly Lehman said: @DFMIT based on this thread, did the reply from @BenTrojahn solve your issue, or are you still keeping with the classic Teams environment? It didn’t work for me. My test user doesn't have any admin roles, MFA is enabled by Conditional access policy but the VDI public IP address is excluded as a trusted location. OneDrive and Outlook sign in without any problems; it’s just Teams 2.1 that’s having issues. I checked the Signin Logs and I noticed Error 9002341 This led me to the comments on this article: https://techcommunity.microsoft.com/t5/windows-it-pro-blog/upcoming-changes-to-windows-single-sign-on/bc-p/4167626/highlight/true#M7419 The failing SSO seems to be a known problem with non-persistant machines. The mentioned workaround in the comments (EnableADAL,DisableAADWAM, DisableADALatopWAMOverride) didn't work for me either. I guess the next thing I will try in the lab is hybrid joining the machines, at the moment i'm using AD Seamless SSO Edited September 2 by Zeno Link to comment Share on other sites More sharing options...
vap0r Posted August 28 Share Posted August 28 Same issue here, been testing like crazy trying to get consistent sign in results with New Teams in my non persistent VDI environment but absolutely no luck. Link to comment Share on other sites More sharing options...
StephenWagner7 Posted August 30 Share Posted August 30 AFAIK, using conditional access policies will not work if the Instant Clone isn't hybrid domain joined (Azure SSO via PRT). Someone please correct me if I'm wrong on this one... Stephen Wagner (President, Digitally Accurate Inc.) VMware vExpert (vExpert Pro, vSphere, vSAN Awards), Omnissa Tech Insider, NVIDIA NGCA Advisor, VMUG Leader, and Director (Board of Directors) at World of EUC Check out my Tech Blog: https://www.StephenWagner.com Link to comment Share on other sites More sharing options...
DFMIT Posted September 17 Author Share Posted September 17 All of our users see the error message, as they all have the MFA requirement. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now