RDS deployment with Azure AD Application Proxy Azure AD Domain Services can work in either deployment: basic or highly available. This removes the complexity of manually syncing users and managing more virtual machines. However, if you don't have a traditional AD and only have an Azure AD tenant-through services like Office365-but still want to leverage RDS, you can use Azure AD Domain Services to create a fully managed domain in your Azure IaaS environment that uses the same users that exist in your Azure AD tenant. The two standard architecture diagrams above are based on a traditional Active Directory (AD) deployed on a Windows Server VM. RDS deployment with Azure AD Domain Services Below are some architectures showing how they incorporate with RDS. Though the standard RDS deployment architectures fit most scenarios, Azure continues to invest in first-party PaaS solutions that drive customer value. RDS architectures with unique Azure PaaS roles Highly available deployment – This contains all necessary components to have the highest guaranteed uptime for your RDS environment.Basic deployment – This contains the minimum number of servers to create a fully effective RDS environment.Remote Desktop Services has two standard architectures: These diagrams are primarily intended to illustrate how the RDS roles are colocated and use other services. However, you can deploy Remote Desktop Services on-premises and on other clouds. The architecture diagrams below show using RDS in Azure.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |