Why am I not picking up DHCP on RIS install?
November 8, 2006 1:24 PM Subscribe
WindowsGeekeryFilter: RIS Installation -- Riprep image installs fine, but will not join domain during the GUI install. Much...
Windows 2003 RIS Server, pushing a riprep Windows XP image. Originally, we boot directly to the NIC and it receives network information from DHCP (which is a different server than the RIS server) and it loads into the image selection screen fine. Select the image, it copies over all the files in the text mode. Once it finishes, it reboots to continue the GUI portion of the install. Once it reboots, it doesn't pick up the IP address and is no longer on the network. Due to this, it will not join the domain.
If you select to continue without joining the domain, it will load into Windows and installs all drivers properly (all in the $OEM$ folder and specified in the .sif file), and the NIC driver is installed properly. It picks up the DHCP perfectly and you can join the domain once you are in Windows itself. It appears that RIS is not getting the correct NIC drivers during the GUI installation phase.
From my understanding, RIS pulls NIC drivers from different locations depending on which phase of the install. My observation is during the text install portion, it pulls from the base image i386 directory. When it reboots, it should pull from the custom image i386 directory. When it loads into Windows, it should officially load the complete driver from the $oem$ directory listed in the .sif file.
The official drivers have special "RIS" inf files to place in the custom image i386 directory, and I've followed that documentation to a T.
Any ideas as to why the NIC is not functioning during the GUI portion of the installation?
Windows 2003 RIS Server, pushing a riprep Windows XP image. Originally, we boot directly to the NIC and it receives network information from DHCP (which is a different server than the RIS server) and it loads into the image selection screen fine. Select the image, it copies over all the files in the text mode. Once it finishes, it reboots to continue the GUI portion of the install. Once it reboots, it doesn't pick up the IP address and is no longer on the network. Due to this, it will not join the domain.
If you select to continue without joining the domain, it will load into Windows and installs all drivers properly (all in the $OEM$ folder and specified in the .sif file), and the NIC driver is installed properly. It picks up the DHCP perfectly and you can join the domain once you are in Windows itself. It appears that RIS is not getting the correct NIC drivers during the GUI installation phase.
From my understanding, RIS pulls NIC drivers from different locations depending on which phase of the install. My observation is during the text install portion, it pulls from the base image i386 directory. When it reboots, it should pull from the custom image i386 directory. When it loads into Windows, it should officially load the complete driver from the $oem$ directory listed in the .sif file.
The official drivers have special "RIS" inf files to place in the custom image i386 directory, and I've followed that documentation to a T.
Any ideas as to why the NIC is not functioning during the GUI portion of the installation?
« Older Who performed this cover of Cher's (ridiculous but... | The Rogue Hair - Beyond Thunderdome Newer »
This thread is closed to new comments.
posted by bda1972 at 9:58 PM on November 8, 2006