Sysprep problem
Results 1 to 5 of 5

Thread: Sysprep problem

  1. #1
    Member
    Join Date
    Sep 2004
    Location
    Netherlands
    Posts
    63

    Sysprep problem

    It's been a while sinds I used sysprep to create an image... since Windows 2000 to be exact. So probably I'm just overlooking something.. Hopefully one of you guys can help me out.

    I've created a Windows XP install. Including software and SP2 and everything. The install is ready for the build.
    I create a folder c:\sysprep, add the necessary files and using setupmgr.exe I create a sysprep.inf.

    All proud and ready to go I run sysprep and tell it to "reseal". The pc shuts down and I feel confident. Until....
    I start the pc again and find that it's not using the settings I defined in sysprep.inf.

    I've tried putting the sysprep folder in different locations and I've looked for switches to tell it to use the .inf file, which I can't find.

    Does anyone know what I'm doing wrong here?

    In advance, thanks for your time and thoughts!

  2. #2
    Member tin.roof.rabbit's Avatar
    Join Date
    Apr 2006
    Posts
    63
    Sysprep will default to the sysprep.inf file that is in the c:\sysprep folder but it depends on what you are telling sysprep to do and how you are declaring the options within the inf. Some of the statements in the inf are only controlled by certain switches.

    are you also using the -mini option?

    Do you have any [OEM *] declarations?

    Sysprep can be a frustrating and confusing beast to work with. I have had to open incidents with Microsoft more then once to help figure out why something is not working.

    You can also check your setup*.log files in the root of the windows directory. This file is appended each time the OS goes through a setup routine.

  3. #3
    Member
    Join Date
    Sep 2004
    Location
    Netherlands
    Posts
    63
    Thanks for your help.

    I do have said declarations. The sysprep.inf contains the serial, the fact that I accept the EULA, the local admin password I want to set, etc.
    It has been created using the setupmgr.exe tool, so the way the file is set up should also be correct...

    It doesn't take ANY of my configured options...

  4. #4
    Member tin.roof.rabbit's Avatar
    Join Date
    Apr 2006
    Posts
    63
    The only thing I can think of is that you are not using the correct paramiters together. If you have all of your paramiters entered correctly Sysprep should pass through the information correct.

    Generally we use the -reseal -mini -quiet when we are creating our images. Below is a sampling from Microsoft's KB article on XP's sysprep.

    Sysprep parameters
    You can use the following optional parameters with the Sysprep command in Windows XP: -activated - Do not reset the grace period for Windows product activation. Use this parameter only if you have activated the Windows installation in the factory.

    Important The product key that you use to activate the Windows installation must match the product key that is located on the COA sticker that is attached to that particular computer.
    -audit - Restarts the computer in Factory mode without having to generate new security IDs (SIDs) or process any items in the [OEMRunOnce] section of the Winbom.ini file. Use this command-line parameter only if the computer is already in Factory mode.
    -bmsd - Populates all the available mass storage devices in the [SysprepMassStorage] section.
    -clean - Clears the critical devices database that is used by the [SysprepMassStorage] section in the Sysprep.inf file.

    -factory - Restarts in a network-enabled state without displaying Windows Welcome or mini-Setup. This parameter is useful for updating drivers, running Plug and Play enumeration, installing programs, testing, configuring the computer with customer data, or making other configuration changes in your factory environment. For companies that use disk imaging (or cloning) software, Factory mode can reduce the number of images that are required.

    When all the tasks in Factory mode are complete, run the Sysprep.exe file by using the -reseal parameter to prepare the computer for end-user delivery.
    -forceshutdown - Shuts down the computer after the Sysprep.exe file finishes.

    Note Use this parameter with computers that have an ACPI BIOS that do not shut down correctly with the default behavior of the Sysprep.exe file.
    -mini - Configures Microsoft Windows XP Professional to use Mini-Setup instead of Windows Welcome. This parameter does not affect Microsoft Windows XP Home Edition, where the first-run experience is always Windows Welcome.

    Note that if you plan to use the Sysprep.inf file to automate Mini-Setup, you must either run the Sysprep tool by using the -mini switch, or click to select the MiniSetup check box in the GUI interface. By default, if you do not choose to run Mini-Setup, Windows XP Professional runs the Windows Welcome.
    -noreboot - Modifies registry entries (SID, OemDuplicatorString, and other registry entries) without the computer restarting or preparing for duplication. This parameter is mainly used for testing, specifically to see if the registry is modified correctly. Microsoft does not recommend this option because making changes to a computer after the Sysprep.exe file has run may invalidate the preparation that was completed by the Sysprep.exe file. Do not use this parameter in a production environment.
    -nosidgen - Runs the Sysprep.exe file without generating new SIDs. You must use this parameter if you are not duplicating the computer where you are running the Sysprep.exe file or if you are preinstalling domain controllers.
    -pnp - Runs the full Plug and Play device enumeration and installation of previous devices during Mini-Setup. This command-line parameter has no effect if the first-run experience is Windows Welcome.

    Use the -pnp command-line parameter only when you must detect and install previous, non-Plug and Play devices. Do not use the sysprep -pnp command-line parameter on computers that only use Plug and Play devices. Otherwise, you will increase the time that it takes for the first-run experience without providing any additional benefit to the user.

    Note When unsigned drivers are unavoidable, use the UpdateInstalledDrivers=yes parameter in conjunction with OemPnPDriversPath= and DriverSigningPolicy=ignore instead of the -pnp command-line parameter to provide a more seamless installation.
    -quiet - Runs the Sysprep.exe file without displaying onscreen confirmation messages. This is useful if you are automating the Sysprep.exe file. For example, if you plan to run the Sysprep.exe file immediately after the unattended Setup program finishes, add the sysprep -quiet command to the [GuiRunOnce] section of the Unattend.txt file.
    -reboot - Forces the computer to automatically restart, and then starts Windows Welcome Mini-Setup, or Factory mode, as specified. This is useful when you want to audit the computer and verify that the first-run experience is operating correctly.
    -reseal - Clears the Event Viewer logs and prepares the computer for delivery to the customer. Windows Welcome or Mini-Setup is set to start the next time that the computer restarts. If you run the sysprep -factory command, you must seal the installation as the last step in your preinstallation process. To do this, run the sysprep -reseal command or click the Reseal button in the Sysprep dialog box.
    http://support.microsoft.com/kb/302577

  5. #5
    Senior Member alakhiyar's Avatar
    Join Date
    Dec 2006
    Location
    Land of Oryx
    Posts
    255
    Check the "Use Mini-Setup" option before resealing.
    (\__/)
    (='.'=)
    (")_(")

Similar Threads

  1. The Problem Saga Continues
    By The Texan in forum Operating Systems
    Replies: 16
    Last Post: June 22nd, 2006, 09:04 PM
  2. A Headache of an Email Problem
    By AngelicKnight in forum General Computer Discussions
    Replies: 14
    Last Post: June 15th, 2006, 05:04 AM
  3. 500 mile email problem
    By Tedob1 in forum Tech Humor
    Replies: 0
    Last Post: December 23rd, 2002, 04:58 PM
  4. C problem...
    By Rna in forum General Programming Questions
    Replies: 4
    Last Post: May 22nd, 2002, 08:03 AM
  5. Help! I've got a nasty IDE problem
    By thesecretfire in forum Hardware
    Replies: 16
    Last Post: May 17th, 2002, 01:31 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •