Module 09 RDS in Windows Services
Module 09 RDS in Windows Services
Even though, we could have selected the Quick Start deployment option and have all three
required Remote Desktop Services (RDS) role services installed on SEA-RDS1, you selected
the Standard deployment option to practice selecting different servers for the RDS role
services. Furthermore, the Quick Start deployment option will create a collection
named QuickSessionCollection and publish the following RemoteApp
Programs: Calculator, Paint, and WordPad.
7. On the Review role services page, review the description of the role services, and then
select Next.
We will now do the actual installation of RDS using Windows PowerShell. The previous steps were
included to demonstrate how to install RDS using Server Manager.
1. Switch to SEA-DC1.
powershell
c. Wait for the installation to complete, which will take approximately 5 minutes,
and then wait as SEA-RDS1 restarts automatically.
6. In Server Manager, in the navigation pane, select Remote Desktop Services. You might
need to select Remote Desktop Services twice.
RDS in Windows Server supports two types of Session Collections on a single RD Session Host: an RD
Session Collection, or a RemoteApp Session Collection. You cannot run both session collection types
on the same RD Session Host by default. Therefore, when you're doing this exercise, you will first
create an RD Session Host collection and verify that it works and then create a RemoteApp Session
collection and verify that as well.
We will now create and configure the session collection using Windows PowerShell. The previous
steps were included to demonstrate how to create a session collection using Server Manager.
1. ON SEA-RDS1, right-click or access the context menu for the Start button, and then
select Windows PowerShell (Admin).
3. Wait for the command to complete, which will take approximately 1 minute.
6. In Server Manager, in the navigation pane, select Collections, and then verify that a
collection named IT is listed in the details pane.
3. On the Session Collection page, select the various settings and notice how the
collection is configured.
5. Select User Profile Disks, and verify that User Profiles Disks is not enabled.
7. Minimize Server Manager.
a. AudioVideoPlayBack
b. AudioRecording
c. PlugAndPlayDevice
d. SmartCard
e. Clipboard
f. LPTPort
g. Drive
Set-RDSessionCollectionConfiguration –CollectionName IT –
ClientDeviceRedirectionOptions PlugAndPlayDevice,
SmartCard,Clipboard,LPTPort,Drive
a. PlugAndPlayDevice
b. SmartCard
c. Clipboard
d. LPTPort
e. Drive
1. Switch to SEA-DC1.
$AccessRule = New-Object
System.Security.AccessControl.FileSystemAccessRule("Contoso\SEA-
RDS1$","FullControl","Allow")
$acl.SetAccessRule($AccessRule)
4. Switch to SEA-RDS1.
This page opens because RD Web is using a self-signed certificate that is not trusted by the
client. In a real production deployment, you would use trusted certificates.
This prompts the Unknown publisher pop up window because certificates for RDS have not yet
been configured.
9. In SEA-RDS1, right-click or access the context menu for Start, select Shut down or sign
out. and then select sign-out.
cd\
1. Switch to SEA-RDS1.
a. When the command has completed, review the information about the published
app, and then minimize the WindowsPowerShell window.
Get-RDRemoteApp -CollectionName IT
a. Examine the output of the command. Notice that you will get a list of all
published RemoteApp programs.
2. On the This site is not secure page, select Details, and then select Go on to the
webpage.
This page opens because RD Web is using a self-signed certificate that is not trusted by the
client. In a real production deployment, you would use trusted certificates.
3. On the RD Web Access page, in the Domain\user name field, enter contoso\jane. In
the Password field, enter Pa55w.rd, and then select Sign in. If prompted by Microsoft Edge to
save the password, select Never.
The Unknown publisher pop-up window displays because you have not yet configured
certificates for RDS.
7. Wait for the RemoteApp Paint program to start, and then test its functionality.
Note: There may be a delay before the published Remote Apps are ready to launch. You may
move on to the next exercise.
5. Wait while the System Preparation Tool (Sysprep) completes and shuts down the VM.
Results: After completing this exercise, you will have prepared a Hyper-V VM to be a virtual desktop
template.