We only use VL so I've never had to do this and could find nothing in Microsoft licensing documentation indicating procedure. That's not surprising as it's mainly about KMS environments. I can only assume for Retail licenses where a server requires more than the base 16-core pack the situation is the same as for CALs i.e. the additional core licenses are for tracking purposes/proof of licensing only and are not installed in the OS.
If you run the following command from an elevated does it report 'License Status: Licensed'
cscript C:\Windows\System32\slmgr.vbs /dli
For OEM licenses HPE supply the unit with a base license Certificate of Authenticity (COA) affixed to the server and then provide a paper license with the COA for the additional licenses to cover the cores.
pseud0
22 Posts
0
July 22nd, 2018 10:00
We only use VL so I've never had to do this and could find nothing in Microsoft licensing documentation indicating procedure. That's not surprising as it's mainly about KMS environments. I can only assume for Retail licenses where a server requires more than the base 16-core pack the situation is the same as for CALs i.e. the additional core licenses are for tracking purposes/proof of licensing only and are not installed in the OS.
If you run the following command from an elevated does it report 'License Status: Licensed'
cscript C:\Windows\System32\slmgr.vbs /dli
For OEM licenses HPE supply the unit with a base license Certificate of Authenticity (COA) affixed to the server and then provide a paper license with the COA for the additional licenses to cover the cores.