I’m doing some stuff on VMware at home that requires a Windows 2003 SP1 RIS installation. I set up my test domain with a DC and workstations. I got RIS ready and started up a client in PXE mode only to get thisL
VXE-E53: No boot filename received
PXE-M0F: Exiting Intel PXE ROM
Operating System not found
I’ve been working with RIS since 2003 and I thought I’d seen everything. Don’t get me wrong, I think it’s been an excellent but underused part of Windows Server. I used it for 2 years to build PC’s on the network that I designed and managed. I googled about for a while and found plenty of people looking for help on this problem without any joy. And then I found a blog entry by a Mark Michaelis that resolved the problem.
I had to add two scope options onto my DHCP server that I’d not seen before:
- 066 Boot Server Host Name: <RIS Server IP Address>
- 067 Bootfile Name: OSchooseri386startrom.com
I fired up the client again and everything worked. Thanks Mark!
A quick update:
Note that my RIS server was also my DHCP server. DHCP was previously installed and authorised. This may have caused the above problem. I also had another problem once I had succesfully laucnhed the RIS client. The client failed to read configuration data for the RIS service. I unauthorised and reauthorised DHCP and this resolved the problem. RIS worked perfectly after this (and quite quickly too I must add).
Oh, I’ve only had a quick read, but anyone planning on using Windows Deployment Services (the succesor to RIS in Windows 2003 SP2 and Longhorn) will need to be familiar with the above two DHCP scope options.