Microsoft teams is used for conducting online meetings and not for controlling computers remotely. For remotely accessing computers, you need to use tools like logmein, R-HUB remote support servers, Teamviewer etc. They are easy to use and work well. This feature will be part of Windows 7/Windows Server 2008 R2 release and works for connections to another client machine (physical or VM), or a Remote Desktop Session Host. How to use Remote Desktop Multimon feature: To use this feature, you must: Connect using the Remote Desktop Client 7.0 (mstsc.exe) available initially on Windows 7/Windows. Jun 01, 2019 I am under the influence this software is compatible with Server operating systems, and when installing using the msi file RDS will run the software normally. My problem is all user profiles that launch the Remote Desktop session get a empty white box as their Teams interface. About eight months ago, I came across a tool in the repository called Remote Desktop Connection Manager ('RDCMan' for short) written by Julian Burger, one of our principal developers on the Windows Live Experiences team. RDCMan is a central place where you can organize, group, and manage your various Remote Desktop connections. You can share your screen in Microsoft Teams however this is only possible when someone is logged into the machine & follows the steps below. Starting a screen sharing session in Teams is quite easy, and in this guide, we’ll show you how you can d.

Important

Media optimization for Teams is supported for Microsoft 365 Government (GCC) and GCC-High environments. Media optimization for Teams is not supported for Microsoft 365 DoD.

Note

Media optimization for Microsoft Teams is only available for the Windows Desktop client on Windows 10 machines. Media optimizations require Windows Desktop client version 1.2.1026.0 or later.

Microsoft Teams on Windows Virtual Desktop supports chat and collaboration. With media optimizations, it also supports calling and meeting functionality. To learn more about how to use Microsoft Teams in Virtual Desktop Infrastructure (VDI) environments, see Teams for Virtualized Desktop Infrastructure.

With media optimization for Microsoft Teams, the Windows Desktop client handles audio and video locally for Teams calls and meetings. You can still use Microsoft Teams on Windows Virtual Desktop with other clients without optimized calling and meetings. Teams chat and collaboration features are supported on all platforms. To redirect local devices in your remote session, check out Customize Remote Desktop Protocol properties for a host pool.

Prerequisites

Before you can use Microsoft Teams on Windows Virtual Desktop, you'll need to do these things:

• Prepare your network for Microsoft Teams.
• Install the Windows Desktop client on a Windows 10 or Windows 10 IoT Enterprise device that meets the Microsoft Teams hardware requirements for Teams on a Windows PC.
• Connect to a Windows 10 Multi-session or Windows 10 Enterprise virtual machine (VM).

Install the Teams desktop app

This section will show you how to install the Teams desktop app on your Windows 10 Multi-session or Windows 10 Enterprise VM image. To learn more, check out Install or update the Teams desktop app on VDI.

Prepare your image for Teams

To enable media optimization for Teams, set the following registry key on the host:

1. From the start menu, run RegEdit as an administrator. Navigate to HKEY_LOCAL_MACHINESOFTWAREMicrosoftTeams. Create the Teams key if it doesn't already exist.

2. Create the following value for the Teams key:

Install the Teams WebSocket Service

Install the latest Remote Desktop WebRTC Redirector Service on your VM image. If you encounter an installation error, install the latest Microsoft Visual C++ Redistributable and try again.

Latest WebSocket Service versions

The following table lists the latest versions of the WebSocket Service:

Updates for version 1.0.2006.11001

• Fixed an issue where minimizing the Teams app during a call or meeting caused incoming video to drop.
• Added support for selecting one monitor to share in multi-monitor desktop sessions.

Install Microsoft Teams

You can deploy the Teams desktop app using a per-machine or per-user installation. To install Microsoft Teams in your Windows Virtual Desktop environment:

1. Download the Teams MSI package that matches your environment. We recommend using the 64-bit installer on a 64-bit operating system.

   Important

   The latest update of the Teams Desktop client version 1.3.00.21759 fixed an issue where Teams showed UTC time zone in chat, channels, and calendar. The new version of the client will show the remote session time zone.

2. Run one of the following commands to install the MSI to the host VM:

   • Per-user installation

     This process is the default installation, which installs Teams to the %AppData% user folder. Teams won't work properly with per-user installation on a non-persistent setup.

   • Per-machine installation

     This installs Teams to the Program Files (x86) folder on a 32-bit operating system and to the Program Files folder on a 64-bit operating system. At this point, the golden image setup is complete. Installing Teams per-machine is required for non-persistent setups.

     There are two flags that may be set when installing teams, ALLUSER=1 and ALLUSERS=1. It is important to understand the difference between these parameters. The ALLUSER=1 parameter is used only in VDI environments to specify a per-machine installation. The ALLUSERS=1 parameter can be used in non-VDI and VDI environments. When you set this parameter, Teams Machine-Wide Installer appears in Program and Features in Control Panel as well as Apps & features in Windows Settings. All users with admin credentials on the machine can uninstall Teams.

     Note

     Users and admins can't disable automatic launch for Teams during sign-in at this time.

3. To uninstall the MSI from the host VM, run this command:

   This uninstalls Teams from the Program Files (x86) folder or Program Files folder, depending on the operating system environment.

   Note

   When you install Teams with the MSI setting ALLUSER=1, automatic updates will be disabled. We recommend you make sure to update Teams at least once a month. To learn more about deploying the Teams desktop app, check out Deploy the Teams desktop app to the VM.

Verify media optimizations loaded

After installing the WebSocket Service and the Teams desktop app, follow these steps to verify that Teams media optimizations loaded:

Remote Desktop Services Microsoft Teams

1. Quit and restart the Teams application.

2. Select your user profile image, then select About.

