What is new in RDS in Windows Server 2016

Hi, guys!

Windows Server 2016 RTM is closer than you think and here is the list of new improvements in RDS .If you would like to suggest new feature or you have something that you want to share with Microsoft staff , please use Remote Desktop User Voice Forum

Update: Windows Server 2016 is available for evaluation

MultiPoint Services

MultiPoint Server (MPS) is a technology and solution based on Windows Server and Remote Desktop Services. MPS was originally built for use in the classrooms and educational institutions and It allows you to provide low-cost sharing between MPS and user stations. User stations can be consist of only monitor, keyboard, mouse (zero clients) and be connected to MPS through USB (usb hubs), video cables or through LAN (RDP-over-LAN, if clients are not zero. for example, laptops, thin clients) MPS uses some of the RDS services (by default): RD Session Host and RD Licensing Server.

Microsoft announced that MultiPoint Server will be moved to Windows Server 2016 as a new server role called as “MultiPoint Services”. It’s also a new RDS deployment type.

remote desktop services_windowsserver2016_1

Please read my post that covers MPS in details

Personal Session Desktops

I hope you know VDI has limitations when it is used in SPLA scenarios (see my post VDI and SPLA) or more simply, you can’t share your VDI infrastructure based on client OS to customers under SPLA. Workaround is to provide session-based desktops to users with Windows Server inside (VDI with Windows Server as guest OS/gold image is also unsupported). To simplify it Microsoft has added new RDS collection– Personal Session Desktops (PSD). PSD allows administrators to create a session-based collection where each user  is assigned to dedicated RD Session Host.

In many RDS deployments Windows Server uses Desktop Experience (helps Windows Server to look as Windows Client OS). Windows Server 2016 brings a some improvements  to Desktop Experience as well.

Update: Windows Store Client, Edge and Modern calculator were included to Windows Server 2016 TPs with Desktop Experience (temporarily). These features are replaced with Windows Store Business, Internet Explorer 11, Classic calculator respectively

Let’s look to some scenarios:

  • If you want to assign user who familiar with Windows 10 only (for example) , it’s easy to achieve it by using PSD and Desktop Experience feature.
  • If user also has administrative privilege on desktop and you are moving him or her to PSD ,  PSD allows you to add these users to local admins on related Session Hosts so they can install/remove and do anything on PSDs.
  • If user wants to have applications that require accelerated graphics , you can implement PSD with new RemoteFX capabilities (below)

PSD was firstly announced in TP2 and has changed in TP3/TP4. We have only one way to implement Personal Session Desktops – PowerShell. There are no any options in GUI to create and manage this type of collections. A graphical user interface is going to be added to the Server Manager for Remote Desktop Services in a future release (I do not expect it until RTM release)

For demo purposes I use Quick Start deployment type (RDCB, RDWA and RDSH will be installed on the same server)

personal session desktops_1personal session desktops_2

personal session desktops_3personal session desktops_5

personal session desktops_6personal session desktops_7

Open PowerShell and type:

#Variable for RD Session Host name
$rdshost="tp4-root.democorp.ru"

To create PDS collection you have to use switch –PersonalUnmanaged (in TP2 was –PersonalSessionCollection)

#Create PDS Collection
New-RDSessionCollection -CollectionName Personal -ConnectionBroker $rdshost -SessionHost $rdshost -GrantAdministrativePrivilege -PersonalUnmanaged

CollectionName Size ResourceType CollectionType CollectionDescription
-------------- ---- ------------ -------------- ---------------------
Personal 1 Remote Desktop PersonalUnmanaged

TIP: If RD SH is already used you unable to create RDS collection . To workaround : remove RD session host from existed collection and try again

New-RDSessionCollection -CollectionName Personal -ConnectionBroker $rdshost -SessionHost $rdshost -GrantAdministrativePrivilege -PersonalUnmanaged
WARNING: The RD Session Host server tp4-root.democorp.ru already exists in another collection.
New-RDSessionCollection : Unable to create the session collection.

Get-RDSessionCollection

CollectionName Size ResourceType CollectionType CollectionDescription
-------------- ---- ------------ -------------- ---------------------
QuickSessionCollection 1 RemoteApp programs PooledUnmanaged

Get-RDSessionCollection|Remove-RDSessionCollection

Assign user to collection 

Set-RDPersonalSessionDesktopAssignment -CollectionName Personal -User democorp\rdsuser -Name $rdshost

Get-RDPersonalSessionDesktopAssignment -CollectionName Personal

CollectionName DesktopName User
-------------- ----------- ----
Personal TP4-ROOT.DEMOCORP.RU DEMOCORP\rdsuser

Go to https://<host fqdn>/rdweb , type user’s credential and you’ll see assigned collections

Note:  there is no PDS collection in the Server Manager – RDS – Collections list.

personal session desktops_9

Start Menu:

