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.
Switching 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!
System Tray Mute during Meeting -- New Teams on Desktop
When I switch to the new Teams, I seem to lose the ability to mute the mic via the system tray during a meeting. Is there any way to regain this ability within the new Teams app? Currently I just revert to the old Teams. I find the system tray control very useful to retain control while working on other virtual desktops during meetings. Thanks, Jonah
New Teams: MsixvcStagingSession failed with error 0x80070570. (0x80070570)
App installation failed with error message: Common::Deployment::MsixvcStagingSession::GetManifestReader in MsixvcStagingSession failed with error 0x80070570. (0x80070570) This error happens instantly, I see a 0% loading bar and then the error occures. I am on a domain machine using a local administrator account. What I have done so far: DISM /online /cleanup-image /check health - ok SFC /Scannow - Founder corruption, fixed it, restart, no change. Deleted ProgramData/Microsoft/*Teams files/folders Delete %appdata%/Local and roaming TEAMS files and TEMP cache. Delete Software Distribution folder content. Used 'Everything' app to find and delete the remaining TEAMS files. Restarted 3-4 times now, no change. Please advise? Thanks, William Croft
Microsoft Cranks Up Deployment Schedule for Teams 2.1
Microsoft released details about the deployment schedule for the new Teams client (2.1) on June 30, 2023. It looks like a lot of work to roll out the new Teams client will happen over the remainder of 2023. It seems like tenants can use the classic Teams client for at least until mid-2024, but soon there’ll only be one Teams client in use, and that’ll be Teams 2.1. https://office365itpros.com/2023/07/04/new-teams-client-schedule/
