FortiSandbox
FortiSandbox provides a solution to protect against advanced threats and ransomware for companies who don’t want to implement and maintain a sandbox environment on their own.
keithli_FTNT
Staff
Staff
Article Id 190159
Description
Symptoms:
Dashboard displays a "!" beside Windows VM:
VM-not-activated-plain.jpg

Scrolling over the "!" beside Windows VM, you may see:
VM-not-activated-popup1.jpg

Logs may also display:
"Start activation WIN7X64VM with key xxxxx-xxxxx-xxxxx-xxxxx-xxxxx"
"Failed to activate WIN7X64VM with key xxxxx-xxxxx-xxxxx-xxxxx-xxxxx"
"Failed to activate WIN7X64VM message="Installation ID: yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy Error: 0xC004C008 The activation server determined that the specified product key could not be used"  "
"Could not activate all the VM images with given keys. Please reburn other valid keys or reboot after changing your environment/network settings"




Scope
This scenario applies to "3: Errors due to Windows being activated too many times" on KB36230 titled "Troubleshooting Windows VM package activation and initialization issues"

Assuming you have tried Solution 1 and 2 unsuccessfully, use the following steps to obtain a key to reset activation limit.

Solution

1.  Get the installation ID from the logs :

Failed to activate WIN7X86VM message="Installation ID: 014305901762758475165340576945056666386683555262446271 Error: 0xC004C008 The activation server determined that the specified product key could not be used"

2.  Split the Installation ID into 9 groups of 6 digits :

014305901762758475165340576945056666386683555262446271

turns into :

014305 901762 758475 165340 576945 056666 386683 555262 446271

3.  Call the Microsoft Activation Service. You can find the phone list here :

http://www.microsoft.com/licensing/existing-customers/activation-centers.aspx

4.  Select the choice 2 – Business Customer

5.  Follow phone system instructions to enter the installation ID

6.  Phone system will ask you some question before to accept

7.  After your request is accepted. Write down the 8 groups of 6 digits

8.  You can hang up

9.  Use the following CLI command on the FSA :

Be careful not to attach space between the confirmation id and the argument, as illustrated in the following example :

> confirm-id -a -kXXXXX-XXXXX-XXXXX-XXXXX-XXXXX -c042532258754869596628901610621951021013844450525

Confirmation ID has been added.

10. Confirm that the entry have been handle by the FSA :

> confirm-id -l

XXXXX-XXXXX-XXXXX-XXXXX-XXXXX 042532258754869596628901610621951021013844450525

11. Reboot the FSA

>reboot

Do you want to continue? (y/n)

12. 2 minutes after the reboot, VM proceed to the activation. You should get theses logs :

FortiSandbox system is up. Start initializing Sandbox VMs.

Start activation WIN7X86VM with key XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

WIN7X86VM was activated successfully with key XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

Activate WIN7X86VM:"Activate windows successfully with key XXXXX-XXXXX-XXXXX-XXXXX-XXXXX Installation ID:

014305901762758475165340576945056666386683555262446271"

 

Note:

  • You may need to repeat the previous step for the second Windows 7 VM.
  • For your information, you need to do the activation of the Windows 7 before active Office license.

Related Articles

Troubleshooting Windows VM package activation and initialization issues

Log Reference: Troubleshooting FortiSandbox Windows VM package activation and initialization issues ...

Contributors