VMware Horizon 7.0 Step by Step : Creating an Application Pool

Introduction

Application Pools in VMware Horizon pool allows  administrator to provides access to  applications hosted on servers in a data center instead  of users personal computers or  devices.  Using  application pools you can deliver a single application hosted on a farm of RDS hosts. Once deployed,  entitled users can access the application from anywhere  on the  network. Application deployed  using Application pools supports  both PCoIP and VMware Blast  display protocols.

Before application pool deployment,  application servers where application will be hosted  is required to be Remote Desktop  Session Host Role installed and applications are installed on the  application server.

Creating Application  Pool  Step  by Step

Prerequisites

  1. Set up RDS hosts.
  2. Create a farm that contains the RDS hosts. See Creating Farms.

Post  creating Farm containing RDS Host,  Click on Application Pools under Catalog. Click on Add to create a new Application pool.

2

Select  the  RDS  farm having  the RDS host  where applications are installed.  You will see the list of hosted applications in RDS farm. Select  the applications you want to be  accessible to  the users. Click Next to  proceed.

3

Click on Finish. Choose “Entitle  users after  this wizard finishes” if  you want to  entitle  applications to  the users immediately after Farm creation.  You can entitle  the applications  at later stage as well.   4 5

Users can see the entitled  applications in the list post  connecting  using VMware Horizon Client.

6 7Summary

Application pool makes the application deployment  process very easy. Instead of deploying applications individually on each user desktops,  you can now deploy the application  only once  and make  accessible to  the  many users. I hope this will be informative for you. Thanks for Reading. Do share it on social media if you find it worth sharing. Happy Learning :-).

VMware Horizon 7.0 Step by Step | Creating SQL Database for Events Database

Introduction

VMware Horizon records events like administrator actions, end-user actions, system failures and errors etc. You can either leverage Microsoft SQL or Oracle Database for recording events. Before proceeding to configure VMware Horizon to log events, In this post we will be covering the steps to create a Microsoft SQL database. You do not need to create an ODBC data source for this database.

Supported Database

Below is a list of supported Databases for storing Events.

 

Database

Service Packs/Releases

Editions

Microsoft SQL Server 2014 (32- and 64-bit)

No SP, SP1

Standard /Enterprise

Microsoft SQL Server 2012 (32- and 64-bit)

SP2

Express / Standard / Enterprise

Microsoft SQL Server 2008 R2 (32- and 64-bit)

SP2, SP3

Express / Standard / Enterprise / Datacenter

Oracle 12c

Release 1 (any release up to 12.1.0.2)

Standard One / Standard / Enterprise

Step by Step : Creating Microsoft SQL Database

Connect to Microsoft SQL Instance using Microsoft SQL Server Management Studio.

1 2

Right click on Databases and click on Create a New Database.3

Type in the Database Name and click on OK.4 5

Next we need to create a new user and map the new database to the new account. Under Security, right click on Login and click on New Login.6

Give the appropriate Login Name to the new Login account. Choose SQL Server Authentication and configure password as per organization password policy.

7

Click on User Mapping and select the new database created earlier. Choose db_owner as the database role for the new database and click OK.8

Database Error while configuring Event viewer database in VMware Horizon Admin Console.

You may get below error message while configuring Event Viewer database in VMware Horizon Admin Console. The reason is because the TCP/IP ports are not configured properly.

11

To correct the above error, connect to Microsoft SQL Server using Microsoft SQL Configuration manager.

10 Under SQL Server Configuration Manager, navigate to SQL Server Configuration Manager –> SQL Server Network Configuration –> Protocols for VIM_SQLEXP –> TCP/IP:

Ensure that the TCP Dynamic Ports and TCP Port values are cleared with no values for:

  • IP1
  • IP2
  • IP3
  • IP4
  • IP5
  • IP6

Change the TCP Port to 1433 if not configured.

12 13

Restart the SQL Server service to get the changes into effect. Once SQL server service get restarted, VMware Horizon Event database can be configured.

Conclusion

In this post I demonstrated the process to create and configure a new database for storing VMware Horizon Events. In next blog I will cover the steps to configure database for VMware Horizon Events via VMware Horizon admin console.

I hope this will be informative for you. Thanks for visiting the blog. Happy learning :-).

 

VMware Horizon 7.0 Step by Step | Creating RDS Desktop Pool

Introduction

In earlier releases of VMware View, RDS Desktop Pool was known as Microsoft Terminal Services pool. In comparison to desktop provisioned in an automated desktop pool where desktops are based on a virtual or physical machine, RDS desktops are based on session to an RDS host. Each RDS host is a windows server that can host multiple RDS Desktops. An RDS Desktop pool is always associated with a farm, VMware View provides load balancing of the RDS Host in a farm by directing connection requests to the RDS host that has the least number of active sessions. An RDS desktop supports the RDP, PCoIP, and VMware Blast display protocols. You can also configure HTML access in case needed.

