John Jolet said on Mon, Sep 26, 2005 at 02:36:42PM -0500: > I would avoid doing that, and here's why: the entries in systemimager > dhcp server will cause machines to be loaded with images. That's > kinda the point, right? So...what happens when someone with one of > these machines for whatever reason, gets pxeboot on top of the boot > priorities list, and hits a production dhcp server with their info in > it? they get reloaded....or at least the danger of that is much > greater. My systemimager/dhcp server is not even on the main > net...it's on a switch with no connection to the main network. Once > the computer is set up, they can get dhcp from wherever.
Heh. This happened to me; I nuked someone's personal machine. OTOH, we re-image machines as a matter of course, so we use groups to place machines into the "never re-image because they aren't ours" category now. My environment is pretty different from most, though. In anyrate, in answer to the first posters question: You need to get them to set DHCP option 140 to the hostname of your imageserver. They should also set "next-server" (a standard DHCP option), to your TFTP server, and "filename" to your pxelinux boot file (in my case, /pxelinux.0). That's enough to make it all work. They then just need to make sure that your hosts get those options sent to them. I'm not sure why "filename" and "next-server" aren't options in the ISC dhcpd configuration; they may actually not be DHCP options as such. M
signature.asc
Description: Digital signature
