locked
XP SP3 Sysprep Does Not Prompt for Computer Name RRS feed

  • Question

  • I recently needed to do a "repair" install of Windows XP SP3.  Since then, sysprep seems to ignore some of the commands in the sysprep.inf file.  It will not prompt for a computer name or the cridentials to join the computer to the domain.  I have tried using the latest version of sysprep as well as older versions and they all work fine except after the repair install.  The referance image is on a VM.  A sample of the inf is below.

     


    [Unattended]
    ExtendOemPartition=0
    OemSkipEula=Yes
    KeepPageFile=0
    DriverSigningPolicy=Ignore

    [Components]
    OEAcess = OFF
    WMPOCM = OFF
    WMAccess = OFF

    [GuiUnattended]
    TimeZone=020
    AdminPassword=*
    OemSkipWelcome=1
    OemSkipRegional=1
    OEMDuplicatorstring="v1.3 Image"

    [UserData]
    FullName="IT"
    OrgName="Company"
    ProductKey=xxxxxxxxxxx

    [Display]
    BitsPerPel=32
    Vrefresh=75
    Xresolution=1024
    Yresolution=768

    [Networking]
    InstallDefaultComponents=YES

    [Identification]
    JoinDomain=Company.com
    MachineObjectOU="OU=Desktops,OU=Computers,OU=Locaion,DC=Company,DC=com"

    [SysprepMassStorage]
    ;
    ; Added for Intel SATA Controller Support
    ;
    PCI\VEN_8086&DEV_2682&CC_0104=C:\Drivers\IntelSATA\iastor.inf
    PCI\VEN_8086&DEV_27C3&CC_0104=C:\Drivers\IntelSATA\iastor.inf
    PCI\VEN_8086&DEV_27C6&CC_0104=C:\Drivers\IntelSATA\iastor.inf
    PCI\VEN_8086&DEV_2822&CC_0104=C:\Drivers\IntelSATA\iastor.inf
    PCI\VEN_8086&DEV_282A&CC_0104=C:\Drivers\IntelSATA\iastor.inf
    PCI\VEN_8086&DEV_2653&CC_0106=C:\Drivers\IntelSATA\iaahci.inf
    PCI\VEN_8086&DEV_2681&CC_0106=C:\Drivers\IntelSATA\iaahci.inf
    PCI\VEN_8086&DEV_27C1&CC_0106=C:\Drivers\IntelSATA\iaahci.inf
    PCI\VEN_8086&DEV_27C5&CC_0106=C:\Drivers\IntelSATA\iaahci.inf
    PCI\VEN_8086&DEV_2821&CC_0106=C:\Drivers\IntelSATA\iaahci.inf
    PCI\VEN_8086&DEV_2829&CC_0106=C:\Drivers\IntelSATA\iaahci.inf
    PCI\VEN_8086&DEV_2922&CC_0106=C:\Drivers\IntelSATA\iaahci.inf
    PCI\VEN_8086&DEV_2929&CC_0106=C:\Drivers\IntelSATA\iaahci.inf
    PCI\VEN_8086&DEV_3A02&CC_0106=c:\Drivers\IntelSATA\iaahci.inf
    PCI\VEN_8086&DEV_3B2F&CC_0106=c:\Drivers\IntelSATA\iaahci.inf


    ; Below driverlist are commonly used XP builtin drivers
    ;
    Primary_IDE_Channel=%systemroot%\inf\mshdc.inf
    Secondary_IDE_Channel=%systemroot%\inf\mshdc.inf
    PCMCIA\*PNP0600=%systemroot%\inf\mshdc.inf
    *PNP0600=%systemroot%\inf\mshdc.inf
    PCMCIA\KME-KXLC005-A99E=%systemroot%\inf\mshdc.inf
    PCMCIA\_-NinjaATA--3768=%systemroot%\inf\mshdc.inf
    PCMCIA\FUJITSU-IDE-PC_CARD-DDF2=%systemroot%\inf\mshdc.inf
    *AZT0502=%systemroot%\inf\mshdc.inf
    PCI\CC_0101=%systemroot%\inf\mshdc.inf
    PCI\VEN_10B9&DEV_5215=%systemroot%\inf\mshdc.inf
    PCI\VEN_8086&DEV_2441=%systemroot%\inf\mshdc.inf
    PCI\VEN_8086&DEV_244A=%systemroot%\inf\mshdc.inf
    PCI\VEN_8086&DEV_244B=%systemroot%\inf\mshdc.inf
    PCI\VEN_10B9&DEV_5219=%systemroot%\inf\mshdc.inf
    PCI\VEN_10B9&DEV_5229=%systemroot%\inf\mshdc.inf
    PCI\VEN_1097&DEV_0038=%systemroot%\inf\mshdc.inf
    PCI\VEN_1095&DEV_0640=%systemroot%\inf\mshdc.inf
    PCI\VEN_1095&DEV_0646=%systemroot%\inf\mshdc.inf
    PCI\VEN_0E11&DEV_AE33=%systemroot%\inf\mshdc.inf
    PCI\VEN_8086&DEV_1222=%systemroot%\inf\mshdc.inf
    PCI\VEN_8086&DEV_1230=%systemroot%\inf\mshdc.inf
    PCI\VEN_8086&DEV_7010=%systemroot%\inf\mshdc.inf
    PCI\VEN_8086&DEV_7111=%systemroot%\inf\mshdc.inf
    PCI\VEN_8086&DEV_2411=%systemroot%\inf\mshdc.inf
    PCI\VEN_8086&DEV_2421=%systemroot%\inf\mshdc.inf
    PCI\VEN_8086&DEV_7199=%systemroot%\inf\mshdc.inf
    PCI\VEN_1042&DEV_1000=%systemroot%\inf\mshdc.inf
    PCI\VEN_1039&DEV_0601=%systemroot%\inf\mshdc.inf
    PCI\VEN_1039&DEV_5513=%systemroot%\inf\mshdc.inf
    PCI\VEN_10AD&DEV_0001=%systemroot%\inf\mshdc.inf
    PCI\VEN_10AD&DEV_0150=%systemroot%\inf\mshdc.inf

    [sysprepcleanup]


    Tuesday, October 25, 2011 5:34 PM

Answers

All replies

  • The sysprep is not prompting for a computer name because the vmware script is assigning the name to it.. Disable the floppy device in Vm options.
    Regards, h9ck3r.
    Wednesday, October 26, 2011 5:45 AM
  • Thanks for the suggestion, unfortunately that did not resolve the issue.  I believe I have however been able to narrow the cause down to something specific to the VM.  If I apply the captured image to a physical device then re sysprep it with the exact same inf file it does work.  This is strange as the sysprep process worked perfectly on the VM until the repair install was preformed.  We are using VMWare Workstation 7.1.4.  Any other suggestions?
    Wednesday, October 26, 2011 2:18 PM
  • Found a KB from Microsoft.  Sysprep doesnt support this method after a in place repair.

    http://support.microsoft.com/kb/828287

    • Marked as answer by ScriptMonkey4 Wednesday, October 26, 2011 8:41 PM
    Wednesday, October 26, 2011 8:41 PM