Reviewer's Guide for View in VMware Horizon 7: … WHITE PAPER | 2 REVIEWER’S GUIDE FOR VIEW IN VMWARE HORIZON 7: INSTALLATION AND CONFIGURATION Table of Contents

TECHNICAL WHITE PAPER – AUGUST 2017

REVIEWER’S GUIDE FOR VIEW IN VMWARE HORIZON 7: INSTALLATION AND CONFIGURATIONVMware Horizon 7 version 7.x

T E C H N I C A L W H I T E PA P E R | 2

REVIEWER’S GUIDE FOR VIEW IN VMWARE HORIZON 7: INSTALLATION AND CONFIGURATION

Table of Contents

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

JMP – Next-Generation Desktop and Application Delivery Platform . . . . . . . . . . . . . . . . . . . . . . . . . 3

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Section A: Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Exercise A1: Verifying Minimum Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Exercise A2: Gathering Installation Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Exercise A3: Downloading Horizon 7 Installers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Exercise A4: Installing Connection Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Exercise A5: Installing Composer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Section B: Initial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Exercise B1: Adding the Product License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Exercise B2: Connecting the vCenter Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Exercise B3: Enabling the Windows Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Exercise B4: Creating an Event Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

All Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

About the Authors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39



IntroductionThe Reviewer’s Guide for View in VMware Horizon 7: Installation and Configuration provides a technical overview of the View component of VMware Horizon® 7 version 7.x. The View component (formerly called Horizon View) offers a virtual desktop infrastructure (VDI) and published applications through Remote Desktop Session Host (RDSH). This is done through a single platform, which simplifies desktop administration and operations, and enhances user experience. In comparison to physical desktops, delivering View virtual desktops from centralized VMware vSphere® servers enhances the security of applications and data and improves IT responsiveness, while at the same time reducing costs. The user enjoys a consistent and responsive experience across devices and locations, while maintaining IT-approved levels of customization.

JMP – Next-Generation Desktop and Application Delivery Platform JMP (pronounced jump), which stands for Just-in-Time Management Platform, represents capabilities in VMware Horizon 7 Enterprise Edition that deliver Just-in-Time Desktops and Apps in a flexible, fast, and personalized manner. JMP is composed of the following VMware technologies:

• VMware Instant Clone Technology for fast desktop and RDSH provisioning

• VMware App Volumes™ for real-time application delivery

• VMware User Environment Manager™ for contextual policy management

JMP allows components of a desktop or RDSH server to be decoupled and managed independently in a centralized manner, yet reconstituted on demand to deliver a personalized user workspace when needed. JMP is supported with both on-premises and cloud-based Horizon 7 deployments, providing a unified and consistent management platform regardless of your deployment topology. The JMP approach provides several key benefits, including simplified desktop and RDSH image management, faster delivery and maintenance of applications, and elimination of the need to manage “full persistent” desktops.

PurposeThis white paper is one of a series of papers to help you evaluate the View component of Horizon 7. This white paper provides exercises to guide you through the basic installation and initial configuration processes. For an overview of View in Horizon 7 key features, and for other white papers to explore the key features—such as instant clones, smart policies, and more—see All Guides.

Note: This guide is designed for evaluation purposes only. It uses the minimum required resources for a basic deployment and does not explore all features. This evaluation environment should not be used as a template for a production environment. For information beyond the considerations of this white paper, see VMware Horizon 7 Documentation.

AudienceThis guide is intended for IT administrators, architects, engineers, and product evaluators who want to install View in Horizon 7 and deploy a VDI environment. Both current and new users of View can benefit from using this guide. You should be familiar with VMware vSphere and VMware vCenter Server®. Some familiarity with other technologies is also helpful, including networking and storage in a virtual environment, Active Directory, identity management, directory services, Simple Mail Transfer Protocol (SMTP), and RSA SecurID.

Before You BeginThis guide is second in the series of guides. We recommend that you follow the guides in order. For information about all guides in the series, see All Guides.

https://blogs.vmware.com/euc/2016/02/horizon-7-view-instant-clone-technology-linked-clone-just-in-time-desktop.html

https://www.vmware.com/products/appvolumes.html

https://www.vmware.com/products/user-environment-manager.html

https://www.vmware.com/support/pubs/view_pubs.html



Section A: InstallationThis section provides exercises to help you evaluate the installation of your View instance. The exercises are sequential and build upon one another, so complete each exercise before moving on to the next.

