PC Review


Reply
Thread Tools Rate Thread

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

 
 
chuwy
Guest
Posts: n/a
 
      14th Jun 2007
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!

 
Reply With Quote
 
 
 
 
Carey Frisch [MVP]
Guest
Posts: n/a
 
      14th Jun 2007
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.

--
Carey Frisch
Microsoft MVP
Windows - Shell/User

---------------------------------------------------------------------------*-----

"chuwy" wrote:

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!

 
Reply With Quote
 
chuwy
Guest
Posts: n/a
 
      15th Jun 2007
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.
> 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.
>
> --
> Carey Frisch
> Microsoft MVP
> Windows - Shell/User
>
> ---------------------------------------------------------------------------**-----
>
> "chuwy" wrote:
>
> 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!



 
Reply With Quote
 
Carey Frisch [MVP]
Guest
Posts: n/a
 
      15th Jun 2007
No.

--
Carey Frisch
Microsoft MVP
Windows - Shell/User

---------------------------------------------------------------------------*-----

"chuwy" wrote:

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.
> 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.
>
> --
> Carey Frisch
> Microsoft MVP
> Windows - Shell/User
>
> ---------------------------------------------------------------------------**-----
>
> "chuwy" wrote:
>
> 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!



 
Reply With Quote
 
silv3rnog@gmail.com
Guest
Posts: n/a
 
      27th Jul 2007
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.
>
> --
> Carey Frisch
> Microsoft MVP
> Windows - Shell/User
>
> ---------------------------------------------------------------------------**-----
>
> "chuwy" wrote:
>
> 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.
> > 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. Eachdifferent
> > type of Windows installation CD has its own unique license agreement.

>
> > --
> > Carey Frisch
> > Microsoft MVP
> > Windows - Shell/User

>
> > ---------------------------------------------------------------------------***-----

>
> > "chuwy" wrote:

>
> > 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!- Masquer le texte des messages précédents -

>
> - Afficher le texte des messages précédents -



 
Reply With Quote
 
silv3rnog@gmail.com
Guest
Posts: n/a
 
      27th Jul 2007
On 14 juin, 22:15, "Carey Frisch [MVP]" <cnfri...@nospamgmail.com>
wrote:
> No.
>
> --
> Carey Frisch
> Microsoft MVP
> Windows - Shell/User
>
> ---------------------------------------------------------------------------**-----
>
> "chuwy" wrote:
>
> 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.
> > 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. Eachdifferent
> > type of Windows installation CD has its own unique license agreement.

>
> > --
> > Carey Frisch
> > Microsoft MVP
> > Windows - Shell/User

>
> > ---------------------------------------------------------------------------***-----

>
> > "chuwy" wrote:

>
> > 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!- Masquer le texte des messages précédents -

>
> - Afficher le texte des messages précédents -



 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Retail / Upgrade product key on SYSPREP'd image? Gordon Fecyk Windows XP Setup 1 26th Mar 2005 09:38 PM
WinXP activation, sysprep, open license, retail license =?Utf-8?B?Sm9lc0NhdA==?= Windows XP Setup 1 12th Mar 2005 10:00 PM
Sysprep and HAL Types Kevin Vaughn Windows XP Hardware 2 18th Nov 2003 07:49 PM
Changing location of Emit built types when running as a Windows service Urs Vogel Microsoft C# .NET 1 30th Oct 2003 11:51 AM
Sysprep and different types of machines annoyed at the lack of documentation Windows XP Setup 1 28th Oct 2003 11:45 PM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 03:23 AM.