Re: Problem with imaging machines- will sysprep fix?

make sure to add the SATA driver to your master and update sysprep.inf
with info about that driver before sealing the image...(In addition to
the normal sysprep -bmsd drivers)

Example with qlogic 2300 scsi controller:

1. Run sysprep -bmsd (populates sysprep.inf)
2. comment out the buildmasstorage = yes in sysprep.inf (since we
already build it)
3. Copy the driver to C:\Drivers\QL23HS20
4. Update oempnpdriverspath in sysprep.inf with C:\Drivers\QL23HS20
5. review the driver inf-file, in this example it looks like this

;*******************************
;QLogic Manufacturer device list
[QLOGIC]
%ql2300.DeviceDesc% = ql2300_Inst,
PCI\VEN_1077&DEV_2312&SUBSYS_01001077,
PCI\VEN_1077&DEV_2312&SUBSYS_01011077,
PCI\VEN_1077&DEV_2312&SUBSYS_01021077,
PCI\VEN_1077&DEV_2312&SUBSYS_010A1077,
PCI\VEN_1077&DEV_2312&SUBSYS_01000E11,
PCI\VEN_1077&DEV_2312&SUBSYS_027D1014,
PCI\VEN_1077&DEV_2312&SUBSYS_01010E11,
PCI\VEN_1077&DEV_2312&SUBSYS_01020E11,
PCI\VEN_1077&DEV_2312&SUBSYS_34BA8086,
PCI\VEN_1077&DEV_2312&SUBSYS_01021749,
PCI\VEN_1077&DEV_2312&SUBSYS_10511734,
PCI\VEN_1077&DEV_2312&SUBSYS_01030E11,
PCI\VEN_1077&DEV_2312&SUBSYS_01040E11,
PCI\VEN_1077&DEV_2312&SUBSYS_01050E11,
PCI\VEN_1077&DEV_2312&SUBSYS_018A1028,
PCI\VEN_1077&DEV_2312&SUBSYS_12BA103C,
PCI\VEN_1077&DEV_2312&SUBSYS_12C2103C,
PCI\VEN_1077&DEV_2312&SUBSYS_12C7103C,
PCI\VEN_1077&DEV_2312&SUBSYS_12C9103C,
PCI\VEN_1077&DEV_2312&SUBSYS_02FB1014

6. update the [SysprepMassStorage] section of sysprep.inf with info
from the driver inf file.

[SysprepMassStorage]
....
700+ rows of builtin drivers
.....
PCI\VEN_1077&DEV_2312&SUBSYS_01001077=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_01011077=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_01021077=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_010A1077=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_01000E11=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_027D1014=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_01010E11=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_01020E11=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_34BA8086=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_01021749=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_10511734=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2322&SUBSYS_01701028=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_01030E11=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_01040E11=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_01050E11=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_018A1028=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_12BA103C=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_12C2103C=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_12C7103C=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_12C9103C=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_02FB1014=C:\Drivers\QL23HS20\OEMSETUP.INF

7. run sysprep -mini -quiet -reseal

Note: Do Not use the -pnp switch (for legacy stuff only)

regards

Johan Arwidmark
Microsoft MVP - Setup/Deployment



On 30 Jan 2006 12:34:17 -0800, "snagrat" <andrew@xxxxxxxxxxxxxxx>
wrote:

>Hi
>
>For years we have been using Ghost to clone machines. If we clone from
>one box to a different box then windows would need repairing and after
>that everything would be fine.
>
>About a year ago we started to use sysprep to reseal the machines
>before cloning large amounts of the same machine, so I am aware of
>sysprep but also aware that I probably don't use it to its full
>potential.
>
>However suddenly we are having huge problems when it comes to cloning
>from one type of machine to a different type. Windows will blue screen
>when it starts up for the first time on the cloned machine (this is
>typical so I thought I would repair windows). Windows will copy all its
>files required to the hard drive and when goes to restart to start the
>full installation it blue screens again.
>
>I then get this loop where it won't boot and it won't repair. I don't
>know why this is.
>
>I have tried using the BuildMassStorageSection line in sysprep before
>cloning with no luck.
>
>I am cloning from a IDE to SATA machine but I have done so in the past
>with no problems.
>
>Can anyone suggest something I can try to get around this problem. I
>have looked briefly into the -factory -pnp switches but don't know if
>these are relevant.
>
>Thanks
>Andy

.

Relevant Pages

  • pro/100 nic driver and imaging
    ... driver. ... Ghost cloning software, and I have configured Sysprep so ... Also have added the install path to ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: Modifying Sysprep
    ... Try adding this registry information to your image before you run sysprep, ... had the same type of dilemna, i have about 4 dif models of dells, id take an ... ;Add driver for intelide ...
    (microsoft.public.win2000.setup_deployment)
  • Re: Problem with imaging machines- will sysprep fix?
    ... > For years we have been using Ghost to clone machines. ... > About a year ago we started to use sysprep to reseal the machines ... > However suddenly we are having huge problems when it comes to cloning ... Windows will blue screen ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: sysprep image and SCSI RAID
    ... just download the driver for the hard drive controller you need for the ... When you seal the image with sysprep, it will install these drivers so ... HD image and dump it on a similar class HD the image works, ... The error message I get when the target machine is booting for the ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: Blue Screen After deploying OSD image
    ... > blue screen when Windows XP starts and the pc reboots. ... The blue screens ... > problem is caused by the following driver and it could be anything linked ...
    (microsoft.public.sms.tools)
Loading