RIS Server Issue

[boarde]

Please help. I am banging my head against the wall trying to implement a RIS server. My problems seem to arise because files I have specified to be copied to the client are not being copied.

The files in

\i386\$oem$\C\officepro97

are not copied. Test files (less than eight characters) are not copied from

\$oem$\$$

to the winnt directory on the client.

I have the network drivers in

\$oem$\$1\Drivers\NIC

and have set the path in the remboot.sif file. Even though the client installs over the network, the network drivers are not loaded when windows is started up. I believe this odd behavior occurs because I have copied the NIC drivers into the i386 directory and these are used during setup. The reason the NIC drivers are not loaded in the newly installed client is because the files are not copied from the server to the client.

I am banging my head against a wall! If anyone knows why files are not copied to the client please be sure to let me know!

Cheers,

 

[ReddLefty]

You must also modify the template file that is used when create a new client. The default .SIF file that it uses is in \RemoteInstall\Setup\<language>\Images\Win2000.pro\I386\Templates\RISTNDRD.SIF

Edit it and modify the following:

[Unattended]
OemPreinstall = yes

then add:

OemPnPDriversPath = \drivers\nic


If you want to add video and sound, then simply add the folders to your \$OEM$\$1\... and add it to the drivers path as such:

OemPnPDriversPath= \drivers\nic;\drivers\video;drivers\sound

Look up MS KB Articles: 246184 and 254078




&quot;In space, nobody can hear you click...&quot;

 

[boarde]

RISTNDRD.SIF did not exist on my server, so created it containing the info stated above. This did not work, my client still didn't pick up the NIC drivers.

How does RISTNDRD.SIF interact with the remboot.sif file? Also, I am not convinced that my server is picking up the changed I am making. After each change I stop and start the binlsvc process. Is this sufficient?