One Images for all Laptops/Desktops

[luckyse7en]

I apologize if this has been asked before, however I was unable to find it. I am trying to create one image that can be loaded on any laptop/desktop in my environment. As far as I am aware I need to use sysprep w/sysprep.inf and not the winbom.ini(factory mode). I have all the drivers loaded on the image and everything loads fine when I do an unattended install for each model using the same unattend.txt file. My sysprep file is as follows:

;SetupMgrTag

[unattended]

OemSkipEula=Yes

ExtendOEMPartition = 1

InstallFilesPath=C:\Windows\CSS\i386

OemPnPDriversPath= "Windows\Drivers\C600;Windows\Drivers\C810;Windows\Drivers\C840;

Windows\Drivers\D600;Windows\Drivers\GX150;Windows\Drivers\GX240;Windows\Drivers\GX260;Windows\Drivers\GX270;

Windows\Drivers\M60;Windows\Drivers\WS340;Windows\Drivers\WS360;Windows\Drivers\WS530;Windows\Drivers\WS650;

Windows\Drivers\X200;Windows\Drivers\zOther;Windows\Drivers\zPrinters"

TargetPath=\WINDOWS

[GuiUnattended]

AdminPassword=*

EncryptedAdminPassword=NO

AutoLogon=Yes

AutoLogonCount=1

OEMSkipRegional=1

OEMDuplicatorstring="XP Load Version 1.0"

TimeZone=20

OemSkipWelcome=1

[userData]

ProductKey=*****-*****-*****-*****-*****

FullName="Authorized User"

OrgName="*********************"

ComputerName=xp

[Display]

BitsPerPel=32

Xresolution=1024

YResolution=768

[TapiLocation]

CountryCode=1

[GuiRunOnce]

Command0=c:\windows\css\start.exe

[identification]

JoinDomain=

DomainAdmin=

DomainAdminPassword=

[Networking]

InstallDefaultComponents=Yes

I have tried 3 machines (2 desktop models and 1 laptop model) and have got inconsistent results on each. Each system gives me a blue screen when it is booting into windows(before mini-setup). After starting the computer in safe mode I see each file being loaded and then it pauses at a file and blue screens. One image I took from a desktop blue screens at "MUP.SYS", the image I took from a laptop blue screened at a video driver file. Could someone please explain what I need to include or steps I need to perform such as removing registry keys or device drivers before I sysprep and image the machine containing the base load.

Any advise would be greatly appreciated.

[Aaron]

post edited to wrap oempnpdriverspath line

[big_gie]

Are you sure you want a sysprep installation?

Isn't a unattended installation simpler? I install xp for both my laptop and desktop and don't have problem... I'm sure I'm not the only one too!

look @ http://unattended.msfn.org/xp/drivers.htm for the driver section. Blue screen usely results from bad drivers, am I right?

good luck...

[Alanoll]

or hardware, like it it fails to initialize and it's a crucial component

[luckyse7en]

I need to use an image for reasons of time constraints. Thank you for your post Alanoll & big_gie. Is thier anyone who has gone down this path and be willing to tell thier experiences?

[Alanoll]