personal session desktops_10

PDS was created with –GrantAdministrativePrivilege switch so my user has been added to local administrators on assigned RDSH (desktop)

personal session desktops_8

RemoteFX Improvements

remotefx-hyper-v-evolution-from-2008-r2-to-2016

In Windows Server 2012 R2, the RemoteFX video adapter has a limitation of 256MB for the maximum amount of dedicated VRAM it exposed, OpenGL 1.1 (!!) and no support for OpenCL.

In real world RemoteFX in 2012 R2 is not suitable for modern applications such as Autocad Re-Cap (OpenGL 3.3, 1Gb VRAM is required) or Photoshop (CC requires OpenGL 2.0 and 512 MB VRAM at least).

Microsoft has got that there is no time to lose and has updated RemoteFX adapter with some VRAM new capabilities which can brake some limiting factors:

  1. A larger dedicated VRAM amount (currently up to 1GB) – A VM can now be configured to obtain up to 1GB of dedicated video memory. Depending on the amount of system memory assigned to the VM, this can provide up to a total of 2GB of VRAM (1GB dedicated and 1GB shared (I need to get some more info about it. I’ve never seen this on official slides ..only @msrdsblog))
  2. Configurable dedicated VRAM – Previously, VRAM was set for a VM dynamically based on the number of monitors and resolution configured for a VM, this association has been removed and now dedicated VRAM can be configured independent of a VM’s number of monitors or resolution. This can be configured using a PowerShell cmdlets in the technical preview.
  3. OpenGL 4.4 and OpenCL 1.1 API Support

These settings can be configured by PowerShell:

NAME
Set-VMRemoteFx3dVideoAdapter

SYNTAX

Set-VMRemoteFx3dVideoAdapter [-VM] <VirtualMachine[]> [[-MonitorCount] <byte>] [[-MaximumResolution] <string>]
[[-VRAMSizeBytes] <uint64>] [-Passthru] [-WhatIf] [-Confirm]  [<CommonParameters>]

P.S. I’ve already mentioned  RemoteFX and Discrete Device Assignment in what’s new in Hyper-V Windows Server 2016.

Improved Connection broker performance + Azure SQL DB for RDCB HA

RDCB was a source of a slow connection time in case of logon storm (many users trying to connect to their sessions) in WS2012/2012R2. That’s why there is significant improvement to handle performance during logon storms and when adding/restarting RD Session Host servers to a farm in WS 2016. Supported environments is up to 10k + concurrent connection requests.

Note: there is a specific KB to boost your RDCB performance in WS102R2 as well

Additionally, with Windows Server 2016 release RDS now supports Azure SQL Database as a database server for RDCB HA configuration. More info is available @Technet

Remote Desktop Services Windows Server 2016 Improvements Connection Broker

Client and miscellaneous updates

List of all and newly added clients :

  • RDP has been updated to version 10 (10586 build in TP4/Windows 10) with H.264 codec improvements. RDP (MSTSX.EXE) with H.264/A444 mode now supports 4k resolution and provides a new level of color conversion and improved fps throughput. A444 Mode (4:4:4 format of , 4:2:2 is used by rdp in 2012/2012r2) is enabled by default for all RemoteFX GPUs (DirectX 11.0 + H.264 HW Encoder has to support Level 4.1/BT.709 color conversion). 
  • (new) Remote Desktop Preview app for Windows 10 and Mac
  • RD Client for Android
  • RD Client for iOS
  • RD Client for Mac

Generation 2 VM Support

We cannot create VDI collection based on Gen2 “gold” VM in 2012 R2.  In Windows Server 2016 Gen 2 VM support has been added so you can use all type of generations as base for personal/pooled collections and personal session based desktops. There is no additional configuration required. *

*If you are not familiar with VDI, I’d recommend to read my post Quick VDI Deployment 

Pen Devices support in Remote Desktop Sessions

If your device supports pen locally and it is running Windows 10 at least, you can write or draw in the session (previously pen devices redirected but treated like a mouse)

No special configuration is needed. Just connect to remote PC and enjoy

Edge and Office 2016 support

New browser Edge from Microsoft is also supported in Remote Session

Outlook 2016 is supported* in pooled VDI and RDSH deployments (*search under Outlook might be slow or does not work as expected. ’cause search indexing depends on the machine ID, which is different for different VMs and indexer could take a long time to complete)

OneDrive for Business sync client is currently not supported for multi-user environments (pooled VDI and RDSH). Users can connect to their resources using the web interface.

Skype for Business is not supported for RDSH deployments. For VDI deployments use Lync VDI Plug-In

If you have Office 365 subscription and going to integrate with RDSH or VDI check out the following guide in PDF

Planning Poster

Going to migrate, build and run RDS environment? This poster can help you. Click to zoom and save in it’s original size. + don’t forget to bookmark updated RDS section @TechNet

