RIS Win2K Server Setup

[Guest]

I am trying to use RIS to deploy 50 servers. I am having issues with the SCSI drivers for this Dell System. The SCSI device is a Perc 3di. I can do a network install but I need to press F6 to load the scsi drivers. Is there anyway I can have the entire RIS Install automated so I do not have to do anything. Any help would be great

 

[Johan Arwidmark]

In the $OEM$ folder, create a folder called Textmode and copy the mass
storage device drivers to that folder (*.sys, *.inf, *.cat and
txtsetup.oem)

Your ristndrd.sif should look something like this...

[MassStorageDrivers]
"Dell PERC 2, 2/Si, 3/Si, 3/Di RAID Controllers" = "OEM"
"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"

[OEMBootFiles]
perc2.sys
perc2.inf
perc2.cat
txtsetup.oem


For more info, check this article

HOWTO: Unattended Installation of Third Party Mass Storage Drivers in
Windows NT and Windows 2000
http://support.microsoft.com/?kbid=288344


regards
Johan Arwidmark

Windows User Group - Nordic
http://www.wug-nordic.net

 

[Guest]

Would this particular way work for a RIS install......

 

[Guest]

I added what you said to my SIF file. WHen I boot up using that I am getting the following error message. "File txtsetup.oem caused an unexpected error (21) at line 1044 in D:\nt\private\ntos\boot\setup\oemdisk.c." WHen I press the continue button it proceeds with the error that it cannot find any mass storage devices.....

 

[Johan Arwidmark]

There might some missing files, try include below files in the
Textmode folder (and also reference them in ristndrd.sif
[OEMBootFiles] section)

perc2.sys
perc2hib.sys
perc2.cat
perc2.inf
perc2mgt.inf
perc2cin.dll
perc2evt.exe

Please reply with the content of your txtsetup.oem (you sometimes need
to make modifications to that file, regarding foremost pathnames)

You also can laborate by copying the *.sys-files to the i386 folder
and modifying the txtsetup.sif file (do make a extra copy first) with
info from the txtsetup.oem file. The sections to be modfied are the
following...

[SourceDisksFiles]
perc2.sys = 1,,,,,,4_,4,1,,,1,4

[SCSI]
perc2 = "Dell PERC 2, 2/Si, 3/Si, 3/Di RAID Controllers"

[SCSI.Load]
perc2 = perc2.sys,4

[HardwareIdsDatabase]
PCI\VEN_1011&DEV_0046&SUBSYS_13649005 = "perc2"
PCI\VEN_1011&DEV_0046&SUBSYS_13659005 = "perc2"
PCI\VEN_1028&DEV_0001&SUBSYS_00011028 = "perc2"
PCI\VEN_1028&DEV_0002&SUBSYS_00021028 = "perc2"
PCI\VEN_1028&DEV_0003&SUBSYS_00031028 = "perc2"
PCI\VEN_1028&DEV_0002&SUBSYS_00D11028 = "perc2"
PCI\VEN_1028&DEV_0002&SUBSYS_00D91028 = "perc2"
PCI\VEN_1028&DEV_000A&SUBSYS_01061028 = "perc2"
PCI\VEN_1028&DEV_000A&SUBSYS_011B1028 = "perc2"
PCI\VEN_1028&DEV_000A&SUBSYS_01211028 = "perc2"
PCI\VEN_9006&DEV_2140&SUBSYS_21409006 = "perc2"
PCI\VEN_9005&DEV_00C5&SUBSYS_00C51028 = "perc2"



Some aricles/whitepapers worth reading

Microsoft Accelerator for Windows Server Deployment.
http://www.microsoft.com/technet/tr...=/technet/itsolutions/msm/wsrvdep/default.asp


regards
Johan Arwidmark

Windows User Group - Nordic
http://www.wug-nordic.net

 

[Patrick J. LoPresti]

I have performed unattended installations of 2000 Server on PERC 3Di
hardware. I did not use RIS, but I performed the same function, which
is automating the deployment.

See <http://unattended.sourceforge.net/> for the system I use.

As for RIS... The "unexpected error (21)" message seems to be a
fairly common problem:

http://groups.google.com/groups?q=RIS+"error+(21)"

