On Fri, Feb 13, 2009 at 12:19:32PM -0700, FoM - Technology Services
wrote:> And here's the problem.... Ghost is using a PXE server so that the
computers
> can be booted off the network and easily re-imaged. Citrix provisioning
> server requires the use of a PXE server so that the thick\thin clients can
> boot off the network directly to the server. But it's standard that the
> first PXE server to answer is what the computer gets.
>
> How can we make (2) PXE servers work in the same network?
>
> I understand that you could separate out the subnets, so that (1) PXE
server
> only answers in that sub-net. But that's only a temporary fix. Once we
have
> Citrix working, then other labs within the schools network may slowly
switch
> over to Citrix as well. And both Ghost and Citrix PXE servers will need to
> co-habitat.
>
> Is there a way that I could set up an PXELinux box so that it's
essentially
> a "PXE Re-Director". For example a user boots up their PC via
Network. It
> will then go to the PXELinux server (as pre-setup via the network somehow)
> and the user is given an option; (a) Citrix or (b) Ghost. By choosing one
> of these items you will then be taken to that particular PXE server of your
> choice and continue on from there.
IIRC in dhcp you can specify the next boot node. But this requires
recording the ethernet address of any hosts you want to boot.
For the dhcpd server on my systems something like:
group {
filename "ghostme.0";
next-server ghost-booter;
host ghost_client1 { hardware ethernet 0:c0:c3:49:2b:57; }
host ghost_client2 { hardware ethernet 0:c0:c3:80:fc:32; }
host ghost_client3 { hardware ethernet 0:c0:c3:22:46:81; }
}
group {
filename "pxelinux.0";
next-server citrix-booter;
host citrix_client1 { hardware ethernet 0:c0:c3:88:2d:81; }
host citrix_client2 { hardware ethernet 0:c0:c3:00:14:11; }
}
would do what you want. Check your dhcp documentation.
--
-- rouilj
John Rouillard
System Administrator
Renesys Corporation
603-244-9084 (cell)
603-643-9300 x 111