Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows VistaWindows XPWindows MeWindows 98Windows 95Virtual PCInternet ExplorerOutlook ExpressWindows MediaSecurity
Related Topics
MS Server ProductsMS OfficePC HardwareMore Topics ...

Windows Forum / Windows XP / Setup and Deployment / July 2007

Tip: Looking for answers? Try searching our database.

Changing Sysprep VLK Windows XP for other types: OEM & Retail

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
chuwy - 14 Jun 2007 19:07 GMT
In our environment, we already have a packaged XP Professional image
(base OS) created for our workstations that uses Volume License Keys
and deployed with Sysprep.  From time to time, we need to clean out
laptops which has OEM CDKEYs, those COA sticker on the bottom of the
laptop.  However, a XP image created for VLK environment will not take
a OEM or Retail CDKEY, what do I need to change to allow Syspre to
accept those keys?  Is it even a valid approach to do this, to my
understanding, the files across the VLK, OEM, and Retail version are
different.  From what I gathered, the PIDGEN.DLL file in SYSTEM32
tells Windows which type it is, maybe we can switch that out for the
OEM and Retail version?  There is also a SETUPP.INI file that contains
the PID field we can change to type of Windows installing, but I see
that is only for a new installation of Windows, it doesn't help me
when I have a already packaged Windows XP image.

Thanks!
Carey Frisch  [MVP] - 14 Jun 2007 21:11 GMT
VL product keys only work with the appropriate VL Windows installation CD.
OEM product keys only work with the appropriate OEM Windows installation CD.
Retail product keys only worth with the appropriate retail Windows installation CD.
Thus, one cannot use an OEM product key with a VL Windows installation CD.
Product keys unlock the license installed by the installation CD.  Each different
type of Windows installation CD has its own unique license agreement.

Signature

Carey Frisch
Microsoft MVP
Windows - Shell/User

---------------------------------------------------------------------------­-----

In our environment, we already have a packaged XP Professional image
(base OS) created for our workstations that uses Volume License Keys
and deployed with Sysprep.  From time to time, we need to clean out
laptops which has OEM CDKEYs, those COA sticker on the bottom of the
laptop.  However, a XP image created for VLK environment will not take
a OEM or Retail CDKEY, what do I need to change to allow Syspre to
accept those keys?  Is it even a valid approach to do this, to my
understanding, the files across the VLK, OEM, and Retail version are
different.  From what I gathered, the PIDGEN.DLL file in SYSTEM32
tells Windows which type it is, maybe we can switch that out for the
OEM and Retail version?  There is also a SETUPP.INI file that contains
the PID field we can change to type of Windows installing, but I see
that is only for a new installation of Windows, it doesn't help me
when I have a already packaged Windows XP image.

Thanks!
chuwy - 15 Jun 2007 03:54 GMT
I understand that the CDKEY will work with the appropriately types of
Windows (VLK, OEM, Retail).  What I am trying to find out is, is there
a configuration one can perform to alter a current XP image build to a
different type of Windows so it allows the Sysprep installation with
pre-configured settings with different types of CDKEYs as deem
appropriate.  Essentially, what it means for me is that I don't have
to make a separately new XP images for VLK, OEM, and Retail,
configured them the same, package it with sysprep, and have 3
different CDs.

On Jun 14, 1:11 pm, "Carey Frisch  [MVP]" <cnfri...@nospamgmail.com>
wrote:
> VL product keys only work with the appropriate VL Windows installation CD.
> OEM product keys only work with the appropriate OEM Windows installation CD.
[quoted text clipped - 26 lines]
>
> Thanks!
Carey Frisch  [MVP] - 15 Jun 2007 04:15 GMT
No.

Signature

Carey Frisch
Microsoft MVP
Windows - Shell/User

---------------------------------------------------------------------------­-----

I understand that the CDKEY will work with the appropriately types of
Windows (VLK, OEM, Retail).  What I am trying to find out is, is there
a configuration one can perform to alter a current XP image build to a
different type of Windows so it allows the Sysprep installation with
pre-configured settings with different types of CDKEYs as deem
appropriate.  Essentially, what it means for me is that I don't have
to make a separately new XP images for VLK, OEM, and Retail,
configured them the same, package it with sysprep, and have 3
different CDs.

On Jun 14, 1:11 pm, "Carey Frisch  [MVP]" <cnfri...@nospamgmail.com>
wrote:
> VL product keys only work with the appropriate VL Windows installation CD.
> OEM product keys only work with the appropriate OEM Windows installation CD.
[quoted text clipped - 28 lines]
>
> Thanks!
silv3rnog@gmail.com - 27 Jul 2007 19:28 GMT
Simple solution to change OEM to VLK.

Unlike what Carey Frisch said, you can your XP VLK disc to solve the
problem.

Boot from the disc, press 'Enter' when prompted to install Windows,
Press 'F8' to accept the agreement, and then select your system drive
and press 'R'. This will run the Windows XP repair feature, which will
keep all your old data, yet replace the Windows components. You'll
enter in the VLK, and you will be set.

On 14 juin, 22:15, "Carey Frisch  [MVP]" <cnfri...@nospamgmail.com>
wrote:
> No.
>
[quoted text clipped - 52 lines]
>
> - Afficher le texte des messages pr?c?dents -
silv3rnog@gmail.com - 27 Jul 2007 19:29 GMT
On 14 juin, 22:15, "Carey Frisch  [MVP]" <cnfri...@nospamgmail.com>
wrote:
> No.
>
[quoted text clipped - 52 lines]
>
> - Afficher le texte des messages pr?c?dents -
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.