Prerequisite

  1. Automated or Manual Farm should already be created. (If not already created, you will be asked to create Farm during Pool creation process)
  2. RDS host status should be in Available.

Step by Step Creating RDS Host Pool

Login to VMware Horizon Admin Console. Go to Catalog –> Desktop Pools and Click on Add.

1

Choose RDS Desktop Pool from the list and Click on Next.2Provide appropriate Pool ID and the Display Name of the pool.

3

Configure the Desktop Pool Settings as per organization requirements. In Lab, I kept the settings default. Click Next to proceed further.4Choose the Farm from the list and click Next.

5

Review the configuration and click on Finish.6

Once created, new RDS pool will be available for entitled users.7

Entitle the users to the pool. 8Once entitled user will be able to login to RDS pool. 9

Conclusion

In this post, I covered the process of creating Remote Desktop Service Desktop pool using exiting Farm. A RDS pool can have either Automated or Manual Form as an backend. You cannot configure Automated and Manual Farms together as an backend to a single pool.

I hope this will be informative for you. Thanks for visiting. Happy Learning 🙂

 

VMware Horizon 7.0 Step by Step | Introduction to VMware Horizon Farms

Introduction to VMware Horizon Farm

VMware Horizon Farms are collection of host providing Remote Desktop Services. A VMware Horizon Farms can have a variable number of RDS hosts providing a common set of applications or Desktops. Before deploying Application or RDS Pool you must specify a farm. Farms also simplifies the management of RDS host, RDS desktops and applications. An administrator can have have a maximum of 200 farms in a VMware Horizon pod and each Horizon Pod can have maximum of 200 RDS Hosts. Farms provides a conveniences of Load Balancing, Redundancy &  Scalability to the administrator

Type of Farms

VMware Horizon provides flexibility to administrators to create Manual or Automated farms depending on enterprise requirements.

Manual Farm

A Manual Farm can have Physical or Virtual RDS host  that already exist in the infrastructure. You need to manually add these RDS hosts at the time of creating a Farm.

2

Automated Farm

An Automated Farm consist of RDS hosts that are linked clone of Virtual machines in vCenter Server. Leveraging View Composer, new RDS hosts are cloned from a single parent virtual machine and are linked to the parent virtual machine reducing the amount of storage requirement. Automated farms support the View Composer recompose operation but do not support the refresh or re-balance operation. You can recompose an automated farm but not a subset of the RDS hosts in the farm

1

So in this post we just covered the Introduction to VMware Horizon Farm, I will be covering the deployment of VMware Horizon Farms ( Automated and Manual ) in upcoming post. Hope this is informative for you. Happy learning :-).

 

VMware Horizon 7.0 Step by Step | Creating an Automated Desktop Pool with Linked Clones

Introduction

Post successful installation of VMware View Connection broker and VMware View Composer Servers we are good for creating Desktops Pools for the end users. Desktop pool is a group of virtual desktops that leverage identically configured virtual machine. Administrators. Apart from centralize administration, administrators can deploy identical applications to specific group of users.

Understanding the purpose (user case, storage infrastructure, application requirement) , using VMware Horizon administrators can create different types of desktop pools.

Types of Desktop Pool

  • Full Clone Pools – Each virtual desktop is a full virtual machine cloned from a template in vCenter.  The virtual machines are managed by View Connection Servers.
  • Linked Clone Pools – Each virtual desktop is based on a snapshot and shares its disk with the parent virtual machine.  Changes to the linked clone are written to a delta disk.  The virtual machines are managed by View Composer.
  • Manual Pools – The machines that make up the manual pool consist of virtual and/or physical machines that have had the View Agent installed.  These machines are not managed by View.
  • Remote Desktop Pool – The machines that make up these pools are Windows Servers with the Remote Desktop Services Role installed.

Steps to Create an Automated Desktop Pool with Linked Clones

Login to VMware Horizon Admin Console. Go to Catalog –> Desktop Pools. Click on Add to create new pool.

1

Select Automated Desktop Pool and click on Next.2

Select appropriate type of User Assignment. Click Next to proceed.

  • Dedicated : User gets the same desktop at each login once assigned. Desktops can be assigned automatically on first logon.
  • Floating : Desktop will be returned to Desktop pool once user logged off from the desktop and marked available for another users.

3

Choose View Composer Linked Clone. Composer server should be up and running and configured. 4

Choose the appropriate Desktop Pool Identification ID and Display Name as per organization policy. Click Next to proceed5

Configure Desktop Pool Setting and Click Next. 6

Provide the appropriate naming pattern for the new desktops in the pool. 7