Windows Server 2016 RDS Planning Poster

Thanks for reading!

Quick VDI Deployment

Remote Desktop Services (RDS) has been improved in Server 2012. Now, RDS allows remote users to gain access to their corporate desktops or published applications running either as sessions on a Remote Desktop Session Host server (using web browser to access, for example) , or virtual machines on a Remote Desktop Virtualization Host server, by using a remoting protocol from various end point devices (unfortunately, Microsoft doesn’t provide any RD clients for Tablet OS=you have to use software from third-party companies). Server 2012 offers two deployment types : virtual-desktop deployment (=VDI) or session-based deployment (=Terminal Services).

Requirements

– Active Directory
– DHCP
– Hyper-V Server
– Sysprepped VHD with Windows 8 or Windows 7 SP1
– Tablet PC or one PC with Windows OS for testing

I’m happy man and I have cluster based on EMC VNX 5100 (FC) attached with two server systems (server01 and server02) joined to forum.local domain. The most important thing that you have to check is NETWORK. During our further deployment steps, RDS will create  virtual switch in Hyper-V and randomly assign NIC as connection.This connection MUST have access to your DHCP-server.

hv

Deployment steps

1) Go to Server Manager – Manage – Add Roles and Features

wizard_1
Click “Next”

2) Choose “Remote Desktop Services installation”

wizard_2
New Windows Server Installation Type

3) Our way is “Quick Start”. Standard deployment allows you to deploy the main RDS roles (Connection Broker, Gateway and etc) on separate servers and make high available RDS systems. Quick Start install necessary roles on one server (stand-alone deployment)wizard_3

4) Select your server for VDI services. In my cases, it’s SERVER01.forum.local

wizard_4

5)  Add your sysprepped VHD. I use VHD with sysprepped WIndows 8 Pro.

To make sysprepped VHD do the following:

  1. Create VM
  2. Mount ISO with Windows 8 or Windows 7 SP1
  3. Install OS
  4. Run sysprep utility (WIN+R – sysprep)
  5. Check “Generalize”  , shutdown options must be “shutdown”

sysprep

wizard_5

6) Check “Restart…” and click Deploy

wizard_6

7) After system restart check that all services configures successful and click “Close”

wizard_7

Configuration steps

By default, wizard creates virtual desktop collection “QuickVMCollection..” . I won’t use this desktop collection ’cause I want to make another one with my settings (for example, I want to store all VDI desktops on cluster shared volume, enable user profile disks and etc).

1) Go to Remote Desktop Services

rds_configuration_1

2) Delete wizard-created collection

rds_configuration_2

3) Click on “Create virtual..” to create new collection

rds_configuration_3

4) Define your settings for the new collection

rds_configuration_4
Type collection name
rds_configuration_5
Select the type of virtual collection. The main difference: pooled – VM “reset to factory” when user log off and users cannot have full rights on VM , private – users may have full rights on thier own VD
rds_configuration_6
Choose virtual desktop template. RDS will use it like an “example” to create VM for users
rds_configuration_7
Next
rds_configuration_8
Define time zone and OU to VDI VMs. In this OU RDS will create computer objects for every created VM (automatically joined to domain). Verify that server account has a necessary rights in this OU! (use delegation if it’s necessary)
rds_configuration_9
Define your group users that has rights for connecting to VDI VMs
rds_configuration_10
Click NEXT
rds_configuration_11
Specify the path for the virtual desktops (vhd,configuration files)
rds_configuration_12
Specify path for user profile disks (if you want to deploy them) and max size for user’s VHDs. Profile disks is personal storage and doesn’t depend from VM on which user logged on.
rds_configuration_13
CREATE
rds_configuration_14
Close this wizard and go to “Collections” in RDS
rds_configuration_15
Right Click on the collection name – task status details and wait while 2 virtual desktops are creating

TESTING

From client PC : 

1) Open your browser and type https://FqdnOfRDserver/rdweb 

rds_configuration_16

2) Use your domain credentials and click on collection name (in my case, demoVDI) . Check that you can log in to VD.

rds_configuration_17

From Tablet:

*I used smartphone based on Android with PocketCloud Remote Desktop Pro installed

Basic recommendations: 

1) Download and install RD client with RD Gateway support (for example, iTap mobile or PocketCloud Remote Desktop Pro)

2) Open your mobile browser

3) Type RD server gateway address (in my case, I use wireless access point with DHCP relay , so I type internal RD server address)

4) Download and open RDP file

android

P.S. Go ahead and publish your remote App 🙂

UPDATE: Microsoft has released own RDP clients for Android and iOS . More info: http://technet.microsoft.com/en-us/library/dn473009.aspx

Note: you cannot create VDI collection from Gen2 VM (2012 R2) + if you are going to use VDI in production it is required to request and assign appropriate certificates for RDS roles (public <>gw, internally issued <> other roles)