Events
Apr 29, 2 PM - Apr 30, 7 PM
Join the ultimate Windows Server virtual event April 29-30 for deep-dive technical sessions and live Q&A with Microsoft engineers.
Sign up nowNote
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
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.