A while back I posted a blog post describing how to setup Kerberos single sign-on in Horizon Workspace 1.5, link: http://blogs.vmware.com/horizontech/2014/01/setting-up-kerberos-single-sign-in-sso-access-in-horizon-workspace-1-5.html. With the release of Horizon Workspace 1.8 we have changed the procedure and logic quite a bit.
This blog post will walk you through the process of setting up Kerberos SSO and hopefully explain some of the new concepts in Horizon Workspace 1.8 while doing so.
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.
By John Dodge, Technical Marketing, VMware
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.
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.
Sing-up here: http://labs.hol.vmware.com
The Lab’s name is: HOL-MBL-1304 – Horizon Workspace – Explore and Deploy
By Cynthia Hsieh, Director, Solution Management, End-User Computing, VMware
This blog is written to help you understand how location awareness can be done in VMware Horizon View. In the world of BYOD or “Bring Your Own Device,” it’s critical your IT organization knows your configuration 4W (who, what, where, when) and 1H (how). Namely, who is accessing? What device do you use to access? What workplace are you trying to join in? Where are you accessing from? When are you trying to access?…
This blog focuses on the client attributes provided by VMware Horizon View which you can leverage and design for location awareness.
One of the new features in the VMware Horizon Workspace 1.5 is the integration of Horizon Mobile. With this update, there also comes an option within the VMware Switch for Android application to utilize either the original VMware Horizon Mobile Management virtual appliance server or the new VMware Horizon Workspace 1.5 vApp environment.
Here is how to setup the VMware Switch for Android with the new VMware Horizon Workspace 1.5.
By Gerald Cheong, contractor, End-User Computing Solutions Management, VMware, and
Manrat Chobchuen, Solutions Architect, End-User Computing Solutions Management, VMware
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.
Here’s how to enable SSH for the Horizon vApps.