Problem with imaging machines- will sysprep fix?

S

snagrat

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
 
J

Johan Arwidmark

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
 
A

Adam Leinss

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.
Click to expand...

Try: http://www.leinss.com/uniimg.html.

I'm guessing the BSOD is a STOP 0X7B error?

Adam
 
J

Johan Arwidmark

Supernice article ...


regards

Johan Arwidmark
Microsoft MVP - Setup/Deployment
 
S

snagrat

I believe it is. It flashes up so quickly I can't see what the error
is.

Reading many articles I believe it is the STOP 0X7B Error.

I'm gonna try the suggestions tonight and post back my findings

Cheers
 
S

Steve Maser

snagrat said:
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.
Click to expand...



Are you sure your "source" machine and "target" machines use the same
HAL?

If not, that could be your problem and not anything to do with the BMSD
section...

- Steve
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

sysprep Windows 2003 SE of multiple partitions 3
sysprep -pnp 1
sysprep / mass storage / imaging 0
Sysprep -factory and -reseal 0
Sysprep 2.0 3
Sysprep doesn't find drivers? 5
Sysprep Alternatives? 4
Sysprep on WinXP? 1

Top