Build and deploy your Remote Desktop Services deployment
A Remote Desktop Services deployment is the infrastructure used to share apps and resources with your users. Depending on the experience you want to provide, you can make it as small or complex as you need. Remote Desktop deployments are easily scaled. You can increase and decrease Remote Desktop Web Access, Gateway, Connection Broker and Session Host servers at will. You can use Remote Desktop Connection Broker to distribute workloads. Active Directory based authentication provides a highly secure environment.
Remote Desktop clients enable access from any Windows, Apple, or Android computer, tablet, or phone.
See Remote Desktop Services architecture for a detailed discussion of the different pieces that work together to make up your Remote Desktop Services deployment.
Have an existing Remote Desktop deployment built on a previous version of Windows Server? Check out your options for moving to WIndows Server 2016, where you can take advantage of new and better functionality around performance and scale:
- Migrate your RDS deployment to Windows Server 2016
- Upgrade your RDS deployment to Windows Server 2016
Want to create a new Remote Desktop deployment? Use the following information to deploy Remote Desktop in Windows Server 2016:
- Deploy the Remote Desktop Services infrastructure
- Create a session collection to hold the apps and resources you want to share
- License your RDS deployment
- Have your users install a Remote Desktop client so they can access the apps and resources.
- Enable high availability by adding additional Connection Brokers and Session Hosts:
If you're a hosting partner interested in using Remote Desktop to provide apps and resources to customers or a customer looking for someone to host your apps, check out Remote Desktop Services hosting partners for information about an assessment you can take about using RDS in Azure as a hosting environment, as well as a list of partners who've passed it.
Submit and view feedback for