What’s new with Virtual Desktop Infrastructure (VDI) In this article, we’ll look first at how Windows Server 20 R2 have improved VDI deployment and administration. This last, the RD Virtualization Host, was the component that enabled the new VDI functionality installing the RD Virtualization Host role automatically installed Hyper-V on the server (if it wasn’t already installed) and took on the task of monitoring and preparing the virtual machines.
The terminal server role became the Remote Desktop Session Host, the TS Session Broker became the RD Connection Broker, the TS Gateway became the RD Gateway, TS Web Access became RD Web Access, and a brand new service, the RD Virtualization Host, appeared. When Microsoft introduced Windows Server 2008 R2, there was a complete overhaul of the entire set of services formerly called Windows Terminal Services, along with a plethora of name changes that served to confuse IT pros. The server-based implementation of Remote Desktop was introduced in Windows NT 4.0 Terminal Services Edition back in 1998 and continued to be called Terminal Services when it was included in Windows 2000 Server, Windows Server 2003 and Windows Server 2008. In Part 2, we’ll look at how additional enhancements and additions have made RDS easier for IT pros to deploy, secure and manage. In Part 1 of this series, we looked at how changes and improvements in Remote Desktop Services in Windows Server 2012/2012 R2 and Windows 8/8.1 have improved the overall experience for end-users. Remote Desktop Services in Windows Server 2012/2012 R2 and Windows 8/8.1 (Part 3).
#SERVER 2016 REMOTE DESKTOP SERVICES RETAIN SESSION ID SERIES#
If you would like to read the other parts in this article series please go to:
0 kommentar(er)
