1. Just wondering if anyone is using Teams on a RDS Server 2016 environment? Looking to test this out but was wondering if anyone has it deployed in that type of environment? It works but the AppData install is a pay but works. In the past it was per user but now you can do it for all the users in a computer.
2. Microsoft Teams for Education. Help drive the transition to inclusive online or hybrid learning, build confidence with remote learning tools, and maintain student engagement. Watch learning tools. 1 Availability of mobile apps varies by country/region. Follow Microsoft 365.

• Microsoft Teams Rds Install Free
• Microsoft Rds Manager
• Install Microsoft Teams On Rds

Microsoft Teams Installation On RDP. Let’s go through the steps of this guide to finish the installation path. Install Microsoft Teams On RDP Admin. 1-As always, you are recommended to open the main page of the company to proceed with a safe and legal download. 2-Click the Downloads Teams button by scrolling down as shown below. Apr 21, 2017 Re: Does Microsoft support Teams in RDS (Remote Desktop Services/Citrix Desktop)? I've got it running a VDI environment without issue. That being said I haven't tried to do a voice/video call yet. Further troubleshooting has led to enabling run as administrator on C: Program Files (x86) Microsoft Teams current teams.exe. This completely resolves the problem for the admin user but any other user trying to launch Teams on the shared desktop is greeted with a UAC prompt.

In the past, Microsoft Teams was a separate installation from Microsoft 365 Apps. But starting with Version 1902, Teams is included as part of new installations of Microsoft 365 Apps. If Teams is already installed on the device, no changes are made to that installation of Teams.

Teams is also being added to existing installations of Microsoft 365 Apps on devices running Windows. For more information about when that occurs, see What about existing installations of Microsoft 365 Apps?.

Note

To complete the installation of Teams on new or existing installations of Microsoft 365 Apps, either restart the device or have the user log off and log back on.

If Skype for Business is already installed on the device, Skype for Business won't be removed and will continue to function as before. Skype for Business will continue to be installed with new installations of Microsoft 365 Apps, unless you configure your installation to exclude it.

You don't have to wait if you're ready now to deploy Teams to the users in your organization. You can deploy Teams for your users by following these instructions or you can have your users install Teams for themselves from https://teams.microsoft.com/downloads.

We also have the steps you can take to exclude Teams from new or existing installations of Microsoft 365 Apps if your organization isn't ready to deploy Teams.

Important

If you're in a GCC High or DoD environment, currently you need to exclude Teams from being installed with Microsoft 365 Apps. Instead, you need to install Teams by using the separate MSI-based installer. For links to the correct version of the MSI-based installer for your environment, see Install Microsoft Teams using Microsoft Endpoint Configuration Manager. In the future, you'll be able to install Teams along with Microsoft 365 Apps in GCC High or DoD environments without needing to use the separate MSI-based installer.

If you're using Office for Mac, see Microsoft Teams installations on a Mac.

If you're using shared computers or Virtual Desktop Infrastructure (VDI), see Shared computer and VDI environments with Microsoft Teams.

When will Microsoft Teams start being included with new installations of Microsoft 365 Apps?

The date when Teams starts being installed with new installations of Microsoft 365 Apps depends on which update channel you're using. The following table shows the schedule.

Note

Teams is also included with the following new installations:

• Microsoft 365 Apps for business, starting with Version 1901, which was released on January 31, 2019. Microsoft 365 Apps for business is the version of Office that is included with some Microsoft 365 business plans, such as Microsoft 365 Business Premium.
• Office for Mac, starting with Version 16.21, which was released on January 16, 2019. Office for Mac comes with any plan that includes Microsoft 365 Apps. For more information, see Microsoft Teams installations on a Mac.

How to exclude Microsoft Teams from new installations of Microsoft 365 Apps

If you don't want Teams included when you install Microsoft 365 Apps on devices running Windows, you can use Group Policy or the Office Deployment Tool. Or, as an alternative, you can let Teams be installed, but use Group Policy to prevent Teams from automatically starting when the user signs in to the device.

If you want to use the Office Deployment Tool, you can use the ExcludeApp element in your configuration.xml file, as shown in the following example.

Tip

Instead of using a text editor to create your configuration.xml, we recommend that you use the Office Customization Tool (OCT). The OCT provides a web-based interface for making your selections and creating your configuration.xml file to be used with the Office Deployment Tool. For more information, see Overview of the Office Customization Tool.

If you're deploying Microsoft 365 Apps by using the Office 365 Client Installation wizard in Microsoft Endpoint Configuration Manager (current branch), you can set Teams to the Off position in the configuration UI.