3. Select Version.

   If media optimizations loaded, the banner will show you Windows Virtual Desktop Media optimized. If the banner shows you Windows Virtual Desktop Media not connected, quit the Teams app and try again.

4. Select your user profile image, then select Settings.

   If media optimizations loaded, the audio devices and cameras available locally will be enumerated in the device menu. If the menu shows Remote audio, quit the Teams app and try again. If the devices still don't appear in the menu, check the Privacy settings on your local PC. Ensure the under Settings > Privacy > App permissions the setting Allow apps to access your microphone is toggled On. Disconnect from the remote session, then reconnect and check the audio and video devices again. To join calls and meetings with video, you must also grant permission for apps to access your camera.

   If optimizations do not load, uninstall then reinstall Teams and check again.

Known issues and limitations

Using Teams in a virtualized environment is different from using Teams in a non-virtualized environment. For more information about the limitations of Teams in virtualized environments, check out Teams for Virtualized Desktop Infrastructure.

Client deployment, installation, and setup

• With per-machine installation, Teams on VDI isn't automatically updated the same way non-VDI Teams clients are. To update the client, you'll need to update the VM image by installing a new MSI.
• Media optimization for Teams is only supported for the Windows Desktop client on machines running Windows 10.
• Use of explicit HTTP proxies defined on an endpoint is not supported.

Calls and meetings

• The Teams desktop client in Windows Virtual Desktop environments doesn't support creating live events, but you can join live events. For now, we recommend you create live events from the Teams web client in your remote session instead.
• Calls or meetings don't currently support application sharing. Desktop sessions support desktop sharing.
• Give control and take control aren't currently supported.
• Teams on Windows Virtual Desktop only supports one incoming video input at a time. This means that whenever someone tries to share their screen, their screen will appear instead of the meeting leader's screen.
• Due to WebRTC limitations, incoming and outgoing video stream resolution is limited to 720p.
• The Teams app doesn't support HID buttons or LED controls with other devices.
• New Meeting Experience (NME) is not currently supported in VDI environments.

For Teams known issues that aren't related to virtualized environments, see Support Teams in your organization.

Collect Teams logs

If you encounter issues with the Teams desktop app in your Windows Virtual Desktop environment, collect client logs under %appdata%MicrosoftTeamslogs.txt on the host VM.

If you encounter issues with calls and meetings, collect Teams Web client logs with the key combination Ctrl + Alt + Shift + 1. Logs will be written to %userprofile%DownloadsMSTeams Diagnostics Log DATE_TIME.txt on the host VM.

Contact Microsoft Teams support

To contact Microsoft Teams support, go to the Microsoft 365 admin center.

Customize Remote Desktop Protocol properties for a host pool

Customizing a host pool's Remote Desktop Protocol (RDP) properties, such as multi-monitor experience or enabling microphone and audio redirection, lets you deliver an optimal experience for your users based on their needs.

Teams And Remote Desktop - Microsoft Community

Enabling device redirections is not required when using Teams with media optimization. If you are using Teams without media optimization, set the following RDP properties to enable microphone and camera redirection:

• audiocapturemode:i:1 enables audio capture from the local device and redirects audio applications in the remote session.
• audiomode:i:0 plays audio on the local computer.
• camerastoredirect:s:* redirects all cameras.

To learn more, check out Customize Remote Desktop Protocol properties for a host pool.

Desktop sharing lets users present a screen or app during a meeting or chat. Admins can configure screen sharing in Microsoft Teams to let users share an entire screen, an app, or a file. You can let users give or request control, allow PowerPoint sharing, add a whiteboard, and allow shared notes. You can also configure whether anonymous or external users can request control of the shared screen. External participants in Teams meetings can be categorized as follows:

Remote Work Microsoft Teams

• Anonymous user
• Guest users
• B2B user
• Federated user

To configure screen sharing, you create a new meetings policy and then assign it to the users you want to manage.

In the Microsoft Teams admin center

1. Select Meetings > Meeting policies.

2. On the Meeting policies page, select Add.

3. Give your policy a unique title and enter a brief description.

4. Under Content sharing, choose a Screen sharing mode from the drop-down list:

   • Entire screen – lets users share their entire desktop.
   • Single application – lets users limit screen sharing to a single active application.
   • Disabled – Turns off screen sharing.

Note

You don't have to enable the calling policy in order for users to use screen share from chat. However, their audio is turned off until they unmute themselves. In addition, the user sharing the screen can click Add Audio to enable audio. If the calling policy is disabled, users won't be able to add audio to the screen share from a chat session.

5. Turn the following settings on or off:

   • Allow a participant to give or request control – lets members of the team give or request control of the presenter's desktop or application.
   • Allow an external participant to give or request control – This is a per-user policy. Whether an organization has this set for a user doesn't control what external participants can do, regardless of what the meeting organizer has set. This parameter controls whether external participants can be given control or request control of the sharer's screen, depending on what the sharer has set within their organization's meeting policies.
   • Allow PowerPoint sharing - lets users create meetings that allow PowerPoint presentations to be uploaded and shared.
   • Allow whiteboard – lets users share a whiteboard.
   • Allow shared notes – lets users take shared notes.

6. Click Save.

Use PowerShell to configure shared desktop

You can also use the Set-CsTeamsMeetingPolicy cmdlet to control desktop sharing. Set the following parameters:

• Description
• ScreenSharingMode
• AllowPrivateCalling
• AllowParticipantGiveRequestControl
• AllowExternalParticipantGiveRequestControl
• AllowPowerPointSharing
• AllowWhiteboard
• AllowSharedNotes

Learn more about using the csTeamsMeetingPolicy cmdlet.