Using KMS Client Setup Keys during deployment

Last month I did a new ConfigMgr 2012 SP1 installation. When deploying the Windows 7 image, which was created by ConfigMgr Capture media, no activation by KMS (Key Management Service) was done. This because MAK (Multiple Activation Key) was used in the image during installation. When deploying the same image afterwards, no KMS activation can be done anymore. There is a solution however; just use the applicable KMS client setup keys below.

KMS Client Setup Keys

Operating System Edition	Product Key
Windows 7
Windows 7 Professional	FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4
Windows 7 Professional N	MRPKT-YTG23-K7D7T-X2JMM-QY7MG
Windows 7 Enterprise	33PXH-7Y6KF-2VJC9-XBBR8-HVTHH
Windows 7 Enterprise N	YDRBP-3D83W-TY26F-D46B2-XCKRJ
Windows 7 Enterprise E	C29WB-22CC8-VJ326-GHFJW-H9DH4
Windows Server 2008 R2
Windows Server 2008 R2 HPC Edition	FKJQ8-TMCVP-FRMR7-4WR42-3JCD7
Windows Server 2008 R2 Datacenter	74YFP-3QFB3-KQT8W-PMXWJ-7M648
Windows Server 2008 R2 Enterprise	489J6-VHDMP-X63PK-3K798-CPX3Y
Windows Server 2008 R2 for Itanium-Based Systems	GT63C-RJFQ3-4GMB6-BRFB9-CB83V
Windows Server 2008 R2 Standard	YC6KT-GKW9T-YTKYR-T4X34-R7VHC
Windows Web Server 2008 R2	6TPJF-RBVHG-WBW2R-86QPH-6RTM4

After using above keys in the Apply Windows Settings step in your task sequence, MAK registration is replaced with KMS. Then activation can be done by the KMS host again. It's still needed however to buy a KMS host key for doing the actual activation, but it will work this way!

When seeing this, activation can be done!

For more information about KMS read this blogpost
For more KMS Client Setup Keys read this thread