If you're deploying Microsoft 365 Apps by using Microsoft Intune, there is a checkbox to exclude Teams on the Configure App Suite pane.

If you're letting your users install Microsoft 365 Apps for themselves from the Office 365 portal, you can't exclude Teams from being included as part of the installation, unless you use Group Policy.

To remove Teams after it's been installed, go to Control Panel > Uninstall a program and uninstall Microsoft Teams and any instances of Teams Machine-Wide Installer. If you previously installed Teams separately from installing Microsoft 365 Apps, you might see multiple instances of Teams Machine-Wide Installer. You can also use PowerShell to remove Teams as shown in this script sample.

What about existing installations of Microsoft 365 Apps?

Teams is also being added to existing installations of Microsoft 365 Apps on devices running Windows as part of the normal update process. There is no change to existing installations of Mac.

Whether Teams gets added to an existing installation of Microsoft 365 Apps is determined by what version is installed, what version you're updating to, and some other factors. Version 1906 that was released in Current Channel in July is the first version that started including Teams as part of the update process. But not all devices updating to Version 1906 or later have received Teams as part of the update process because the rollout has been a gradual process over several months. So if you've updated a device to the latest version of Microsoft 365 Apps, but Teams hasn't been installed, that is probably expected and not necessarily an error. It's likely a future update will install Teams. If you want Teams on that device now, you can install it manually from https://teams.microsoft.com/downloads.

Important

If you're updating your existing installation of Microsoft 365 Apps to Version 1908 (Build 11929.20300) or later, Teams will be added. To complete the installation of Teams after the update, either restart the device or have the user log off and log back on.

The date when Teams can start being added to existing installations of Microsoft 365 Apps depends on which update channel you're using. The following table shows the schedule.

If you don't want Teams to be added to existing installations of Microsoft 365 Apps when you update to a newer version, you can use Group Policy or the Office Deployment Tool. Or, as an alternative, you can let Teams be added, but use Group Policy to prevent Teams from automatically starting when the user signs in to the device.

If you want to use the Office Deployment Tool, you need to run the Office Deployment Tool in /configure mode on each device before you update to the new version of Microsoft 365 Apps. The following is a configuration.xml file you can use with the Office Deployment Tool to exclude Teams from being added to your existing installation of Microsoft 365 Apps for enterprise.

Note

• Be sure you're using the most current version of the Office Deployment Tool available on the Microsoft Download Center.
• If your existing installation of Microsoft 365 Apps has excluded other apps, such as Access, you need to include a line in your configuration.xmi file for each of those excluded apps. Otherwise, those apps will be installed on the device.
• If you have Microsoft 365 Apps for business installed, use O365BusinessRetail for the Product ID in your configuration.xml file.

Also, in some situations, doing an Online Repair results in Teams being installed. For example, if Microsoft 365 Apps is configured to get updates from the Office Content Delivery Network (CDN) and the update channel or version you're using includes Teams as part of the installation.

Use Group Policy to control the installation of Microsoft Teams

If your organization isn't ready to deploy Teams and you use Group Policy, you can enable the Don't install Microsoft Teams with new installations or updates of Office policy setting. You can find this policy setting under Computer ConfigurationPoliciesAdministrative TemplatesMicrosoft Office 2016 (Machine)Updates.

Note

• This policy setting only applies if you are installing or updating to Version 1905 or later of Microsoft 365 Apps.
• To use this policy setting, download at least version 4882.1000 of the Administrative Template files (ADMX/ADML), which were released on July 9, 2019.

If you enable this policy setting, Teams won't be installed in the following scenarios for Version 1905 or later:

• New installations of Microsoft 365 Apps
• Updates to existing installations of Microsoft 365 Apps
• Users installing Microsoft 365 Apps for themselves from the Office 365 portal
• An Online Repair of an existing installation of Microsoft 365 Apps

If you have Microsoft 365 Apps for business or can't use Group Policy for some other reason, you can add the preventteamsinstall value to the HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftOffice16.0commonofficeupdate key in the registry. The type for preventteamsinstall is REG_DWORD and the value should be set to 1 if you don't want Teams installed.

Use Group Policy to prevent Microsoft Teams from starting automatically after installation

If you want Teams to be installed, but don't want Teams to start automatically for the user after it's installed, you can use Group Policy and enable the Prevent Microsoft Teams from starting automatically after installation policy setting. You can find this policy setting under User ConfigurationPoliciesAdministrative TemplatesMicrosoft Teams.

