After upgrading several different environments to Horizon Workspace 1.8, it’s become clear to me that the “offline upgrade” feature is something that should be used whenever possible. Maybe it’s just the environments I’ve worked in, but going from 1.5 to 1.8 takes much much longer than going from 1.0-1.5. This guide is intended to help you accomplish an offline upgrade from 1.5 to 1.8, while having a plan to restore to 1.5 in case of a failure. This is the fastest process I have found to perform the upgrade. Even with these measures, I’d plan on getting a 4-5 hour outage window for a production environment (2 connector, service, gateway, data virtual appliances)
In this post I’ll show in detail how to configure Horizon Workspace to use an external database during the install process. This post is part of a series showing how to configure VMware Horizon Workspace in a production environment. You’ll need an external database to have multiple service virtual appliances, so this should be a requirement for your environment. This process was suprisingly not trivial for me, however it could have something to do with the fact that I haven’t used postgres sql in the past.
So yesterday, VMware released Horizon Workspace 1.5. HUGE improvement over the GA release… Holey smokes. Any further tutorials will reference this version.
Anyways, more to the point. In this post I will demonstrate how to do a base configuration of Horizon Workspace using an internal Microsoft Certificate Authority with Nginx as a frontend. This setup is only acceptable for setting up workspace in a lab environment, since in a production environment you’ll need a trusted third party cert. Doing this in a lab environment is important because it will allow you to set up and test every feature you’ll be using in a production environment.
- Microsoft Active Directory Certificate Services
- Linux Machine running Nginx
- Horizon Workspace 1.5 Downloaded and installed with no configuration.
- We’ll be using the workspace FQDN of hzn.test.in (This obviously assumes the domain of test.in)
I’ve never met a VMware Admin who will use the console to access a VM if they have a choice. There are plenty of tutorials out there that will show you how to do this, but since I’m starting a series, I guess I’ll throw the same info on the internet, but put my own spin on it.
I’ve been working with Horizon Workspace since it went GA in March. At this point in time, I’m happy to say that I’ve got Workspace set up in a production environment.
In this series, I will be covering how I configured each part of this suite. I would expect that this process will become exponentially easier as time goes on. One thing to note is that I will write these posts assuming that you are at least moderately familiar with linux and Workspace. I will not go into details on how to install packages, deploy the VA, use the web interface. Use Google if you’re looking for that boring stuff 🙂 Here we go!