To start setting up a working View environment, complete the following installation exercises:

• Exercise A1: Verifying Minimum Requirements

• Exercise A2: Gathering Installation Data

• Exercise A3: Downloading Horizon 7 Installers

• Exercise A4: Installing Connection Server

• Exercise A5: Installing Composer

Exercise A1: Verifying Minimum RequirementsBefore you begin the installation exercises in this guide, make sure you have the following infrastructure components installed and configured and that your environment meets minimum requirements for hardware, server, and installation.

1. Verify that your environment meets the following infrastructure requirements:

• VMware vSphere and vCenter Server – To take advantage of the new features of this release, you must first install and configure VMware vSphere and VMware vCenter Server in your environment. Next, you install the Connection Server, which functions as the management component of View. For up-to-date compatibility information, see the VMware Product Interoperability Matrices.

– VMware vSphere 6 .0 Update 1 or later, including VMware vCenter Server 6 .0 Update 1 or later (for more information, see VMware vSphere 6 Documentation)

– VMware ESXi™ host or hosts configured in the vCenter Server instance

• Active Directory domain controller – An authentication infrastructure that includes Active Directory, DNS, and DHCP is required. View integrates with your Microsoft Active Directory, a Windows service for authenticating and authorizing users and computers, applying and enforcing security policies, and installing and updating software. The Connection Server joins to Active Directory and sets up a lightweight directory service instance for the storage of View configuration information.

• SSL certificate – By default, View includes a self-signed certificate that can be used for testing purposes. For a production environment, we recommend that you replace the self-signed certificate with an approved certificate signed by a certificate authority, a trusted entity that issues digital certificates verifying another digital entity’s identity on the Internet.

• SQL database – You can download and install Microsoft SQL Server Management Studio Express with Advanced Services to get both database and management tools, or use an existing SQL server in your environment. For more information, see Database Requirements for View Composer and the Events Database.

• License – You must have a valid product license key to use View. Obtain and make note of the license serial number.

2. Verify that your environment meets the networking requirements. At least 1 Gbps network connectivity between all the required Horizon 7 components and desktops is recommended.

http://www.vmware.com/products/vsphere.html

http://www.vmware.com/products/vcenter-server.html

http://www.vmware.com/resources/compatibility/sim/interop_matrix.php

https://www.microsoft.com/en-ie/download/details.aspx?id=42299

https://docs.vmware.com/en/VMware-Horizon-7/7.2/com.vmware.horizon-view.installation.doc/GUID-5B2266B8-EA3C-4F49-BABB-2D0B91DE6C1D.html#GUID-5B2266B8-EA3C-4F49-BABB-2D0B91DE6C1

https://docs.vmware.com/en/VMware-Horizon-7/7.2/com.vmware.horizon-view.installation.doc/GUID-5B2266B8-EA3C-4F49-BABB-2D0B91DE6C1D.html#GUID-5B2266B8-EA3C-4F49-BABB-2D0B91DE6C1



3. Verify that your environment meets the following recommended hardware minimums for the View components:

COMPONENT RECOMMENDED VIRTUAL CPUS RECOMMENDED RAM

Connection Server 4 vCPUs 12 GB

Composer 4 vCPUs 12 GB

Table A1-1: Hardware Requirements

4. Verify that your operating system meets the following requirements for a View deployment:

OPERATING SYSTEM ARCHITECTURE EDITION MINIMUM DISK SPACE

Windows Server 2008 R2 SP1 64-bit Standard and Enterprise 40 GB

Windows Server 2012 R2 64-bit Standard 40 GB

Windows Server 2016 64-bit Standard 40 GB

Table A1-2: Operating System Requirements

5. Verify that your environment meets the minimum requirements for the Horizon Administrator console. The Horizon Administrator console is a web-based application that installs when you install Connection Server. You can use it for configuration, for many of the explorations in the guides in this series, and for analytical activities.

COMPONENT REQUIREMENT

Browser Launch the Horizon Administrator console from a supported browser:• Internet Explorer 10 or 11

• Firefox

• Chrome

• Safari 6 or later

• Microsoft Edge (Windows 10)

Display Adobe Flash Player 10.1 or later is required to use the Horizon Administrator console with your web browser.

Certificates The Horizon Administrator console host must trust the root and intermediate certificates of the Connection Server host.

Table A1-3: Horizon Administrator Console Requirements

For more information, see VMware Horizon 7 Documentation.

