Devlin7

Hi, I'm new here. On Monday, our server applied Windows 2003 SP2 and upgraded RIS to WDS. We have been using RIS for the past 2 years to PXE boot some Linux thin clients. I have been manually adding computers to Active Directory [prestage], supplying a guid to recognise and setting a remote install server path pointing to the Linux boot image. [\Setup\English\Images\Thinstation\I386\templates\pxelinux.0] [see Prestage.jpg] Now when a client boots it sits trying to get an IP address and then states that PXE boot failed. After a while I realised that machine was getting an IP address [DHCP logs], it appears that it wasn't getting the boot image. I decided to set option in DHCP to download the image and this has been an effective work around to problem. Normally, when I PXE boot I get the RIS screen which allows me to logon as an Admin and then select the image I want to install. The only exception to this is if the machine has already been prestaged with a boot image [and the netbootMachineFilePath set to \Setup\English\Images\Thinstation\I386\templates\pxelinux.0] in which cases it just boots straight into Linux. [see adsiedit.jpg] It seems that WDS has brokem my ability to prestage. WDS doesn't seem to want to work in either LEGACY mode or Mixed mode. If I don't specify option 67 in DHCP no boot image is found. [see DHCP.jpg] WDS config has x86 machine pointing to a file called bootrom.pxe [Mixed mode], but this doesn't seem to exist. If I point option 67 to \\server\reminst\OSChooser\i386\startrom.com I get my windows menu but I can't bypass it without logging on as an administrator. After reading the web for 8 hours yesterday I still haven't found how to make WDS act like RIS did before the upgrade. The DHCP solution works but it means I need to make a reservation for each machine that needs a different image and I can no long RIS my machines because the moment a machine PXE boots it starts Linux. Any suggestions? [other than backout SP2!]