Windows error code 21 is "device not ready", which may (or may not) be
trying to tell you "file not found". Which files are you placing
under $OEM$\Textmode? What are you using for your [OEMBootFiles]
section?

As Johan suggests, you definitely want to read
<http://support.microsoft.com/?id=288344>. See also
<http://support.microsoft.com/?id=275334>, which describes creating
$OEM$\$$\OemDir and copying the DLLs there; I had to do this to get my
PERC controllers working.

In addition, I recommend reading
<http://www.mail-archive.com/[email protected]/msg00107.html>.
But I also laugh at my own jokes.

- Pat

 

[Emmers Presson [MSFT]]

1. At the same level as the I386 folder of the RIS image, create a $OEM$
folder. Under the $OEM$ folder create a folder $1\Drivers\Perc3di take the
files from the Perc3di drivers disk and place them in the
$oem$\$1\Drivers\Perc3di folder.

2. Create a new folder under $OEM$ named textmode. Copy all of the files
included from the driver disk as we did with the Perc3di folder.

3. Create a new folder under $OEM$ named $$ under that create a folder named
OEMDIR and place the following files in this folder:

perc2cin.dll
perc2evt.exe

3. In the Txtsetup.oem (in both folders) modify the file slightly:

change
------
[Files.Scsi.perc2]
driver = d1, perc2.sys, perc2
driver = d1, perc2hib.sys, perc2hib
catalog = d1, perc2.cat
inf = d1, perc2.inf
inf = d1, perc2mgt.inf
dll = d1, perc2cin.dll
dll = d1, perc2evt.exe

to
----
[Files.Scsi.perc2]
driver = d1, perc2.sys, perc2
driver = d1, perc2hib.sys, perc2hib
catalog = d1, perc2.cat
inf = d1, perc2.inf
inf = d1, perc2mgt.inf
;dll = d1, perc2cin.dll
;dll = d1, perc2evt.exe

NOTE: If you do not remark out the 2 dll entries you will get an error
during the
install.

You may also have to edit the line:

[Disks]
d1 = "Dell PERC 2, 2/Si, 3/Si, 3/Di Windows 2000 Device Drivers", \raidisk1,


....depending on file system. If using NTFS then the line is fine, If using
FAT use the following:


[Disks]
d1 = "Dell PERC 2, 2/Si, 3/Si, 3/Di Windows 2000 Device Drivers", \raidisk1,
..

4. Next we have to edit the .SIF file that we are using. Add 2 sections to
the file

[MassStorageDrivers]
"Dell PERC 2, 2/Si, 3/Si, 3/Di RAID Controllers"=OEM

and

[OEMBootFiles]
perc2.sys
perc2hib.sys
perc2.inf
txtsetup.oem

NOTE: The default name of the .SIF file is
RemoteInstall\Setup\<Language>\Images\<Dir_name>\I386\Templates\Ristndrd.sif


5. This should be all we have to do to make this work. stop and restart the
BINL service and test.
--
Emmers Presson [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

I am trying to use RIS to deploy 50 servers. I am having issues with the

SCSI drivers for this Dell System. The SCSI device is a Perc 3di. I can do
a network install but I need to press F6 to load the scsi drivers. Is there
anyway I can have the entire RIS Install automated so I do not have to do
anything. Any help would be great

 

[Guest]

Thank you for the advice but unfortunately I keep getting the same error....I followed your instructions word for word thinking I may I screwed it up myself but no. Any more ideas would be great. Like I said the f6 and using disk works great but the automated complains about line 1044 of the txtsetup.oem

 

[Patrick J. LoPresti]

To recap, the error you are seeing is:

File txtsetup.oem caused an unexpected error (21) at line 1044 in
D:\nt\private\ntos\boot\setup\oemdisk.c.

Read the message carefully. It is NOT referring to line 1044 of
txtsetup.oem. It is referring to line 1044 of oemdisk.c, which is
part of the Windows source code. In other words, this error message
can only be fully understood by a Microsoft developer.

Windows error code 21 is "device not ready". Not terribly useful.

Hm, here is a thought. Perhaps the system is scanning the available
drives looking for the drivers. (This is not so far fetched; do a
Google search on txtsetup.oem and "tag file"...) Do you have anything
in the floppy or CD-ROM of the system? Can you see the machine trying
to access the floppy or CD-ROM just before this message appears?

- Pat