Changes to the Windows Server 2008 licensing policy
Keep sharing the good news! We make changes to the licensing policy (more precisely, our leadership in the United States). Thanks again to Andrei Beshkov for the news provided.
On January 16, 2009, licensing policy changes came into force that state the following: In case your Windows Server 2008 is used only as a virtualization platform, Windows Server 2008 CAL is not required.
Ps. CAL - client access liciense, that is, speaking in Russian, client license to connect to the server. About licensing Windows Server 2008 can be read here .
Let's look at the main scenarios for using Windows Server 2008 and how they will be affected by this change.
Scenario 1. A customer deploys Windows Server 2008 without the Hyper-V role.
No changes in licensing as for deployment in a physical environment. CAL for Windows Server 2008 is still needed.
Scenario 2. A customer deploys Windows Server 2008 Hyper-V to consolidate servers running Windows Server 2003.
For a physical server, CAL is not required. CAL required for the appropriate version of Windows Server (in this case, Windows Server 2003)
Scenario 3. Customer deploys Windows Server 2008 Hyper-V to consolidate servers running Windows Server 2003 and Windows Server 2008.
For a physical server, CAL is not required. Windows Server 2008 CALs are required for Windows Server 2008-based virtual servers. For Windows Server 2003 servers, you can use either Windows Server 2003 CALs or Windows Server 2008 CALs.
The official document from Microsoft in which it is described, everything I spoke about and to which you can refer if necessary is called the Volume Licensing Brief . In this document, look at the Client Access Licenses and External Connectors section, which says the following:
')
Most Microsoft servers require Client Access Licenses (CALs) and have optional optional external connector (EC). The CAL and EC are requirements. CALs are directly or indirectly.
You must not be able to find out what to do. In this case, it is being used solely to:
I. run hardware virtualization software,
Ii. provide hardware virtualization services, or,
Iii. run software on the licensed server.
However, it’s not a problem.
In addition, Windows Server 2008 doesn’t need to be authenticated or approved.
In the near future, the above changes will appear on the official Windows Server 2008 portal, in Product Use Rights documents and price lists of products.
I hope the news will be useful :)
On January 16, 2009, licensing policy changes came into force that state the following: In case your Windows Server 2008 is used only as a virtualization platform, Windows Server 2008 CAL is not required.
Ps. CAL - client access liciense, that is, speaking in Russian, client license to connect to the server. About licensing Windows Server 2008 can be read here .
Let's look at the main scenarios for using Windows Server 2008 and how they will be affected by this change.
Scenario 1. A customer deploys Windows Server 2008 without the Hyper-V role.
No changes in licensing as for deployment in a physical environment. CAL for Windows Server 2008 is still needed.
Scenario 2. A customer deploys Windows Server 2008 Hyper-V to consolidate servers running Windows Server 2003.
For a physical server, CAL is not required. CAL required for the appropriate version of Windows Server (in this case, Windows Server 2003)
Scenario 3. Customer deploys Windows Server 2008 Hyper-V to consolidate servers running Windows Server 2003 and Windows Server 2008.
For a physical server, CAL is not required. Windows Server 2008 CALs are required for Windows Server 2008-based virtual servers. For Windows Server 2003 servers, you can use either Windows Server 2003 CALs or Windows Server 2008 CALs.
The official document from Microsoft in which it is described, everything I spoke about and to which you can refer if necessary is called the Volume Licensing Brief . In this document, look at the Client Access Licenses and External Connectors section, which says the following:
')
Most Microsoft servers require Client Access Licenses (CALs) and have optional optional external connector (EC). The CAL and EC are requirements. CALs are directly or indirectly.
You must not be able to find out what to do. In this case, it is being used solely to:
I. run hardware virtualization software,
Ii. provide hardware virtualization services, or,
Iii. run software on the licensed server.
However, it’s not a problem.
In addition, Windows Server 2008 doesn’t need to be authenticated or approved.
In the near future, the above changes will appear on the official Windows Server 2008 portal, in Product Use Rights documents and price lists of products.
I hope the news will be useful :)
Source: https://habr.com/ru/post/49482/
All Articles