C
chuwy
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!
(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!