When you finish verifying that you have the infrastructure components needed and your environment meets all hardware, server, and installation requirements, proceed to the next exercise to gather information needed during installation.




Exercise A2: Gathering Installation DataExpedite the installation process by gathering the information needed during installation ahead of time.

1. Gather the following information about your VMware vCenter Server.

CONNECTION SERVER CONFIGURATION INFORMATION

vCenter Server host name FQDN

vCenter Server port number (Default: 443)

vCenter Server administrator user name

vCenter Server administrator password

Table A2-1: Information About the VMware vCenter Host

2. Gather the following information required when creating virtual machines (VMs) for Connection Server and Composer.

CONNECTION SERVER CONFIGURATION INFORMATION

Static IP address configured

Host name of a virtual machine joined to the domain

Virtual machine host name FQDN in DNS with reverse lookup records defined

Windows Firewall turned on

COMPOSER CONFIGURATION INFORMATION

Static IP address configured

Host name of a virtual machine joined to the domain

Virtual machine host name FQDN in DNS with reverse lookup records defined

Windows Firewall turned on (optional)

ODBC driver installed for your database

Table A2-2: Information About the VMs for Connection Server and Composer



3. Gather the following Active Directory information required during installation.

ACTIVE DIRECTORY DATA FOR VIEW CONFIGURATION INFORMATION

Server name of an Active Directory domain controller in the environment

FQDN of an Active Directory domain controller in the environment

Active Directory user name with privileges to join computers to the domain, create and delete computer objects, and write properties in the domain

Table A2-3: Information About the Active Directory

4. Gather the following SQL database information required when installing Composer.

SQL SERVER DATA FOR COMPOSER CONFIGURATION INFORMATION

IP address for the host of the SQL database

FQDN for the database host

Database instance name

Name of the database for Composer data

Login credentials with database owner rights on the database

Table A2-4: Information About the Database

5. Make sure that the Microsoft .NET Framework has been upgraded to version 4.6.1 to avoid installation failure. The Microsoft .NET Framework enables you to run applications written with the .NET Framework, such as desktop applications. The .NET (also known as a Redistributable Package or the Runtime Environment) is included with most Windows computers. For more information, see Microsoft .NET Framework 4.6.1 RC Web Installer for Windows.

When you finish collecting the information to be used during installation, proceed to the next exercise to download the installer files.

https://support.microsoft.com/en-us/help/3088520/microsoft-.net-framework-4.6.1-rc-web-installer-for-windows



Exercise A3: Downloading Horizon 7 InstallersAfter gathering the information needed during installation, download the installation files, also called installers.

1. On any web browser, navigate to the VMware Horizon 7 Product Evaluation Center, and log in. If you do not already have an account, you can create one here.

Figure A3-1: Log In

2. In the Product Evaluation Center, scroll down to the License Information, and make note of the Horizon 7 Enterprise license.

Figure A3-2: Make Note of Nicense Information

https://my.vmware.com/en/web/vmware/evalcenter?p=horizon-7



3. Scroll down to Download Packages, download the following packages, and note where you store them for reference during the installation process:

• Horizon Connection Server (64-bit)

• Horizon Agent (64-bit)

• Horizon Composer

Figure A3-3: Download Installer Packages

4. Navigate to Download VMware Horizon Clients and download VMware Horizon Client™ (64-bit). Horizon Agent and Horizon Client are required for exercises in other guides (see All Guides).

Figure A3-4: Download Horizon Client

When you finish downloading the installation files, proceed to the next exercise to start the installation process.

http://www.vmware.com/go/ViewClients

T E C H N I C A L W H I T E PA P E R | 1 0


Exercise A4: Installing Connection ServerAfter downloading the installation files, start the installation process by installing the Connection Server on a virtual machine.

The Connection Server acts as a broker for client connections by authenticating and directing incoming user desktop requests. When you install the Connection Server, the Horizon Administrator console is installed as well. The Horizon Administrator console is the web-based interface for the management, provisioning, and deployment of virtual desktops. As an administrator, you can centrally manage thousands of virtual desktops from a single Horizon Administrator console.

1. Verify that the virtual machine targeted for the Connection Server installation meets the requirements listed in Verifying Minimum Installation Requirements, and log in.

Note: It is recommended that you run a Windows update before installation.

2. Navigate to the Connection Server installation file that you downloaded in Downloading Horizon 7 Installers, run the installer, and when the welcome page opens, click Next.

