Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Invalid Product Key Error Deploying HPC Compute Node


Symptoms

When deploying a HPC compute node you may see the following error message:

"The unattend answer file contains an invalid product key. Either remove the invalid key or provide a valid product key in the unattend answer file to proceed with Windows installation."

The setuperr.log will contain the following:

2011-12-13 11:16:45, Error      [0x060551] IBS    Callback_Productkey_Validate: EditionID for product key was NULL.
2011-12-13 11:16:45, Error      [0x060554] IBS    Callback_Productkey_Validate: An error occurred writing the product key data to the blackboard.
2011-12-13 11:16:45, Error      [0x06011a] IBS    Callback_Productkey_Validate_Unattend:Product key did not successfully validate.[gle=0x00000490]
2011-12-13 11:16:45, Error      [0x0603c7] IBS    Callback_Productkey_Validate_Unattend:Did not pass validation; halting Setup.[gle=0x00000490]
2011-12-13 11:16:45, Error      [0x060120] IBS    Callback_Productkey_Validate_Unattend: An error occurred preventing setup from being able to validate the product key; hr = 0x80300006[gle=0x00000490]

↑ Back to the top


Cause

If the template used to deploy the compute node contains a ProductKey entry that is set to a MAK key you will encounter this error message.  MAK keys cannot be installed during the WindowsPE phase of setup. Only retail or evaluation keys can be installed during this phase of setup. 

↑ Back to the top


Resolution

Remove the ProductKey entry from the node template and install the MAK key after setup is complete.  To do this add a "Run OS command" tasks to the node template that does the following:

  • cmd /c cscript.exe %windir%\system32\slmgr.vbs /ipk <MAK key>

This command can be added to the Deployment phase right after the "Disconnecting from installation share". 

↑ Back to the top


More Information

Microsoft does not recomend using MAK activation with compute nodes because compute nodes are commonly rebuilt on a regular basis which can lead to a situation where your MAK key activation count is consumed.  KMS activation is the recomended method to activate compute nodes.  KMS client activation is automatic and requires less administative effort. 

If you do use a MAK key for a small deployment it is recomended to move the "Activate the operating system on the node" step to the deployment phase otherwise every time you run the Maintenance task on a compute node the slmgr.vbs /ato step will consume another activation from the MAK key. 

↑ Back to the top


Keywords: vkball, kb

↑ Back to the top

Article Info
Article ID : 2655555
Revision : 1
Created on : 1/8/2017
Published on : 12/21/2011
Exists online : False
Views : 101