User Profile
PavithraT
MicrosoftJoined 8 years ago
User Widgets
Recent Discussions
Microsoft Teams application window sharing is now generally available on Windows 365
We are happy to announce that Microsoft Teams application window sharing is now generally available on Windows 365 for Windows users. With application window sharing, users can now choose a specific window to share from their desktop screen. Previously, users could only share their full desktop windows or a Microsoft PowerPoint Live presentation. Application window sharing will help reduce the risk of displaying sensitive content during meetings/calls and keep meetings focused by directing participants to specified content. Getting Started The following minimum versions are required to enable the feature on Windows 365: Windows Desktop Client version 1.2.3770 WebSocket service version 1.31.2211.15001 To share your application window in a Microsoft Teams call, select Share content in your call window. Then click the Window panel to choose a window to share. Set up Teams on Windows 365 New to the service? Refer to the Teams on Windows 365 documentation on how to setup Microsoft Teams. Microsoft Teams Application window sharing is also available on Azure Virtual Desktop. To learn more, go to: https://aka.ms/AVDTeamsApplicationWindowSharingWindows 365 End-User Experience Survey
Hi All We, the Windows 365 service team, would like to hear from you on end-user experience so far. Tell us about what clients you use, whether your user stories are lit up with our clients, etc. This will help us prioritize features and tune our experience specifically to what end-users want. To participate, fill in the survey here - survey form Additionally, you can provide feedback from either from our end user portal or from our web client. Thank you for helping us by providing feedback.Teams Multi-window support and Call Me generally available on Windows 365
We are happy to announce that Teams Multi-window support and Call Me are now generally available on Windows 365. The Multi-window capability provides users the option to pop out chats, meetings, calls, or documents into separate windows to help streamline their workflow. It also brings new experiences to Windows 365 such as, Call Me. Previously, during a Teams meeting, if a user went to check their calendar, the meeting window would minimize to the corner of the screen. Now with Multi-window support, users can view full-sized, separate windows for meetings/calls and the main Teams client during a Teams meeting. Additionally, meeting and call controls such as mute, video, chat, leave, and more are now located at the top of the meeting window so that they are always available and never block the underlying content. Separate windows View meetings and calls in separate windows from the main Microsoft Teams client. Meeting controls Easier access to meeting controls now located at the top of the meeting screen, out of the way of content and video being shared. Call me This new feature allows users a way to transfer a Teams call to their phone over a PTSN network. Getting started To enable Microsoft Teams Multi-window on Windows 365, you must have installed Teams Desktop version 1.5.00.11865 or later. You can download this version here: MSI (125MB) or EXE (121 MB). After the Teams desktop client is updated to version 1.5.00.11865, you will see a banner (see screenshot below) when you open the new Teams desktop client for the first time. Restart Teams desktop app to turn on Multi-window. To verify Multi-window is on, right- click on any chat and if “pop out chat” is showing in the options, Multi-window has been successfully turned on. Call me feature is automatically available with Multi-window. Refer to Set up the Call me feature on how to set up your phone. Set up Teams on Windows 365 Microsoft Teams comes included in the Windows 11 and Windows 10 images optimized for Microsoft 365 apps. For more information on how to enjoy the best Teams experience, refer to the Teams on Cloud PC documentation. Teams on Azure Virtual Desktop Teams Multi-window is also available on Azure Virtual Desktop. To learn more, visit https://aka.ms/AVDTeamsMultiwindowBlog.Microsoft Teams background effects generally available on Windows 365
We are happy to announce that Teams background effects are generally available on Windows 365. Now, users can make meetings more personalized and avoid unexpected distractions by applying background effects. Meeting participants can select one of the available images to change their background or choose to blur their background. Background effects help keep the focus on the conversation while bringing new ways to meet face to face. Background blur subtly conceals everything in the background while the participant’s silhouette remains clear and isolated. Getting started To use Teams background blur on Windows 365, please ensure the following: Minimum version of Teams Desktop Client should be 1.5.00.11865 or later - MSI (125MB) or EXE (121 MB) Minimum version WebSocket service should be 1.1.2111.01001 Minimum version of Windows Desktop Client should be 1.2.3004 Please refer to Change your background for a Teams meeting on how to turn on background blur. Note: Blurring your background might not prevent sensitive information from being visible to other people in the call or meeting. Set up Teams on Windows 365 New to the service? Refer to the Teams on Windows 365 documentation on how to setup Microsoft Teams. Teams on Azure Virtual Desktop Teams background effects is also available on Azure Virtual Desktop. To learn more, visit https://aka.ms/AVDTeamsBackgroundEffects.Re: Cloud PC Teams video and audio
A couple of things to check: Do you have the right version of Teams for background blur - 1.5.00.11865? Did you restart the Teams app / Cloud PC after the Teams version was installed? We realized that one of our gallery images had Teams auto-update removed. We are adding that back to our next set of images. But for you already installed Cloud PCs you can follow the manual steps or the remediation script that I posted here: https://techcommunity.microsoft.com/t5/windows-365/how-to-re-enable-teams-auto-update-in-windows-365/m-p/3494416#M703How to re-enable Teams auto-update in Windows 365
In some Windows 365 Cloud PCs, the ability for the installed Teams client to automatically update has been affected along with the ability to check for updates. To rectify the problem, Teams Machine Wide Installer and the Teams client must be uninstalled, and then reinstalled. Reinstalling Teams can be a difficult task to accomplish if one doesn’t wish to disturb end users at work. Further complicating the matter is that the Teams client automatically installs only on user logon. To lower the complexity of fixing the problem while not impacting end users, we have written a Proactive Remediation package that takes end users into account. More information on Proactive Remediation Link to the Teams Fix - Proactive Remediation Package The detection script is checking to see if the Teams client is installed in the Users’ profile, which exists under c:\users\[user name]\appdata\local\Microsoft\Teams. If it is not found there, it will return non-compliant. The remediation script first checks to see if it has successfully run to completion before. If it has not, it then checks to see if a user is logged in and in an inactive state. If the user is logged in and active, the script exits, and Proactive Remediation will try again later. If the user is not logged in or active, the remediation process begins. The remediation script downloads the latest version of the Teams Machine Wide Installer MSI, uninstalls the Teams client, uninstalls the existing Machine Wide Installer installation, checks for a Registry Key than can cause issues with Teams client installations, then checks the user state again. If the user is not logged into their Cloud PC, the script will return compliant. Once the user logs back into their Cloud PC, the Machine Wide Installer will trigger the Teams client installation automatically. If the user is logged in but inactive, the remediation script creates a child PowerShell script, and XML file used to create a scheduled task, and registers the scheduled task that will initiate the Teams client installation when the user reconnects to their Cloud PC. All files are downloaded to C:\Windows\Temp. The amount of time that the scheduled task stays active is configurable in the Remediation script by modifying the $DateOffset variable. The child script checks for the existence of files it is supposed to remove, and this is done to ensure that the Teams client isn’t reinstalled every time the user connects. If the files exist, the script assumes it hasn’t successfully run before and launches the Teams client installer. Once the installation is complete, the script will attempt to delete the scheduled task. If the user doesn’t have administrative rights, it will not be able to remove the scheduled task and it will expire at its given time. The script will then remove the files used in this process. If the user does not reconnect to their Cloud PC by the time the scheduled task expires, the remediation script will run again and recreate the scheduled task. All the scripts in this solution generate their own logs to help admins troubleshoot issues. These logs are all written to C:\Windows\Temp. These logs are: Detection Script - Teams-MWI-detect.log Remediation Script - Teams-MWI-remediate.log Child Remediation Script - Teams-MWI-remediate-child.log The remediation script automates the whole process but if you want to manually fix this issue, you can do so by following these steps: On the Cloud PC, navigate to Settings > App > Apps and features. Search for Microsoft Teams. Uninstall Microsoft Teams and Teams Machine-Wide Installer. Download the latest version of Microsoft Teams from here. Open a command prompt and install the Teams client using the following command: msiexec.exe /I %Filepath to the downloaded Teams MSI% ALLUSERS=1 Restart the Cloud PC. The Teams client is now installed with automatic updates turned on.Teams on VDI – We need your feedback
Hi All Thank you for your ongoing partnership in our journey to support and improve the Microsoft Teams experience on virtual desktop environments. We understand that there is always room to improve for which we want to learn from your expertise and experience. Kindly fill this 5 min survey and provide us with your candid feedback. This will great help us in focusing our investments in the right areas. Survey form Thanks for taking time to provide us feedback.Re: Cloud PC Teams video and audio
MattMT You need to ensure that you are using the Media Optimized version of Teams while connecting from a supported Remote Desktop client. This will allow the Audio and video to be redirected and used. This does not work on the W365 or AVD web client. Ensure you have the latest version for all components involved: Minimum version of Teams Desktop Client should be 1.5.00.11865 or later - MSI (125MB) or EXE (121 MB) Minimum version WebSocket service should be 1.1.2111.01001 Minimum version of Windows Desktop Client should be 1.2.3004 This is not a generally reported issue and also not seen in any of our dogfooding environments. We are keeping track of it to ensure there is no regression. Let me know if you are still seeing this after the updates.Announcing Public Preview: Tool to migrate from Azure Virtual Desktop Classic to ARM
We are excited to announce the public preview of the migration tool that will allow you to migrate your Azure Virtual Desktop Classic resources to ARM. There are multiple new features that have been released to ARM and we would love for all our customers to get access to them and make their service experience better. Migrate automatically from Azure Virtual Desktop (classic) (preview) - Azure | Microsoft Docs has all the info to get you started with your migration.Announcing general availability of Azure Virtual Desktop service metadata storage in UK and Canada
Hi All On Jun 9th 2021 we announced the general availability of metadata storage in Europe for Azure Virtual Desktop. Today we added both UK and Canada to the generally available list of geographies to store service metadata in. For more info on what data is being stored, please visit here - Data locations for Azure Virtual Desktop - Azure | Microsoft DocsAnnouncing general availability of Azure Virtual Desktop service metadata storage in Europe
We are excited to announce the general availability of storing Azure Virtual Desktop service metadata in the Europe geography. This feature allows customers to choose West Europe and North Europe as regions to create their service objects in. The Azure geography associated with these regions is where the metadata for the host pool and other service objects will be stored. Additionally, we also started the public preview for metadata storage in the UK geography that includes the UK South and UK West regions. With this update, Azure Virtual Desktop supports storing metadata in the following geographies: United States (US) (Generally available) Europe (EU) (Generally available) United Kingdom (UK) (Public preview) Learn more about the types of data being stored here - Data locations for Azure Virtual Desktop - Azure | Microsoft DocsAnnouncing public preview of Windows Virtual Desktop service metadata storage in Europe
We are excited to announce the public preview of storing service metadata in Windows Virtual Desktop in the Europe geography. This feature allows customers to choose West Europe and North Europe as regions to create their service objects in. The Azure geography associated with these regions is where the metadata for the host pool and other service objects will be stored. With this update, Windows Virtual Desktop supports storing metadata in the following geographies: United States (US) (Generally available) Europe (EU) (Public preview) Getting started: To get the latest list of supported regions, re-register the resource provider: On the Azure portal, go to Subscriptions and select the relevant subscription. Select Resource Provider. Select Microsoft.DesktopVirtualization, then select Re-register from the action menu. When you re-register the resource provider, you won't see any specific UI feedback or update status. The re-registration process also won't interfere with your existing environments. To create a host pool, follow the instructions here : Windows Virtual Desktop host pool Azure portal - Azure | Microsoft Docs as before. The new regions will be displayed when you click on the “Location” drop down. Learn more about Azure geographies at the Azure datacenter map. The following documentation links will be updated shortly: Data locations for Windows Virtual Desktop - Azure | Microsoft Docs Windows Virtual Desktop host pool Azure portal - Azure | Microsoft Docs Windows Virtual Desktop environment host pool creation - Azure | Microsoft Docs
