This blog post explains how to setup Workspace Portal in a High Availability cluster using internal database. This blog post is based on the KB-article 2094258.
Creating a Workspace Portal cluster is very simple. You simply clone your first VM instance of the Workspace Portal and you have a cluster. It does require a load balancer and that the Workspace Portal’s Fully qualified domain name (FQDN) is pointing to your load balancer.
Are you interesting in learning more about VMware Workspace Portal or are given the task to deploy Workspace Portal within your organization? Perhaps you are an existing Workspace customer now looking for information on how to update to latest version?
Look no further. The Workspace Portal 2.1 Hands-On Lab is designed for you. With its 9 modules it covers topics such as an overview of the product, how-to update from Workspace 1.8.2, how-to manage certificates, Clustering and much, much more..
By Dean Flaming and Jim Yanik – VMware End User Computing Technical Enablement Team
One of the new functionalities of VMware Horizon 6 with View is the ability to handle Global Name Space support with the new Horizon 6 feature known as Cloud Pod Architecture. This ability allows for users of your View environment to easily handle connection to their virtual desktop using a single name no matter where they reside geographically.
By Dean Flaming, Sr. Technical Marketing Manager – Technical Enablement, End-User Computing, VMware
On behalf of the many folks who helped make this happen, I am proud to announce the release of the Horizon 6 with View Introduction Hands On Lab! This lab is a guided tour of Horizon 6 with View specifically focusing on the new features.
This Horizon 6 with View lab is designed to demonstrate and introduce you to the new Horizon 6 features, starting with the ease of installation and configuration of View, RDS-hosted application setup and configuration, RDS-hosted desktop setup and configuration, and Cloud Pod Architecture configurations, including some scenarios.
In Horizon Workspace 1.5 you configured the URL for View client access on your Connector. In Horizon Workspace version 1.8 that is all changed. To allow for greater flexibility you now specify the View URL on a per Network Range basis.
This allows you to more easily specify an internal URL for your internal clients and an external URL for your external users.
Last night Horizon Workspace 1.8 was released. While being a minor release it comes with some major new features and functionality.
Citrix-based Application (XenApp) integration
From the Horizon Workspace User Portal, users can now launch Citrix-based applications via XenApp 5.0, 6.0, and 6.5 using single sign-on. This feature requires Citrix Receiver to be installed on the client and supports Mac, PC, iOS and Android devices.
One of the most commonly asked questions amongst customers and partners are how-to setup Kerberos Single-Sign-On (SSO) into Horizon Workspace. Therefore I decided I should create this detailed step-by-step blog post on how to configure Kerberos in Horizon Workspace version 1.0 and 1.5.
Configuring Kerberos SSO into Horizon Workspace greatly enhances the end-user experience. If the end-user login to their domain joined desktop and access the Horizon Workspace web portal they will not be asked to sign-in once more, but are allowed access based on their Kerberos token. The Horizon Client version 1.5.2 also makes use of Kerberos SSO. Seamless to the users the Horizon Client will try to authenticate to the Horizon Workspace using Kerberos. If successful no further interaction from the end-user is required. This is especially useful in a Horizon View environment using non-persistent floating desktop pools.
Recently my EUC Reference Architecture team had the opportunity to see the Nexenta VSA for View (NV4V) for Horizon View in action (see our Reference Architecture posting here). I have to admit to being impressed by both the product and the enabling potential of a well-executed virtual storage accelerator (VSA) strategy. There are a couple of notable incumbents and newcomers in the VSA space. Atlantis Computing ILIO has enjoyed some great wins (check out their VMware Reference Implementation Study here), and Fusion-io’s ioVDI product looks very promising, although we’ve not had the chance to evaluate it yet. But rather than address them all in a one-size fits all article, here I’m going to focus on Nexenta VSA for View (NV4V).
Although you can read plenty online about NV4V and other VSA technology, I’ll give you a short explanation of why a well-crafted VSA product provides great benefits to your business.