Figure A4-1: VMware Horizon 7 Install Wizard Welcome Page



3. On the License Agreement page, accept the end-user license agreement, and click Next.

Figure A4-2: Accept the End-User License Agreement

4. On the Destination Folder page, accept the default location, and click Next.

Figure A4-3: Accept the Default Location



5. On the Installation Options page, select the Horizon 7 Standard Server install option, accept the Install HTML Access option to allow users to connect via web browsers, accept the default IPv4 protocol option, and click Next.

Figure A4-4: Accept Installation Default Options

6. On the Data Recovery page, enter the password and verification, as well as a reminder for your own future reference, and click Next.

Figure A4-5: Establish the Data Recovery Password and Reminder



7. On the Firewall Configuration page, accept the default to configure the firewall automatically, and click Next.

Figure A4-6: Configure the Windows Firewall Automatically

8. On the Initial Horizon 7 Administrators page, enter the domain user or domain group to authorize access to the Horizon Administrator console, and click Next.

Figure A4-7: Authorize a Domain User



9. On the User Experience Improvement Program page, you can deselect the Participate anonymously in the user experience improvement program option to opt out of the program, and click Next.

Figure A4-8: Choose Whether or Not to Provide Anonymous Usage Data

10. On the Ready to Install the Program page, click Install.

Figure A4-9: Initiate the Installation Process



11. On the Installer Completed page, click Finish.

Figure A4-10: Finish the Installation Process

12. On your desktop, click the Horizon 7 Administrator icon to launch it.

Figure A4-11: Locate the Horizon Administrator Icon



13. Log in to the Horizon Administrator console.

Figure A4-12: Horizon Administrator Console Login Page

Note: It is recommended that you check for new patches and run Windows Update if new patches are found, in case the installation process enabled any operating system features for the first time.

For more information, see Install View Connection Server with a New Configuration in View Installation.

When you finish installing the Connection Server, proceed to the next exercise to install the Composer.

Exercise A5: Installing ComposerHorizon 7 uses Composer, also called View Composer, to create and deploy linked-clone desktops in vCenter Server. Linked-clone desktops can optimize your use of storage space and facilitate updates. (Instant-clone desktops, another feature, improve and accelerate the process of cloning virtual desktops, and use even less storage and less expense because the desktop is deleted when the user logs out. Both instant-clone and linked-clone desktops are covered in other white papers. For more information, see All Guides.)

Note: Do not install Composer on the same virtual or physical machine as Connection Server, Horizon Agent, Horizon Client, or other Horizon 7 software components. For this exercise, Composer is installed on a standalone machine.

1. Verify the following for the Composer installation:

• Target virtual machine meets minimum requirements for installation.

• Appropriate native SQL Server database is installed.

2. Log in to the target virtual machine, navigate to the Composer installer file, and launch it.

Figure A5-1: Run the Composer Installer File




3. When the welcome page of the Composer installation wizard appears, click Next.

Figure A5-2: Welcome Page

4. On the License Agreement page, review and accept the end-user license agreement, and click Next.

Figure A5-3: Accept the End-User License Agreement



5. On the Destination Folder page, accept the default location, and click Next.

Figure A5-4: Accept the Default Destination Folder

6. On the ODBC Data Source Administrator page, under the System DSN tab, click Add.

Figure A5-5: Add an ODBC System Data Source



7. On the Create New Data Source page, select the driver for the Microsoft SQL Server database provided with vCenter Server, and click Finish.

Figure A5-6: Select the SQL Server Database Driver

8. On the Create a New Data Source to SQL Server page, enter the following information, and click Next.• Name – Unique name that refers to the data source

• Description – Optional

• Server – Identify the SQL Server

Figure A5-7: Enter Data Required to Create a Data Source



9. On the Create a New Data Source to SQL Server page, select With SQL Server authentication using a login ID and password entered by the user, enter the SQL Server login ID and password, and click Next.

Figure A5-8: Enter Login ID and Password

10. On the Create a New Data Source to SQL Server page, select the Change the default database to check box, and from the drop-down menu, select the database that you created for Composer data, and click Next.

Figure A5-9: Change the Default Database



11. Accept the defaults, and click Finish.

Figure A5-10: Finish Creating a New Data Source

12. On the ODBC Microsoft SQL Server Setup page, click Test Data Source to verify the connection to the database.

Figure A5-11: Test the Connection to the New Data Source



