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..
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.
If you are new to Horizon Workspace and want to get kick started sing-up for the VMworld 2013 Hands-on Lab, now available online. In this 101 Lab you will gain hands-on experience with data sharing, SAML integration and other useful features.
One of the challenges in enterprise application management is the large number of applications that the average enterprise user needs to access. Single sign-on (SSO) is an effective way to make access more convenient for the user and at the same time more secure for the enterprise.
Some SSO solutions are based on integrated Active Directory (AD) on the corporate intranet. One big drawback of this approach is that it restricts the Web application to the corporate intranet. This results in lack of flexibility in deployment options as well as certain security compromises.
VMware Horizon Workspace uses the Security Assertion Markup Language (SAML) 2.0 standard to support SSO. This support allows more flexibility and better security than an integrated AD solution. This article describes SAML concepts and shows how to set up a sample Web application in Horizon Workspace with SAML, so you can see SSO in action. It also discusses the considerations and integration points for a Web application to support SAML 2.0 integration with Horizon Workspace.
Are you a fan of SSH vs. virtual console access? I am. I much prefer to access a Linux/Unix vApp via SSH than via the remote console as this allows me to use Terminal on my Mac vs. opening a remote session to a virtual Windows system to then run the vSphere Infrastructure Client (VIC). It's a personal preference, I admit. But enabling SSH does allow for direct SCP access as well.