Sysprep

[Bobby Hendrix]

I am tring to build one image for a HP compaq dc5000mt, a HP dc5000mt with Hyper Threading and a HP xw4100 with Hyper Threading . Can someone please tell me where I could find the mass storage controllers for each machine? Now after reading some of these forms it seems that sysprep can't be fully utilized. I thought one of the main features of sysprep was to allow one image to work on several machines? Can someone please put me on the right path?
Thanks for your time and effort.

[Bryan Eley]

Bobby, not sure if this is what sort of info you are asking for, but I found this thread that might give you some pointers:

"You need to add the drivers to your [SysprepMassStorage] section of
the sysprep.inf file.

To follow up ... here is all you should need to put under
[SysprepMassStorage]
I have included a sample out of the one that I use for discussion:

[SysprepMassStorage]
PCI\VEN_0E11&DEV_B178&SUBSYS_40800E11="c:\sysprep\drivers\storage\cpqcissm.i
nf"
PCI\VEN_0E11&DEV_B178&SUBSYS_40820E11="c:\sysprep\drivers\storage\cpqcissm.i
nf"

The first part of the string is the PCI DeviceID. This can be found in the
*.inf file included with the drivers.
NOTE: make sure to include the entire string. As you'll note above, there
is a difference in the SUBSYS part of the srting. Make sure to include the
Entire Device ID (see below where the ID comes from)

The second part of the string is the path to the *.inf file for the drivers.
You will need to include all *.cat, *.dll, *.inf and *.sys files that come
with the driver. I have copied mine to a directory within my sysprep
folder, so that they will be deleted after they are loaded.

With the example above, I can Load an HP Proliant system with either a Smart
Array 5i or 532 Controller Card.

This came from a lot of trial and error as I haven't found very good
documentation on it.

================
PCI Device ID example

[COMPAQ_HDC]
%smart_5300.DeviceDesc%=cpqcissm_Inst, PCI\VEN_0E11&DEV_B060&SUBSYS_40700E11
%smart_integrated_5i.DeviceDesc%=cpqcissm_Inst,
PCI\VEN_0E11&DEV_B178&SUBSYS_40800E11
%smart_532.DeviceDesc%=cpqcissm_Inst, PCI\VEN_0E11&DEV_B178&SUBSYS_40820E11
%smart_5312.DeviceDesc%=cpqcissm_Inst, PCI\VEN_0E11&DEV_B178&SUBSYS_40830E11
%smart_641.DeviceDesc%=cpqcissm_Inst, PCI\VEN_0E11&DEV_0046&SUBSYS_409A0E11
%smart_642.DeviceDesc%=cpqcissm_Inst, PCI\VEN_0E11&DEV_0046&SUBSYS_409B0E11
%smart_6400.DeviceDesc%=cpqcissm_Inst, PCI\VEN_0E11&DEV_0046&SUBSYS_409C0E11
%smart_6400_EM.DeviceDesc%=cpqcissm_Inst,
PCI\VEN_0E11&DEV_0046&SUBSYS_409D0E11 "

[Bobby Hendrix]

Hi Bryan,
Thanks for the quick responce, I should let you know that I am pretty new to the sysprep thing. I am going to try your suggestions but first I have one question and is it necessary to load every .inf file within C:\Windows\inf folder the for each computer in the[SysprepMassStorage] within the sysprep.inf file in order for all three computer to run off of one image?
Thanks again for all of your help

[Bryan Eley]

Frankly, Bobby, I'm not 100% sure off the top of my head, but I don't think so. Hopefully someone out there more familiar with the arcana involved with sysprep can answer that specific question more precisely.

Incidentally, if you are new to sysprep, take a look at the Microsoft powerpoint about sysprep at tech.cuip.net/guide/MS-docs/so4.ppt for Windows 2000

Finally, if you haven't already, check out labmice.net. They have a lot of nice tips and such for IT folks and might have some additional info.

Bryan

[Bobby Hendrix]

Again,
Thanks Bryan for all of your help and very useful advice.

[Bobby Hendrix]

Bryan,
One last question, let's say I have two computer that are the same. The only difference in on is a P4 and the other is a P4 with Hyper Threading, the same image sould work on both or would it not work because it's a different chipset? What do you think?
Thanks

[Bryan Eley]

Bobby,
Sorry for the delay...

That's an excellent question. While a hyperthreaded processor isn't really a multi-processor component, it isn't really a uni-processor component either (though you techincally COULD disable hyperthreading in the BIOS, if the BIOS permitted it--though that would defeat the purpose of having the HT processor, wouldn't it? ;-D ), but it would be detected as sort of a dual-processor, as you probably have noticed from the performance tab of task manager on such systems. From what I've read, it wouldn't work on both due to the different kernel requirements of each processor.