Windows 2012 r2 remote desktop services vdi sysprep

WINDOWS 2012 R2 REMOTE DESKTOP SERVICES VDI SYSPREP FULL

These servers would provide public connectivity to the session host farm. For this Windows 2012 R2 would be best, there have been tremendous advances in 2012 R2 Gateway Services. Create a load balanced group of Remote Desktop Gateway Servers so that we don't have to publish port 3389.

These servers would serve as launchpad and would be disposable / load balanced so as to be completely interchangeable. There would be no personalized data for users on these servers, as MYDOCS / DESKTOP / FAVORITES would all be redirected via GPO to the user home directory. These servers would not have any applications installed on them and would serve ONLY as a landing ground / launch pad for users to run applications provided by RemoteApp servers. Users would connect to this through Remote Desktop gateway servers and / or through a remote desktop RemoteApp server / RDWeb server.

WINDOWS 2012 R2 REMOTE DESKTOP SERVICES VDI SYSPREP FULL

Create a group of load balanced session host servers for users to land on for a full desktop experience.I will describe the setup in case I'm not being clear: I was hoping to have this farm be somewhat unique, however, in that I wanted to setup an embedded system of RDP session host landing servers that themselves were running RemoteApp client. I was considering trying to setup an RDP farm with either Windows 2008 R2 or Windows 2012 R2, I'm not sure which.

Windows 2012 r2 remote desktop services vdi sysprep