Microsoft OEM Licensing-Windows Server
Microsoft OEM Licensing-Windows Server
Table of contents
Licensing.................................................................................................................................................................................2
Differences between license types .....................................................................................................................................5
I’ve got an OEM license—now I need to know… ...............................................................................................................5
Activation................................................................................................................................................................................8
Support ................................................................................................................................................................................ 14
Microsoft Software Assurance.......................................................................................................................................... 16
Downgrade rights............................................................................................................................................................... 16
Upgrade rights .................................................................................................................................................................... 19
Virtualization and OEM licensing ...................................................................................................................................... 19
Standard Edition for Windows Server 2012 and Windows Server 2012 R2 .............................................................. 21
Datacenter Edition for Windows Server 2012 and Windows Server 2012 R2 ........................................................... 23
Windows Server 2008 R2 Datacenter Edition ................................................................................................................ 23
Server Manager in Windows Server 2012 and Windows Server 2012 R2 .................................................................. 24
Client access licenses ........................................................................................................................................................ 24
Remote Desktop Services CALs........................................................................................................................................ 27
Reseller information .......................................................................................................................................................... 29
References .......................................................................................................................................................................... 30
Welcome to HP’s FAQ document for Windows® Server OEM OS products and Microsoft® OEM application solutions on HP
ProLiant servers. This guide answers many of the questions our customers ask about licensing Windows Server products on
their HP ProLiant server systems. The questions we encounter mostly center on three general categories; products,
activation, and support—which we’ve used as the structure of this document.
We will review basic Windows Server licensing and differences between license types. In addition, these topics are covered:
• Customer questions focused on “I’ve got an OEM license—now I need to know…”
• Activation and Support
• Microsoft Software Assurance, downgrade rights, and virtualization with OEM licensing
• Specific product questions for Active Product Families
• Client access licenses (CALs) and Remote Desktop Services (RDS) CALs
• Reseller questions
Licensing
1. What types of Windows Server licenses are available?
In general, Microsoft Server software licenses fall into three categories: volume licensing, OEM licensing, and retail licensing.
Retail licenses, are generally sold pre-packaged in a box, they may be the most expensive and the most complete, and
customers are usually home users or small businesses. OEM licenses are available from HP when buying a new computer,
and typically offer the best price, and HP Support Services are available for your OEM license. Microsoft volume licenses are
available from Microsoft licensing resellers, including HP Software Licensing and Management Solutions (SLMS) in many
countries. Volume licenses generally cost more than OEM licenses, but may be purchased separately from hardware and
offer additional flexibility for larger companies with more complex IT requirements. The rest of this FAQ will focus on HP
OEM licenses. For additional information about Microsoft Retail or Volume Licensing, refer to microsoft.com/licensing.
Microsoft license options From HP factory (preinstall and From HP authorized distributor and
non-preinstall) (OEM) HP Reseller Option Kit (ROK)
Terms and restrictions HP OEM or ROK license may only be marketed and sold to an end user along with a new HP
ProLiant server.
End user cannot move OEM licenses from the server (unless Microsoft Software Assurance is
added). Note that an HP OEM license is covered by the same HP warranty or service terms that
cover the HP ProLiant server which it accompanies.
Microsoft Software Available; must be purchased separately from an authorized Microsoft licensing reseller (such as
Assurance available? HP SLMS) within 90 days of initial license purchase. Important to highlight that only licenses for the
latest version of a product are eligible for Software Assurance.
2
Technical white paper | HP FAQ for Microsoft OEM licensing—Windows Server
Operating systems
• Windows Server 2012 R2 Foundation, Essentials, Standard, and Datacenter Editions: hp.com/go/ws2012R2
• Windows Server 2012 Foundation, Essentials, Standard, and Datacenter Editions: hp.com/go/ws2012
• “Additional licenses” for Windows Server 2012 Standard—Each HP OEM license for Windows Server 2012 Standard and
Windows Server 2012 R2 Standard support up to 2 physical processors and up to 2 concurrent Windows Server virtual
machines (VMs). “Additional licenses” may be added to a server to support more processors and/or more concurrent VMs.
Windows Server 2012 Standard Additional Licenses apply for Windows Server 2012 R2 Standard.
• “Additional licenses” for Windows Server 2012 Datacenter—Each HP OEM license for Windows Server 2012 Datacenter
and Windows Server 2012 R2 Datacenter support up to 2 physical processors and an unlimited number of concurrent
Windows Server VMs. “Additional licenses” may be added to a server to support more processors. Windows Server 2012
Datacenter Additional Licenses apply for Windows Server 2012 R2 Datacenter.
• Windows Server 2008 R2 Foundation, Standard, Enterprise, and Datacenter Editions: hp.com/go/ws08r2
4. How many CALs are included with each HP OEM Windows Server license?
CALs per license type are as follows:
• Windows Server 2012 R2 Foundation, Windows Server 2012 Foundation, and Windows Server 2008 R2 Foundation
support up to 15 users, and do not require Windows Server CALs.
• Windows Server 2012 R2 Essentials and Windows Server 2012 Essentials support up to 25 users, and do not require
Windows Server CALs.
• Windows Server 2012 R2 and Windows Server 2012 Standard and Datacenter Editions come with zero CALs. Windows
Server 2012 CALs are available separately and are required for each user or device that accesses Windows Server 2012
R2 or earlier.
• Windows Server 2008 R2 Standard Edition comes with five Windows Server 2008 CALs. Additional Windows Server 2012
CALs (which also work with Windows Server 2008 R2) are available separately.
• Windows Server 2008 R2 Enterprise Edition comes with either 10 or 25 Windows Server 2008 CALs, depending on the kit.
Look for “10 CAL” or “25 CAL” in the description. Additional Windows Server 2012 CALs are available separately.
• Windows Server 2008 R2 Datacenter Edition comes with zero CALs. Windows Server 2012 CALs are available separately.
• Windows Small Business Server 2011 Standard and Premium Add-on became end of sales on December 31st, 2013. Only
Small Business Server 2011 CALs are available from HP.
3
Technical white paper | HP FAQ for Microsoft OEM licensing—Windows Server
If you received your OEM OS from a reseller, the COA should have been affixed to a new server by the reseller. OEM COAs are
tied to the hardware with which they were purchased and cannot be transferred to another system unless you purchase
Microsoft Software Assurance for the OEM license, in which case you have the same reassignment rights that apply to a
Microsoft volume license for the product. Note that an OEM OS is considered part of the new server on which it is delivered,
so it is covered by whatever HP warranty applies to the new server.
6. What exactly comes inside each of these kits for each license type?
4
Technical white paper | HP FAQ for Microsoft OEM licensing—Windows Server
The ROK is available only to resellers from HP authorized distributors. This kit provides the value of an HP OEM license for
the customer, along with the additional services and/or products that most HP channel partners offer to our customers.
5
Technical white paper | HP FAQ for Microsoft OEM licensing—Windows Server
10. My server was dead on arrival (DOA). I purchased an OEM Windows Server license
from HP with the server—what do I do?
The HP OEM license is effectively part of your server, so it is covered by the same warranty terms. If, for example, you end
up requiring a replacement server under warranty, the replacement server will also come with the same HP OEM license
(and the original HP OEM license would go back to HP when you return the DOA server).
14. Can I convert an evaluation copy of Windows Server 2012 to fully licensed product?
Yes, first verify the OS current installation; run from an elevated command prompt: DISM /online /Get-CurrentEdition
(current edition will typically include the word eval along with the normal product name)
Run DISM /online /Get-TargetEditions (The results should show the products the current installation can be
converted/upgraded to)
Run DISM /online /Set-Edition:<edition ID> /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula (For the
edition, type in what was returned in the Get-CurrentEdition command. The command will set the edition type, inject the
appropriate product key, and accept the EULA in a single command. Server will reboot.)
6
Technical white paper | HP FAQ for Microsoft OEM licensing—Windows Server
17. If I “retire” a server with an OEM license on it, can I use that software on a new
server?
No. To put it simply, an OEM product is “married” to the original server on which it was installed. OEM licenses are not
transferable from one machine to another, unless covered by Microsoft Software Assurance. The software cannot be moved
from server to server, even if the original server it was installed on is no longer in use. This is true for all OEM software—
both OSEs and applications. Note that OEM CALs are different: they must be associated with a single user or device, but the
license owner may change that assignment if, for example, an employee or device is replaced.
18. What ProLiant Support Packs (PSPs) and HP SmartStart work with which Windows
OS?
PSPs are end of life (EOL) as of June 2012 and HP SmartStart is also EOL and was delivered only on G7 and earlier HP
ProLiant ML and DL 300, 500, and 700 series servers and on enclosures for HP ProLiant BL G7 and earlier servers.
SmartStart has been replaced by HP Intelligent Provisioning (hp.com/go/intelligentprovisioning) for HP ProLiant Gen8
servers. HP Intelligent Provisioning (HP IP) provides a server provisioning tool that eliminates media and time-consuming
effort and all needed drivers and software tools are pre-loaded onto ProLiant Gen8 servers. HP IP recognizes if system
software is out-of-date and automatically downloads the latest version updates direct from the Internet.
19. Where can I find drivers and firmware for my Windows-based server?
Drivers and firmware are found in two places:
• Drivers and firmware listed by OS version are loaded in the HP Support Center (HP SC) at hp.com/go/hpsc for each server
and option, and are listed as “Support and Drivers” in right-hand navigation bars.
• The SPP, which is a comprehensive collection of firmware packages for servers, controllers, storage, blades, and
enclosures, as well as system software components (drivers, agents, and utilities), is all tested together as a bundled set
for an extended cycle. HP SUM deploys all of these firmware and software components. The SPP contains the features,
functionality, and contents of the former HP Smart Update Firmware DVD and the PSPs, and has an extensive portal
containing all the valuable information you will need to make an informed decision.
– More information can be found at this link for HP SPP at hp.com/go/spp.
– It is available for download at hp.com/go/spp/download.
– Extensive server support guides exist at its documentation page at hp.com/go/spp/documentation.
20. How is Windows Server 2003 supported; for example, is it included in the SPP?
Windows Server 2003 is not supported in the SPP, and Microsoft has discontinued its hardware certification program for
Windows Server 2003. Microsoft originally sent out certification discontinuation notices to server manufacturers on
December 31, 2009, and then extended certification to July 13, 2010, which was well before the SPP timeframe. In addition,
Windows Server 2003 has been on extended support from Microsoft since July 2010, and Microsoft will end all support for
Windows Server 2003 in July 2015. Details on Microsoft’s discontinuation of hardware certification for Windows Server 2003
can be found at the following Microsoft website: microsoft.com/whdc/whql/resources/news/whqlnews_020210.htm.
Details about Microsoft support lifecycle for Windows Server 2003 or other Microsoft software products may be found at
microsoft.com/lifecycle.
7
Technical white paper | HP FAQ for Microsoft OEM licensing—Windows Server
Activation
21. How do I activate Windows Server 2012?
To activate the current key installed into the OS:
Right-click Computer.
Click Properties.
Click View details in Windows Activation.
Click Activate.
8
Technical white paper | HP FAQ for Microsoft OEM licensing—Windows Server
9
Technical white paper | HP FAQ for Microsoft OEM licensing—Windows Server
23. If HP Intelligent Provisioning was not used to preactivate my OEM OS, then how do I
activate it using the product’s user interface?
Windows Server 2008 R2:
To get to the Windows activation screen, right-click Computer. Then click Properties. Depending on the OS version, the
screens you then see will resemble these.
Click Activate Windows now.
10
Technical white paper | HP FAQ for Microsoft OEM licensing—Windows Server
This brings up the Windows activation screen. From this screen, choose Type a different product key. (This is found on the
COA label that should be adhered to your server.)
Type in your product key and follow the prompts. Your license should then be activated.
11
Technical white paper | HP FAQ for Microsoft OEM licensing—Windows Server
In the Windows activation box, type in the product key. (This is found on the COA label that should be adhered to your
server.) Then click Activate.
24. What is my password set to for Windows Server 2008 R2, Windows Server 2012, or
Windows Server 2012 R2?
If you have purchased Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2 preinstalled, you will be
required to provide a password during the initial interview process. If you installed Windows Server 2008 R2, Windows
Server 2012, or Windows Server 2012 R2 from media, then you are required to provide a password before your first logon.
Please set a password that is easy for you to remember, but hard for a stranger to figure out. The best passwords are at
least eight characters long and include a mix of letters, numbers, and special characters.
12
Technical white paper | HP FAQ for Microsoft OEM licensing—Windows Server
26. What do I do if my activation grace period is running out and I am having trouble
activating my product key?
Windows Server 2012 and Windows Server 2012 R2 no longer have an activation grace period. You need to provide a valid
product key for the Windows Server you are attempting to install during setup/out-of-box-experience, and the OS will
automatically try to activate the product key. If the activation attempt fails (no Internet connection or invalid product key),
the OS will simply continue to prompt the user for activation including the option to provide a different product key.
Any version of Windows Server 2008 R2 software will require activation within 10 days. The 10-day activation period can be
reset up to four times by running the slmgr.vbs script to reset it back to 10 days. To do this, follow these steps:
1. Click Start, and then click Command Prompt.
2. Type slmgr.vbs -dli, and then press Enter to check the current status of your activation period.
3. To reset the activation period, type slmgr.vbs –rearm, and then press Enter.
4. Restart the computer.
This procedure resets the activation period to 10 days, and can be used up to four times. After this, you will need to either
activate or reinstall the product key.
Note
Internet connection is recommended.
1. Either use the run selection from the start programs menu or open a command window.
2. Type: slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX (the “5x5” product key from the COA label attached to the
server).
3. It will take the OS up to 30 seconds to respond, saying that the product key was successfully inserted.
4. Then go through the activation process again and choose Activate. No need to click Type a different product key, as
it was already manually injected in the previous steps.
28. What do I do if the manual product key injection process does not result in my
Windows Server 2008 R2 product being activated?
If for some reason, the OS still requires activation after you follow the manual product key injection and activation process,
then follow the steps below:
1. Run the Microsoft Diagnostics Tool, as it will dump information from the OS that gives details on what might be going
on with the activation process as well as information on the key being used. The tool can be downloaded from the
Microsoft website and must be run within the OS. Go to go.microsoft.com/fwlink/?linkid=52012 to download the WGA
Diagnostic tool.
2. Capture a high-resolution picture of the COA label.
13
Technical white paper | HP FAQ for Microsoft OEM licensing—Windows Server
3. Call HP Support and provide the picture of the COA label as well as the results of the Microsoft Diagnostics Tool.
4. HP will then work to help resolve the issue.
29. What do I do if the manual product key injection process does not result in my
Windows Server 2012 or Windows Server 2012 R2 being activated?
If for some reason the OS still requires activation after you followed the manual product key injection process, then follow
the steps below:
1. Make sure you are logged on with an administrator account.
2. Press the Windows key on your keyboard.
3. Type “cmd” (There is no window as there is in the Windows Server 2008 R2 Start menu—just start typing, and the
search function will pick up automatically.).
4. Select the “Command Prompt” tile from the search results displayed on the desktop.
5. In the Command Prompt window, type (without the quotation marks): “licensingdiag.exe –report
%userprofile%\desktop\report.txt –log %userprofile%\desktop\repfiles.cab” + Enter.
6. Capture a high-resolution picture of the COA label.
7. Call HP Support and provide the picture of the COA label as well as the report.txt and repfiles.cab that have been
generated on your desktop compressed into a *.zip archive.
8. HP will then work to help resolve the issue.
30. I can’t find the phone activation wizard under Windows Server 2012 R2, how do I
activate via the phone?
The phone activation wizard can be launched by running “SLUI -4”. This will bring up the phone activation wizard and provide
country specific phone numbers.
Support
32. What type of warranty support does HP provide for HP OEM Windows Server
products?
HP’s only warranty obligations with respect to software distributed by HP under the HP brand name are set forth in the
applicable end-user license or program license agreement provided with that software. If the removable media on which HP
distributes the software proves to be defective in materials or workmanship within 90 days of purchase, your sole remedy
shall be to return the removable media to HP for replacement.
HP also provides electronic or telephone support for initial setup for 90 days from date of purchase.
Initial setup support includes:
• Answering installation questions (how-to, first steps, and prerequisites)
• Setting up and configuring software and options supplied or purchased with HP hardware products (how-to and first
steps)
• Interpreting system error messages
• Isolating system problems
• Obtaining support pack information or updates for software purchased or supplied with HP hardware products
14
Technical white paper | HP FAQ for Microsoft OEM licensing—Windows Server
HP ProLiant Global Limited Warranty and Technical Support Terms can be found at:
h18004.www1.hp.com/products/servers/platforms/warranty/index.html
33. What type of support services does HP provide beyond warranty support?
HP has a full range of support and consulting services for your product that can be purchased locally. However, some
support and related products may not be available in all countries. For information on availability and cost of these services,
refer to the HP website at: hp.com/services/microsoft.
35. What information do I need to have available when I contact HP for support?
Be sure to have the following information/documentation available before you call:
• Proof of purchase (to be sent via fax or email)
– An invoice with software and server SKUs (HP or distributor SKU)
– A high-resolution picture of the COA affixed to the server showing the 5x5 product key
Note
If proof of purchase is not readily available, be prepared to provide the type of Windows product being requested—include
the edition, plus the HP server type, model, and serial number.
37. I’ve lost my media for my Windows Server OS. How can I get a replacement?
You will need to go to the following website to request replacement media go to hp.com/go/wsdowngrade. A media kit for
replacement may only be requested from HP for a Windows Server license purchased from HP or an HP authorized reseller.
HP is able to send replacement media kits for all Windows Server 2003 R2 and later versions. The kit will not include license
keys. Media replacement kits are shipped from the U.S, so please allow 1-2 weeks for delivery (depending on customs
requirements and shipping method). Upon order fulfillment, you will receive an email with shipment tracking number and
expected delivery details.
15
Technical white paper | HP FAQ for Microsoft OEM licensing—Windows Server
38. I downloaded and installed a “time bomb” trial version of a Microsoft Server OS.
It’s telling me to buy the software. Can I install an OEM software license?
Only if you already purchased the OEM license when you purchased the server, otherwise, no. An OEM license may only be
acquired in conjunction with a new computer. If you already have your computer, then you may either buy a retail license or
purchase a volume license from an authorized licensing reseller such as HP SLMS.
In case you do have the OEM license, you can follow the procedure on question 14 to convert the evaluation copy to a fully
licensed product.
41. What happens if I have a license for an older version of Windows Server and want to
upgrade to the latest version but have not purchased Microsoft Software Assurance for
the license?
You need to purchase a new Windows Server license for each server that you will be upgrading. Unlike service packs and
feature packs, each new release of Windows Server is a full OS and requires a new server license. Software Assurance is not
available for previous versions of Windows Server; Software Assurance is only available for the latest version of a product.
Downgrade rights
42. What are my downgrade rights?
Many Microsoft software products include the right to use an earlier version of the software in place of the version you
licensed. For information on the downgrade rights for your Microsoft product, refer to the end-user license terms of your
Microsoft software license. Additional information about downgrade rights may be available at the Microsoft website for
each product family (microsoft.com/oem/en/licensing/sblicensing/pages/downgrade_rights.aspx).
16
Technical white paper | HP FAQ for Microsoft OEM licensing—Windows Server
44. What are the activation requirements for the downgrade scenario?
For Microsoft products that require activation, if you are using a previous version under downgrade rights, you will need to
activate it with a valid product key for that downgrade version. As noted in the end-user license terms for your software
license, neither Microsoft nor HP are obligated to provide you with downgrade media or product keys. In general, when
customers are exercising downgrade rights, they reuse the product key from a previously obtained license to activate the
downgrade version. If automatic activation fails when doing this, the customer will be prompted to phone a Microsoft
Activation Center. When they explain to the Activation Center analyst that they are reusing a key under downgrade rights,
the analyst will assist them to activate the downgrade version.
Alternatively, if using an HP OEM license for Windows Server, HP may be able to provide media and a product key for a
downgrade version on request from the HP OEM customer. Either contact an HP Call Center to request the media or go to
the HP website at hp.com/go/wsdowngrade. The media kit will be shipped from the U.S., so allow 3 to 10 business days for
delivery (depending on customs requirements and shipping method). The kit will not include your license keys. The kit will
provide instructions on how to obtain your product keys.
17
Technical white paper | HP FAQ for Microsoft OEM licensing—Windows Server
The following table lists the number of instances per license that you can run at the same time in a virtual OS environment
within a physical server.
Standard 1
Enterprise 4
18
Technical white paper | HP FAQ for Microsoft OEM licensing—Windows Server
Upgrade rights
49. Why does HP OEM media not support upgrade installation, while Microsoft media
does?
Unlike Microsoft media, where the customer may already have a server running on an old version of Windows Server, OEM
media can only be sold with new servers, so the assumption is that there is no upgrade. Because of that assumption, HP has
disabled the upgrade function. If a customer wants to upgrade to a new version of Windows Server, then the new version
will need to be reinstalled.
50. I bought Windows Server Standard from HP with my new HP ProLiant server, but I
really meant to buy Windows Server Datacenter. Can I do an upgrade?
Unfortunately, Microsoft does not offer an in-place upgrade between editions of Windows Server. If you noticed your error
as soon as you made it, please contact HP for a return.
As soon as you get the Datacenter license, you can follow procedure on question 65 to convert the installation from
Standard to Datacenter.
52. Why do I get a “system not supported” message when I try to install HP OEM media
on top of VMware?
To allow the HP OEM media to detect that it’s being installed on HP hardware, you will need to add the following
configuration line to the VM configuration file:
“SMBIOS.reflecthost=TRUE”
54. How do OS licensing rules for VMware vMotion, Windows Server Clustering
Services, and the Microsoft System Center Virtual Machine Manager differ?
Refer to each product’s online documentation and license terms for details. The following answer is specific to licensing for
Windows Server in virtualized environments. Note that the licensing terms for Windows Server in virtualization deployments
are the same regardless of which hypervisor is used to manage the VMs.
Similar licensing rules apply to both Windows Server Clustering Services and VMotion, and System Center Virtual Machine
Manager. While VMotion and System Center Virtual Machine Manager move instances of virtual operating system
environments (OSEs) between physical servers, the Windows Server licenses are assigned to physical servers and remain
with the physical server to which they were assigned. When an instance is moved to a new physical server, that new server
19
Technical white paper | HP FAQ for Microsoft OEM licensing—Windows Server
must already have appropriate licenses assigned to it. Because Windows Server Datacenter Edition permits an unlimited
number of instances of the server software to run in virtual OSEs, in multiserver installations with VMotion, and with System
Center Virtual Machine Manager, it offers you the greatest flexibility to move instances between servers without having to
track the number of instances running or needing to worry about being under licensed.
56. Can you use Citrix® XenServer with an HP OEM license for Windows Server?
Yes. You can use Citrix XenServer with an HP OEM license according to the Citrix documentation, pages 11–12:
Installing a BIOS-locked VM
1. Run the vm-install copy-bios-strings-from command and specify the host-uuid as the host from which the strings
should be copied (that is, the host that the media was supplied with):
xe vm-install copy-bios-strings-from=<host uuid> \
template=<template name> sr-name-label=<name of sr> \
new-name-label=<name for new VM>
This returns the UUID of the newly created VM. For example:
xe vm-install copy-bios-strings-from=46dd2d13-5aee-40b8-ae2c-95786ef4 \
template="CentOS 5.3" sr-name-label=Local\ storage \
new-name-label=newcentos
7cd98710-bf56-2045-48b7-e4ae219799db
2. If the relevant BIOS strings from the host have been successfully copied into the VM, the command “This vm-is-BIOS-
customized” will confirm this:
xe vm-is-bios-customized uuid=<VM uuid>
For example:
xe vm-is-bios-customized \
uuid=7cd98710-bf56-2045-48b7-e4ae219799db
This vm-is-BIOS-customized.
Note
When you start the VM, it will be started on the physical host from which you copied the BIOS strings.
A VM can be:
• BIOS-generic: The VM has generic XenServer BIOS strings.
• BIOS-customized: The VM has a copy of the BIOS strings of a particular host in the pool.
• Without BIOS strings: Immediately after its creation.
20
Technical white paper | HP FAQ for Microsoft OEM licensing—Windows Server
Warning
It is your responsibility to comply with any EULAs governing the use of any BIOS-locked OSs that you install.
Release notes
There are many versions and variations of Windows with different levels of support for the features provided by XenServer.
This section lists notes and errata for the known differences. support.citrix.com/servlet/KbServlet/download/23830-102-
645654/guest.pdf
57. How many physical/virtual installations can I have with the various versions of the
OS?
OS version Physical OSE Virtual OSE
58. Can I buy two HP OEM Windows Server 2008 R2 Standard Edition licenses for one
physical server, with the intention of running them each in a VM (non-Microsoft VM)?
Yes. Microsoft licensing (FPP, OEM, and VL) allows this.
Standard Edition for Windows Server 2012 and Windows Server 2012 R2
59. Is there any difference in the code between the Standard and Datacenter Editions
of Windows Server 2012 or Windows Server 2012 R2?
No. They are identical other than the product name and branding. It’s the “unlimited virtualization” licensing that offers
significant additional value in Datacenter.
60. What are the differences in licensing for Windows Server Standard vs. Datacenter
Editions?
Datacenter permits unlimited virtualization and the base license supports up to two CPUs.
The Standard base license permits only two VMs and supports up to two CPUs.
21
Technical white paper | HP FAQ for Microsoft OEM licensing—Windows Server
The base OEM license for Windows Server Datacenter supports 2 physical processors, and an unlimited number of
concurrent VMs. You may “stack” more than one Standard license on a server to support additional physical processors
and/or concurrent VMs. Likewise; you may “stack” more than one Datacenter license on a server to support additional
physical processors. When buying “stacked” OEM licenses direct from HP, HP will fulfill the second and subsequent licenses
with an “additive” or “additional” license, which does not include redundant media.
62. How do I calculate the number of Windows Server licenses I need for a server
solution?
For the Datacenter Edition of Windows Server 2012 or Windows Server 2012 R2, simply divide the number of physical
processors by 2 (round up), and that is the number of licenses you need since each Datacenter license supports 2 physical
processors and an unlimited number of concurrent VMs.
For the Standard Edition of Windows Server 2012 or Windows Server 2012 R2, the number of licenses you will need
depends on the number of physical processors on the server and the maximum number of virtual server instances you will
be running concurrently. The larger of these two numbers determines the number of total licenses required. Each license
covers up to two physical processors and 2 concurrent VMs, and you can “stack” as many licenses on the server as needed
to cover the physical processors and concurrent VMs. However, note that Windows Server 2012 Datacenter and Windows
Server 2012 R2 Datacenter permit an unlimited number of VMs, so only “stack” Standard licenses for VM density if the total
cost is less than licensing Datacenter. For example:
• You have a 2-processor server: 2 physical processors/2 (number of processors covered by a license) equals 1.
You will need one license to cover a 2-processor server.
• You have a 4-processor server: 4 physical processors/2 (number of processors covered by a license) equals 2.
You will need two licenses to cover a 4-processor server.
• You have an 8-processor server: 8 physical processors/2 (number of processors covered by a license) equals 4.
You will need four licenses to cover an 8-processor server.
Your pricing for Standard and Datacenter licenses may vary from this guideline, but in general Datacenter costs less if you
will ever need to run near 10 or more concurrent VMs for each 2 physical processors on a server.
64. Does an OEM license for Windows Server 2012 Standard Edition or Windows Server
2012 R2 Standard Edition come with CALs?
No. As of Windows Server 2012 and onwards, OEM licensing has been aligned to Microsoft Volume Licensing, in that CALs
are purchased separately. This assures that each customer can purchase only and exactly the number of CALs they need.
22
Technical white paper | HP FAQ for Microsoft OEM licensing—Windows Server
65. I accidentally installed Windows Server 2012 Standard, but wanted Datacenter. Can
I convert the installation to Datacenter?
Yes, you can convert Standard Server installation over to Datacenter. As long as you have bought Datacenter OS license.
First verify the OS currently installed; run from an elevated command prompt: DISM /online /Get-CurrentEdition (current
edition should show ServerStandard)
Run DISM /online /Get-TargetEditions (The results should show ServerDataCenter as the edition capable of upgrading to)
Run DISM /online /Set-Edition:<edition ID> /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula (For the
edition type in what was returned in the Get-CurrentEdition command. It should show ServerDataCenter as the target
edition. The command will set the edition type, inject the appropriate product key, and accept the Eula in a single command.
Server will reboot.)
Datacenter Edition for Windows Server 2012 and Windows Server 2012 R2
66. When does it make sense to get Windows Server Datacenter vs. Standard Edition?
It depends on your needs, but a rule of thumb is that if you think you might ever need to run near 10 or more concurrent
Windows Server VMs on a server, then Datacenter, with its unlimited virtualization rights, is the best choice.
67. What is the maximum CPU support that Windows Server Datacenter Edition has?
Both the Standard and Datacenter Editions of Windows Server 2012 and Windows Server 2012 R2 have the same capacity
limits: up to 320 logical processors per physical server, and up to 64 virtual CPUs per VM.
69. I installed Server 2012 Datacenter, but I want Server 2012 Standard. Can I convert
the current installation from Server Standard to Server Datacenter?
No, you can’t convert from Datacenter to Standard. A fresh installation is required.
71. Can I buy a 2-CPU license on HP ProLiant 4 CPU server with two processors installed
and purchase an additional 2-CPU license when I install the second and third CPUs?
HP doesn’t offer post-sale for additional licenses, they should be purchased at the same time as the base OS license with
the ProLiant Server, Customers must purchase additional licenses directly from Microsoft to support additional processors.
72. Can you buy a 2-CPU license and “divide” the license between two servers?
No.
23
Technical white paper | HP FAQ for Microsoft OEM licensing—Windows Server
73. How many CALs are included in the HP OEM Datacenter Edition?
Zero.
75. Can I manage advanced virtualization environments with Windows Server 2012 or
Windows Server 2012 R2?
Customers who wish to manage a more advanced virtualization environment can purchase Microsoft System Center 2012
and deploy key capabilities and functionality as needed (for example, Configuration Manager, Operations Manager, Virtual
Machine Manager, Data Protection Manager, and others), in addition to Windows Server 2012 and Windows Server 2012 R2
integrated management solutions.
Customers with the largest and most sophisticated midsize business customers (50–500 PCs), or those wishing to manage
a more advanced virtualization environment, can leverage the combined value of integrated management solutions
delivered with System Center 2012 and Windows Server 2012 or Windows Server 2012 R2.
76. What new management capabilities are delivered in Windows Server 2012?
Windows Server 2012 delivers new and more powerful management capabilities—such as Share Nothing Live Migration and
Inbox Replication (Hyper-V Replica)—that make it easier to manage and maintain the IT infrastructure while delivering great
customer value.
For TS CALs or RDS CALs differences, see questions 97 and questions 99.
24
Technical white paper | HP FAQ for Microsoft OEM licensing—Windows Server
80. Can I use my Windows Server 2008 CALs to access Windows Server 2008 R2?
Yes, since CAL versions are not updated for an “R2” release.
81. If a user or device accesses a server running Windows Server 2008 but is
authenticating via a third-party authentication application (non-Microsoft based
authentication), does the user or device still require a Windows Server 2008 CAL?
Yes. If the user or device is authenticating by any means to a server running Windows Server 2008, a Windows Server 2008
CAL is needed.
82. Can I use a Windows device CAL and a Windows user CAL to access the same server?
Also, can I use a RDS device CAL and a RDS user CAL on the same terminal server?
Yes. Windows device and user CALs, as well as RDS device and user CALs, can be used on the same server.
83. I have some extra Windows Server 2003 CALs that are not being used. Can I apply
these to servers running Windows Server 2008 R2?
No. CALs must be the same version as—or higher than—the server software they are accessing. In other words, users or
devices accessing a server running Windows Server 2008 R2 must have Windows Server 2008 CALs.
85. I have some extra Windows Server 2008 CALs that are not being used. Can I apply
these to servers running Windows Server 2012?
No. CALs must be the same version as—or higher than—the server software they are accessing. In other words, users or
devices accessing a server running Windows Server 2012 must have Windows Server 2012 CALs.
25
Technical white paper | HP FAQ for Microsoft OEM licensing—Windows Server
87. Can I use a Windows Server 2012 user CAL to access a server running Windows
Server 2003?
Yes. A Windows Server CAL permits access to all earlier versions of Windows Server.
88. Do I need to upgrade my Windows Server CALs to access future releases of Windows
Server?
All future releases of Windows Server will require Windows Server CALs of the same version for the customer’s internal
users and devices accessing the Windows software. Customers can either acquire new Windows Server CALs when the new
version is released, or maintain Microsoft Software Assurance on their prior-version CALs, which gives the rights to the next
version.
89. I have Microsoft Software Assurance for my CALs. Can I switch between user and
device CALs?
Volume licensing customers may switch from one to the other when they renew their Microsoft Software Assurance. You
must designate your CALs as device or user when you upgrade them.
90. Will I be allowed to switch between Windows Server 2008 device CALs and user
CALs? What about TS CALs or RDS CALs?
If your Windows CALs are covered under Microsoft Software Assurance, you can convert those Windows CALs from device
CALs to user CALs, or vice versa, when you renew your Microsoft Software Assurance. If your Windows CALs are not covered
under Microsoft Software Assurance, you may not switch. Your choice is permanent. This also applies to TS-CALs and RDS
CALs.
91. Are CALs required for Windows Web Server 2008 R2?
No. Windows Web Server 2008 R2 is licensed by a server license only and no CALs are required. However, when Windows
Web Server 2008 and Windows Web Server 2008 R2 are used as a scale-out front end for applications running on back-end
servers, Windows Server CALs may still be required on these back-end servers running Windows Server.
92. What is the difference between a Windows Server 2008 R2 license and a Windows
CAL? Why do I need both?
The Windows Server 2008 R2 license gives the license holder the right to install and use the server software. The Windows
CAL grants the right for a device or user to access the server software. The two-component license provides a low entry
price and a way to pay for capacity used: the more devices or users accessing the server software, the greater the license
fees or price. The model therefore offers license affordability to organizations of all sizes.
93. Are the five CALs that come with my purchase of the HP Windows Server 2008 R2
license designated on a per-user or per-device basis?
For these first five CALs, you get to choose—that is, you can designate whether those CALs are user or device CALs.
For any additional CALs you acquire after that, you purchase the type (user or device) of CAL you desire.
94. Can I split a CAL pack into user and device CALs?
Windows Server 2008 R2 comes with a 5 Pack of CALs included. This initial 5 pack can be split into user and device CALs. For
any additional CALs you require, you must purchase the specific type of CAL (user or device) that is needed. Additional CAL
packs cannot be split up. In the case that you need less than five devices or user CALs, Microsoft has introduced single CALs
to address this concern. With single CALs, you can purchase exactly what you need.
26
Technical white paper | HP FAQ for Microsoft OEM licensing—Windows Server
Windows Server 2012 and Windows Server 2012 R2 do not include any CALs by default; they need to be purchased
separately as needed. HP currently offers 5, 10, and 50 CAL packs (user or device) which cannot be split up, single CALs are
also available.
98. What do you need to do if you want to downgrade your RDS CALs or a TS CAL?
To downgrade TS/RDS CALs to Windows Server 2003 R2, call the TS Clearinghouse and obtain Windows Server 2003 TS CAL
key (refer to TS downgrade rights):
• In the U.S., call (888) 571-2048.
• Outside the U.S., click Start, point to Programs, click Administrative Tools, and then click Terminal Services Licensing.
• In the Terminal Services Licensing console, right-click your license server, and then click Properties.
• Click Connection Method, and then click Telephone.
• Click the appropriate country, and then click OK.
• On the Action menu, click Install Licenses, and then click Next.
• Call the appropriate customer service center using the telephone number that is displayed.
• Click Cancel to exit the Terminal Services Licensing console.
99. What is the difference between a Windows Server 2008 TS CAL and a Windows
Server 2008 R2 RDS CAL?
For Windows Server 2008 and Windows Server 2008 R2, there is no difference—a Windows Server 2008 TS CAL can be
activated on a Windows Server 2008 R2 RDS License Server, and a Windows Server 2008 R2 RDS CAL can be activated on a
Windows Server 2008 TS License Server.
27
Technical white paper | HP FAQ for Microsoft OEM licensing—Windows Server
Note
A client that received a TS CAL from the previous license server will continue normal operation until its TS CAL expires. When
the previously issued TS CAL expires, the terminal server will request a new TS CAL from the new license server on behalf of
the client.
7. After you have confirmed that the terminal servers in your environment can discover (contact) the new license server,
deactivate the previous license server. For more information, see Deactivate a Terminal Services License Server.
8. Uninstall (remove) the TS Licensing Role Service from the previous license server. For more information, see Uninstall
the TS Licensing Role Service.
For more information about moving, upgrading, or migrating to a Windows Server 2008 TS license server, see the TS page
on the Windows Server 2008 TechCenter. (go.microsoft.com/fwlink/?LinkId=73931). For additional information, visit:
• Managing TS Licensing
• Microsoft Clearinghouse
Locating the Microsoft Clearinghouse telephone number for your country or region. To locate the Microsoft Clearinghouse
telephone number when the license server is activated:
1. Click Start, point to Administrative Tools, point to Terminal Services, and then click TS Licensing Manager.
2. Select the license server. On the View menu, click Properties.
3. On the Connection Method tab, in the Connection Method list, select Telephone.
4. In the Select Country or Region list, select your country or region, and then click OK.
5. On the Action menu, click Install Licenses, and then click Next.
6. The Microsoft Clearinghouse telephone number for your country or region is displayed. Write down the telephone
number, and then click Cancel. For additional information, visit
technet.microsoft.com/en-us/library/cc754677(WS.10).aspx.
Deactivating a TS license server: You might need to deactivate a TS license server when the certificate of the server has
expired or becomes corrupted, or when the server is being redeployed. When you deactivate a TS license server, the license
28
Technical white paper | HP FAQ for Microsoft OEM licensing—Windows Server
server will not be able to issue permanent TS per-device CALs to additional clients until the license server is activated again.
However, a deactivated license server is able to issue TS per-user CALs and temporary TS per-device CALs.
You can deactivate a license server by using one of the following methods:
• Deactivate a Terminal Services License Server Automatically
• Deactivate a Terminal Services License Server by Using the Telephone
You cannot deactivate a TS license server using the Web browser connection method. For additional information, visit
Managing TS Licensing.
Reseller information
101. I’m a reseller and I’d like to know the difference between COEM and HP OEM.
The COEM product is what is often referred to by Microsoft as System Builder or Channel OEM. Microsoft is the point of
contact for the purchase of this license type for resellers who want to marry the license to a white box server. The customer
may not transfer the license to another server unless they have purchased Microsoft Software Assurance within the first 90
days of purchase of the license. Microsoft Software Assurance is only available for the latest version of a product.
The HP OEM products are designed and tested for HP servers, providing you and your customers with confidence in
deploying the ideal combination of OS and HP ProLiant server. With the HP OEM versions, your customers will also receive
90-day free telephone support from the purchase date of the new server and license.
102. I’m a reseller. How can I learn more about the HP ROK?
For more information on HP OEM ROK, go to hp.com/go/rok.
103. Do the purchases of both HP OEM (factory integrated option) and HP OEM ROK
option count towards my HP x86 server and Microsoft partner program goals?
Yes. HP OEM Microsoft Server licenses count toward both HP and Microsoft goal attainment partner programs.
104. I’m a reseller. I’ve heard about a training site from HP and Microsoft called Coffee
Coaching—what is it?
HP Microsoft Coffee Coaching is a community where resellers can learn and interact with Microsoft and HP subject matter
experts to become more knowledgeable on key technologies to help you better serve your customers. Become a follower
on the following social media sites:
• facebook.com/CoffeeCoaching
• youtube.com/CoffeeCoaching
• twitter.com/CoffeeCoaching
• blog.com/CoffeeCoaching
• linkedIn/CoffeeCoaching
29
Technical white paper | HP FAQ for Microsoft OEM licensing—Windows Server
References
Visit the following websites to learn more about the subjects covered in this FAQ:
• hp.com/go/proliantwindows
• hp.com/go/ws2012r2
• hp.com/go/ws2012
• hp.com/go/ws2008r2
• hp.com/go/rok
• hp.com/go/coffeecoaching
• hp.com/go/windows/documentation
• hp.com/go/wincert
• hp.com/go/WindowsFAQ
• microsoft.com/licensing/about-licensing/client-access-license.aspx
• microsoft.com/sa
• HP ProLiant Global Limited Warranty and Technical Support Terms
h18004.www1.hp.com/products/servers/platforms/warranty/index.html
• Microsoft Solutions Services
hp.com/services/microsoft
• Microsoft Support Lifecycle Policy
microsoft.com/lifecycle
• HP support for Windows Server products
welcome.hp.com/country/us/en/wwcontact_us.html
Learn more at
hp.com/go/proliantwindows
© Copyright 2012-2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only
warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should
be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Microsoft and Windows are U.S. registered trademarks of the Microsoft group of companies. Itanium is a trademark of Intel Corporation in the U.S. and other
countries. Citrix is a trademark of Citrix Systems, Inc. and may be registered in the U.S. and other countries.