Teams Remote Desktop Server

 admin



Remote desktop licensing is a must-have for teams with developers and other users away from the local network. By purchasing remote desktop user CALs, you can add as many remote users as you want to your existing server. Learn Which Remote Desktop Licenses Are Right for You Searching for remote desktop licensing to fit your deployment needs? Download this app from Microsoft Store for Windows 10, Windows 8.1, Windows 10 Mobile, Windows Phone 8.1, Windows 10 Team (Surface Hub), HoloLens. See screenshots, read the latest customer reviews, and compare ratings for Microsoft Remote Desktop. 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. @WernerVermelis-5761, As we are mainly responsible for general issue of Microsoft Teams. Your question which is involved in Remote desktop is not included in Teams, I would remove the office-teams-windows-itpro tag.

-->

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.

This article describes the requirements and limitations for using Microsoft Teams in a remote desktop services (RDS) environment.

What is RDS?

Remote Desktop Services (RDS) is the platform of choice for building virtualization solutions for every end customer need. RDS lets you deliver individual virtualized applications, provide secure mobile and remote desktop access, and provide end users the ability to run their applications and desktops from the cloud.

RDS offers deployment flexibility, cost efficiency, and extensibility. RDS is delivered through a variety of deployment options, including Windows Server 2016 for on-premises deployments, Microsoft Azure for cloud deployments, and a robust array of partner solutions.Depending on your environment and preferences, you can set up the RDS solution for session-based virtualization, as a virtual desktop infrastructure (VDI)

Currently, Teams in a remote desktop services environment is available with support for collaboration and chat functionality. To ensure an optimal user experience, follow the guidance in this article.

Teams on RDS with chat and collaboration

If your organization wants to only use chat and collaboration features in Teams, you can set user-level policies to turn off calling and meeting functionality in Teams.

Remote

Set policies to turn off calling and meeting functionality

You can set policies by using the Microsoft Teams admin center or PowerShell. It might take some time (a few hours) for the policy changes to propagate. If you don't see changes for a given account immediately, try again in a few hours.

Calling polices: Teams includes the built-in DisallowCalling calling policy, in which all calling features are turned off. Assign the DisallowCalling policy to all users in your organization who use Teams in a virtualized environment.

Meeting policies: Teams includes the built-in AllOff meeting policy, in which all meeting features are turned off. Assign the AllOff policy to all users in your organization who use Teams in a virtualized environment.

Assign policies using the Microsoft Teams admin center

To assign the DisallowCalling calling policy and the AllOff meeting policy to a user:

  1. In the left navigation of the Microsoft Teams admin center, go to Users.

  2. Select the user by selecting to the left of the user name, and then select Edit settings.

  3. Do the following steps:

    a. Under Calling policy, select DisallowCalling.

    b. Under Meeting policy, select AllOff.

  4. Select Apply.

To assign a policy to multiple users at a time:

  1. In the left navigation of the Microsoft Teams admin center, go to Users, and then search for the users or filter the view to show the users you want.
  2. In the ✓ (check mark) column, select the users. To select all users, select the ✓ (check mark) at the top of the table.
  3. Select Edit settings, make the changes that you want, and then select Apply.

Or, you can also do the following steps:

Installing MS Teams On Shared RDS Server 2019 - Microsoft ...

  1. In the left navigation of the Microsoft Teams admin center, go to the policy you want to assign. For example:

    • Go to Voice > Calling policies, and then select DisallowCalling.
    • Go to Meetings > Meeting policies, and then select AllOff.

  2. Select Manage users.

  3. In the Manage users pane, search for the user by display name or by user name, select the name, and then select Add. Repeat this step for each user that you want to add.

  4. When you're finished adding users, select Save.

Assign policies using PowerShell

The following example shows how to use the Grant-CsTeamsCallingPolicy to assign the DisallowCalling calling policy to a user.

To learn more about using PowerShell to manage calling policies, see Set-CsTeamsCallingPolicy.

The following example shows how to use the Grant-CsTeamsMeetingPolicy to assign the AllOff meeting policy to a user.

To learn more about using PowerShell to manage meeting policies, see Set-CsTeamsMeetingPolicy.

-->

If you use Remote Desktop Services (RDS) to provide shared computers to users in your organization, you can install Microsoft 365 Apps on those computers. But, you have to use the Office Deployment Tool and enable shared computer activation to do the installation.

The following are two common RDS scenarios:

  • Install Microsoft 365 Apps on an RDS server.

  • Install Microsoft 365 Apps on a shared virtual machine.

What you need to get started

The following is a list of prerequisites that you need to deploy Microsoft 365 Apps or the Project and Visio desktop apps with RDS:

  • One of the following plans:
    • An Office 365 (or Microsoft 365) plan that includes Microsoft 365 Apps for enterprise, purchased through a Volume Licensing Program.
    • A Microsoft 365 Business Premium plan that includes Microsoft 365 Apps for business.
    • For the Project and Visio desktop apps, a subscription plan that includes those products.
  • The Office Deployment Tool, which is available on the Microsoft Download Center.
  • A separate user account for each user who logs on to the shared computer.
  • An eligible license assigned to each user account.
  • A version of Windows listed in the Microsoft 365 plans for business, education, and government system requirements.
  • Reliable connectivity between the shared computer and the internet.
  • If you're deploying Microsoft 365 Apps on a shared virtual machine, Microsoft supports using Hyper-V only.

Note

  • The ability to enable shared computer activation is a Microsoft 365 Business Premium entitlement and not a feature of Microsoft 365 Apps for business in general.
  • The reliable internet connectivity is required because the shared computer must be able to contact the Office Licensing Service on the internet to obtain a license for each user who uses the Microsoft 365 Apps on the computer and then activate Microsoft 365 Apps. Internet connectivity is also needed to renew the license, which occurs every few days.

Install Microsoft 365 Apps on an RDS server

In this scenario, you install Microsoft 365 Apps on a computer configured as a Remote Desktop Session Host server. This enables multiple users to connect remotely to this computer. The users can each run Office programs, such as Word or Excel, at the same time. The overall process is the same for the Project and Visio desktop apps.

Here are the basic steps of how to install Microsoft 365 Apps on an RDS server:

Teams Remote Desktop Server

  1. Install and configure Windows Server.

  2. Install and configure the Remote Desktop Session Host role service.

    For example, follow these steps to install RD Session Host on Windows Server.

    For users to be able to connect remotely to the server to use Microsoft 365 Apps, their accounts must be members of the Remote Desktop Users group on the RD Session Host server.

  3. Use the Office Customization Tool to create a configuration file. Make sure to tick the Shared Computer box in the Licensing and activation section. Export the resulting configuration file and save it to the same location as the extracted Office Deployment Tool.

    You can also create a configuration file using a text editor. Make sure that it includes the following line:

    You use the SharedComputerLicensing setting to enable shared computer activation, which is required to use Microsoft 365 Apps on a shared computer.

  4. Use the Office Deployment Tool and the configuration file to install Microsoft 365 Apps on the RD Session Host server.

See Full List On Docs.microsoft.com

At this point, users can connect to the RD Session Host server and use Microsoft 365 Apps. Users can connect to the server by using Remote Desktop Connection, which is available in Windows, or by using other Remote Desktop clients.

Install Microsoft 365 Apps on a shared virtual machine

In this scenario, you install Microsoft 365 Apps as part of a client operating system image, such as one running Windows 8.1 or Windows 10. Then, you use RDS and Hyper-V to create a group of virtual machines based on that image. These virtual machines can be shared by multiple users. In RDS, this is known as either a virtual desktop pool or a pooled virtual desktop collection, depending on which version of RDS that you're using.

MS Teams On RDS - Microsoft Tech Community

Note

You can also use RDS to assign a virtual machine to a specific user. RDS calls that a personal virtual desktop. In that scenario, you don't use shared computer activation, because the virtual machine isn't shared among multiple users.

Isntall Teams On Remote Desktop Server

Here are the basic steps of how to configure RDS to deploy Microsoft 365 Apps on a shared virtual machine:

Install Microsoft Teams Using MSI

  1. Create the operating system image:

    • Follow the instructions to Deploy Microsoft 365 Apps as part of an operating system image. In Step 2 of the instructions, make sure that your configuration.xml file also includes the following line to enable shared computer activation:
    • You also need to make some RDS-specific changes on the virtual machine, such as enabling Remote Desktop.

  2. Install and configure Windows Server.

  3. Install and configure RDS.

    For example, follow these steps to deploy a virtual desktop collection on Windows Server.

Microsoft Teams Remote Desktop Server

After you've completed all the RDS configuration steps, users can connect to any of the virtual machines and run Microsoft 365 Apps.

Cannot Use Video Or Audio Call With Teams On RDS Server ...

Related articles