Remote Desktop Services in Windows Server 2016 Technical Preview 3
First published on CloudBlogs on Aug 19, 2015
Hello everyone, my name is Shanmugam Kulandaivel from the Remote Desktop Services (RDS) Team
The Technical Preview 3 (TP3) release of Windows Server 2016 was made available for download earlier today. If you haven’t downloaded the TP3 build yet, head over to the
to read about TP3 and take it for a
and let us know what you think.
In this post, I want to provide an overview of all the new RDS features that are available in the TP3 build. I also want to call out some of the features that are not fully complete yet (TP3 is not a production ready release) so that you have prior information about potential issues.
First, let’s start with all the exciting features that are ready for evaluation.
Enabling RDS in the cloud - Personal Session Desktops
: The new Personal Session Desktops capability in TP3 build allows administrators to deploy server based personal desktops in the cloud. With Personal Session Desktops every user gets an assigned RD Session Host VM and administrators can optionally enable administrative rights for users. Personal Session Desktops can also leverage RemoteFX vGPU. See
Introducing Personal Session Desktops
for more details.
Support for Gen 2 VMs:
RDS in TP3 supports Gen2 VMs.
You can now create Gen2 VMs and use those as template images for pooled/ personal VM collections and Personal Session Desktop collections. No additional configuration is required.
Windows Multipoint services (WMS):
Windows Multipoint Services is a simple, low-cost, single-server multi-user solution that is easy to deploy, highly durable and easy to manage. Multipoint is now part of Windows Server 2016 as an optional role service – you don’t need to deploy a separate WMS SKU to leverage WMS functionality.
Microsoft Edge browser in RDSH:
Lastly, the new
is now available in Windows Server 2016 TP3 build for testing.
There are few features that are not complete yet (TP3 is not a production ready release).
Scalability of RD Session Host
: TP3 build is not fully optimized for performance and hence the user density (number of users that you can support in a single server) with the TP3 build is lower than Windows Server 2012 R2.
Support for Windows Store Applications in RD Session Host Collections and Pooled VM Collections
: TP3 build does not support running Windows Store Applications in a RD Session Host collection or in a Pooled VM Collection running Windows 10.