Deployment of multiple computers using cloning of the first machine RRS feed

  • Question

  • I am in the process of installing twelve new computers with the same configuration.  After removing all of the bloatware that comes on the machine from the manufacturer, installing all of the Windows XP updates, installing MS Office corporate, and installing all of the MS Office updates, I want to clone the hard drive and simply reproduce the image on the remaining machines to save time.  My concern is that even though each machine has a valid Windows Vista Business w/ XP downgrade Product Key from the manufacturer,  when the hard drive is cloned they will all end up with the same product key and appear to Microsoft as if one number is being used illegally multiple times and not allow for future updates.  My question, is there a way to reset the product keys to the original product keys (easily) from the manufacturer after the hard drives are cloned?
    Thursday, August 6, 2009 9:53 PM


All replies

  • Hello BobTechSupervisor,

      Yes, you can use the http://www.microsoft.com/genuine/selfhelp/XPPkuinst.aspx to change out the cloned key with the proper key.

    Hope that helps,
    Darin MS
    Friday, August 7, 2009 4:17 PM
  • Hello BobTechSupervisor,

    Especially if these computers are going to be participating in a Windows Server domain, you plan is not only going to run afoul of WGA, you're going to have issues with the domain as well.

    Microsoft supports two methods of deployment via cloning:  (1) use the OEM Preinstallation Kit if you are an OEM or are deploying OEM images, and (2) use the sysprep utility if you are deploying customized Volume Licensing images.

    The Product Key Updater will change the Product key and as such will address WGA issues, but it does not to my knowledge address changing the SID.  See this MS KB:  http://support.microsoft.com/default.aspx?scid=kb;EN-US;314828
    For great advice on all topics XP, visit http://www.annoyances.org/exec/forum/winxp
    Friday, August 7, 2009 4:36 PM
  • Thanks for both of the replys.  After running the Windows Product Key Update Tool it gives me the following error message "The product key entered  is not a valid key for this system."  I have verified the Key on the Windows Tag and retyped it several times with no luck.  After following Dan's link and reading about SIDs I thought it might need the original SID.  After a restore from the manufacturers disks I ran NewSID and recorded the SID.  I then reloaded the cloned image, ran NewSID again, enteredthe original SID, rebooted, then ran Key Updater, with the same results.  Oh well, so much for a good idea to save time.
    Friday, August 7, 2009 10:39 PM
  • Hello BobTechSupervisor,

    On one of the computers that has the newly purchased XP installed, run this utility, click the Copy button to copy its report to the clipboad, then come back and open up a reply, then Paste the report into the reply.

    Let's have a look, hopefully you did not end up buying counterfeits!
    For great advice on all topics XP, visit http://www.annoyances.org/exec/forum/winxp
    Saturday, August 8, 2009 12:30 AM
  • What utility Dan?  But I am pretty sure that the XP is not counterfeit.  These are brand new machines from HP in factory sealed boxes, each with a different product key.
    Sunday, August 9, 2009 12:09 PM
  • Hello BobTechSupervisor,

    Yikes, I forgot to provide the link to the mgadiag utility:  http://go.microsoft.com/fwlink/?linkid=52012

    When people enter the CoA PK into the PK updater and it returns the "not valid for this system" error, that usually means either a product key-product mismatch (trying to use an XP Home PK on an XP Pro installation, for example).  Sometimes the counterfeit stuff has Volume Licensing PKs printed on fake OEM CoA, which would also return that "not valid for this system error."
    For great advice on all topics XP, visit http://www.annoyances.org/exec/forum/winxp
    Monday, August 10, 2009 12:33 AM
  • Dan,

    Thanks for all the assistance.  Here are the results of mgadiag.

    Diagnostic Report (1.9.0011.0):
    WGA Data-->
    Validation Status: Genuine
    Validation Code: 0

    Cached Validation Code: N/A
    Windows Product Key: *****-*****-2MDY9-F6J9M-K42BQ
    Windows Product Key Hash: jY+nlE0RT38EEXpeUqSdQPABSQc=
    Windows Product ID: 76487-OEM-2211906-00101
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 5.1.2600.2.00010100.3.0.pro
    ID: {4213BE86-223C-438A-AEFF-F99E30F15880}(3)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: Registered,
    Signed By: Microsoft
    Product Name: N/A
    Architecture: N/A
    Build lab: N/A
    TTS Error: N/A
    Validation Diagnostic: 025D1FF3-230-1
    Resolution Status: N/A

    WgaER Data-->
    ThreatID(s): N/A
    Version: N/A

    WGA Notifications Data-->
    Cached Result: 0
    File Exists: Yes
    WgaTray.exe Signed By: Microsoft
    WgaLogon.dll Signed By: Microsoft

    OGA Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    OGAExec.exe Signed By: N/A, hr = 0x80070002
    OGAAddin.dll Signed By: N/A, hr = 0x80070002

    OGA Data-->
    Office Status: 100 Genuine
    Microsoft Office Professional Edition 2003 - 100 Genuine
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: B4D0AA8B-604-645_B4D0AA8B-604-645_025D1FF3-230-1_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files\Internet Explorer\IEXPLORE.exe
    Download signed ActiveX controls: Prompt
    Download unsigned ActiveX controls: Disabled
    Run ActiveX controls and plug-ins: Allowed
    Initialize and script ActiveX controls not marked as safe: Disabled
    Allow scripting of Internet Explorer Webbrowser control: Disabled
    Active scripting: Allowed
    Script ActiveX controls marked as safe for scripting: Allowed

    File Scan Data-->

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{4213BE86-223C-438A-AEFF-F99E30F15880}</UGUID><Version>1.9.0011.0</Version><OS>5.1.2600.2.00010100.3.0.pro</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-K42BQ</PKey><PID>76487-OEM-2211906-00101</PID><PIDType>2</PIDType><SID>S-1-5-21-3516855654-1342095433-1210078382</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>HP Compaq dx2450 Microtower</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies, LTD</Manufacturer><Version> 5.60</Version><SMBIOSVersion major="2" minor="4"/><Date>20090220000000.000000+000</Date><SLPBIOS>Compaq,Hewlett,Hewlett,Compaq</SLPBIOS></BIOS><HWID>B9E533F701840079</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central Standard Time(GMT-06:00)</TimeZone><iJoin>0</iJoin><SBID><stat>2</stat><msppid></msppid><name>Hewlett-Packard Company</name><model>HP Compaq dx2450 Microtower</model></SBID><OEM/><GANotification><File Name="WgaTray.exe" Version=""/><File Name="WgaLogon.dll" Version=""/></GANotification></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{90110409-6000-11D3-8CFE-0150048383C9}"><LegitResult>100</LegitResult><Name>Microsoft Office Professional Edition 2003</Name><Ver>11</Ver><Val>146447DE76DA502</Val><Hash>8bPBtQNCUZFJsBByyEzv7lB/kEk=</Hash><Pid>73931-641-0283161-57476</Pid><PidType>14</PidType></Product></Products><Applications><App Id="15" Version="11" Result="100"/><App Id="16" Version="11" Result="100"/><App Id="18" Version="11" Result="100"/><App Id="19" Version="11" Result="100"/><App Id="1A" Version="11" Result="100"/><App Id="1B" Version="11" Result="100"/><App Id="44" Version="11" Result="100"/></Applications></Office></Software></GenuineResults>  

    Licensing Data-->

    HWID Data-->

    OEM Activation 1.0 Data-->
    BIOS string matches: yes
    Marker string from BIOS: 10072:Compaq Computer Corporation|1005F:Compaq Computer Corporation|1005F:Compaq Computer Corporation|1005F:Hewlett-Packard Company
    Marker string from OEMBIOS.DAT: Compaq,Hewlett,Hewlett,Compaq

    OEM Activation 2.0 Data-->

    Monday, August 10, 2009 4:32 PM