I've built up and tore down my vRealize Automation lab several times in the past month in order to familiarize myself with some of the pitfalls. As a result, I've run into some installation gotchas that I noted down, and decided to post them here.
VMware vRealize Automation makes it easy for us to provide our end users with the ability to request and manage their own virtual machines using a “self-service” portal. With very little configuration required, we can add vSphere virtual machine templates to a vRA service catalog for users to consume. vRA can then handle the request management for new virtual machines and when approved by the appropriate approvers, even provision the new VMs by cloning the template.
There seems to be some confusion as to whether or not the Identity Appliance that ships as part of vRealize Automation (previously known as vCloud Automation Center, which will be referred to as vCAC 6 for the rest of this article) is required when deploying vCAC 6.1 in conjunction with vSphere 5.5 and later.
As of vSphere 5.1, Single Sign-On (SSO) is a pre-requisite to installing the components for and including vCenter Server. It’s no secret that VMware’s initial implementation of SSO in vSphere 5.1 was terrible. It was over complicated in terms of its implementation requirements, even requiring its own database, to be manually set up using SQL scripts. Thankfully, VMware addressed many if not all of the SSO issues in its release vSphere 5.5, with SSO now being a much more simple and robust component in your vSphere 5.5 environment.
I remember struggling to get my head around Apache Webserver file permissions. It's a common issue, and I've seen forum posts this weekend with users struggling to get it right. That s what's prompted this post.
To allow the Apache web server process (httpd) to access and serve files from virtual host directories, httpd requires at least read access. However, with content management systems, httpd might also require write access to virtual host directories.
I've always wanted to find a cost effective way to implement 2-factor authentication. Commercial solutions are expensive, and if you are a small business, you might not want to spend a small fortune on implementing an enterprise solution with hardware tokens. I stumbled across Google Authenticator a while back and started to wonder how it can be used to implement a free 2-factor authentication solution in my lab. I also found a few posts that suggested teaming it up with Freeradius and that's really where this post started.
I've been looking into enabling audio recording in VMware View Desktops. This would be useful as it would allow the use of applications such as Skype and TeamSpeak within VMware View published desktops.
By default, the VMware View Agent which is installed within the desktop operating system installs the VMware Virtual Audio Driver. The VMware Virtual Audio Driver enables audio playback from the View Desktop to be played through the VMware View Client. However, the VMware Virtual Audio Driver does not enable analog audio input from the View Client to the View desktop. With the VMware Virtual Audio Driver, audio recording within the View Desktop from an audio source connected to the View Client, such as a microphone, is not possible and applications that rely on Audio input will not function correctly.