Temporary and Page files are classified as disposable files. If you choose them to be redirected to Non – Persistent Disk , the disk will be deleted wheneve the VM is shut down. Choose the option as per your organization requirements.

8

Choose if you want to choose VMware Virtual SAN. Click Next to proceed. 9

Choose the parent virtual machine & snapshot which you want to use as gold image for desktops in the pool. Configure Virtual Machine location in vSphere Datacenter, Cluster and Resource pool to be used. 10Choose Storage Accelerator, Reclaim VM disk space and Black out times as per the user case requirements.

11Choose the Domain and the AD Container you want to host pool desktops.  12

Review the configuration and Click Finish to deploy new Desktops. 13

14

Deployment will take some time. Wait till the till the time Status changed to Available / Provisioned. 15 16 17

Assigning Virtual Desktops to Users / Groups

Once desktops get successfully provisioned, Users / Groups should be entitled new virtual desktops. Click on Add Entitlement and add users / group to the list of entitled users.18

Connecting Virtual Desktops using VMware View Horizon Client

Post entitlement, entitled users can connect to entitled virtual desktops using VMware Horizon Client or Web Access. 19 20 21 22 23

This concludes the deployment of new Automated Virtual Desktops using Linked clone. I hope this will be informative for you. Thanks for Reading!!. Be social and share it in social media, if you feel worth sharing it. Happy Learning 🙂

 

VMware Horizon 7 : Backing Up and Restoring View Configuration Data

VMware recommends that all three components be backed up at the same time to avoid data discrepancies.

  • View Connection Server
  • View Composer Data
  • vCenter Server Database

You can back up your View and View Composer configuration data by scheduling or running manual backups using View Admin Console. You can use the backup and restore features to preserve and migrate View configuration data in new instance. Once you are done with initial configuration of View a regular backup of View and View Composer Configuration data can be scheduled. When backup is performed using VMware View Admin Console, View backs up the View LDAP configuration data and View Composer database.  Once backed up both set of backup files will be stored in the same location.

You can either perform manual backup, schedule backup or manually export LDAP data using vdmexport utility. The vdmexport utility can export View LDAP data as encrypted LDIF data, plain text, or plain text with passwords and other sensitive data removed.

Backup up VMware View Configuration and Composer Database manually.

1

2

3

4

Scheduling Backup for VMware View Configuration and Composer Database

Screenshot-4

Export Configuration Data from View Connection Server

Locate the vdmexport.exe command executable file located in C:\Program Files\VMware\VMware View\Server\tools\bin. Open Command prompt execute

  • vdmexport -f configuration_data.LDF
  • vdmexport -f configuration_data.LDF -v ( export data in plain text format )
  • vdmexport -f configuration_data.LDF -c ( export data in plain text format with passwords and sensitive data removed )

Restoring VMware View Configuration and Composer Database

A manual restore of VMware View Configuration and Composer database can be performed using VMware View Connection Server LDAP configuration files and View Composer database files that were backed up by View. You can restore VMware View Configuration and Composer database using  vdmimport & SviConfig utility. LDIF Configuration file exported via VMware View Admin console will be in encrypted. You must decrypt the LDIF file before import it. If you have exported the LDIF file in plain text using vdmexport utility. It is not required to decrypt the LDIF configuration file before importing it.

Procedure to import LDIF Configuration 

  • Stop all instance of Connection Server
  • Stop all instance of Security Server
  • Uninstall all instance of Connection Server. Uninstall both VMware Horizon View Connection Server and AD LDS Instance VMwareVDMDS.
  • Install one instance of View Connection Server.
  • Stop the View Connection Server instance by stopping the Windows service.
  • Decrypt the encrypted LDIF file using

vdmimport -d -p recovery_password -f encrypted_configuration_file.LDF > decrypted_configuration_file.LDF

  • Import the configuration file using vdmimport -f decrypted_configuration_file.LDF.
  • Uninstall View Connection Server. Uninstall only the package VMware Horizon View Connection Server.
  • Reinstall View Connection Server.
  • Verify the configuration
  • Re-install the replica servers.
  • Start the security server instances.

If you find security server in inconsistent state, reinstall the security server.

Restoring VMware Composer Database:

  • Stop the VMware Horizon View Composer service on VMware Composer Server.
  • Open Command prompt go to directory C:\Program Files(x86)\VMware\VMware View Composer\
  • Execute the command

sviconfig -operation=restoredata -DsnName=target_database_source_name_(DSN) -Username=database_administrator_username -Password=database_administrator_password -BackupFilePath=path_to_View_Composer_backup_file

  • Start the VMware Horizon View Composer service.

This concludes the process of performing manual and scheduled backup via VMware View Admin console. Thanks for Reading!!. Be Social and share it in Social media, if you feel worth sharing it.