Windows 7 Ultimate Gvlk Klyuchica

Hi, I have a KMS host configured on my domain controller, I am using MDT 2010 and WDS to re-image my client machines. MDT2010 and WDS runs on a separate machine. 3 months before I got a KMS to activate my windows 7 clients.

Krishita soni • 7 Pins. More from krishita soni Quilling art. Krishita soni • 21 Pins. More from krishita soni Challenges to try out this year! Krishita soni • 16 Pins.

When I install my KMS host, I double checked on the count increase. Now after 3 months, suddenly my re imaging failed with an error 'Activate Windows Failed' I rang Microsoft and found that I am still using my MAK and all my MAK's are used.

I checked my KMS today and the total count says 470 machines. I cant understand what's going on. Can any one help me please:(?

Thanks SNRRK. VL editions of Windows7 (VL Pro or VL Ent) ship with a KMSclient pkey already present.

If you have added an MAK pkey into your unattend or TS, then either remove that if using VL media, or, substitute with the generic Win7 KMSclient pkey. If the OS you are deploying is Win7PRO, the pkey in the deployed OS must be the generic KMSclient pkey for Win7PRO. If the OS you are deploying is WS2008R2STD, the pkey in the deployed OS must be the generic KMSclient pkey for WS2008R2STD. Generic KMSclient pkeys (GVLK) are here: NB: you can use slmgr.vbs or VAMT, to remotely substitute KMSclient pkey in place of MAK pkey, on your deployed machines. This might be helpful if you need to get up to 25 KMSclients so that the KMShost begins issuing activations to KMSclients. Don (Please take a moment to 'Vote as Helpful' and/or 'Mark as Answer', where applicable. This helps the community, keeps the forums tidy, and recognises useful contributions.

KMS does not and cannot count beyond 50. I think you are looking at the wrong counter. The only counter which really matters, is 'current count'. All the other (cumulative) counters, are really just counting client-request packets and these are not individual machines.

Use the slmgr.vbs script at your KMShost and also at a deployed client - the information displayed when you use slmgr.vbs /dli all should show the client license type (either KMSclient or MAK) and the status this article will help you understand the output from the script: Don (Please take a moment to 'Vote as Helpful' and/or 'Mark as Answer', where applicable. This helps the community, keeps the forums tidy, and recognises useful contributions. What is the exact error message and error number?

Is the error occurring during the TS, or after the TS is completed? Does your TS have a licensing activation step in it? If your KMShost is running WS2008R2, this is fine, that can issue activations for Win7 just fine.

Is the client actually contacting your KMShost? (check the KMShost event logs) Don (Please take a moment to 'Vote as Helpful' and/or 'Mark as Answer', where applicable. This helps the community, keeps the forums tidy, and recognises useful contributions. Code: 0xC004C020 Description: The activation server reported that the Multiple Activation Key has exceeded its limit. It seems that your pkey is still not correct. On this client machine, run: cscript slmgr.vbs /dli Is the pkey a partial match to your MAK or does it partially match the GVLK?

MAK will be similar to this: C: Windows System32>cscript slmgr.vbs /dli Microsoft (R) Windows Script Host Version 5.8 Copyright (C) Microsoft Corporation. All rights reserved. Name: Windows(R) 7, Enterprise edition Description: Windows Operating System - Windows(R) 7, VOLUME_MAK channel Partial Product Key: P6XPR License Status: Licensed (The KMShost event logs are on the KMShost server) check this for further examples/explanation: Don (Please take a moment to 'Vote as Helpful' and/or 'Mark as Answer', where applicable. This helps the community, keeps the forums tidy, and recognises useful contributions. KMS does not and cannot count beyond 50. I think you are looking at the wrong counter. The only counter which really matters, is 'current count'.