All of our unix sysadmin's workstations reside on a network where a Windows DHCP server is in charge (AKA authoritative). So jumping start a machine isn't easy with either DHCP or BOOTP anymore. With BOOTP, the RARP broadcast cannot even reach the jumpstart server. With DHCP, it's a little different. The DHCP requests can get to the jumpstart server and the jumpstart server is also nice enough to hand out the IP address and other jumpstart-related stuff. But the client always favors the offer from the Windows DHCP server which is authoritative for the whole network. Changing that is out of question, so I am thinking it's time to explore the wanboot option.
I went over the installation guide and it looked very easy to set up the jumpstart with wanboot. If I hadn't heard that JET 4.2 would be out in mid April, I would probably have followed the installation guide and manually set up the wanboot server already. I will just wait for a little longer and if it isn't up for download by early next week then I will probably just follow the guide and manually set up the wanboot server.
