Jump to content
Welcome to our new Citrix community!
  • 0

Win 7 Enterprise can no longer activate with KMS after 2.10.3.5 upgrade


Kyle Quinby1709157031

Question

Took the last upgrade to 2.10.3.5, and our Win 7 Ent image which was fine until now will no longer activate with KMS. If we do a new version of the current production OS layer version (which works fine), when the OS layer version comes up for editing, slmgr.vbs /ato will no longer activate with the 0xC004F074 "Licensing service reported that the computer could not be activated. The Key Management Service (KMS) is unavailable" error.

 

Working to get off of the 2.x environment (4.x already in place along with Win 10), but trying to keep the lights on during the migration. The previous prod version is working fine, but any new versions now will not activate. Only difference is the Unidesk upgrade.

 

Upgrading gold image tools makes no difference.

 

Update :

The symptom we are trying to solve for is our Office 2010 layer could not update because it showed Windows as not genuine.

Link to comment

6 answers to this question

Recommended Posts

  • 0

Office KMS and WIndows KMS are totally separate.  Just in case anyone is reading this you shouldn't run the runipk scripts in your office layer.

 

But maybe you had run them in the past in your office layer and some files got pulled into it that are confusing kms on the desktops.

 

Glad it worked for you.  If you have more problems you may just wnat to remake your office layer and dont run any windows kims commands.

 

Rob

  • Like 1
Link to comment
  • 0
6 hours ago, Rob Zylowski1709158051 said:

Office KMS and WIndows KMS are totally separate.  Just in case anyone is reading this you shouldn't run the runipk scripts in your office layer.

 

But maybe you had run them in the past in your office layer and some files got pulled into it that are confusing kms on the desktops.

 

Glad it worked for you.  If you have more problems you may just wnat to remake your office layer and dont run any windows kims commands.

 

Rob

 

Quite possible that somehow the OS key had been inputted in this layer. Very odd.

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...