Exclusive: HP wields blades to ease desktop management
Innovative Consolidated Client Infrastructure replaces desktop PCs with thin clients connected to blade serversFollow @infoworld
The first step for an administrator is to prepare the bc1000 for use by installing the OS and end-user applications. This is a rather mundane task, but no different than setting up a desktop PC, with one interesting difference: Each blade will load a copy of a client management agent. In essence, that agent facilitates centralized administration of blade PCs using RDP.
RDP is an essential part of the CCI management arsenal. It offers the tools to manage many blade PCs with little effort. For instance, using RDP, an administrator can create an image from a working unit and later deploy the same image to a single target or in parallel to multiple blades.
Deploying the same image to another blade is a simple drag-and-drop procedure, although the GUI also helps you create scripts that selectively drive a new image to a blade, based on criteria such as the IP address, user, or computer name.
I tested CCI wearing my end-user hat on an already configured blade. If you are familiar with Windows RDC (Remote Desktop Connection), getting used to CCI-virtualized PCs should be painless. I started RDC on my thin client, then typed the IP address of my blade PC and my log-in info to access my applications remotely.
After creating a Word file on one client, I logged off, moved to another client, and logged in with the same credentials. As expected, I regained access to my file.
A parallel benefit: The local machine contains no data to be stolen, hence the damage caused by a theft is limited to the cost of the equipment.
Although Windows makes it possible to pursue the same objective of client independence with techniques such as roaming users’ profiles, the thin-client approach wins because of its simplicity and easy setup. Furthermore, users can access their data and applications from any computer with an RDC client. For example, with proper firewall settings and a decent connection, traveling users can easily access their virtual PC remotely from their laptops.
A comprehensive CCI configuration can include techniques to protect users from broken blades, such as adding a NAS device and redirecting users’ writes to network shares on that appliance. Setting up such a configuration should be easy using plain vanilla NAS appliances and creating proper user rules in Active Directory.
To test recovery, I began editing a Word document, then simulated a failure by cutting power to the blade PC without saving my work. My thin client displayed an error message warning that the connection with the blade was lost. I changed the IP address in RDC to point to a different blade; after I logged in, I was immediately able to access my virtual desktop and test documents, including the one open at the time of the crash. I did notice that the changes made since the last Word autosave were gone. Nevertheless, I had recovered in minutes, and with minimal data loss.
Having a user enter a new IP address during fail-over is a minor inconvenience, but it can be avoided completely if you install an application that provides automatic IP address fail-over, such as Big-IP from F5 Networks.
By the end of my evaluation, I had mostly positive remarks about CCI. However, XP-only support is a factor that could discourage potential users. The complexity of the setup, with its blend of Active Directory, NAS devices, IP load balancing, and blade administration servers could be another spoiler. Still, I would be hard-pressed to remove any of those components, as they all bring benefits to the solution.
Ultimately, the decision to embrace CCI depends on how much value the additional reliability and ability to better manage users’ applications brings to your company. HP estimates that the cost savings of CCI compared with the traditional approach can be substantial. But for many companies, the nonmonetary benefits alone can be a sufficient motivation to embrace virtualized desktops.