<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Sysprep different machines OEM licensing and retail questions]]></title><description><![CDATA[<p dir="auto">I work in a computer shop and we get many different variations of machines. I have found all of the sysprepping resources I would need to make things work on these machines but I’m concerned about the licensing.</p>
<p dir="auto">I planned to create a few master images and activate them after windows is installed. I usually call in all the OEM keys anyway after installing by hand.  Microsofts article states that sysprepping an OEM is unsupported but that doesn’t mean impossible.</p>
<p dir="auto">So my question is,  if I use an OEM winxp SP3 or a retail SP3 to do my initial master image, will I be able to activate it properly afterwards or will sysprepping this convert my licensing to corp somehow hoping for a VLK key?</p>
<p dir="auto">I noticed some people leave a series of X’s where the VLK key would go. Does this tell sysprep that we won’t be providing a key at that moment or does it error out at that point?  You can imagine the envy I have for techs that get to work with the same hardware all day long. <img src="http://forums.fogproject.org/assets/plugins/nodebb-plugin-emoji/emoji/android/1f615.png?v=7ddmg541643" class="not-responsive emoji emoji-android emoji--confused" style="height:23px;width:auto;vertical-align:middle" title=":/" alt="😕" /></p>
<p dir="auto">I did some sysprepping a very long time ago and remember having it not work properly with OEM keys but I’m not sure if that was a funny disc I was using from the start or if it has to do with the sysprep itself.</p>
]]></description><link>http://forums.fogproject.org/topic/334/sysprep-different-machines-oem-licensing-and-retail-questions</link><generator>RSS for Node</generator><lastBuildDate>Sat, 17 Oct 2026 12:55:24 GMT</lastBuildDate><atom:link href="http://forums.fogproject.org/topic/334.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 20 Feb 2012 06:31:50 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Sysprep different machines OEM licensing and retail questions on Wed, 22 Feb 2012 13:33:37 GMT]]></title><description><![CDATA[<p dir="auto">No problem.</p>
<p dir="auto">I’ll also point you to the updated version of oemscan which is just about perfect in my opinion - [url]<a href="http://siginetsoftware.com/forum/showthread.php?541-OEMSCAN_ADDON_MULTIOEM-v1.8%5B/url%5D" target="_blank" rel="noopener noreferrer nofollow ugc">http://siginetsoftware.com/forum/showthread.php?541-OEMSCAN_ADDON_MULTIOEM-v1.8[/url]</a></p>
<p dir="auto">I’ve worked on that project with mr. Smartiepants to some degree testing it out.  It works great as a batch script or an SFX package.</p>
<p dir="auto">Good luck, and if you need more help let us know.</p>
]]></description><link>http://forums.fogproject.org/post/6150</link><guid isPermaLink="true">http://forums.fogproject.org/post/6150</guid><dc:creator><![CDATA[ssx4life]]></dc:creator><pubDate>Wed, 22 Feb 2012 13:33:37 GMT</pubDate></item><item><title><![CDATA[Reply to Sysprep different machines OEM licensing and retail questions on Mon, 20 Feb 2012 20:06:21 GMT]]></title><description><![CDATA[<p dir="auto">Thanks! I’ll try this and report back with my findings.</p>
]]></description><link>http://forums.fogproject.org/post/6098</link><guid isPermaLink="true">http://forums.fogproject.org/post/6098</guid><dc:creator><![CDATA[bradgillap]]></dc:creator><pubDate>Mon, 20 Feb 2012 20:06:21 GMT</pubDate></item><item><title><![CDATA[Reply to Sysprep different machines OEM licensing and retail questions on Mon, 20 Feb 2012 15:28:00 GMT]]></title><description><![CDATA[<p dir="auto">You actually can use OEM keys with sysprep. You need to make sure they are ROYALTY OEM KEYS, as shown here - [url]<a href="http://en.wikipedia.org/wiki/System_Locked_Pre-installation%5B/url%5D" target="_blank" rel="noopener noreferrer nofollow ugc">http://en.wikipedia.org/wiki/System_Locked_Pre-installation[/url]</a></p>
<p dir="auto">Your second task will be to use the runonce command and make a batch script for this following application below. It will auto insert the oemslp key based off of the hardware bios.</p>
<p dir="auto">[url]<a href="http://www.msfn.org/board/topic/82638-oemscan-automated-multi-manufacture-pre-activation-utility/%5B/url%5D" target="_blank" rel="noopener noreferrer nofollow ugc">http://www.msfn.org/board/topic/82638-oemscan-automated-multi-manufacture-pre-activation-utility/[/url]</a></p>
<p dir="auto">Also to clarify further you want to use an OEM MEDIA DISK (a generic one from MSFN).  A pressed dell / hp / etc. disk is not what you want.  You want an un-edited oem disk for XP (one with a hologram for example).  Use that media to build your image.</p>
]]></description><link>http://forums.fogproject.org/post/6096</link><guid isPermaLink="true">http://forums.fogproject.org/post/6096</guid><dc:creator><![CDATA[ssx4life]]></dc:creator><pubDate>Mon, 20 Feb 2012 15:28:00 GMT</pubDate></item></channel></rss>