<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Windows activation annoyances &#8211; not one but two</title>
	<atom:link href="http://www.itwriting.com/blog/1932-windows-activation-annoyances-not-one-but-two.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.itwriting.com/blog/1932-windows-activation-annoyances-not-one-but-two.html</link>
	<description>Tech writing blog</description>
	<lastBuildDate>Sun, 12 Feb 2012 21:04:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Emil Ehrs</title>
		<link>http://www.itwriting.com/blog/1932-windows-activation-annoyances-not-one-but-two.html/comment-page-1#comment-948654</link>
		<dc:creator>Emil Ehrs</dc:creator>
		<pubDate>Fri, 09 Dec 2011 17:16:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.itwriting.com/blog/1932-windows-activation-annoyances-not-one-but-two.html#comment-948654</guid>
		<description>I can also confirm that the HPActive.cmd script fixed the validation problem.</description>
		<content:encoded><![CDATA[<p>I can also confirm that the HPActive.cmd script fixed the validation problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pierre John</title>
		<link>http://www.itwriting.com/blog/1932-windows-activation-annoyances-not-one-but-two.html/comment-page-1#comment-583008</link>
		<dc:creator>Pierre John</dc:creator>
		<pubDate>Mon, 16 May 2011 07:22:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.itwriting.com/blog/1932-windows-activation-annoyances-not-one-but-two.html#comment-583008</guid>
		<description>I can confirm that the HPActive.cmd script also fixes the problem with HP-branded SBS 2011 media.</description>
		<content:encoded><![CDATA[<p>I can confirm that the HPActive.cmd script also fixes the problem with HP-branded SBS 2011 media.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kieran</title>
		<link>http://www.itwriting.com/blog/1932-windows-activation-annoyances-not-one-but-two.html/comment-page-1#comment-226952</link>
		<dc:creator>Kieran</dc:creator>
		<pubDate>Fri, 13 Aug 2010 11:00:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.itwriting.com/blog/1932-windows-activation-annoyances-not-one-but-two.html#comment-226952</guid>
		<description>Ron is correct. I&#039;m trying to install SBS2008Std (HP Branded) on a ML350G6 that has the 2nd-license Server 2008 running Hyper-V as a host. I couldn&#039;t install SBS2008 as a guest as it said the system is not a supported platform. Running HPActive.cmd (as per post http://bit.ly/bCi3FA) has let me install SBS2008. No restart of the physical (host) OS was required.</description>
		<content:encoded><![CDATA[<p>Ron is correct. I&#8217;m trying to install SBS2008Std (HP Branded) on a ML350G6 that has the 2nd-license Server 2008 running Hyper-V as a host. I couldn&#8217;t install SBS2008 as a guest as it said the system is not a supported platform. Running HPActive.cmd (as per post <a href="http://bit.ly/bCi3FA" rel="nofollow">http://bit.ly/bCi3FA</a>) has let me install SBS2008. No restart of the physical (host) OS was required.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ron</title>
		<link>http://www.itwriting.com/blog/1932-windows-activation-annoyances-not-one-but-two.html/comment-page-1#comment-226733</link>
		<dc:creator>ron</dc:creator>
		<pubDate>Thu, 12 Aug 2010 22:46:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.itwriting.com/blog/1932-windows-activation-annoyances-not-one-but-two.html#comment-226733</guid>
		<description>For the benefit of anyone else who finds this post, the HPactive.cmd program on the HP-branded Windows server OS DVD does the same thing as the previous HPVirtualOSE.exe-plus-vbs script combo.  After the host OS is installed and Hyper-V installed, run HPactive.cmd to allow the HP-branded OS media to be used for a Hyper-V guest OS install.</description>
		<content:encoded><![CDATA[<p>For the benefit of anyone else who finds this post, the HPactive.cmd program on the HP-branded Windows server OS DVD does the same thing as the previous HPVirtualOSE.exe-plus-vbs script combo.  After the host OS is installed and Hyper-V installed, run HPactive.cmd to allow the HP-branded OS media to be used for a Hyper-V guest OS install.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tim</title>
		<link>http://www.itwriting.com/blog/1932-windows-activation-annoyances-not-one-but-two.html/comment-page-1#comment-150621</link>
		<dc:creator>tim</dc:creator>
		<pubDate>Thu, 26 Nov 2009 07:22:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.itwriting.com/blog/1932-windows-activation-annoyances-not-one-but-two.html#comment-150621</guid>
		<description>Ross

Well, there is always the trial approach. Let us know if you get a sensible answer from HP though, or the LHBL.vbs script.

Tim</description>
		<content:encoded><![CDATA[<p>Ross</p>
<p>Well, there is always the trial approach. Let us know if you get a sensible answer from HP though, or the LHBL.vbs script.</p>
<p>Tim</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ross</title>
		<link>http://www.itwriting.com/blog/1932-windows-activation-annoyances-not-one-but-two.html/comment-page-1#comment-150618</link>
		<dc:creator>Ross</dc:creator>
		<pubDate>Thu, 26 Nov 2009 06:25:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.itwriting.com/blog/1932-windows-activation-annoyances-not-one-but-two.html#comment-150618</guid>
		<description>Hi Guys,

I came accross the same problem and have so far spent about 6 hours in total talking to HP and still no result. How ever there is a Advisory Document on the HP website that is worth a read except for when you get to Step 3(Thats is where i am at but no luck finding the File). HP have no idea what the problem is!

Ross</description>
		<content:encoded><![CDATA[<p>Hi Guys,</p>
<p>I came accross the same problem and have so far spent about 6 hours in total talking to HP and still no result. How ever there is a Advisory Document on the HP website that is worth a read except for when you get to Step 3(Thats is where i am at but no luck finding the File). HP have no idea what the problem is!</p>
<p>Ross</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Susan</title>
		<link>http://www.itwriting.com/blog/1932-windows-activation-annoyances-not-one-but-two.html/comment-page-1#comment-147937</link>
		<dc:creator>Susan</dc:creator>
		<pubDate>Sun, 01 Nov 2009 01:05:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.itwriting.com/blog/1932-windows-activation-annoyances-not-one-but-two.html#comment-147937</guid>
		<description>Can you ping me directly because something is not right.  As far as we&#039;re aware it shouldn&#039;t bios check you in order to set up that virtual.</description>
		<content:encoded><![CDATA[<p>Can you ping me directly because something is not right.  As far as we&#8217;re aware it shouldn&#8217;t bios check you in order to set up that virtual.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tim</title>
		<link>http://www.itwriting.com/blog/1932-windows-activation-annoyances-not-one-but-two.html/comment-page-1#comment-147858</link>
		<dc:creator>tim</dc:creator>
		<pubDate>Sat, 31 Oct 2009 07:33:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.itwriting.com/blog/1932-windows-activation-annoyances-not-one-but-two.html#comment-147858</guid>
		<description>@Susan

There&#039;s a ton of Product IDs in the package:

One for SBS physical
One for 2nd server physical
One for SBS virtual
One for 2nd server virtual

plus a few for SQL :-)

The one that was obscured was 2nd server physical - which is needed for the hyper-v host.

Since the product specifically comes with a product key for sbs virtual you would think it is supported; but the media supplied fails because of a pre-check for HP hardware. 

Tim</description>
		<content:encoded><![CDATA[<p>@Susan</p>
<p>There&#8217;s a ton of Product IDs in the package:</p>
<p>One for SBS physical<br />
One for 2nd server physical<br />
One for SBS virtual<br />
One for 2nd server virtual</p>
<p>plus a few for SQL <img src='http://www.itwriting.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>The one that was obscured was 2nd server physical &#8211; which is needed for the hyper-v host.</p>
<p>Since the product specifically comes with a product key for sbs virtual you would think it is supported; but the media supplied fails because of a pre-check for HP hardware. </p>
<p>Tim</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Susan</title>
		<link>http://www.itwriting.com/blog/1932-windows-activation-annoyances-not-one-but-two.html/comment-page-1#comment-147840</link>
		<dc:creator>Susan</dc:creator>
		<pubDate>Sat, 31 Oct 2009 01:32:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.itwriting.com/blog/1932-windows-activation-annoyances-not-one-but-two.html#comment-147840</guid>
		<description>P.S. you can slrearm that eval and tell it to go away.</description>
		<content:encoded><![CDATA[<p>P.S. you can slrearm that eval and tell it to go away.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Susan</title>
		<link>http://www.itwriting.com/blog/1932-windows-activation-annoyances-not-one-but-two.html/comment-page-1#comment-147839</link>
		<dc:creator>Susan</dc:creator>
		<pubDate>Sat, 31 Oct 2009 01:31:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.itwriting.com/blog/1932-windows-activation-annoyances-not-one-but-two.html#comment-147839</guid>
		<description>Mind you I&#039;m more familiar with Volume license and not OEM media but there&#039;s typically two product keys.  One is a key to be used on a physical install, the other is a key to be used in a virtual install.

So that I&#039;m clear you installed a base Win2k8?

And then tried to put the OEM of SBS 2008 in that HyperV platform?</description>
		<content:encoded><![CDATA[<p>Mind you I&#8217;m more familiar with Volume license and not OEM media but there&#8217;s typically two product keys.  One is a key to be used on a physical install, the other is a key to be used in a virtual install.</p>
<p>So that I&#8217;m clear you installed a base Win2k8?</p>
<p>And then tried to put the OEM of SBS 2008 in that HyperV platform?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

