Horizon View

Have you ever worked with a Horizon View pool with 10 VM’s and deleted 3 and it recreated as 11? May want to pay attention to learn how you can reuse view desktop names. First you will need to connect to the ADAM database on one of your servers. Use KB2012377 for instructions. To connect to the View ADAM database: Log in to one of the View Connection Servers as Domain Administrator.

I am currently troubleshooting some issues with the Horizon event database having some performance issues. Working with support they pointed me to KB2094580. By Default the view event database is not indexed. I was curious as to way I always had issues pulling up events in the Horizon View Administrative interface, but as soon as I followed the steps, it was almost immediate now, where i use to have to wait an extremely long time.

Horizon 6.2 is now available and Linux support has improved. Previously it was only supported on a limited set of older operating systems. Originally when we deployed we had deployed Ubuntu 12.04, however now the newer kernel 14.04 is supported so I will show you how to upgrade your desktop to the latest version and now use the new agent as well. If you followed my previous post to disable Console access.

Horizon 6.2 Introduced Biometric Authentication, with initial support for TouchID on IOS devices. This post will explain how to enable it, as its not really something greatly documented right now. I think they are aware and hopefully in a future update this will be easier. Here is a link to the current VMware documentation. NOTE: This feature does require a 3rd party trusted signed certificate to work. From my current testing and speaking with others self-signed certificates will not function.

I had the opportunity to upgrade my Horizon View environment from 6.1 to 6.2. As always VMware has made this very easy! First download the bits from here. The upgrade documentation can also be found here. Warning: In my environment I do not have a composer server, if you had one this would be upgraded first The upgrade order is as follows. Composer Server, Connection Servers and then Security Servers.

So I have had some time to play around with the new Linux Horizon View Agent and using Ubuntu as a VDI guest and it works pretty well. However as most of us have seen, when a user is logged onto the guest the screen is shown in the console. In some organizations this may pose a privacy or security risk. Right now there is no true workaround as that is how the view session is handled, however there is a workaround to disable console access.

So Horizon View 6.1.1 was released recently with added support for published applications to finally be accessible via the HTML client. The process is pretty straightforward, however I came across one hiccup I wanted to share. I am assuming you have already upgraded your View Composer, Connection and Security Servers and are now focused on getting the agents up to date. Install/Update Agents on virtual desktops to 6.1.1 (The HTML Access 3.

I was in the process of getting vRealize for Horizon configured, and as I was going through the broker agent configuration for the life of me I couldn’t get the eventdb portion to work. Everytime i entered in the user name and password, I would receive the following error. FAILED (Format of the initialization string does not conform to specification starting at index 88.) I knew it wasn’t a password issue as I was able to logon to SQL Manager with no issue, and the Horizon View EventsDB was working fine, so I went on a google search to try to hunt through logs.

So I have been working in a few situations where i have wanted to use Horizon 6 published (RDS) applications but having to either launch the Horizon View client within a VDI or have users be forced to logon again has been a deal breaker. Upon further research i finally found the right combination of settings to allow users to launch the RDS Hosted Applications via a Shortcut and automatically login to the view client making this process seamless.