13. Verify that the test completed successfully, and click OK to continue.

Figure A5-12: Verify That the Test Completed Successfully

Note: If your connection test was unsuccessful, click OK, and in the next window, click Cancel to go back and change the parameters in the previous windows. Retest until the test result is successful.



14. Click OK to add the System Data Source Name (DSN) to your System Data Sources list.

Figure A5-13: Add the System DSN to the System Data Sources List



15. On the ODBC Data Source Administrator page, in the System DNS tab, select the new database, and click OK.

Figure A5-14: Select the New Database

16. On the Database Information page, click ODBC DSN Setup to establish a new DSN to define the connection between Composer and your database, enter the user name and password, and click Next.

Figure A5-15: Enter Database Information



17. On the VMware Horizon 7 Composer Port Settings page, accept the default SOAP port for Composer communication, and click Next.

Figure A5-16: Accept Default SOAP Port

18. On the Ready to Install page, verify the destination folder, and click Install.

Figure A5-17: Start the Installation Process



19. On the Installer Completed page, click Finish.

Figure A5-18: Finish the Installation Process

20. To finalize the installation, click Yes to reboot the virtual machine.

Figure A5-19: Restart the System

For more information, see Install the View Composer Service in View Installation.

When you finish installing the Composer, you have completed the basic installation of the View component. Proceed to the next section to perform the initial configuration processes.




Section B: Initial ConfigurationThis section provides exercises to help you evaluate the initial configuration of your View instance. The exercises are sequential and build upon one another, so complete each exercise before moving on to the next.

To finish setting up a working View environment, complete the following initial configuration exercises:

• Exercise B1: Adding the Product License Key

• Exercise B2: Connecting to the vCenter Server

• Exercise B3: Enabling Windows Server Desktops

• Exercise B4: Creating an Event Database

Exercise B1: Adding the Product License KeyThe first step of initial configuration after installing the Connection Server is to add a product license key. The first time you log in to the Connection Server, the Horizon Administrator opens to the Product Licensing and Usage window.

1. In Horizon Administrator under View Configuration > Product Licensing and Usage, click Edit License.

Figure B1-1: Edit the License

2. In the Edit License window, enter the 25-character serial number of the product license key, and click OK.

Figure B1-2: Provide the License Serial Number



3. In the Horizon Administrator console, verify that the license expiration date has not already passed, and that the licenses for Desktop, Application Remoting, Composer, and Instant Clone are all enabled.

Figure B1-3: Verify Successful License Edit

For more information, see Install the Product License Key in View Installation.

After installing the product license key, proceed to the next exercise to configure the vCenter Server connection.

Exercise B2: Connecting to the vCenter ServerConfigure View to connect to a vCenter Server instance in your View deployment. The vCenter Server creates and manages the virtual machines used in View desktop pools. View uses a secure channel (SSL) to connect to the vCenter Server instance.

1. Verify that your environment includes the following prerequisites:

• Connection Server license (see Adding the Product License Key)

• vCenter Server account with permissions to create and delete computer objects and write properties in the domain

• SSL server certificate (for this exercise, the default certificate is used)

• Connection Server trusts the root CA certificate for the server certificate installed on vCenter Server

• vCenter Server that contains ESXi hosts

2. On the Horizon Administrator console under View Configuration, click Servers, and in the vCenter Server pane, click Add.

Figure B2-1: Add a vCenter Server




3. On the Add vCenter Server page under VC Information, enter the FQDN or IP address of the vCenter Server instance, and the user name and password for the administrator on the vCenter Server. Accept the default values for the port and other advanced settings, and click Next.

Figure B2-2: Enter vCenter Server Settings

4. If an Invalid Certificate Detected prompt is displayed, click View Certificate.

Figure B2-3: View the Invalid Certificate



5. Accept the certificate.

Figure B2-4: Accept the Certificate

6. On the Add vCenter Server page under View Composer, select Standalone View Composer Server, configure the Composer Settings, and click Next.

Figure B2-5: Enter the Composer Settings

• Server Address – Enter the required server address, either the FQDN or IP address, of your View Composer virtual machine.

• User name – Enter the user name of your vCenter Server account.

• Password – Enter the password of your vCenter Server account.

• Port – Modify the port value only if you modified it during the View Composer installation. Otherwise, use the default.



7. If an Invalid Certificate Detected prompt is displayed, click View Certificate.

Figure B2-6: View the Invalid Certificate

