Teams Account picker list empty on Welcome screen?
We have a shared computer (conference room), on which people sign in into Teams with "This App only". After the meeting, they sign out. Teams restarts and shows the Welcome screen with the text "Pick an account to continue". Suddenly, this list with saved accounts is now empty. Did something changed in the last update(s) of Teams? If it is an improved security/privacy update, why is the text still shown "pick an account..." if this list remains empty?
New Teams: New meetings/chats opening on wrong screen
With the new Teams version when I join a meeting the window opens on the wrong screen. Formerly the window opened on the same screen as the main Teams window. Now it opens on the main screen. Since I am running an RDP session on the main screen and the window opens in the background of it, I don't see the window. That makes the new version unusable to me. The same thing happens to chats when I start a chat out of the new "Persons" app (actually Personen since I am using the German version) that seems to have replaced the old Contacts in the Chat app. That happens even though I have configured all chat windows to open in the main window. Please fix before you force this on everyone. (I hope someone from Microsoft is listening here. The "Share your feedback" button unfortunately doesn't work, it links to a site that says "Service unavailable".)
New Teams not loading with FSLogix 2210 HF4, Horizon non-persistent VDI
Hi all, We've been testing the latest Teams 2.1 Bootstrapper on our non-persistent Horizon VDI machines but having issues once we bring FSLogix into the mix. We are able to deploy new Teams onto our base image and when using a local profile it launches and runs as expected from the shortcut in the Start Menu. Similarly on our physical PCs Classic Teams > New Teams upgrades without issue (we're not running FSLogix on physical machines... yet) When logging in with FSLogix enabled (frxtray shows version 2.9.8228.50276) the Teams shortcut is present, however clicking it produces a white progress bar and no further action. We have updated our Redirections.xml to one we found here https://www.jeffriechers.com/wiki/teams-2-1-with-fslogix-setup-guide/comment-page-1/ If we look at the properties of the Windows Store App for Teams it returns 16KB, which seems wrong? Looking in Event Viewer AppxPackaging log we see this error, can't find much online relating to it. App manifest validation warning: Declared namespace http://schemas.microsoft.com/appx/manifest/uap/windows10/7 is inapplicable, it will be ignored during manifest processing. I note from another thread that there's a GPO for ODFC called IncludeTeams that needs to be turned on to roam the new Teams cache etc. https://learn.microsoft.com/en-us/microsoftteams/new-teams-vdi-requirements-deploy HKEY_LOCAL_MACHINE\SOFTWARE\Policies\FSLogix\ODFC\IncludeTeams However we don't use ODFC as FSLogix is in single-profile mode as recommended here... https://learn.microsoft.com/en-us/fslogix/tutorial-configure-odfc-containers Using the ODFC container in a dual container configuration isn't necessary or recommended. So my question is: does anyone have new Teams 2.1 working with FSLogix HF4 and single container profile? is ODFC required for Teams 2.1 to operate? If so is there any definitive MS documentation to say this as it seems rather vague and support are not giving us any further information has anyone got a stable non-persistent VDI desktop working with Teams 2.1 and FSLogix in general? Any input much appreciated as it feels like we've hit a wall here at present. The MS documentation suggests Hotfix 4 is meant to be the supported configuration for Teams 2.x but struggling to find evidence of a working setup. As an aside the reason we're running FSLogix in the first place is in order for OneDrive client to be deployed onto our non-persistent VDI machines as Microsoft don't support Roaming Profiles for this (which is what we used for roaming user data previously)Teams V2 auto start on the nonpersistent VDI devices
Hi, Does anybody knows should it be possible to have a new teams starting automatically when using nonpersistent VDI devices? Users are able to turn auto start on, but still Teams stays away. Microsoft have had this document as well around this topic: New Teams auto-start but as VDI type sometimes affect to some service I was wondering could it be reason as well. Earlier it was so much easier to apply app into RUN hive on registry and problem solved, but now with MSIX-based applications this is not anymore that easy. If this should be troubleshooted, then what process btw is the one which should be launching Teams? Just wondering how to trace that. With RUN hive, this was so much more clear.
New Microsoft Teams on Citrix VDI (w/ FSLogix profiles)
Hello, we're trying to deploy the New Microsoft Teams in our infrastructure. Technical details: - Citrix CVAD 1912LTSR CU8 (VDAs are running 2311.0.0.247) - Windows 10 22H2 19045.4291 - Teams 24074.2321.2810.3500 - Citrix HDX Optimized - FSLogix 2210 hotfix 3 (2.9.8784.63912) - Machines are deployes using both PVS and MCS New Teams opens up, but the "Account/Status management" drop-down menu at the top-right of the MS Teams window disappears immediately. As a result, users can't manage their status and change their profile settings. Screenshot of what's missing: What MS Teams looks like in our Citrix VDI environment: Troubleshooting done so far: - New Teams re-deployment (completely uninstalled and installed) - Cache cleared - User profile (FSLogix) reset and re-created from scratch Any idea on what could be the cause of the issue? Thank you ZenoSwitching to NEW Teams error message "Your admin has restricted access to the new teams"
Hello Team, On Teams Admin Center 365 we have enabled the Teams update policy for the Global/Org Default to New Teams Only but some users are getting "Your admin has restricted access to the new teams" window when they click the toggle button to try new teams. When they try to switch back to classic they are getting "Your org is installing the new version of teams. We'll let you know when it's ready". I have checked: - user account has license and Teams is enabled in Apps - user account has classic teams running - verified that the update policy is set to the account - user can access teams web version and can switch to New Teams - under apps and features I can verify that New Teams is installed Are there other recommended troubleshooting steps? (clearing cache or reinstall?) Thanks!
Unable to use "callto:" to initiate a call in new Teams
We used to be able to run the command "%LOCALAPPDATA%\Microsoft\WindowsApps\ms-teams.exe callto:email address removed for privacy reasons" to initiate a call in the classic version of Teams, but since upgrading to the new Teams client we get "Sorry, we're unable to complete the call." I've tested the command with a phone number "%LOCALAPPDATA%\Microsoft\WindowsApps\ms-teams.exe callto:3059999999" and confirmed this still works and will prompt me in Teams if I'd like to call this number, it just doesn't find the person when using their email: I found the following Q&A post https://learn.microsoft.com/en-us/answers/questions/1179266/callto-working-in-teams where Microsoft stated "external deep link like callto: are not supported" but using a deeplink like the example in https://learn.microsoft.com/en-us/microsoftteams/platform/concepts/build-and-test/deep-link-workflow?tabs=teamsjs-v2#deep-link-to-start-an-audio-video-call-with-users, launches the browser first before redirecting to Teams, which is the behavior we are hoping to avoid. We can still use the classic Teams for now but considering it will be replaced with the new Teams by March 31, 2024, we wanted to get confirmation if callto: will not be supported in the new Teams. If it's no longer supported, how can we initiate a call in Teams from a command without launching the browser first?
New Teams Client is crashing when Jabra Evolve 75 Headset is muted by putting the microphone up
We have a strange issue with the new Teams client. When the Mic is put up, the headset is actually muting Teams. However, with the new Teams client, if the headset is put Teams crashes sometimes. Teams crashes also reproducible if the mic is put up before joining a conference. Anybody has the same problem or a solution for that? The Evolve Headset is connected via a Jabra 370 USB dongle.
