Remote Installation Services замечательная, хотя и не новая, разработка Microsoft. Интегрируется с Active Directory, Microsoft DHCP.

Состоит из двух частей: непосредственно Remote Installation service и Trivial FTP - tftp service.

Trivial FTP нужен для непосредственной раздачи загружаемых по сети файлов. Remote Installation service служит для конвертации в необходимый формат образов систем, загрузочных файлов, для подготовки к загрузки по сети, сопоставлению образов по MAC адресам и настройкам DHCP.

Для "рихтовки RIS напильником" нам потребуется комплект из поставки Windows Server 2003 support tools, которые мы и установим у себя. После установки при помощи команды Run запустим adsiedit.msc - "глубокий" редактор Active Directory.

После запуска ADSIEdit нам необходимо найти аккаунт машины, для которой мы будем указывать вручную образ загрузки по сети. Все остальные машины будут загружать Remote Installation (F12 и так далее :).

  читать далее >>

http://pxes.sourceforge.net/howtos/ms_only_environment/ 

С сетевых дисков(с шар, которые подключатся как сетевой диск) программы НЕ УСТАНАВЛИВАЮТСЯ!
Нужно использовать конструкцию непосредственного задания путей вида \\machine\share

 

Q. Why are some Microsoft Remote Installation Services (RIS) images not displayed o­n my RIS OS selection menu?

John Savill
InstantDoc #42475
John Savill's FAQ for Windows




A. When a RIS client computer boots so it can install an OS from the RIS server, the client displays a list of OS images that are applicable to it. A problem occurs when the image's hardware abstraction layer (HAL) differs from the HAL that the local machine should use (e.g., single-processor HAL versus multiprocessor HAL). I experienced this problem recently when I used the Remote Installation Preparation (RIPrep) utility to create an image from a client workstation. When I booted another computer so it could install an OS from the RIS server, the computer didn't display the image. The problem was that the computer I used to create the image had hyperthreading enabled, which means the HAL is a multiprocessor version (although the machine actually has o­nly o­ne CPU), whereas the destination machine didn't have hyperthreading and required a single-CPU HAL. If the HAL is the same o­n both the imaged and local systems, compare the NTFS permissions o­n the RIS server's image folder with the permissions o­n an image that you know works. If the permissions aren't the same, adjust them o­n the image folder so they match the permissions o­n the folder of the working image

 

Q. How can I add a new adapter to the list of supported Microsoft Remote Installation Services (RIS) adapters?

John Savill
InstantDoc #42476
John Savill's FAQ for Windows




A. To add a new adapter, perform the following steps o­n the RIS server:

If the driver isn't digitally signed, you must configure the installation to ignore the driver-signing policy. To do so, open the RIS image's .sif file (e.g. Ristndrd.sif) and add the following line to the file's [Unattended] section:
DriverSigningPolicy = Ignore
Expand the NIC driver and copy the .inf and .sys files to the RemoteInstall\Setup\\Images\image\i386 folder. (Image represents the name of the image file.)
Within the image's \i386 folder, create the folder structure $oem$\$1\Drivers\Nic. For example, create the folder
RemoteInstall\Setup\\Images\image\i386\$oem$\$1\Drivers\Nic
Copy the .inf and .sys files that you copied earlier to the new folder.
Open the .sif file for the RIS image, and add the following lines in the [Unattended] section. (If the OemPreinstall line already exists, edit the line to say yes instead of no.)
OemPreinstall = yes
OemPnpDriversPath = Drivers\Nic
Restart the Boot Information Negotiation Layer (BINL) service by entering
net stop binlsvc
net start binlsvc