<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Philip Wilmot &#187; Windows Server</title>
	<atom:link href="http://philipwilmot.co.uk/blog/category/windowsserver/feed/" rel="self" type="application/rss+xml" />
	<link>http://philipwilmot.co.uk/blog</link>
	<description>the ever learning IT professional</description>
	<lastBuildDate>Wed, 12 Jan 2011 18:31:06 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Windows 7 &amp; Windows Server 2008/R2 KMS</title>
		<link>http://philipwilmot.co.uk/blog/2009/12/windows-7-windows-server-2008r2-kms/</link>
		<comments>http://philipwilmot.co.uk/blog/2009/12/windows-7-windows-server-2008r2-kms/#comments</comments>
		<pubDate>Fri, 18 Dec 2009 12:03:22 +0000</pubDate>
		<dc:creator>Phil</dc:creator>
				<category><![CDATA[Windows 7]]></category>
		<category><![CDATA[Windows Server]]></category>

		<guid isPermaLink="false">http://philipwilmot.co.uk/blog/?p=5</guid>
		<description><![CDATA[Understanding Microsoft&#8217;s Volume Activation 2.0 they brought in with Vista and Server 2008 (and now Windows 7 &#38; Server 2008 R2) can be a bit hard to get your head around. Although I can kind of understand why Microsoft stopped VLK, mainly down to easy piracy, moving to something quite different can be frustrating if [...]]]></description>
			<content:encoded><![CDATA[<p>Understanding Microsoft&#8217;s Volume Activation 2.0 they brought in with Vista and Server 2008 (and now Windows 7 &amp; Server 2008 R2) can be a bit hard to get your head around. Although I can kind of understand why Microsoft stopped VLK, mainly down to easy piracy, moving to something quite different can be frustrating if you don&#8217;t do your homework.<br />
<strong> </strong></p>
<p><strong>How KMS Works</strong><br />
A server acts as the KMS Host, Clients then contact the KMS server. Once the KMS threshold has been met, the KMS host will send a activation request to Microsoft. The KMS Host will then activate the Clients. The KMS threshold is 5 for Windows Server 2008/R2 and 25 for Windows 7. If there are not enough clients to meet the threshold for activation then they will report to the KMS Host every two hours until the threshold is met.</p>
<p><strong>KMS Host Keys Matched to Products They Activate<br />
</strong>There are several key types. The table below, taken from TechNet, explains which type of key should be used and what they will activate. For example if you only have Standard and Enterprise Server you will only need KMS B key.<strong> </strong></p>
<table border="1">
<tbody>
<tr>
<th>Volume product group</th>
<th>Windows products</th>
<th>Key type</th>
<th>Products activated by key type</th>
</tr>
<tr>
<td>Windows Vista</td>
<td>Windows Vista Business<br />
Windows Vista Enterprise</td>
<td>KMS</td>
<td>Windows Vista Business<br />
Windows Vista Enterprise</td>
</tr>
<tr>
<td>Windows 7</td>
<td>Windows 7 Professional<br />
Windows 7 Enterprise</td>
<td>KMS</td>
<td>Windows Vista Business<br />
Windows Vista Enterprise<br />
Windows 7 Professional<br />
Windows 7 Enterprise</td>
</tr>
<tr>
<td>Windows Server 2008 R2<br />
Server Group A:</td>
<td>Windows Web Server® 2008 R2<br />
Windows Server 2008 R2 HPC Edition<br />
Windows HPC Server 2008 R2</td>
<td>KMS_A</td>
<td>Windows Server 2008 R2 Group A<br />
Windows Server 2008 Group A<br />
Windows Vista Volume Editions<br />
Windows 7 Volume Editions</td>
</tr>
<tr>
<td>Windows Server 2008 R2<br />
Server Group B</td>
<td>Windows Server 2008 R2 Standard<br />
Windows Server 2008 R2 Enterprise</td>
<td>KMS_B</td>
<td>Windows Server 2008 R2 Group A<br />
Windows Server 2008 Group A<br />
Windows Server 2008 R2 Group B<br />
Windows Server 2008 Group B<br />
Windows Vista Volume Editions<br />
Windows 7 Volume Editions</td>
</tr>
<tr>
<td>Windows Server 2008 R2<br />
Server Group C</td>
<td>Windows Server 2008 R2 Datacenter<br />
Windows Server 2008 R2 for Itanium-Based Systems</td>
<td>KMS_C</td>
<td>Windows Server 2008 R2 Group A<br />
Windows Server 2008 Group A<br />
Windows Server 2008 R2 Group B<br />
Windows Server 2008 Group B<br />
Windows Server 2008 R2 Group C<br />
Windows Server 2008 Group C<br />
Windows Vista Volume Editions<br />
Windows 7 Volume Editions</td>
</tr>
</tbody>
</table>
<p><strong>slmgr<br />
</strong>Microsoft tool for configuring and managing activations from Windows. A few useful commands working with KMS.</p>
<p><code>slmgr /dlv<br />
</code>This will give you information regarding your software licensing service. Use this to check the client count contacting the KMS Host.</p>
<p><code>slmgr /rearm<br />
</code>Rearms the activation using the existing product key.</p>
<p><code>slmgr /upk<br />
</code>This will uninstall the product key.</p>
<p><code>slmgr /ipk &lt;Product Key&gt;<br />
</code>This will allow you the enter or change the product key.</p>
<p><code>slmgr /ato<br />
</code>This is the command line to activate windows.</p>
<p><code>nslookup -type=srv _vlmcs._tcp<br />
</code>This will tell you which server is listed in DNS for Volume Licensing. Basically what server is your KMS Server.</p>
<p><strong>Need Default KMS Client key?</strong><br />
Microsoft provide the default KMS clients keys on their TechNet help site. Vista &amp; Server 2008 <a href="http://technet.microsoft.com/en-us/library/cc303280.aspx" target="_blank">here</a> or Windows 7 &amp; Server 2008 R2 <a href="http://technet.microsoft.com/en-us/library/dd772269.aspx" target="_blank">here</a>.</p>
<p><strong><span style="text-decoration: underline;">Installing Windows Server &amp; Windows 7 Using KMS</span></strong></p>
<p><strong>First Server installation of Windows Server 2008 or R2</strong><br />
If you have not used KMS before and you are installing your first Windows Server 2008 use a KMS product key from your licensing agreement. This will act now as your KMS Host server. This product key will activate with Microsoft.</p>
<p><strong>Further Server Installations of  Windows Server 2008 or R2</strong><br />
When it give you the chance to enter a product key do not enter anything, it should by default use a built in KMS Client key. Should you enter the same key as your first server or any other KMS product key you will have two servers acting as KMS Host. This is OK only if you PLAN to have two KMS Host servers. If you entered a KMS product key and realised you shouldn&#8217;t have, then we need to replace this key with a default KMS Client key.</p>
<p>Open a elevated command prompt and use the following commands. A restart will most likely be required after uninstalling the existing product key. You can find the KMS Client product key <a href="http://technet.microsoft.com/en-us/library/cc303280.aspx" target="_blank">here (Vista &amp; Server 2008)</a> or <a href="http://technet.microsoft.com/en-us/library/dd772269.aspx" target="_blank">here (Win7 &amp; Server 2008 R2)</a> , scroll down till you find the <em>KMS Client Setup Keys.</em></p>
<p><code>slmgr /upk<br />
</code> <code>slmgr /ipk &lt;Product Key&gt;</code></p>
<p><strong>Installations Of Windows 7<br />
</strong>Use the same guidelines as Further Server Installations. A default KMS client key is built into the installation of Windows 7, you will notice when installing it will not ask for a product key.</p>
<p><strong>Activating Windows 7 with Windows Server 2008 (not R2)<br />
</strong>You will most likely encounter problems when trying to activate Windows 7 when you have a Windows Server 2008 acting as a KMS Host. The problem here is that the KMS Host only knows about Vista and Server 2008, not Windows 7 and Server 2008 R2. An <a href="http://www.microsoft.com/downloads/details.aspx?familyid=D284F030-642F-443B-85CE-74EF449D5AB4&amp;amp;displaylang=en" target="_blank">update</a> has been released that updates Windows Server 2008. Once the update has been installed on the KMS Host the server will need to be restarted. <em><strong>You will then need to update the KMS Host with a KMS Server 2008 R2 key, even though you are only running Server 2008</strong>.</em> You can find the KMS Host key from your licensing agreement.</p>
<p><code>slmgr /ipk &lt;Product Key&gt;</code></p>
<p>Followed by a stop and start of a KMS Service</p>
<p><code>net stop slsvc</code></p>
<p><code>net start slsvc</code></p>
<p>You should then find your Windows 7 can contact the KMS Host. If the threshold is not met, it will report that it could not activate. This is perfectly normal and you should not worry.<br />
However it is advisable that if your long term plan is to have a number of clients under the threshold then you should consider using MAK keys instead.<br />
See <a href="http://philipwilmot.co.uk/blog/2010/01/windows-7-kms-to-mak/" target="_blank">here</a> for when to use MAK and how to convert to it.</p>
<p>For more information regarding KMS and activation then the <strong>Volume Activation Technical Reference Guide</strong> is a good place to start. It can be found <a href="http://technet.microsoft.com/en-us/library/ee355153.aspx" target="_blank">here</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://philipwilmot.co.uk/blog/2009/12/windows-7-windows-server-2008r2-kms/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

