Systems Deployment

This *May* work.

Install the scsi controller in the PC where you are creating the image from. Add a Scsi disk also. This should load the driver in windows. Reboot once if told.

Now sysprep the machine and try putting the image on the another one with the scsi controller.

the above step is correct. But you need to change the boot.ini as well though in my case they look the same

scsi boot.ini (My scsi server)

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise" /noexecute=optout /fastdetect

IDE/SATA boot.ini (My desktop)

[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect

Thanks for your reply that makes alot of sense. In the process of testing now.

When I've gone from IDE to SATA, I needed to add the drivers to the OemPnPDriversPath in addition to the MassStorage section. Try adding the following to your sysprep and see if it helps:

OemPnPDriversPath = Drivers\hdd\adaptec2120

G'luck,
Jay

Regardless of how many pages have been written about the [SysprepMassStorage], I don't use it. It even crashes sysprep.

I use another method, which I got from some site which is offline now. I just change the IDE driver to standard IDE controller and then create the image. Yet to see a machine who failed to start up. I have tried it with Intel and Via chipsets and also several Toshiba/Acer and HP/Compaq laptops.

Of course using the same drivers as in the final system(s) sounds equally good.

ORIGINAL: dvdzonenz

Regardless of how many pages have been written about the [SysprepMassStorage], I don't use it. It even crashes sysprep.



Not sure why you wouldn't use it. When done correctly, it works very well when creating a single hardware independant image.

But my images works just fine! Perhaps you should also try what I have found. After all I did that [SysprepMassStorage] for a long time too but then I landed on some page searching for tips to make such an image. I even added Sata sections but frankly none is needed.

Try it. Add drivers from Bashrat's pack and you have a real nice image. My image has worked everywhere. Even on the Toshiba P100 laptop that does not have PATA in it.

sysprep.inf

;SetupMgrTag
[GuiUnattended]
AdminPassword="password"
EncryptedAdminPassword=NO
OEMSkipRegional=1
TimeZone=290
OemSkipWelcome=1
[UserData]
ProductKey=
FullName="user"
OrgName=""
ComputerName=*
[TapiLocation]
CountryCode=64
Dialing=Tone
AreaCode=09
[RegionalSettings]
LanguageGroup=1
[Identification]
JoinWorkgroup=WORKGROUP
[Networking]
InstallDefaultComponents=Yes
[Unattended]
OemSkipEula=Yes
InstallFilesPath=C:\sysprep\i386
TargetPath=\WINDOWS
UpdateInstalledDrivers=Yes
KeepPageFile=0
UpdateUPHAL=ACPIAPIC_MP,C:\Windows\Inf\Hal.inf
DriverSigningPolicy=Ignore
[URL]
Home_Page=http://www.google.com
[Branding]
BrandIEUsingUnattended=Yes
[Proxy]
Proxy_Enable=0
Use_Same_Proxy=0
[GuiRunOnce]
Command0=c:\task1.bat
Command1=c:\task2.bat
Command2=c:\task3.bat
Command3=c:\task4.bat


I'm not familiar with Bashrat's driver pack, but in my experience with any driver pack is that it adds drivers gallore to account for every possible hardware out there. I would much rather be specific about which drivers I include in my image along with versions and avoid overbloating it with unnecessary files.

More than 1 way to skin a cat, as always. Glad to hear you found a method that works for your environment.

- Jay

Bashrat's pack is an overkill. I don't use it because it slows down the detection of hardware.

All that -bmsd does is add some drivers's list. And all those drivers are handled by IDE. Make the video to VGA and you have a universal image!

This is not for my environment alone. I have tested it on not sure how many places and it always works.

Good. Hopefully it helps mindlessautomaton get fixed.

Actually his packs are very well thought ones. He has put them in categories so you don't have to use all of them if you don't want to. The massstorage one is quite small.
I will put a small listing here.


Directory of D:\deee\driverpackchipset\DriverPacks
05/21/2009 03:40 PM <DIR> .
05/21/2009 03:40 PM <DIR> ..
03/23/2009 06:56 AM <DIR> D
07/20/2008 08:48 PM 256,803 DP_Chipset_wnt5_x86-32_803.zip
07/20/2008 08:39 PM 37,650 DP_CPU_wnt5_x86-32_804.7z
12/09/2008 04:43 AM 40,136,592 DP_Graphics_A_Languages_wnt5_x86-32_810.7z
12/09/2008 04:40 AM 47,867,378 DP_Graphics_A_PhysX_wnt5_x86-32_810.7z
07/21/2008 11:21 AM 88,957,132 DP_Graphics_A_wnt5_x86-32_804.7z
12/09/2008 04:14 AM 57,742,819 DP_Graphics_A_wnt5_x86-32_8103.7z
07/21/2008 01:31 PM 54,863,292 DP_Graphics_B_wnt5_x86-32_804.7z
12/09/2008 04:35 AM 98,768,804 DP_Graphics_B_wnt5_x86-32_810.7z
07/21/2008 04:52 AM 67,115,877 DP_Graphics_C_wnt5_x86-32_804.7z
12/09/2008 04:37 AM 51,424,639 DP_Graphics_C_wnt5_x86-32_8101.7z
07/21/2008 12:14 AM 7,364,052 DP_LAN_wnt5_x86-32_8053.7z
07/19/2008 07:34 PM 5,180,852 DP_MassStorage_wnt5_x86-32_805.7z
07/20/2008 05:17 AM 46,162,492 DP_Sound_A_wnt5_x86-32_805.7z
07/22/2008 11:40 PM 60,083,733 DP_Sound_B_wnt5_x86-32_805.7z
07/20/2008 06:24 AM 21,077,373 DP_WLAN_wnt5_x86-32_806.7z
04/08/2007 06:52 AM 420 DriverPack_CPU_wnt5_x86-32.ini
11/05/2008 06:39 PM 2,268 DriverPack_Graphics_A_wnt5_x86-32.ini
10/13/2008 01:04 AM 2,793 DriverPack_Graphics_B_wnt5_x86-32.ini
10/13/2008 01:06 AM 2,177 DriverPack_Graphics_C_wnt5_x86-32.ini
05/14/2008 05:02 PM 770 DriverPack_LAN_wnt5_x86-32.ini
06/01/2008 02:02 PM 75,188 DriverPack_MassStorage_wnt5_x86-32.ini
04/02/2008 03:37 AM 4,214 DriverPack_Sound_A_wnt5_x86-32.ini
04/12/2008 09:47 PM 3,525 DriverPack_Sound_B_wnt5_x86-32.ini
05/21/2009 03:40 PM 0 list.txt
24 File(s) 647,130,843 bytes
3 Dir(s) 206,273,306,624 bytes free



Well, I was able to get the image to boot successfully on a SCSI array. Now however, it is hit or miss as to whether this image works on other non-scsi hardware. It looks as though the image may be having issues with SATA now. Unfortunately, I do not have any helpful information to report. I will offer more as soon as it is available.

Are you getting a 7b stop error on SATA drives?

DeployTech,

That is exactly right, but only when I attempt to add a SCSI controller to the image. I've tried both methods listed above and get the similar results. However, if I do not attempt to add the SCSI controller the updated image will image both PATA and SATA just fine.

I still think it is likely something very simple I am overlooking.

Righto. In my sysprep entries I tend to put in in static entries for SATA\SCSI controllers for the in the MassStorage section, and then set
[Sysprep]
BuildMassStorage=Yes (or run it from the command line).

I'll dig an old file out and make sure I'm on target there.

What OS are you imaging and are you using MDT or BDD to do it?

J

Here is an old sysprep snippet. As said earlier, I have never had any issue with SATA. I just used my IDE images on it.


<code>

[Sysprep]
BuildMassStorageSection=yes

[SysprepMassStorage]
; for Intel SATA Controller
PCI\VEN_8086&DEV_2652&CC_0106=c:\windows\inf\iaahci.inf
PCI\VEN_8086&DEV_2653&CC_0106=c:\windows\inf\iaahci.inf
PCI\VEN_8086&DEV_27C1&CC_0106=c:\windows\inf\iaahci.inf
PCI\VEN_8086&DEV_27C5&CC_0106=c:\windows\inf\iaahci.inf
PCI\VEN_8086&DEV_2681&CC_0106=c:\windows\inf\iaahci.inf
PCI\VEN_8086&DEV_2821&CC_0106=c:\windows\inf\iaahci.inf
PCI\VEN_8086&DEV_2652&CC_0104=c:\windows\inf\iastor.inf
PCI\VEN_8086&DEV_27C3&CC_0104=c:\windows\inf\iastor.inf
PCI\VEN_8086&DEV_2682&CC_0104=c:\windows\inf\iastor.inf
PCI\VEN_8086&DEV_27C6&CC_0104=c:\windows\inf\iastor.inf
PCI\VEN_8086&DEV_2822&CC_0104=c:\windows\inf\iastor.inf
; End for Intel SATA Support


*pnp0a00=c:\windows\inf\machine.inf
*pnp0a01=c:\windows\inf\machine.inf
</code>

Hey dvdzonenz
Regardless of how many pages have been written about the [SysprepMassStorage], I don't use it. It even crashes sysprep.
Looks like you do use it after all.
:)

Yep, that looks like the process I use.

So, get your SCSI Drivers and put the Device ID into the SysprepMassStorage section, with a path to the drivers on C:
like C:\drivers\SCSI\

Make sure the drivers are in place and the correct device IDs are specified.
Create your image, rinse and repeat as required. If the drivers aren't present, it won't work when you test it.

The build mass storage adds native Windows XP drivers to the list, but adds about 15 minutes to the sysprep process. It'll just sit for ages but it is actually doing something.

No. I don't use it at all. But I do know what others use.

Try removing that area and use just the standard IDE driver. It will work the same.

BTW my current PC has this


Name Intel(R) 82801GB/GR/GH (ICH7 Family) Serial ATA Storage Controller - 27C0
Manufacturer Intel
Status OK
PNP Device ID PCI\VEN_8086&DEV_27C0&SUBSYS_B0021458&REV_01\3&13C0B0C5&0&FA
I/O Port 0x0000F000-0x0000F00F
Driver c:\windows\system32\drivers\pciide.sys (5.1.2600.0 (XPClient.010817-1148), 3.25 KB (3,328 bytes), 8/17/2001 1:51 PM)


And the image was made in a VM with IDE