8. On the Certificate Information page, review the thumbprint of the default self-signed certificate that was generated during installation, and click Accept.

Figure B2-7: Accept the Certificate

9. On the Add vCenter Server page under View Composer Domains, click View Composer Domains, and in the View Composer Domains pane on the right, click Add.

Figure B2-8: Add the Composer Domain



10. On the Add Domain page, enter the domain name, user name, and password, and click OK.

Figure B2-9: Enter the Domain Data

Note: The user name and password are the credentials for your domain account. This account must have permission to create computer objects, delete computer objects, and write properties in the domain or in the OUs (organizational units) that you select when creating desktops in later exercises (see All Guides).

11. Under View Composer Domains, verify the information and click Next.

Figure B2-10: Verify the Domain Data



12. Under Storage, accept the defaults for Storage and click Next.

Figure B2-11: Accept Storage Setting Defaults

13. Under Ready to Complete, review the vCenter Server information, and click Finish.

Figure B2-12: Finish the Process

14. On the vCenter Servers tab, verify the vCenter Server that you just connected to your View environment.

Figure B2-13: Verify That vCenter Server Is Connected

When you have finished configuring your View environment to connect to the vCenter Server, proceed to the next exercise to enable Windows Server desktops.



Exercise B3: Enabling Windows Server Desktops You can enable Windows Server to use as a master image for creating desktop pools. This enables you to use Windows Server 2012 R2 VMs as single-session View desktops, as well as RDSH servers. Desktop pools provide the advantages of centralized desktop management, such as applying settings or applications to all desktops in a pool. You can also automate the process of generating virtual desktops as needed and set parameters so you always have enough remote desktops for use but never overreach available resources.

1. In Horizon Administrator, under View Configuration on the left, select Global Settings, and in the General pane, click Edit.

Figure B3-1: Access Global Settings



2. In the General Settings page, select the check box Enable Windows Server desktops, and click OK.

Figure B3-2: Enable Windows Server Desktops

After you finish enabling the Windows Server VM to use as a master image for creating desktop pools, proceed to the next exercise to create an event database for event logging.



Exercise B4: Creating an Event DatabaseCreate an event database to send View events to a SQL Server, making the event data available to analytics software. Although the event database is not required for every View environment, the event database is required for some of the exercises in All Guides, such as storing data when you use the Composer to deploy linked-clone desktop pools. The Composer does not contain a database by default, so you install a SQL Server in this exercise, and add the event database to it. This database stores vCenter Server and Active Directory connections, linked-clone desktop data, and replicas created by Composer.

1. Create a SQL Server database (for more information, see Microsoft SQL Server documentation).

2. To use vCenter Server to launch the SQL Server Configuration Manager, right-click the SQL Server instance, and select Open Console.

Figure B4-1: Launch the SQL Server Configuration Manager

3. In the SQL Server Configuration Manager, expand SQL Server Network Configuration, and select Protocols for <server_name>.

• In the list of protocols, right-click TCP/IP, and select Properties.

• Set the Enabled property to Yes.

• For the IPAll IP Address setting, accept the default port 1433, or assign a port. (For more information, see the Microsoft SQL Server documentation.)




4. In Horizon Administrator under View Configuration, select Event Configuration, click Edit, and in the Edit Event Database page, enter the following information, and click OK.

Figure B4-2: Configure the VMware Horizon Administrator Event Database

• Database server – Enter the DNS name or IP address.

• Database type – Accept the default Microsoft SQL Server.

• Port – Accept the default port number (1433) used to access the database server.

• Database name – Enter the event database name created on the database server.

• User name – Enter the user name of the user you created for this database using SQL Server Authentication.

• Password – Enter the password and confirmation.

• Table prefix – Enter a prefix for the tables in the event database, such as VE, to enable the database to be shared among View installations.

5. On the Event Configuration page, you can see the configuration details.

Figure B4-3: View the Event Database Details



6. Select Monitoring > Events to verify that the connection to the event database is successful.

Figure B4-4: Monitor Events

When you finish setting up the event database, you have completed all of the exercises in this guide. Your Horizon 7 instance is completely installed and initial configuration is complete. You can proceed to explore the features and capabilities of the View component of Horizon 7 with the help of the All Guides.

