Book Image

VMware Horizon Workspace Essentials

By : Joel Lindberg, Peter Bjork, Peter von Oven
Book Image

VMware Horizon Workspace Essentials

By: Joel Lindberg, Peter Bjork, Peter von Oven

Overview of this book

Table of Contents (16 chapters)
VMware Horizon Workspace Essentials
About the Authors
About the Reviewers


In the last few years, the market has exploded with new devices, applications, and services that have been focused on being easy to access and consumable with little technical knowledge. It's pretty much now become the norm to visit an online store, choose an application, and start using it immediately.

The traditional approach has been to deploy Windows on physical machines and use some form of distribution system for deploying applications and securing data. Users would be working from 9 to 5 in the office, physically sitting in front of their desktop PCs, and therefore they would consider it secure.

Corporate IT risks turning into a slow-moving dinosaur that does not contribute, but rather hinders innovation and the users' ability to be productive. Users are starting to avoid involving IT since it takes a long time to get anything done, and is slow moving. There is now a real threat that corporate IT becomes irrelevant and starts getting competition from these outside trends.

VMware has a track record in innovation, often where others get stuck. The origin of Horizon Workspace was a cloud identity services platform called MyOneLogin. It was developed by a company called TriCipher. TriCipher was founded in 2000 and acquired by VMware in August 2010.

Horizon Application Manager 1.0 was released in May 2011. This was also the first time that VMware unveiled their Project Horizon vision, with Application Manager being the first solution delivered against that vision. Horizon Application Manager was a user-centric management service for accessing cloud applications and included an identity-as-a-service hub that securely extended the users' existing identity, and allowed users to access web-based applications in a secure manner from any device.

Since the solution was still a cloud service, one of the top priorities for VMware was to convert it into an on-premise solution. (This was highly in demand especially by European customers who have strict data privacy laws.)

In August 2011, VMware released Horizon Workspace 1.5, and now customers could choose to install it on premise. During 2011, VMware acquired other companies such as Wanova to expand their capabilities. Horizon Suite 1.0 was announced in the spring of 2013. The idea with the Suite is that the customer could now buy one Stock Keeping Unit (SKU) to solve all their needs for end-user computing, from managing physical desktops to mobile management. The Suite includes Horizon Workspace, Horizon View, and Horizon Mirage, along with ThinApp, Workstation, and Fusion.

What this book covers

Chapter 1, Getting Started with VMware Horizon Workspace, gives you an overview of all the components you need to have in place before you start the installation process of Horizon Workspace.

Chapter 2, Design, Install, and Configure, covers the basic sizing, configuration, and the installation of Horizon Workspace 1.5. After making sure that all the prerequisites are in place, we will start deploying Horizon Workspace.

Chapter 3, Horizon Files, looks at the architecture behind Horizon Files and then enables and configures this feature.

Chapter 4, Integrating SaaS Applications, covers one of the core features of Horizon Workspace, that is the ability to entitle and consume web-based applications. In this chapter, we will talk about SAML authentication and how to configure Horizon Workspace to broker to SaaS applications.

Chapter 5, Mobile Management, discusses the mobile management capabilities of VMware Horizon Workspace 1.5, including configuration, device enrollment, and how to entitle users to mobile applications.

Chapter 6, Integrating ThinApp Packages, will look at how to manage Windows-based applications using VMware ThinApp.

Chapter 7, Horizon View Integration, will talk about how to integrate Horizon View so that the users can access their virtual desktop directly from their Workspace.

Chapter 8, Troubleshooting, will cover the most common issues that come up during the installation and configuration of Horizon Workspace.

Appendix, Useful Links, provides a number of useful links for additional information and references used in this book.

What you need for this book

To get the most out of this book, you should have some experience of working as an IT administrator with skills and knowledge on building and designing end user environments, and have an understanding of the challenges faced by users.

Throughout the book, you have the opportunity to follow step-by-step practical guides in deploying Horizon Workspace and its key features and functionalities in a lab environment. If you want to work through the practical examples, you will need the following infrastructure:

  • 1 vCenter Server

  • 1 ESXi host server with:

    • A minimum of 8 cores

    • 16 GB RAM

    • 500 GB of local or SAN-attached storage

  • Windows Server 2008 R2 Active Directory with DNS configured

  • VMware Horizon Suite, which offers the following components:

    • Horizon Workspace 1.5

    • Horizon View 5.3

    • ThinApp (packages created for Horizon Workspace)

  • developer account (required for SaaS integration)

  • iOS Device (iPhone or iPad)

  • Android smartphone (VMware Ready device and/or Android device)

Who this book is for

This book is aimed at IT professionals who are relatively new to the Horizon Workspace product, looking to understand the technology at a deeper level and how it will help deliver end-user environments. It will explain how the technology works, how to set it up, and then how to get started with deploying and managing the key features and functionalities.

It will guide you through the best practices in designing a Horizon Workspace solution, both for production installations and in proof of concept and pilot environments.

At the end of this book, you will have built the skills and knowledge to design, configure, install, and manage a Horizon Workspace infrastructure to deliver the tools a user needs to get their job done.


In this book, you will find a number of styles of text that distinguish between different kinds of information. Here are some examples of these styles, and an explanation of their meaning.

Code words in text are shown as follows: "Log in to Horizon Workspace using testuser2, as shown in the following screenshot:"

Any command-line input or output is written as follows:

VMware-Horizon -Workspace-1.x.x-XXXX.exe /v ENABLE_DATA=0

New terms and important words are shown in bold. Words that you see on the screen, in menus or dialog boxes for example, appear in the text like this: "If something is not correct or you need to make a change later, simply click on Edit to change the settings."


Warnings or important notes appear in a box like this.


Tips and tricks appear like this.

Reader feedback

Feedback from our readers is always welcome. Let us know what you think about this book—what you liked or may have disliked. Reader feedback is important for us to develop titles that you really get the most out of.

To send us general feedback, simply send an e-mail to , and mention the book title via the subject of your message. If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide on

Customer support

Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.


Although we have taken every care to ensure the accuracy of our content, mistakes do happen. If you find a mistake in one of our books—maybe a mistake in the text or the code—we would be grateful if you would report this to us. By doing so, you can save other readers from frustration and help us improve subsequent versions of this book. If you find any errata, please report them by visiting, selecting your book, clicking on the errata submission form link, and entering the details of your errata. Once your errata are verified, your submission will be accepted and the errata will be uploaded on our website, or added to any list of existing errata, under the Errata section of that title. Any existing errata can be viewed by selecting your title from


Piracy of copyright material on the Internet is an ongoing problem across all media. At Packt, we take the protection of our copyright and licenses very seriously. If you come across any illegal copies of our works, in any form, on the Internet, please provide us with the location address or website name immediately so that we can pursue a remedy.

Please contact us at with a link to the suspected pirated material.

We appreciate your help in protecting our authors, and our ability to bring you valuable content.


You can contact us at if you are having a problem with any aspect of the book, and we will do our best to address it.