Desktop virtualisation is easy, yet hard

Category : VDI

With RemoteFX becoming more of a reality, it got me thinking in to the way VDI is misunderstood and hyped.

As has been proclaimed before, VDI is seen as the silver bullet for IT’s desktop management woes. IT reclaims control of the desktop and therefore decreases opex whilst increases customer satisfaction/perception and everyone lives happily ever after. Almost. It’s only part of the puzzle.

To really make a virtual desktop solution sing, you need to concentrate on the user. Initially ignore the broker, ignore the hypervisor, ignore the infrastructure…. look at your applications, user profiles and user data and work backwards.

What is the point of having an elastic infrastructure that can weather the most demanding of user scenarios if your apps are still provisioned in an antiquated way.

What is the point of having the best protocol, so your user’s can enjoy YouTube during their lunchtimes if it takes them 30 mins to log on in the morning because their profiles are huge.

Not a lot…

Don’t forget this…

Category : Antivirus, Citrix, VDI

AntiVirus isn’t glamorous. Therefore the this press release will likely be forgotten pretty quickly.

Summarised, it’s McAfee’s collaboration with Citrix to provide centralised protection for virtual desktops. This shouldn’t be underestimated.

This is just another step in abstracting another painful part of the user’s environment from the OS provider greater control, simplified creation and increased predictability of the end user experience. Apps, profile, files/data, and AV. What’s next?!

Where art though CVP…

Category : Citrix, VDI, VMware, View

Caught a tweet from @robupham to @tom_howarth today regarding Citrix Synergy and it startled me somewhat. Enough to write about it anyway – it regards the announcement of Citrix XenClient.

image

Last year, VMware announced the Client Virtualisation Platform (CVP). A type 1 client hypervisor to go head to head with XenClient. 15 months later, XenClient is here but it’s pretty quiet on the CVP front. Annoying because I see the client hypervisor as one of the boons for a VDI deployment.

As has been stated many a time, the Capex arguments for VDI are non existent. It’s all about Opex. In the Enterprise, I see the client side hypervisor as greatly reducing the costs related to desktop/laptop lifecycles.

By abstracting the user’s environment from the hardware, lifecycle management becomes a case of waiting for the courier to deliver the replacement. No acceptance testing, no imaging or pre-staging. Glorious.

In addition, there’s also the promise of near native desktop performance using the client hypervisor. Sounds like a win win.

The problem is, without CVP, we’re left with offline/local desktops in View. This is all very good if you use a BYOPC model, but if you don’t have this, the management overhead per user doubles. Two OS deployments (updates, troubleshooting et al), two copies of AntiVirus and likely duplicated applications. That sounds like a nightmare scenario to me.

Which leads me back to the original tweet. Having tested both XenDesktop and View, my experience is that XenDesktop is more mature and has a far greater feature set but View has a better core infrastructure and is far more simpler. VMware are adding features so that they can ‘catch up’ to Citrix, but with announcements like this and huge gaps in the View product set (remote access, end point performance tracking, etc), it feels like VMware are constantly one step behind at the moment.

Therefore I can safely say, I’m a VMware customer and I want a client hypervisor. Am I alone?

Introduction to the PCoIP Management Console

Category : PCoIP, VDI

Last week I received a shiny Wyse P20 for a proof of concept using VMware View 4. Having been testing with Windows Embedded Standard Edition thin clients and standard desktop machines, I was keen to see how these Zero Clients compared.

image

Upon receiving the terminal, I downloaded the Teradici PCoIP Management Console. This software is actually a VMware workstation VM which a quick import in to vCenter sorted out.

After booting the VM, you’re presented with a fairly standard configuration screen to set the password, hostname, IP and so on.

image

Logging on with a web browser, the management console is fairly clean and simple.

image

The management is split in to three main components, devices, groups and profiles. The idea being that you assign a profile to a group – add devices to that group and the policy should cascade to the end client.

The end clients register with the management console by using a DNS-SRV record. Using Windows DNS, this can be set by creating a new record, selecting ‘Other New Records’ and then Service Location (SRV).

imageimage

The SRV record required the service name to be _pcoip-tool and the host to be populated with the hostname of the PCoIP Management Console.

Clicking Update DNS SRV records verifies that the DNS-SRV record is propagating.

image

The video below has a quick run through of adding a client, attaching a profile and a couple of other features.

The simplicity of this configuration is impressive – from never having touched a PCoIP thin client, I had it being centrally managed, with cascaded policies and automated firmware deployment within 30 minutes.

Next up is the actual performance review of the Wyse P20 utilising View 4.0 with PCoIP….

View 4.0 – black screen upon login

Category : VDI, View

I’ve been running a proof of concept lately with View 4.0 and Windows 7 and have had a constant showstopper issue (experimental… I know!).

Using PCoIP, 80% of the time when the end user logs in they will be greeted by a black screen for a couple of seconds and then the session will quit. Logging back in works as normal.

Looking at the View 4.0 release notes there are a few mentions of black screens but only one relevant to Windows 7:

When View Client attempts to connect to a Windows 7 desktop using PCoIP, a blank black screen will appear instead of the Windows Security dialog box if the Windows 7 desktop fails to perform single sign-on, for example, if the desktop does not join the domain.

At first, I thought this issue may have been one with my template and not deploying properly through Composer, but after testing through the console this was quickly ruled out.

With the release of View 4.0.1 comes a rather interesting KB (KB1016961) from VMware.

This KB refers to the same SSO issues mentioned above but this time indicates that a legal disclaimer can trip up the SSO process! The workaround is to disable any disclaimers.

Definitely one that will trip up a few POCs up in the early stages I feel.