This just in, X1 welcomed as overlord

I, for one, welcome our new X1 overlords..

Earlier today, Richard Hayton and Manu Chauhan announced the tech preview release of X1 Storefront and Receiver X1 for Web and I’ve been excited since I saw Richard demo it earlier this year.

Homage to Kent Brockman aside, I think this update is deserving of attention. I’ve spent the better part of 6 years listening to enterprises (from the smallest of small, to the largest of large) describe their wants, desires and challenges delivering simple, secure and seamless access to critical business applications, desktops and data. Many have looked to Citrix for Disaster Recovery and Business Continuity solutions, others leverage it for line of business applications and there are those that use Citrix as their primary desktop and application solution.

Over all those years, through all of the conversations, conference calls, GoToMeetings, WebExes, LiveMeetings, Proof of Concepts there are 4 building blocks, if you will, I’ve been discussing, demonstrating and architecting:

  • Client
  • Gateway (optional)
  • Resource Aggregator
  • Infrastructure

Ignoring the “Infrastructure” for a moment, 2 of the 3 (and in some cases the remaining is optional) just got a major overhaul. We’re not talking “Citrix added a new theme, yay” or “Citrix changed the look again..still need those WI features” – no, this is the first hint at an evolved Client/Resource Aggregator and even better integration should you look at NetScaler as your Gateway of choice. With an extensible Client able to connect securely to an extensible Resource Aggregator, the underlying infrastructure becomes amorphous – a commodity resource (physical/virtual, on-premise/off-premise, owned/leased)  and to a certain extent irrelevant. The goal has always been in seamlessly connecting an employee with their workspace, so they can be as productive as possible wherever they are. Yes, there are countless design decisions related to the infrastructure, but without the right client/gateway/aggregator (user experience) none of it matters.

Receiver X1 is about uniting the Citrix experience, across both client and server components – Receiver X1 for Web and X1 Storefront “today”, X1 XenMobile Server “tomorrow” – and I’m excited to dig in and see what the future holds.

~ldf

Virtual Stepping Stones

Simple Question:

Is desktop virtualization a key stepping stone for cloud computing in the enterprise?

Sure, as someone that spends most of their day (and quite a few evenings) working on desktop virtualization and cloud computing projects — okay, mostly desktop virtuailzation, but cloud discussions are increasingly common and I enjoy the blog/twitter debates — it might seem natural for me to consider desktop virtualization a primer for enterprise adoption of cloud computing.

How can I not, though? Setting aside licensing and business concerns for a moment, the idea of taking a relatively static workload, like a physical desktop, and migrating it into an elastic, virtualized, self-service platform makes a lot of sense. Its no wonder VMware was so quick to move from server virtualization to desktop virtualization. Its also why Citrix was ready, willing and able to move in that direction, building on their success with TS/RDS-based solutions. It might not be the end-all-be-all for all users and it may only serve specific use-cases at the moment (or long-term), but I would argue that cloud architects and desktop virtualization architects would learn a lot from each other if they made time for collaboration.

Some people might argue that being able to deliver desktops as a service, the ultimate goal of most VDI or RDS-based projects, doesn’t automatically make it cloud computing; which may be true, but doesn’t really matter and misses the crux of my argument. Desktop virtualization architects can learn a lot from the “pie-in-the-sky” cloud architects that are championing DevOps, pushing the envelope with elasticity, metering, chargeback and the reality of consumption-based pricing for IT resources. How long have enterprises struggled with the device-centric days of managing physical PCs? How can these “new” concepts be applied to one of IT’s oldest recurring costs, the physical PC?

If you still think I’m off-base, consider the excellent blog post by @reillyusa, titled 1-2-3 easy as VPC. In it, he outlines a theoretical evolution of the AWS and Citrix capabilities which would allow an enterprise to securely leverage public cloud resources to deliver Windows “crapplications” to both internal and external users. His thought experiment, and at this point in time I would consider it an experiement, just goes to show that enterprises thinking about cloud computing come at it from many angles. It’s yet another use case for hybrid cloud, and this time targeting a subset of the broader desktop virtualization technologies, namely application virtualization.

  • ACME Corp. has several client / server LoB applications that it would like to use the flexible nature of AWS to “serve” them from. The applications are not accessed outside of North America and are used between 8am-8pm Eastern Time.
  • ACME Corp. uses Citrix XenApp to provide access to the applications.
  • The user base is internal and external, but all have valid Active Directory accounts for ACME Corp. environment.

Now, for more of a private on-premise feel, consider the large VDI environments enterprises are deploying. They are having desktop sizing and scalability discussions. They are digging into the various performance concerns that VDI introduces — App Streaming, Profile/Personalization and OS Boot Storms, to name just a few — and ultimately they need to be able to show financial and/or operational gains to the check signers. Many of these projects are being spurred by Windows 7 migrations, the increasing proliferation of mobile devices and the opportunistic problem-solving that us humans are so damn good at. In and of itself, not cloud computing, but a veritable smorgasbord of lessons learned that can be applied across an organization.

It’s like a virtual stepping stone. Tackling desktop workloads in the enterprise is one area where you can test your meddle for what it takes to build a private cloud and you can do it today, for good reasons. At the same time, you can learn from the technical, financial and political challenges that go hand-in-hand with the development of a private cloud or the adoption of public off-premise cloud computing. I find the two painfully intertwined, even if the end-state is to have anywhere access to an elastic application that cares not for its VM master or the silly desktop you might access it from.

-LF