


Remote Desktop Services session host server

Remote Desktop Services connection broker (provided for high availability) Remote Desktop Services connection broker and web resource server
#Win 2012 r2 remote desktop services accounts install#
In below procedures we’ll be performing a lab tutorial to install a Windows 2012 Remote Desktop Services Farm consisting of the following servers and roles: This allows the server to run RemoteApp and session-based desktops.Įnables authorized users to connect to virtual desktops, RemoteApp programs, and session-based desktops on the corporate network or over the Internet. In a full deployment we can have the following roles:Ĭonnects or reconnects a client device to RemoteApp programs, session-based desktops and virtual desktops.Įnables users to connect to resources provided by session collections and virtual desktop collections by using the Start menu or a web browser.Ī server running the Remote Desktop Protocol Server. When designing Windows 2012, Microsoft has put a lot of effort in centralising all the configuration panels for a Remote Desktop Services deployment in one central management console, they even have implemented deployment wizards to make the whole installation process easy to handle.Ī Microsoft Windows 2012/R2 Remote Desktop Services deployment is divided into several roles which can be installed on separate servers. This article outlines one possible way to set-up a remote desktop services farm in Windows 2012 R2.īefore Windows 2012 came on the scene, setting up remote desktop services involved a lot of manual labour, installing several components managed in a heap of management snap-ins.
