KMS 1.2 Update for Windows 2008

As of the 24th of August the update for Windows 2008 has been published on Windows download center:

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=d284f030-642f-443b-85ce-74ef449d5ab4

Enjoy

Key Management Service (KMS) 1.2 Update

For KMS hosts that are running Windows 2003 is available:

64 bit: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=1678151b-b577-476f-87da-df54024b98e2

32 bit: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=f3a0d90c-b7fd-44cf-bf81-11587adc599f

The release of the update for Windows 2008 is not anywhere to be seen, but we should see it soon..

So if you KMS server is running Windows 2008, you still will not be able to register your Windows 7 & Windows 2008 R2 operation systems...

Windows Server 2008R2 and Windows 7 KMS failed activation

Should you have a lot of Windows 7 Enterprise or Windows 2008R2 failing KMS activation it is because it needs an updated component on the KMS host. Key Management Service 1.2 should be installed. Microsoft promised it on RTM. But it seems that it is late.

It should be released today on Microsoft download center, så search for KMS 1.2 later today.

Releasing operating systems, that cannot register... Not going to comment.......

Windows 2008R2 & Windows 7 KMS installation keys

Use these keys in the SCVMM templates, when you create one, if you are installing Windows 2008R2 or Windows 7 VM's

http://technet.microsoft.com/en-us/library/dd772269.aspx

Includes KMS client setup keys. Useful when creating SCVMM Guest OS profiles.

--snippet--

Manually Activate a KMS Client
By default, KMS clients automatically attempt to activate themselves at preset intervals. To manually activate KMS clients (for example, disconnected clients) before distributing them to users, use the Control Panel System item, or run slmgr.vbs /ato at an elevated command prompt. The Slmgr.vbs script reports activation success or failure and provides a result code. To perform activation, the KMS client must have access to a KMS host on the organization’s network.

Converting MAK Clients to KMS and KMS Clients to MAK
By default, Windows 7 and Windows Server 2008 R2 operating systems use KMS for activation. To change existing KMS clients to MAK clients, simply install a MAK key. Similarly, to change MAK clients to KMS clients, run:

slmgr.vbs /ipk

where KmsSetupKey is one of the setup keys shown below.

After installing the KMS setup key, activate the KMS client by running cscript c:\windows\system32\slmgr.vbs /ato.

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 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

NB!: These note that these keys can only be used to install the OS and the client will search for a KMS host once installed and is OOB period.

The Cable Guy NAP on the Internet

Please read this article about Network Access Protection (NAP) on the Internet. Very good article on health checking computers connected to the internet. How to manage and check your mobile users.


http://technet.microsoft.com/en-us/magazine/dd744660.aspx

MDM Roadmap

From the SCMDM Blog about the roadmap:

We’ve recently been asked a few questions about the SCMDM roadmap and future versions. Here’s a quick overview of what is to come.
At the recent MMS and Tech Ed US 2009 conferences, the System Center Configuration Manager team revealed some important news regarding the future of device management. Here are a few of the key messages that were shared:
The next major release of Configuration Manager will have the major MDM functionality for device management including SW Dist, Inventory, Settings Management, reporting, etc;
Both desktops and mobile devices can be managed by a "single pane of glass";
Device Management will not require the use of a VPN server;
Corporate network access can be obtained by "then current" solutions supported by the mobile device client and server infrastructure;
Mobile device management will embrace the same "user centric" model as recently announced (more here);
Product roadmaps for both Configuration Manager 2007 (DM) and Mobile Device Manager both converge on this next version of Configuration Manager
While there are surely more details that everyone would like to hear, this should be great news for those wanting to hear a confirmation that Microsoft is committed to continuing and improving mobile device management. We’ll be sure to keep you updated with future developments on this blog, so watch this space!

Problems creating templates for 2008 and Vista in VMM ?

Create the virtual machine ON the Hyper-V box and not deploy a new machine via VMM. Then configure the virtual machine on the Hyper-V box. Remember to set the security to blank password and enable that it can use a blank password in local security policies.
When you have configured and installed applications, boot a last time and then go to the VMM console and create a template from the virtual machine you just created on the Hyper-V box.

I have tested that this works on several installations where I have seen the problem with creating Windows 2008 and Vista template that work in VMM.

I will create a nice guide and post it here later