Лицензирование Windows 10 в среде VMware Horizon 7

Мы проводим исследование, касающееся возможного использования VMware View.
Если Вам интересна информация о том, как наиболее выгодно использовать VMware View, обосновать эффективность применения VDI в Вашей компании, Вы можете поучаствовать в исследовании и получить отчет по результатам.
Заполнение опросников займет 1-2 минуты. Принять участие.

Полезные ссылки

Основной принцип лицензирования Windows 7 или Windows 10 в среде VMware Horizon 7 , равно как и в решении VDI на базе других производителей программного обеспечения, следующий:

Лицензироваться должно право доступа к операционной системе Windows 7 или Windows 10 , установленной на виртуальном рабочем столе.
При этом приобретать лицензии на Windows 7 или 10 , установленные на виртуальных рабочих столах не надо.

Если доступ к виртуальному рабочему столу происходит с рабочей станции, работающей под управлением Windows с действующим контрактом Software Assuarance, лицензия на право доступа к виртуальному рабочему столу на такое устройство не требуется.

Виртуальным рабочим столам, использующим серверные ресурсы серверов под управлением Windows Server (или других программных продуктов, требующих лицензии CAL), требуется лицензия Server CAL.
Лицензия может быть приобретена на устройство или на пользователя. Лицензия CAL, приобретенная на пользователя распространяется и на физическую и на виртуальную среду.

Лицензирование Windows 7 или 10 при миграции с Windows XP на физических рабочих станциях (без использования виртуальных рабочих столов)

Исходные данные:
Имеется 100 рабочих станций с Windows XP.
Рабочие станции Windows XP не покрыты контрактами Software Assurance.
Необходимо мигрировать физические рабочие станции на Windows 7 или на Windows 10 .

Необходимо купить:
Чаще всего политика компании предусматривает замену рабочих станций после пяти лет службы.
Исследования показывают, что для успешной миграции на Windows 7 в этом случае потребуется обновить (заменить) порядка 25% рабочих станций.

Необходимо для 75% ( 75 штук) приобрести обновление лицензий Windows 7 , 25% ( 25 штук) рабочих станций будут новые и могут закупаться с лицензиями OEM.
К лицензиям OEM можно приобрести Software Assurance в течение 90 дней с момента покупки рабочих станций (в нашем примере Software Assuarance приобретаться не будет).

Итого:
Нам понадобятся: 75 лицензий Windows 7 , 25 OEM лицензий Windows 7 , 25 новых рабочих станций.
75 лицензий Windows 7 — $250 x 75 = $18750 ;
25 рабочих станций с OEM Windows 7 — $800 x 25 = $20000 ;

Всего: $38750

Чтобы получить расчет миграции на Windows 10 , отправьте запрос на нашу почту .

Лицензирование Windows 7 или Windows 10 при миграции с Windows XP на виртуальные рабочие столы.

Исходные данные:
Имеется 100 рабочих станций с Windows XP. Рабочие станции Windows XP не покрыты контрактами Software Assurance. Необходимо мигрировать на виртуальные рабочие столы.

Необходимо купить:
Виртуальные рабочие столы будут располагаться на одном или нескольких физических серверах под управлением гипервизора ESXi.
Предварительно можно освободить часть серверов, консолидировав физические сервера (виртуализировав их). От 50% до 60% серверов при консолидации окажутся свободными, и мы сможем использовать их для виртуализации рабочих столов.
Мы не будем касаться вопросов консолидации и виртуализации в данном разделе.
Исчерпывающую информацию можно найти по ссылке Консолидация вычислительных ресурсов.

Необходимо купить на каждую физическую рабочую станцию лицензию на право доступа к виртуальному рабочему столу — VDA ( 100 штук).
Для организации самих виртуальных рабочих столов необходимо использовать VMware Horizon 7 .

Итого:
Нам необходимо приобрести 100 лицензий VDA.
100 лицензий VDA — $100 x 100 = $10000 (в год);
100 лицензий VMware Horizon 7 — $30000 ;

Всего: $40000

Как видно из примеров, сумма, необходимая для миграции на физических рабочих станциях и на виртуальных рабочих столах, практически одинаковая.
На второй и в последующие годы придется продлевать лицензии VDA.
Но затраты на продление с лихвой компенсируются преимуществами VMware Horizon 7 .

