Ghost Solution Suite

 View Only

  • 1.  Sysprep failure from console

    Posted May 31, 2007 03:51 PM
    Greetings!
    My department runs several labs on our campus with various hardware setups.  I decided to tackle one with our newly updated GSS 2.0 software.  I've encountered a few issues with Ghost console and sysprep.  We're running XP and have the proper version of sysprep.  We've been using the GhostCast server for several years and upgraded to 11 in hopes of simplifying some things. 
    I am attempting to pull/create an image from a machine and run sysprep through the console.  I've followed the instructions I found via the Symantec documentation on creating a sysprep configuration and building an image create task.  However, when I run the task, I get a failure message when it tries to run sysprep and it fails to create the image file because of this.   I made sure that the necessary sysprep files (including the .inf) were present on both the client and the console machines when I created the sysprep configuration for the task.  The .inf file is below:

    ;SetupMgrTag
    [Unattended]
        OemSkipEula=Yes
        InstallFilesPath=C:\sysprep\i386

    [GuiUnattended]
        AdminPassword="xxxxx"
        EncryptedAdminPassword=NO
        OEMSkipRegional=1
        TimeZone=35
        OemSkipWelcome=1

    [UserData]
        ProductKey=xxxxxxxxxxx
        FullName="ITDS"
        OrgName="`EKU"
        ComputerName=AC#

    [SetupMgr]
        DistFolder=C:\windist
        DistShare=windist

    [Identification]
        JoinDomain=student.eku.edu

    [Networking]
        InstallDefaultComponents=Yes


    Does anyone have any idea what I could be doing wrong or what is missing?  I'm near my wits end trying to figure this out so we can get our labs reimaged efficiently.  Thanks in advance!

    LD

    Message Edited by DoniL on 05-31-200712:53 PM



  • 2.  RE: Sysprep failure from console

    Posted Jun 01, 2007 12:42 AM
    Hi,
     
    Thanks for posting the sysprep answer file.  There are few things need to be considered.  The ComputerName only accepts letters, numbers and hyphens.  "#" is not valid and will cause auto mini-setup broken.  The other is when using sysprep answer file to join a domain, a domain name, domain admin name and password need to be provided.  They should look like:
     
    [Identification]
    JoinDomain=student.eku.edu
    DomainAdmin=blahblahblah
    DomainAdminPassword=blahblah
     
    You mentioned there is failure message and the task fails, can you please post the message along with the task log?  I'd like to look at the task scenario as well (select the task from right pane then right click and select task scenario).  What is the status of the client machine after the task tailed - does it reboots from Windows into pre-OS DOS and remains in the DOS with communication messages displayed on the screen or does it return to Windows after the reboot?  If it returns to Windows, does Windows mini-setup run?  Also I'd like to know whether you can create an image from the same machine using console task without sysprep?
     
    Best Regards,
    Jenny