Eksempel på inf fil til sysprep

[trrunde]

Prøver å bruke sysprep på noen laptopper som skal klargjøres, jeg har prøvd å kjøre uten å ha noen inf fil, men da skjer det ikke noe, så jeg lurer på om jeg må ha denne filen, men jeg vet ikke hvordan denne filen skal bygges opp. Har noen et eksempel på denne filen?

[S.M.]

Her er noe tatt rett fra hjelp.

 

Klikk for å se/fjerne innholdet nedenfor

Create the Sysprep.inf answer file

The Sysprep.inf answer file is a text file that scripts the answers for a series of graphical user interface (GUI) dialog boxes. To create a Sysprep.inf answer file that is used by the Sysprep tool, you can use a text editor or you can use the Setup Manager tool that is included on the Windows XP CD and is also included with the Microsoft Windows XP Resource Kit. The answer file must be renamed to Sysprep.inf, and must reside in the Sysprep folder in the root of the drive where Windows XP is installed, or these files can reside on a floppy disk. If the Sysprep folder is named differently, the Setup program ignores it. There is not a parameter for specifying the Mini-Setup Wizard answer file.

 

 

Sysprep.inf answer file format and parameters

• The Sysprep.inf answer file format and parameters are the same as the Unattended.txt file for Windows XP, but only the following sections and parameters are supported:

 

[unattended]

ExtendOemPartition

OemPnPDriversPath

OemSkipEula

InstallFilesPath

KeepPageFile

ResetSourcePath

UpdateHAL

UpdateUPHAL

UpdateInstalledDrivers

TapiConfigured

 

[GuiUnattended]

AdminPassword

Autologon

AutoLogonCount

OEMDuplicatorString

OEMSkipRegional

OEMSkipWelcome

TimeZone

 

[userData]

Supports the same set of entries as the Unattend.txt file.

[LicenseFilePrintData]

Supports the same set of entries as the Unattend.txt file.

[GuiRunOnce]

Supports the same set of entries as the Unattend.txt file.

[Display]

Supports the same set of entries as the Unattend.txt file.

[RegionalSettings]

Supports the same set of entries as the Unattend.txt file.

[Networking]

Supports the same set of entries as the Unattend.txt file.

[identification]

Supports the same set of entries as the Unattend.txt file.

[TapiLocation]

[sysprep]

Automatically generates the entries in the [sysprepMassStorage] section.

[sysprepMassStorage]

Allows you to use the same image on computers with different mass-storage devices.

 

Back to the top

 

Use the Setup Manager tool to create the Sysprep.inf answer file

To install the Setup Manager tool and to create an answer file, follow these steps: 1. Open My Computer, and then open the Support\Tools folder on the Windows XP CD.

2. Double-click the Deploy.cab file to open it.

3. On the Edit menu, click Select All.

4. On the Edit menu, click Copy To Folder.

5. Click Make New Folder.

 

Type the name that you want for the Setup Manager folder, and then press ENTER. For example, type setup manager, and then press ENTER.

6. Click Copy.

7. Open the new folder that you created, and then double-click the Setupmgr.exe file. The Windows Setup Manager Wizard starts.

8. Follow the instructions in the wizard to create an answer file.

For additional information about how to create an answer file, click the following article number to view the article in the Microsoft Knowledge Base:

308662 (http://support.microsoft.com/kb/308662/) HOW TO: Use Setup Manager to create an answer file in Windows 2000

Back to the top

 

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.

[Grim_Fandango]

Du MÅ ha en fil som heter eksakt sysprep.inf, og denne MÅ ligge i en katalog som heter SYSPREP, og denne katalogen MÅ ligge rett under rota på den bootbare partisjonen.

 

Du kan lage slike inf filer ved å kjøre "setupmgr.exe" filen i sysprep katalogen

[trrunde]

fikk det faktisk til uten inf fil, jeg hadde glemt å krysse av for mini setup, dermed ble det noe kluss og jeg fikk melding om at systemet ikke var riktig installert.

[Christian.]

Du må vel fylle inn diverse info når maskinen starter opp hvis du har brukt minisetup? Med en sif fil vill den fylle inn automatisk så en spiller å skrive inn noe eller trykke på noen knapper

[trrunde]

ja må det, men det var dette jeg ønsket pga jobber i en butikk der jeg skal klargjøre pc-er, går da mye raskere å installere en "mal" og kjøre sysprep på denne og ta image av, i stedet for å installere alle oppdateringer + programmer osv på hver eneste maskin.

[Nukem]

Har et eksempel liggende tror jeg et sted. hvis det skulle være intresant.

[enden]

Du kan lage slike inf filer ved å kjøre "setupmgr.exe" filen i sysprep katalogen

... som du igjen henter fra deploy.cab på Windows-CD-en. Greit å få med seg, da de aller færreste har en mappe som heter sysprep med et program som heter setupmgr.exe liggende på OS-partisjonen fra før

 

Og i stedet for å satse på potesielt halvinformative eksempler vil jeg heller anbefale å faktisk gjøre dette selv så du får se alle muligheter du har til å automatisere installasjonen. Det er relativt enkelt - sannsynligvis enklere enn å sette seg inn i en eksempelfil. http://support.microsoft.com/kb/302577