大网数据广告活动
远程桌面与会话

Remote Desktop Services - Build anywhere

· 52CE 我爱测

Planning information to help you determine where to host your RDS deployment.

Deploy on-premises, in the cloud, or a hybrid of the two. Modify your deployment as your business needs change.

Regardless of where you are, the underlying architecture of the Remote Desktop Services environment remains the same:

  • You still must have an internet-facing server to utilize RD Web Access and RD Gateway for external users
  • You still must have an Active Directory and--for highly available environments--a SQL database to house user and Remote Desktop properties
  • You still must have communication access between the RD infrastructure roles (RD Connection Broker, RD Gateway, RD Licensing, and RD Web Access) and the end RDSH or RDVH hosts to be able to connect end-users to their desktops or applications.

This flexibility allows you to get the best of both worlds:

  • The simplicity and pay-as-you-go methods associated with the cloud and the online world.
  • The familiarity and hassle-free way of leveraging heavy resources that already exist on-premises.

For additional information, look at how to build and deploy your Remote Desktop Services deployment.

Source: Microsoft Learn / Windows Server documentation by Microsoft and contributors (upstream author metadata: robinharwood). Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / Windows Server documentation
适用范围
Windows Server · Source date 7/3/2024
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。