7.0

Table Of Contents
Procedure
1 Log in as an administrator.
2 Start Server Manager.
3 Select Add roles and features.
4 On the Select Installation Type page, select Role-based or feature-based installation.
5 On the Select Destination Server page, select a server.
6 On the Select Server Roles page, accept the default selection and click Next.
7 On the Select Features page, under User Interfaces and Infrastructure, select Desktop Experience.
8 Follow the prompts and finish the installation.
Configure the Windows Firewall Service to Restart After Failures
Some Windows Server 2012 R2, Windows 8.1, and Windows 10 machines that are deployed as single-
session desktops do not become available immediately after they are provisioned. This issue occurs when
the Windows Firewall service does not restart after its timeout period expires. You can configure the
Windows Firewall service on the parent or template virtual machine to ensure that all machines in a desktop
pool become available.
If you encounter this issue during provisioning, the Windows event logs display the following error: The
Windows Firewall service terminated with the following service-specific error: This operation
returned because the timeout period expired.
This issue occurs on Windows Server 2012 R2, Windows 8.1, and Windows 10 machines. Other guest
operating systems are not affected.
Procedure
1 On the Windows Server 2012 R2, Windows 8.1, or Windows 10 parent or template virtual machine from
which you will deploy a desktop pool, select Control Panel > Administrative Tools > Services.
2 In the Services dialog box, right-click the Windows Firewall service and select Properties.
3 In the Windows Firewall Properties dialog box, click the Recovery tab.
4 Select the recovery settings to restart the service after a failure occurs.
Setting Drop-down Menu Option
First failure:
Restart the Service
Second failure:
Restart the Service
Subsequent failures:
Restart the Service
5 Select the Enable actions for stops with errors check box and click OK.
6 Deploy or redeploy the desktop pool from the parent or template virtual machine.
Install Horizon Agent on a Virtual Machine
You must install Horizon Agent on virtual machines that are managed by vCenter Server so that Connection
Server can communicate with them. Install Horizon Agent on all virtual machines that you use as templates
for full-clone desktop pools, parents for linked-clone desktop pools, parents for instant-clone desktop pools,
and machines in manual desktop pools.
To install Horizon Agent on multiple Windows virtual machines without having to respond to wizard
prompts, you can install Horizon Agent silently. See “Install Horizon Agent Silently,” on page 30.
Setting Up Desktop and Application Pools in View
26 VMware, Inc.