SummaryThis white paper is one of a series of guides that explore the View component of VMware Horizon 7. This guide provides an overview of the recommended requirements for setting up an evaluation deployment, and exercises to walk you through the installation and configuration processes. For a more detailed overview of View in Horizon 7 and capabilities, and for additional exercises to explore those capabilities—such as instant clones, smart policies, and more—see All Guides. For information beyond the considerations of this white paper, see VMware Horizon 7 Documentation.

All GuidesYou can explore many key features and capabilities in the Reviewer’s Guide series for View in VMware Horizon 7:

• Overview

• Installation and Configuration

• Preparing Virtual Machines for Desktop Pools

• Instant Clones

• Desktop Pools

• Publishing Applications with VMware Horizon 7

• Smart Policies

• Provisioning Users


https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/vmware-view-horizon-7-reviewers-guide.pdf

https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/vmware-view-horizon-7-reviewers-guide-install-configure.pdf

https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/vmware-view-horizon-7-reviewers-guide-preparing-virtual-machines-desktop-pools.pdf

https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/vmware-view-horizon-7-reviewers-guide-instant-clones.pdf

https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/vmware-view-horizon-7-reviewers-guide-desktop-pools.pdf

https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/vmware-horizon-7-application-publishing.pdf

https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/vmware-view-horizon-7-reviewers-guide-smart-policies.pdf

https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/vmware-view-horizon-7-reviewers-guide-provisioning-users.pdf



Additional ResourcesYou can find out more about Horizon 7 from the following resources:

• VMware Horizon 7 (including View component)

• VMware Horizon 7 Documentation

• VMware Horizon 7.1 Is GA! What’s New – Part 1 (VMware blog post)

• VMware Horizon 7.1 Is GA! What’s New – Part 2 (VMware blog post)

• VMware vSphere

• VMware vCenter Server

• Microsoft SQL Server Management Studio Express

• Microsoft .NET Framework 4.6.1 RC Web Installer for Windows

• VMware Consulting Professional Services Organization (PSO)

• VMware Product Interoperability Matrices

• Self-Help Resources from VMware

• VMware Horizon Support Center

• VMware Technical white papers

• Try VMware Horizon for Free

• VMware Product Evaluation

• VMware Knowledge Base

• VMware Product Guide

About the AuthorsThis white paper was written by Cindy Heyer Carroll, End-User-Computing Technical Marketing Technical Writer, VMware, with much appreciation for assistance from

• Donal Geary, End-User-Computing Technical Marketing Reference Architect Engineer, VMware

• Graeme Gordon, Senior End-User-Computing Architect, Desktop Technical Marketing, VMware

• Marilyn Basanta, Group Manager, Global Platform Engineering & Analytics, VMware

FeedbackThe purpose of this white paper is to assist you. Your feedback is valuable. To comment on this paper, contact VMware End-User-Computing Technical Marketing at [email protected].

http://www.vmware.com/products/horizon.html


https://blogs.vmware.com/euc/2017/03/vmware-horizon-7-1-whats-new.html

https://blogs.vmware.com/euc/2017/03/vmware-horizon-7-1-whats-new-part-2.html

http://www.vmware.com/products/vsphere.html

http://www.vmware.com/products/vcenter-server.html


https://support.microsoft.com/en-us/help/3088520/microsoft-.net-framework-4.6.1-rc-web-installer-for-windows

http://www.vmware.com/professional-services.html

http://www.vmware.com/resources/compatibility/sim/interop_matrix.php

https://www.vmware.com/support/support-resources.html

https://www.vmware.com/support/horizon-view.html

http://www.vmware.com/techpapers.html#/?client=tech_paper&num=25&filter=0&site

http://www.vmware.com/products/horizon/horizon-hol.html

http://www.vmware.com/try-vmware.html

https://kb.vmware.com/selfservice/microsites/microsite.do

http://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/product/vmware-product-guide.pdf

mailto:euc_tech_content_feedback%40vmware.com?subject=

VMware, Inc. 3401 Hillview Avenue Palo Alto CA 94304 USA Tel 877-486-9273 Fax 650-427-5001 www .vmware .comCopyright © 2017 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents listed at http://www.vmware.com/go/patents. VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies. Item No: 5125-VMW-WP-HORIZON72-INSTALLATION-CONFIGURATION-USLET-20170807 8/17

Documents

Reviewer's Guide for View in VMware Horizon 7: … WHITE PAPER | 2 REVIEWER’S GUIDE FOR VIEW IN VMWARE HORIZON 7: INSTALLATION AND CONFIGURATION Table of Contents