In this video I take you through configuring NVIDIA vGPU with a GRID K2 card on a Microsoft Remote Desktop Services Host (RDSH) with VMware Horizon 6.2. In less than 10 minutes you can configure your RDSH virtual machine with a vGPU profile to deliver high performance 3D applications.
Becoming a VCDX (VMware Certified Design Expert) doesn’t mean you have reached the path to enlightenment or qualify you for an immediate pay rise. There, I said it. That is the reality. Yes it is the highest level of certification by VMware but it should NOT be your end game. The VCDX should be an incremental goal to where you want to be, you just might not realize it yet.
I’ve had a lot of time recently to catch up with the latest tweets and blogs from the virtualization community and I’ve noticed a few misconceptions about the VCDX. I have also seen some excellent comments from other VCDX’s that reflect what I am about to say.
In The Beginning
Back in the early days when the VCDX was in low double digits, there were awards, branded beer, and songs around the camp fire under the star lit sky. Well maybe not the last one but it was a big celebration and rightly so. The number of VCDX title holders are in the hundreds now and I wouldn’t think it is practical to have such a merry dance and award ceremony each time someone achieves their VCDX. Don’t get me wrong I would love this to be case, camp fire songs included, but that just isn’t going to happen.
If you’re not already running Horizon View 5.3… why not? Since Horizon View 5.3 was released VMware have already extended it’s functionality again with Feature Pack 1. If you’re not familiar with Feature Packs, they’re essentially shiny new updates and features to the core product release. These can be updates to View clients (E.g. iOS, Android, Windows) or the View server functionality itself. Anyway, the topic of this post is troubleshooting as I’ve seen some instances where the Feature Pack installation fails.
Horizon View 5.3 Feature Pack 1 provides the following features and updates:
- Multimedia redirection (MMR) for Windows 7 (previously limited to Windows XP)
- Flash URL redirection
- Real-time Audio-Video (RTAV)
- HTML Access
- Unity Touch
In addition Unity Touch, HTML Access and RTAV are extended to support Windows Server 2008 and Windows 8.1, although HTML access is Tech Preview for Windows 8 or 8.1.
I’ve noticed that a few people have had issues installing the Feature Pack which may be due to the customization of the Windows 7 virtual desktop master image. Firstly, if you followed the VMware View Optimization Guide for Windows 7 then you may have disabled some Windows services that are required by the Feature Pack. Once such service is “Desktop Window Manager Session Manager (UxSms)” which is a required component for Windows 7 MMR. If this is disabled then you will get the following error: “
Error 1920.Service Desktop Window Manager Session Manager (UxSms) failed to start. Verify that you have sufficient privileges to start system services.”
If you don’t want to use all of the Feature Pack components listed above then you can choose not to install one or more, so if you don’t use Windows 7 MMR then simply deselect it during the Feature Pack 1 installation. Otherwise, enable the Desktop Window Manager Session Manager services (set to Automatic) and the Feature Pack will install. This service allows for Aero, 3D effects and high resolution support.
Note: This service is always on with Windows 8 and cannot be disabled.
If you have problems installing other components then check that required services are not disabled, or there are no restrictions in place preventing the VMware virtual Webcam or Audio drivers from being installed.
Following on from my previous video blog where I described how VMware View Linked Clones are created, I have decided to make this available as a more detailed written article. VMware View Composer is a service that can run on either the vCenter server or on a standalone dedicated machine. In this technical deep dive I describe what makes a linked clone, the role of View Composer and exactly what it does.
View Composer consists of a web service (SIM), the Universal File Access (UFA) service and other components it relies on such as ADutil and the vCenter API. View Composer receives instructions from View Manager as XML messages, and initiates the linked clone creation using vCenter API calls and the SIM service (Scalable Image Management, a.k.a Composer). In essence it’s a workflow engine. [Read more…] about VMware View Composer Linked Clone Technical Deepdive
After stopping for a coffee break on my 250 mile journey home this week, I posted this quick video on how to monitor VMware Horizon View virtual desktop for performance issues using ESXTOP. I discuss the key performance metrics to look at, such as CPU Ready Time (%RDY) and Co-Stop (%CSTP) in addition to memory ballooning (MCTLSZ) and swapping to disk. Enjoy!
Determining if multiple vCPUs are causing performance issues: http://kb.vmware.com/kb/1005362
Technical deep dive into VMware View Composer Linked Clones, and the workflow behind the creation of linked clone desktops. Based on VMware View 5.2, this whiteboard technical overview and live demonstration covers View Composer, the vCenter API (CloneVM_Task method), VMware Universal File Access (UFA) and Active Directory computer account creation.
VMware View has offered the ability to serve your desktops as linked clones since View 3.0 with View Composer, but with View 5.1 I still get asked many questions about how linked clones work, how snapshots are involved, delta files, and what other files make up each linked clone virtual desktop. You are probably already familiar with VMDK (Virtual Machine Disks) and snapshots, but the process View Composer takes to create linked clones may still be a bit of a mystery to you. Since the addition of View Storage Accelerator (VSA) in View 5.1 there are also some additional files that are created. This article will describe the files used by linked clones. [Read more…] about Understanding VMware View 5.1 Linked Clones
For my first post of 2013, I have decided to dive straight into sizing for VMware View 5.1. If you are planning a VMware View implementation then at some stage you will need to look at sizing, and calculating factors like how many desktops per View desktop pool, in addition to network configuration and storage considerations. The purpose of this article is to discuss sizing and configuration maximums for VMware View 5.1. Since VMware ESX 3.x, a configuration maximums document has been published by VMware for each version of vSphere that details the supported maximums for networking, compute, storage, vCenter, host, and even vCloud Director. Because there is no single ‘configuration maximums’ document for VMware View 5.1, I have included reference documents and material at the bottom of this article. [Read more…] about Sizing for VMware View 5.1 Composer Desktop Pools