Van de Miscrosoft site
The following restrictions on FPP licensing apply to VDI scenarios:
1.Each FPP license permits use of only a single VM per user. Hence, each VM needs its own licensed copy of Windows for VDI. For users
that need access to multiple VMs, this may prove expensive.
2.Multiple simultaneous users cannot share VMs, as each VM licensed with an FPP copy of Windows needs to be assigned to one user at a time.
3.The FPP licensed VM can only exist on a single computer at any given point of time. If you have to move the VM to another server, it
has to be completely moved off the original machine.
Er worden nu dus ipv op hardware gebaseerde licenties, opeens per user licenties gevraagd. Aan een kant wel logische omdat alles op dezelfde hardware draait (de server/cluster) maar gaat wel tegen hun eigen licentiemodel in wat jarenlang gehanteerd is. (niets zo lastig als krampachtig vasthouden aan 'oude' verdienmodellen...
Nu is Microsoft niet de eenvoudigste als het gaat om inzichtelijke licentievoorwaarden, maar ze bedenken in ieder geval wel een model voor (ver)nieuw(end)e technieken. )
Ik lees nog even verder in de license agreement en dat beperkt de boel nog wat verder en is wellicht waar je op doelt:
IMPORTANT USE RIGHTS FOR VIRTUAL DESKTOP LICENSING
Term of License
Windows VDA is a subscription only model, as it offers the desktop-as-a-service similar to other software-as-a-service offerings.
However, there is no Service Provider License Agreement (SPLA) available for virtual desktop licensing. Windows VDA is coterminous
with your license agreement, meaning that the subscription that is entered into cannot be terminated early. If a customer is currently
already licensed on a subscription based license agreement like Enterprise Agreement Subscription the virtual desktop licensing can be
purchase mid-life and will terminate with the parent agreement.
Windows VDA is non-perpetual, which means you may not access your virtual desktops through the licensed device if the
corresponding Windows Software Assurance coverage or the windows VDA term expires.
Assigning Windows VDA to a device:
Before the user can access their virtual desktop, they must assign their Windows VDA license to a device. Devices can be defined as thin
client, employee owned machine, corporate owned machine not covered by Software Assurance, a hardware partition or blade
computer. Reassignment of the Windows VDA license to another device is possible only after 90 days of the last assignment of that
license. The exception is that you may reassign your license sooner if you retire the licensed device due to permanent hardware failure.
Licensing Windows for Virtual Desktops
Extended Roaming Rights in Windows VDA
The single primary user of the corresponding Windows VDA licensed device may access their virtual desktop from any other device that
is not owned or affiliated with their organization. This adds great flexibility to the Windows VDA license, enabling the single primary
user to roam on devices such as home PCs, hotel kiosks, internet café’s etc. However, this use right is only valid for the primary user of a
licensed windows VDA device at work. If the Windows VDA device does not have a primary user (such as a shared terminal on a shop
floor), then this use right does not apply.
Note: roaming rights are only applicable to devices not owned or affiliated with the organization. If a user is roaming within their
corporate network, then all devices that will be used to access virtual desktops within the corporate network will need to be licensed
either through Windows client SA, or with a separate Windows VDA license.
Misshien is het dan toch kosten effectiever om naar een ander DaaS OS om te gaan zien...
[Reactie gewijzigd door robb_nl op 24 mei 2011 10:05]