Мы рассматривали только лицензирование.
В следующих статьях мы определим основные шаги по миграции, предложим методы оптимизации миграции и дальнейшего администрирования и оценим временные затраты.

А пока, самое время определить, в чем Управление виртуальными рабочими столами в VMware Horizon|VDI VMware.
По мере накопления данных, мы сможем сказать, насколько снизятся расходы, на управление рабочими станциями, а пока заметим, что только лишь возможность централизованного резервного копирования почти полностью отыгрывает разницу в цене между физическими и виртуальными рабочими столами.

Свяжитесь с нами удобным Вам способом:
e-mail: vmware@v-grade.ru, тел.: +7(495)662-58-98
Так же Вы можете задать нам вопрос или оставить заявку, используя форму чата в нижнем правом углу экрана.

Мы приложим максимальные усилия, чтобы обеспечить Вас самой передовой информацией по лицензированию и предложить адекватный уровень цен на лицензии и поддержку VMware.

Конфигуратор VMware vSphere

Консолидация серверов

question

Windows Server 2019 Datacenter licensing for VMware?

If you have VMware for hypervisor, and you have a bunch of Windows Server guests on VMware, how many licenses of Windows Server 2019 Datacenter do you need? Is it one per host server? or one per processor per host server? If i had seven host servers and two procs each server, would i need 14 Datacenter licenses?

Just checking in to see if the information provided was helpful.

If the reply helped you, please remember to mark it as an answer.
If no, please reply and tell us the current situation in order to provide further help.

2 Answers

Licensing is the same regardless of the hypervisor being used. Licensing is based on host core count.

Each host needs to be licensed.

A minimum of 8 core licenses is required for each physical processor and a minimum of 16 core licenses is required for each server.

Core licenses are sold in packs of two.

Standard Edition provides rights for up to 2 Operating System Environments or Windows Servers containers with Hyper-V isolation when all physical cores in the server are licensed. For each additional 1 or 2 VMs, all the physical cores in the server must be licensed again.

DataCenter Edition provides rights for unlimited Operating System Environments or Windows Servers containers with Hyper-V isolation when all physical cores in the server are licensed.

AVMA keys can be used only when the host is DataCenter edition

—please don’t forget to Accept as answer if the reply is helpful—

Vmware and windows licensing

Licensing Policies

VMware License Transfer and Account Change Processes

On this page, we explain the different processes which apply to the following scenarios:

• You wish to transfer ownership of the license to a third party (“ License Transfer”); or
• You wish to amend VMware’s records to reflect a data entry error or a change in your account details (“ Account Change”).

1. VMware License Transfer

VMware operates a strict policy on license assignment and transfers. VMware’s software license grant to the customer is personal to that customer (ie, the license is not transferable to a third party – a “third party” being any entity (including a related entity) which is not recorded in VMware’s systems as being the authorised licensee of the software licenses in question). As VMware’s software license grant is personal to the customer, transfer requests may be approved or declined by VMware at VMware’s sole discretion. That said, requests which fall under the following categories will be considered favorably:

• Acquisition, merger or divestiture
• Sale of assets due to bankruptcy
• Start of an IT outsourcing arrangement
• Termination of an IT outsourcing arrangement
• Change in government machinery
• In-region corporate group restructures

VMware will also have regard to the terms of your contract if the transfer of licenses was contractually agreed between the parties, as well as any applicable laws which prohibit VMware from restricting the transfer of licenses.

For further information relating to the above, please refer to the VMware License Assignment & Transfer Policy.

2. VMware Account Change

VMware allows changes to customer account details in certain instances. Valid reasons for account changes include:

• Customer has changed its company name, other than as a result of a merger or acquisition, and the old company name no longer exists
• VMware data entry errors
• VMware channel partner data entry errors
• Customer wishes to combine duplicate Entitlement Accounts under one Entitlement Account
• Customer wishes to separate its licenses into two separate Entitlement Accounts (each to be held in the name of the same legal entity)

