KMS Activation Errors after Deployment

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 2

After being told by tech support that I'm the only person in the entire world that has experienced this problem, I thought I would see if anyone else has really experienced this.

After creating and deploying a Win 7 image with Snap Deploy 4, the newly imaged machine will not activate against a KMS. I receive the following:

"Error Code: 0xc004f035 The Software Licensing Service reported that the computer could not be activated with a Volume license product key. Volume licensed systems require upgrading from a qualified operating system. Please contact your system administrator or use a different type of key."

I do not understand why this would be a machine/Microsoft issue. I can load Win 7 from disk, then activate against KMS with no problem. It's after I create and deploy the image (with a unique SID) that I can't activate against KMS.

Has anyone else seen this?

Fri, 12/06/2013 - 14:49
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Member
Posts: 0
Comments: 69

Hello Jonathan,

You are not the only once facing the problem. However as noted the problem is not fully Acronis problem.
If you are creating a master image of a machine that was not rearmed (slmgr /rearm) then once that image is deployed the new machine will have the same CMID (Client Machine ID) and will come to KMS as the same machine as original. There is no way to change CMID except rearm.
So you should either deploy an image that is rearmed or use "Applications to run" to:
1. Run first script that will:
rearm the target machine:
slmgr /rearm
schedule onstart activation script. (because you must reboot after rearm). Use "schtasks" command. Make sure you schedule a task ONSTART with SYSTEM and HIGHEST runlevel (see schtasks create /help).
reboot the machine
2. Activation script that will:
run slmgr /ipk, /ato and so on.
unschedule itself.

Please let me know if you have any questions.

Tue, 12/10/2013 - 21:46
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 2

Thanks for the information, but this does not alleviate the problem. We tried doing this on the machine we were going to capture the image from, along with the machines that we have pushed the image to. It's weird because the machine we capture the image from will activate through KMS. However, the machines that receive the image, will not activate through KMS.

Tue, 12/10/2013 - 22:53
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Member
Posts: 0
Comments: 69

I used the above solution with running /rearm on target system with scripts and it was working fine.
I advise you to contact our support and we will be able to assist you to make sure that everything was done correctly. We will also provide you the build with the fix for "not being able to reboot".

Tue, 12/10/2013 - 22:56
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 2

I understand that it may work for you, however it does not for us. Also, where did you get that we were not able to reboot?

Thu, 12/12/2013 - 16:09
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Member
Posts: 0
Comments: 69

There was a problem with "Applications to run":
If your script takes a lot of time to work it stops the machine from rebooting when you change SID.
So in your case you will most likely face this problem since /rearm takes up to a minute sometimes.
Since you have problems with the provided solution I advise you to contact our support and we can investigate your case individually.

Thu, 12/12/2013 - 16:12