Citrix announced today that they have acquired a Cloud control panel company called EMS Cortex. EMS Cortex makes a web-based cloud control panel that automates the provisioning of an array of Microsoft Products including Exchange, SharePoint, OCS, Web Hosting, SQL Server, DNS, RDS, Microsoft Dynamics CRM, and Hyper-V. The EMS Cortex control panel also automates the provisioning of Citrix XenApp applications and desktops. I am personally very excited about this news because I use Cortex in my current job at Xcentric.
What is EMS Cortex?
In a multi-tenant hosting environment, it is very important to have a strict provisioning routine to ensure consistency. EMS Cortex makes a web-based control panel to automate the provisioning process used in multi-tenant hosting environments. Cortex provisions Active Directory OUs, user accounts, groups, file shares, SharePoint sites, Citrix XenApp resources, etc. Through the use of Cortex, you no longer have to visit multiple consoles to provision users – just set up the user in Cortex and the rest is taken care of. This is good because Cortex removes the human error factor.
As I mentioned before, we use Cortex at Xcentric. Cortex is the centralized provisioning engine for our multi-tenant hosting environment. There are a lot of good things about Cortex and some things I wish I could change (I’ve already started talking with Cortex about the things I wish I could change). I’m hopeful that we, the community, will see even more Citrix-focused integration points in future releases.
How EMS Cortex Works
Cortex is a multi-tier application consisting of the following components:
- SQL Database – for configuration, users, customers, auditing and reporting.
- Web Services – for real time interaction with Active Directory and other hosted services.
- Provisioning Engine – via Microsoft Message Queue (MSMQ), provisioning requests are dispatched to the provisioning engine.
The Cortex web application is loosely coupled with the other Cortex components. This loose coupling provides several security benefits, as the web server has no dependency on Active Directory it can essentially operate outside of the managed domain. Cortex can also manage multiple domains.
Image source: http://ems-cortex.com/architecture/how-cortex-works.aspx
What will Citrix do with EMS Cortex?
Now, the things I’m about to share are purely off the top of my head and are not necessarily the direction Citrix intends on taking this product (although I hope they do).
Virtual Machine automation – ok, I kind of cheated on this one because Cortex already integrates with Hyper-V. But this automation is solely based on System Center Microsoft Virtual Machine Manager. So, it would be cool to provision VMs for XenServer and *gasp* VMware. SCVMM is somewhat sketchy with VMware ESX and vSphere and there is currently no SCVMM integration with XenServer (although, there were some screenshots of SCVMM and XenServer at Synergy last year – not sure where that is now). So, either SCVMM will have to amp up on vendor support or Cortex will need to go native API for vendors besides Microsoft.
Cloud bursting – this one goes along with the Virtual Machine automation. Citrix has been working with Amazon Web Services, SoftLayer, and even has their Citrix Cloud Center (C3). So, it would be cool to see some hooks built in for platforms like these. Imagine being able to provision an tenant in one of the vendor clouds instead of provisioning local resources.
Access Gateway Policy provisioning – Cortex provides a lot of self-service functionality for tenants. It would be cool to give tenants the ability to define Access Gateway policies tailored to their own needs without the help of a system administrator.
XenDesktop integration – currently, Cortex only supports hosted apps and desktops via XenApp. It would be nice to see integration with XenDesktop.
PowerShell – the current API for Cortex is a mixture of web services and a somewhat proprietary API for the MSMQ. It would be cool to see some PowerShell cmdlets to interface with the provisioning lifecycle.
Workflow Studio – Citrix Workflow Studio is all about infrastructure automation/orchestration. Wouldn’t it be cool if Workflow Studio has activities to create a user that utilized the Cortex provisioning engine? Workflow Studio already has an activity to create Active Directory users, but imagine an activity that used Cortex to create a user instead – thus provisioning all the other “stuff” like Exchange, SharePoint, file system, website access, etc. as well. That would be cool.
Storage provisioning – one piece that we still have to provision manually at Xcentric is dedicated storage for each tenant. It would be cool to see some kind of storage provisioning system – maybe pull in the StorageLink group?
Single tenant support – For the near term, the Cortex Cloud Control Panel will be offered as a standalone product on a subscription basis, as it was prior to the acquisition. Cortex is great for multi-tenant environments, but it is also very helpful in a single tenant environment. So, it would be cool to see Cortex rolled into one of the editions of XenDesktop or XenApp.
Postini integration – this is another feature that currently isn’t offered by Cortex. Granted, Google gives you a cool utility to sync users with LDAP directories, but it would be even cooler if Cortex worked with Postini API’s directly.
I could keep making this list for a while. Needless to say, I’m very excited about this acquisition.