In order to effect the changes in 1 or 2 above, please contact your Customer Support representative (ph: US English Language Support: 877 486 9273 (Local Toll Free: 650 475 5345), or for international phone numbers please see https://www.vmware.com/support/us_support.html, or file a service request online by logging in to My VMware and selecting Get Support from the Quick Links menu). Our support representatives will (i) make a preliminary assessment regarding the validity of your request, (ii) identify the required supporting documentation (if any) and (iii) seek required approvals; in order to process this request.

For more information about filing a Support Request, see Filing a Support Request in My VMware (2006985).

Vmware and windows licensing

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

I have 3 Vmware ESx physical servers running various guests with different OS versions.
I need understand how 2019 licensing works if i need to install one 2019 Datacenter VM on one of them.
— Do i have to buy one license for the CPU where i’ll install the 2019?
— What if i need to move that 2019 VM between those machines?
— What if the ESXi machine where i move the VM has more CPU than the original one?
— What if i need to build a second VM on the same server runnnig the first one?
— If i need to move one of the 2 2019VM to another server, do i have to buy another CPU license?

Answers

You’ll need to license each physical host according to core count and the max number of VMs that could be on it even for one second. In the case of DataCenter licenses the VM count is not an issue. You can only use AVMA activations when you install a DataCenter host. In your case (ESXi) just reuse the same key to active virtual machines on that host.

• A minimum of 8 core licenses is required for each physical processor and a minimum of 16 core licenses is required for each server.
• Core licenses are sold in packs of two.
• Standard Edition provides rights for up to 2 Operating System Environments or Windows Servers containers with Hyper-V isolation when all physical cores in the server are licensed. For each additional 1 or 2 VMs, all the physical cores in the server must be licensed again.

Regards, Dave Patrick .
Microsoft Certified Professional
Microsoft MVP [Windows Server] Datacenter Management

Disclaimer: This posting is provided «AS IS» with no warranties or guarantees, and confers no rights.

License Microsoft Windows Server in a VMware environment – Part 1

Last week I had another nice discussion around the 90 day assignment rule for Windows Server licensing on a VMware environment. To answer this shortly: You may move running instances between licensed servers without acquiring additional licenses. However you cannot exceed the maximum number of instances each server is licensed to run.

Microsoft Operating System Environments (OSE)

Microsoft defines Operating System Environments for allocating licenses. This is a nice and flexible way to accommodate customer demand. To understand how licensing works under virtualization, it is important to understand how Microsoft defines an OSE.

An “operating system environment” is:

1 all or part of an operating system instance, or all or part of a virtual (or otherwise emulated) operating system instance which enables separate machine identity (primary computer name or similar unique identifier) or separate administrative rights, and

2 instances of applications, if any, configured to run on the operating system instance or parts identified above.

Microsoft makes a distinction between physical and virtual. A physical operating system environment is configured to run directly on a physical hardware system. The operating system instance used to run hardware virtualization software (for example, VMware) or to provide hardware virtualization services (for example, VMware) is considered part of the physical operating system environment. A virtual operating system environment is configured to run on a virtual (or otherwise emulated) hardware system. A physical hardware system can have either or both of the following:

• one physical operating system environment and one or more virtual operating system environments

When running Windows on a VMware environment you will have multiple virtual OSE’s running on top off for instance VMware ESX.

The breakeven point of licensing VMs

Windows 2008 comes in several products and licensing opportunities.

(1 Processor)
€ 2.999,-

A CAL is roughly about $ 40,- (All retail prices) For keeping this simple I won’t take the CALs into account and will blog about it in a blog post later on.

When comparing the above licenses, when implementing a VMware virtual environment with servers containing 2 Quad core processors (or higher, more core density) it is best to use Datacenter licenses if it is mostly a Microsoft infrastructure running.

2p * 2.999, = $ 5.999,-

We found that 7 VMs is the breakeven point to switch to Datacenter edition licensing. If the virtual environment is going to run more than 7 virtual machines on top of an ESX server, Datacenter licensing is the way to go.

Some real life cases

We use Microsoft Enterprise licensing for ESXi servers running 4 virtual XenApp servers and we use Microsoft Datacenter licensing for most of the environments we have build. Often running with 16 or more Virtual Machines on top of an ESX server, makes the licensing cost per virtual machine 4.510,- / 16 = 282,-

Things you should know about Datacenter licensing

• Servers with Windows Server Standard or Enterprise licenses covered by Software Assurance can be “stepped up” to a Windows Server Datacenter Edition processor license to take advantage of its unlimited virtualization rights.
• The 64-bit version of Datacenter Edition can be licensed for 128-way systems, with each partition capable of supporting a maximum of 64 processors.
• You may not run instances of Datacenter on a server with less than two processors.

Note that partitioning of a Datacenter system is supported logically at a licensing level and physical level. In other words, you are not required to obtain more Datacenter Edition server licenses than the total number of processors on that server ( 2 processor minimum ).

Licensing for Peak Capacity

An ESX server running virtual OSE’s must have assigned licenses equal to or exceeding the number of running instances. You need to be aware and look sharp on the peak capacity running on the ESX server, with HA and DRS check how many instances could be running/landing on an ESX server. For instances a VMware cluster of 3 ESX servers all running 8 virtual OSE’s in normal production, will run 12 virtual instances on 2 ESX servers when in maintenance mode or when a HA failure is detected. So every ESX server must have 12 Windows 2008 Standard licenses assigned or 3 Windows 2008 Enterprise server licenses or must have 2 Windows 2008 Datacenter licenses assigned.

Myths and Answers

There is a lot of Fear Uncertainty and Doubt (FUD) out in the field around the whole licensing Microsoft Products on a VMware environment. So will bust the most common myths out there.

Myth: You may not move a virtual Windows server from 1 ESX server to another ESX server within 90 days.

‘For Windows Server software, except in a few cases (see “Assignment of Licenses” above), licenses may only be reassigned to new hardware after 90 days. This, however, does not restrict the dynamic movement of virtual OSEs between licensed servers. As long as the servers are licensed and do not simultaneously run more instances than the number for which they are licensed, you are free to use VMotion and System Center Virtual Machine Manager to move virtualized instances between licensed servers at will’

Myth: You do have to license every template and non-running virtual machines stored on the SAN.

Answer: You only need to license the servers running the workload, so not templates standby servers or disaster recovery machines on an other site. As long as they don’t run any load.

If a server is licensed, then stored or non-running instances of Windows Server and other Microsoft servers do not require separate licenses. The use rights permit you to store any number of instances under each license. You can also store instances on a large storage area network (SAN) or store instances on your servers without needing additional licenses for each instance. (See also page 2 of the Licensing Brief Microsoft Windows Server 2008 to Run with Virtualization Technologies)

Myth: I cannot run Windows 2003 anymore or I need to acquire special licensing to run Windows 2003/8 standard edition.

Answer: In place of the licensed version, you may run prior versions or lower editions in any of the OSEs of the licensed server. For example, if you have a server licensed for Windows Server 2008 Enterprise, you may run instances of Windows Server 2008 Standard or Windows Server 2003 R2 Enterprise Edition or Windows Server 2003 R2 Standard Edition in any of the allowed five instances on the server. As an extension of the above rights, you may also run prior versions of lower editions. You may not run more instances on the server than your licenses allow. (See also page 4 of the Licensing Brief Microsoft Windows Server 2008 to Run with Virtualization Technologies)

Conclusion

I must say the last year Microsoft went from the bad boy on the block of virtual environments to the good guys, helping their customers out with redesigning licensing around their products for virtual environments. Next to come is the VECD licensing that will be shifted into SA or you can buy a special Windows Virtual Desktop Access (Windows VDA) costing $100 per year per device and aimed at organizations who are using endpoints that do not have a Windows SA license.

• As long as the servers are licensed and do not simultaneously run more instances than the number for which they are licensed, you are free to use VMotion to move virtualized instances between licensed servers at will.
• You are allowed and may downgrade to a prior version like for example Windows 2003 if needed.

You won’t have any problems with the 90 day reassignment rule of Windows licenses, if you make sure you have the proper licensing in place for the physical VMware boxes.

Links and Sources

Good source of information regarding the subject are the Microsoft Licensing Briefs you can find here:

Product	Maximum permitted running virtual instances	Price
Windows Server 2008 Standard (+10 CALs)
Windows Server 2008 Enterprise (+25 CALs)
Windows Server 2008 Datacenter (no CALs)