As you can see, it’s simple to deploy VDI with Remote Desktop Services. Deploying
session virtualization uses the same process, except that no virtual machines are
required. The same wizard is used to deploy, and the same Connection Broker can be
used for multiple session virtualization collections and VDI collections. I walk
through a session host deployment in a video at http://youtu.be/_dkxyr03Er4.
Personal Session Desktops
Also notice in Figure 11.12 a Personal Session Desktop environment, which at the time
of writing is managed with PowerShell. For Personal Session Desktops, you must pre-
create the Remote Desktop Session Host instances, which are then mapped 1:1 to a
user. Personal Session Desktops cannot be pooled. To enable a pool of RDSH VMs for
users to connect to 1:1, simply deploy a number of RDSH servers in a standard RDSH
session collection and then configure the session limit to 1 on each RDSH server.
There is no rollback with Personal Session Desktops, as Personal Session Desktops
utilizes the session host deployment model, plus rollback/checkpoints are not
supported in public clouds like Azure anyway.
As previously mentioned, a benefit of the Personal Session Desktops feature over
traditional VDI is that it uses a server OS instead of a client OS, and the RD
Virtualization Host component is not required on the virtualization hosts. This makes
Personal Session Desktops a good solution for public cloud scenarios where
components cannot be installed on the fabric.
The following PowerShell creates an example Personal Session Desktop deployment
consisting of two RDSH instances that are then each mapped to a user. In my
environment, both the RDSH instances are VMs running Windows Server 2016.
However, technically this example should work with physical and virtual instances
and even pre-Windows Server 2016 RDSH instances.
#Define the RDSH instances that will be targets within the Personal
#Session Host collection
$RDSH1 = "savdalrdsh01.savilltech.net"
$RDSH2 = "savdalrdsh02.savilltech.net"
#Define the users that will be mapped to desktops
$User1 = "savilltech\john"
$User2 = "savilltech\bond"
#Set the target connection broker (that already exists) and collection name
$CollectionName = "PDSCollection"
$ConnectionBroker = "savdalrds16.savilltech.net"
#Add the RDSH instances to the connection broker
Add-RDServer -Server $RDSH1 -Role "RDS-RD-Server" -ConnectionBroker $ConnectionBroker Add-RDServer -Server $RDSH2 -Role "RDS-RD-Server"
-ConnectionBroker $ConnectionBroker
#Create the new collection granting users local admin privileges
New-RDSessionCollection -CollectionName $CollectionName `