i can only say on behalf of Unattended setups (as i don't use sysprep or have i experimented), but my distro is used on about 7 different computers all using different hardware from one another, but I have had to have any problems with it.

[creany]

Add this section to your sysprep.inf

[sysPrep]

BuildMassStorageSection=Yes

Sysprep then prepopulates the necessary driver information so that Windows can load the correct drivers when the operating system boots on a computer that uses one of the predefined mass-storage controllers. This should avoid some of the blue screens that happen after a reboot.

This is the first step I might give you. The next is maybe break up laptops and desktops. Seem to be a large difference in its hardware. Two images is better than 10 to begin with.

Cheers

Creany

[trevhayman]

Hi, I had this same problem when I was creating images of Windows 2000. For Windows XP you will want to add the following sections if they do not exist in your sysprep.inf file.

[sysprep]

BuildMassStorageSection=yes

[sysprepMassStorage]

For information on this please see microsoft knowledge base artical 303786. This only works for Windows XP and NOT Windows 2000. For Windows 2000 you wil need to populate the SysprepMassStorage section manually for each controller and not use the BuildMassStorageSection=yes because it simply doesn't workin under Windows 2000. Here is an example below of what the Sysprep.inf file should look like for Windows 2000.

[unattended]

DriverSigningPolicy=Ignore

InstallFilesPath=C:\sysprep\i386

TargetPath=\WINNT

OemPnPDriversPath="winnt\drv\1p\vid;winnt\drv\1p\nic;winnt\drv\110\snd"

OemPreinstall=Yes

UpdateInstalledDrivers=Yes

[GuiUnattended]

OemSkipWelcome=1

OEMSkipRegional=1

[userData]

FullName="YourName"

OrgName="YourCompanyName"

[Display]

BitsPerPel=16

Xresolution=800

YResolution=600

Vrefresh=60

[RegionalSettings]

LanguageGroup=1

Language=00000409

[OEM_Ads]

Background=installer_background_16.bmp

[setupMgr]

DistFolder=C:\sysprep\i386

DistShare=win2000dist

[GuiRunOnce]

Command0=

[identification]

JoinDomain=ad-ent

[Networking]

InstallDefaultComponents=Yes

[sysprepMassStorage]

PCI\CC_0101 = "c:\winnt\inf\mshdc.inf"

PCI\VEN_8086&DEV_2411&SUBSYS_24118086 = "c:\winnt\inf\mshdc.inf"

PCI\VEN_8086&DEV_7111&SUBSYS_00000000 = "c:\winnt\inf\mshdc.inf"

PCI\VEN_8086&DEV_248A&SUBSYS_01221028 = "c:\winnt\inf\mshdc.inf"

PCI\VEN_8086&DEV_24CB = "c:\winnt\inf\mshdc.inf"

PCI\VEN_8086&DEV_2411 = "c:\winnt\inf\mshdc.inf"

PCI\VEN_8086&DEV_244B = "c:\winnt\inf\mshdc.inf"

PCI\VEN_8086&DEV_248A = "c:\winnt\inf\mshdc.inf"

PCI\VEN_8086&DEV_1222 = "c:\winnt\inf\mshdc.inf"

PCI\VEN_8086&DEV_1230 = "c:\winnt\inf\mshdc.inf"

PCI\VEN_8086&DEV_2421 = "c:\winnt\inf\mshdc.inf"

PCI\VEN_8086&DEV_2441 = "c:\winnt\inf\mshdc.inf"

PCI\VEN_10B9&DEV_5229 = "c:\winnt\inf\mshdc.inf"

PCI\VEN_8086&DEV_7010 = "c:\winnt\inf\mshdc.inf"

PCI\VEN_8086&DEV_7111 = "c:\winnt\inf\mshdc.inf"

PCI\VEN_8086&DEV_7199 = "c:\winnt\inf\mshdc.inf"

PCI\VEN_9005&DEV_008F = "c:\winnt\inf\scsi.inf"

PCI\VEN_9005&DEV_0080 = "c:\winnt\inf\scsi.inf"

PCI\VEN_1000&DEV_0030 = "c:\winnt\inf\scsi.inf"

PCI\VEN_101E&DEV_1960 = "c:\winnt\drv\330\scsi\OEMSETUP.INF"

*PNP0F03 = C:\WINNT\INF\MSMouse.inf

*PNP0F0B = C:\WINNT\INF\MSMouse.inf

*PNP0F0E = C:\WINNT\INF\MSMouse.inf

*PNP0F12 = C:\WINNT\INF\MSMouse.inf

*PNP0F13 = C:\WINNT\INF\MSMouse.inf

*PNP0300 = C:\WINNT\INF\keyboard.inf

*PNP0301 = C:\WINNT\INF\keyboard.inf

*PNP0302 = C:\WINNT\INF\keyboard.inf

*PNP0303 = C:\WINNT\INF\keyboard.inf

*PNP030b = C:\WINNT\INF\keyboard.inf

*PNP0343 = C:\WINNT\INF\keyboard.inf

*PNP0344 = C:\WINNT\INF\keyboard.inf

*PNP0345 = C:\WINNT\INF\keyboard.inf

[Commands]

"C:\sysprep\sysprep.exe -clean"

Have a good time with this. Some items don't actually need to be in there but I wanted you to have this information.

Lastly on a XP sysprep.inf file you will not want to put anything in the "[sysprepMassStorage]" if you will be using the "BuildMassStorageSection=yes" in the [sysprep] section because it will cause this not to work. It's saver not to place anything hin the sysprepmassstorage section on XP

Trevor