Synergy 2015 Keynote – Citrix Cloud Workspace 2


So today we got the Synergy 2015 keynote, delivered by the usual suspect, Mark Templeton. Here I am at 3:26am in the morning after a couple beers and scotch I had a couple hours ago with old time pals like Shawn Bass, Harry Labana, Ron Oglesby and Michel Roth. Great night and tons of interesting discussions.

After all that I decided to give you my thoughts on what I think is the most important announcement from today’s keynote, the Citrix Cloud Workspace (CCW). Before I go any further let me tell you upfront that my view has nothing to do with the cloud at this stage and that I truly believe the way to go right now is to actually forget about the cloud for a moment. And you will understand why.

For that to happen we must take a look at what Microsoft announced a couple weeks ago: the Azure pack. If you do not know what that is, in a nutshell, it is on-premises Azure. You bring it in-house and now you use the exact same tools/procedures to create your infrastructure on-premises as it would be done off-premises, in the cloud. Why is that important?

First, it eliminates the distinction between on-premises and off-premises as you do things the exact same way, no matter where your stuff is running. That means if one day for whatever reason you decide the cloud is the way to go you already know everything on how to get there. You just point whatever automation/procedures you have to a different container, the cloud. Done.

Secondly, it gives a taste of the cloud to anyone that at this stage will not go for it. It plants the seed on everyone’s head about Azure, showing on-premises how the whole thing works. Without going off-premises.

Finally, everything around the cloud revolves around heavy automation. Many things happen in background, with IT not even really aware of what is going on to get you where you need to be. What I mean by that is, as an example, when I deploy a new application on Azure RemoteApp (ARA) with my custom image (my 2012R2 box with the apps I want to be available), I do not see exactly how Microsoft is actually doing it on Azure. Not that I care. As long as I end up with my apps there and assigned to the users that need them, I am good. The end result is indeed a huge simplification on how we build infrastructure and also how quick we do it. Night and day difference, not to mention the great reduction on human errors as the whole procedure is automated and you barely see it.

Take what I just said and look at Citrix Cloud Workspace. As of today I can have all the backend stuff up there and point all to my XenApp/XenDesktop on-premises. But that is not where the value is IMHO.

If Citrix brings CCW on-premises, I can now deploy my whole XenApp/XenDesktop environment in a heavily automated way. In a couple clicks I can have a PoC up and running for 500 people. The simplification between front end components (RDS Session Hosts, VMs with the VDA, etc) and the backend (StoreFront, DDCs, Databases, Domains) is huge thanks to the connector architecture in use. And again, this erases the line between on-premises and off-premises. If one day you decide you should burst to the cloud or move all up there, everything you have done on-premises is EXACTLY the same thing you would do in the cloud. No more distinction.

This is where Citrix has to go with CWC IMHO. Make the product completely location agnostic, working the exact same way and with the exact same connector no matter if on-premises or off-premises. This will greatly help with multi-domain authentication, SQL connectivity and so on.

This is the way to go moving forward with any solution actually, Citrix or not.

I hope VMware is reading this.

CR

2,098 total views, 2 views today


Leave a comment

Your email address will not be published. Required fields are marked *

2 thoughts on “Synergy 2015 Keynote – Citrix Cloud Workspace

  • Shaun Ritchie

    Interesting read but I think one reason Citrix will probably never do this is that WorkSpace Cloud control plane is split between AWS and Azure (can’t remember the exact details of what is where and why). Whereas Azure is all based on standard MS infrastructure which is all available to customers on prem, AWS is obviously not a portable infrastructure so parts of the CWC control plane would have to be redesigned to make this work.

    • crod Post author

      If this was written abstracting things like the underlying cloud it attaches to, there is no reason it would be hard to port this to an Azure like only solution that would tie easily into an infrastructure with the Azure Pack. I cannot comment on the internals but I can bet this would be very easy to port to an on-premises only solution.