By enabling this policy setting before Teams is installed, Teams won't start automatically when the user logs in to the device. Once a user signs in to Teams for the first time, Teams is configured to start automatically the next time the user logs into the device. The user can configure Teams to not start automatically by configuring user settings within Teams or by clearing the Open Teams on startup check box on the sign in screen for Teams.

Tip

If you've already installed Teams but you want to use this policy setting to prevent Teams from starting automatically, enable this policy setting and then run this script on a per-user basis to reset the autostart setting for Teams.

But even if you enable this policy setting so that Teams doesn't start automatically, an icon for Microsoft Teams will appear on the user's desktop.

Important

• This policy setting only applies if you are installing or updating to the following versions of Microsoft 365 Apps:
  • Version 1906 or later of Current Channel
  • Version 1902 (Build 11328.20368) or later of Semi-Annual Enterprise Channel or Semi-Annual Enterprise Channel (Preview)
  • Version 2003 or later of Monthly Enterprise Channel
• To use this policy setting, download at least version 4882.1000 of the Administrative Template files (ADMX/ADML), which were released on July 9, 2019.

If you have Microsoft 365 Apps for business or can't use Group Policy for some other reason, you can add the PreventFirstLaunchAfterInstall value to the HKEY_CURRENT_USERSOFTWAREPoliciesMicrosoftOffice16.0Teams key in the registry. The type for PreventFirstLaunchAfterInstall is REG_DWORD and the value should be set to 1 if you don't want Teams to automatically start after installation.

Shared computer and VDI environments with Microsoft Teams

If devices in your organization are shared by multiple users, be aware that Teams is installed separately for each user that signs into that device. Installations of Teams average about 500 mb, so hard disk space, as well network bandwidth for updates, might become an issue for these shared devices installed with Teams. In cases where shared devices are used by a significant number of users, you might want to consider not installing Teams on those shared devices.

If you plan to use Teams in a Virtual Desktop Infrastructure (VDI) environment, see Teams for Virtualized Desktop Infrastructure. Teams installed with Microsoft 365 Apps as described in this article is NOT currently supported in VDI environments.

Feature and quality updates for Microsoft Teams

After Teams is installed, it's automatically updated approximately every two weeks with new features and quality updates. This update process for Teams is different than the update process for the other Office apps, such as Word and Excel. For more information, see Teams update process.

Microsoft Teams installations on a Mac

If you're using Version 16.21, or later, of the Office suite install package to deploy on a Mac, Teams will be included as part of the installation.

If you don't want Teams included as part of the installation, there is an Office suite install package available that doesn't include Teams. You can also use the install packages for individual applications, such as Word or Excel. For links to the most current install packages, see Update history for Office for Mac.

If you're letting your users install Office for themselves on a Mac, such as from https://teams.microsoft.com/downloads, you can't exclude Teams from being included as part of the installation.

To uninstall Teams on a Mac, quit Teams by right-clicking the Teams app in the dock, then hold down Option and choose Force Quit. Open the Application Folder, select Microsoft Teams, and move it to the Trash.

What about Office 365 plans that don't include Microsoft Teams?

Some Office 365 plans include Microsoft 365 Apps, but don't include the Teams service. Even if a plan doesn't include the Teams service, Teams will still be installed with Microsoft 365 Apps, as described earlier in this article. To prevent Teams from being installed, follow the steps outlined earlier in this article.

For Office 365 plans that don't include the Teams service, a free trial version of Teams that's valid for 1 year is available. Your users can start using it when they sign in to Teams. For more information about this free trial version and providing your users access to it, see Manage the Microsoft Teams Commercial Cloud Trial offer.

Additional information about installing Microsoft Teams

• There is no change to new or existing installations of Office 2019, such as Office Professional Plus 2019.
• Teams is installed with Microsoft 365 Apps in the same way that Teams is installed if you use the MSI-based installer for Teams. For each new user that signs into the device, the Teams installer runs and the Teams application is installed in the user's AppData folder.
• The architecture (sometimes referred to as the bitness) of Teams and Microsoft 365 Apps installed on the device don't have to match. For example, you can install the 32-bit version of Teams on a device running the 64-bit versions of Microsoft 365 Apps. To change the architecture of Teams, for example from 32-bit to 64-bit, you need to uninstall the 32-bit version of Teams and then install the 64-bit version of Teams.
• For more information for IT Pros about Microsoft Teams, see Microsoft Teams documentation.

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:

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.

Microsoft Teams Rds Install Free

Contact Microsoft Teams support

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

Microsoft Rds Manager

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.

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.

Install Microsoft Teams On Rds

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