So in practice it doesn’t matter if a VMware View customer has 1,000,000 powered on VMs. When you buy VMware View, the definition of "Powered On Virtual Desktop" then morphs into a powered on VMs that you have active connections to. When an enterprise buy vSphere Desktop licenses, it really is Powered on VMs (since there is no way for VMware to measure concurrency – VMware doesn’t have a broker here to monitor connection usage. However, the term "Powered On Virtual Desktop" machine can be a little bit confusing, especially in a ELA context. This aligns with what the standard licensing for VMware View is. On the VMware View Admin dashboard, under View Configuration, Product Licensing and Usage administrator will find the system usage reporting (above image) demonstrating the highest number of simultaneous active connections to VMware View desktops seen at any one time. Pricing, Licensing and Support help to define the context. A ELA may be different for each customer, however, typically VMware View measures licensing as number of concurrent powered-on desktops.Ī concurrent connection is defined as a powered on virtual desktop receiving a remote connection from a device or running locally on a device. Is VMware View licensed per median concurrency or maximum concurrency?īefore I go ahead it is important to clarify that a ELA defines a different license type for VMware View than the typical EULA.Should I use the numbers virtual desktop in my vSphere Clusters?.How should my enterprise be reporting VMware View usage?.This is not in any way an official response from VMware around licensing, and if you have any questions you should contact your VMware sales rep. This blog post is aimed to help you understand how to report VMware View usage under an ELA agreement. Customers under VMware ELA may deploy as many VMware products as they wish based on agreement and need to report usage back to VMware. Questions about VMware View licensing often appear in my radar, especially from customers under ELA.
0 kommentar(er)
