Ghost Solution Suite

 View Only
Back to discussions
Expand all | Collapse all

Configuration Failed -- Error id: 338 1.1:\sysprep\sysprep.inf

  • 1.  Configuration Failed -- Error id: 338 1.1:\sysprep\sysprep.inf

    Posted Mar 23, 2007 11:59 AM
    We recently upgrade from GSS 1.0 to 2.0 and since then we have probleme with computer configuration task. It always fail after after cloning. When the client reboot it stay in the ghost virtual boot partition. If we exit the client console manually the computer reboot and the sysprep do is job fine. Of course, the configuration isn't the one it should be. If we re-run a configuration task, every things work fine. I don't understand why is it not working right after a cloning task? Can someone help me on this?
      
    The only thing that as change in the image is that we upgrade the ghost client. The image as been captured in GSS 2.0 with the same sysprep files that we were using with GSS 1.0.
     
    Console Message
    Create machine account  Success
    Prepare Configuration      Success
    Configuration                    Failed
    Error Log
    Error id: 338  1.1:\sysprep\sysprep.inf
     
     
    Client Message
    Received message Message <Clone>{ Name = "SERVERpushXXX"}
    Received message Message <Configuration>{ ErrorFile = "ghconfer.txt"}
    ...
    ghconfig.exe /a
    ...
    Received message Message <Configuration>{ ErrorFile = "ghconfer.txt"}
    Received message Message <Open>{ What = File, Name = "ghconfer.txt" Mode Read}
    ...
     
    Sysprep
    ;SetupMgrTag
    [Unattended]
       OemSkipEula=Yes
       InstallFilesPath=C:\sysprep\i386
       DriverSigningPolicy=Ignore
       UpddateInstalledDriver=Yes
       OemPNPDriversPath=windows\inf;windows;windows\Driver Cache\i386;drv\620\aud;drv\620\chip;drv\mon;drv\620\nic;drv\620\vid;drv\380\aud;drv\380\chip;drv\mon;drv\380\nic;drv\380\vid;
    [GuiUnattended]
       AdminPassword=*
       EncryptedAdminPassword=NO
       OEMSkipRegional=1
       TimeZone=35
       OemSkipWelcome=1
    [UserData]
       ProductKey=XXX-XXX-XXX-XXX-XXX
       FullName="CI"
       OrgName="UdeS"
       ComputerName=*
    [Display]
       BitsPerPel=32
       Xresolution=1280
       YResolution=1024
       Vrefresh=60
    [TapiLocation]
       CountryCode=107
       AreaCode=819
    [RegionalSettings]
       LanguageGroup=1
       SystemLocale=00000c0c
       UserLocale=00000c0c
       InputLocale=0c0c:00001009
    [SetupMgr]
       DistFolder=C:\sysprep\i386
       DistShare=windist
    [Identification]
       JoinWorkgroup=WORKGROUP
    [Networking]
       InstallDefaultComponents=Yes
    [SysprepMassStorage]
    ;Dell precision 380 et GX620
    PCI\VEN_8086&DEV_27C0=C:\drv\620\chip\ich7ide.inf
    PCI\VEN_8086&DEV_27DF=C:\drv\620\chip\ich7ide.inf
    ;Dell precision 380 AHCI
    PCI\VEN_8086&DEV_27C1=C:\drv\380\chip\iaahci.inf


  • 2.  RE: Configuration Failed -- Error id: 338 1.1:\sysprep\sysprep.inf

    Posted Mar 23, 2007 10:06 PM
    With post-configuration in GSS2, it's done by a program in DOS rather than by drivers that run during Windows boot; one of the things this allows us to do is work much, much better with Sysprep - if there's a setting you ask the console to change but Sysprep is set to run in the image, the GhConfig tool detects this and automatically edits the sysprep.inf file in the image to get the right settings applied (whereas in earlier versions, Sysprep would often strip out the changes the console tried to make).

    Unfortunately, the code in GhConfig that processes the INF file didn't really understand the proper INF file syntax, so this part:

    [SysprepMassStorage]
    ;Dell precision 380 et GX620
    PCI\VEN_8086&DEV_27C0=C:\drv\620\chip\ich7ide.inf
    PCI\VEN_8086&DEV_27DF=C:\drv\620\chip\ich7ide.inf
    ;Dell precision 380 AHCI
    PCI\VEN_8086&DEV_27C1=C:\drv\380\chip\iaahci.inf

    is making it choke with the error 338, because it thinks - incorrectly - that the second comment line saying "Dell precision 380 AHCI" isn't valid.

    Completely editing out that comment line should let it proceed, but we also have a version of GhConfig that is much more robust in its handling of INF files and if you get in touch with me at nigel dot bree at gmail dot com I can arrange a download for you.

    Message Edited by Nigel Bree on 03-24-200702:07 PM