Tuesday, November 8, 2016

VMware Horizon Licensing

Many of the times, many of us get really confused by the different channels of communication of licensing.  In this case for VMware Horizon.

The most confusing part is always Named and Concurrent user license.  In my previously article on Horizon Suite, which is the current Horizon bundle, this has not change.

To keep things simple, I am going to put down the sources and wordings in case any of the sources ever get removed.

From VMware Product Guide, page 56 for Horizon Enterprise:

Active Connection: any connections to Powered On Desktop Virtual Machines, Terminal Services Sessions and physical computers.
Concurrent Users: the total number of users accessing or using the Software at any given time to maintain an Active Connection to their desktop through an endpoint device.
Named User: Your single designated employee or Third Party Agents who have been authorized by You to use the Software in accordance with the terms of this Agreement.


The confusion comes when the VMware Product Guide for other products that is part of Horizon bundle e.g. VSAN in page 14:

Concurrent Users: the total number of users accessing or using the Software at any given time.

Notice that this did not state the word "Active Connection".  This is why the meaning of concurrent get everyone confused.


This is how I will summarise the below:
Named User: The number of user that will be using the VDI from your Active Directory entries.
Concurrent Users: A total of active connections at any one time to the Horizon Connection server.

Note: This only applies to VMware Horizon licensing.  For 3rd party VDI on vSphere, this will be based on vSphere Desktop guideline.

Tuesday, November 1, 2016

VMware and AWS Partnership a Win-Win

Over the last few weeks of new over the announcement of VMware Cloud on AWS partnership.  This brings lots of attention to the IT market where two of the domain giant come together to make it bigger.

Why is this a Win-Win?  Let's take a look.

AWS

  • With the partnership, VMware will definitely lease the data centres spaces from AWS irregardless AWS doing well or not they got another constant revenue.
  • It make more sense to use AWS services e.g. S3 storage, etc. as your workload can be directly accessing it within AWS's Data Centre.
  • With VMware's partnership, it adds another valid reason for AWS's customer or VMware's customers to consider AWS external services and this brings business opportunities for AWS tapping into VMware's customers base.



VMware

  • Leverage on AWS's Data Centres, VMware can now achieve more public cloud offering around the world in terms of locations.
  • Able to leverage on AWS presence, VMware will allows customers to achieve the hybrid cloud vision mentioned since more than 4 years ago.



A bit of history of VMware public cloud strategy.

VMware started with VMware Service Provider Program (VSPP) few years back, however not many service providers pick up and the offering of VMware Cloud at different countries was not growing.

VMware in 2013 started vCloud Air, building their own data centers or co-locate with a partner but fully owned and operate by VMware.  This added questions is VMware competing with their VSPP.

VSPP was then rebrand to vCloud Air Network (VCAN).  This time round together with vCloud Air this expanded more locations but the growth didn't make it huge.  Was just better during VSPP time.

Now in 2016 with first IBM's Softlayer adopting VMware Cloud followed by AWS's partnership, VMware finally make its public cloud offering around the world accelerated in the greatest scale possible.

I am looking forward to see more customers able to adopt the use of VMware Cloud and having to finally truly fulfills the possibility of portability and mobile between private and public, a true hybrid cloud where at this part of the world, ASEAN, has never been made possible.

VMUG Singapore by VMware and HPE

If you are in Singapore, do remember to register for VMUG Singapore event sponsored by VMware and HPE. Look for the event details here . ...