Hi,

I've decided that I won't be using our K2000 to deploy winxp due to the amount of work it'll take to setup the drivers and hal files. I carry on using it for win7 deployments and the k1000 for patching and updating.

So I'm going to carry on using acronis for our xp machines which uses microsoft RIS to netboot. How do I go about having two netboot (PXE) servers on the same network though? Has anyone tried this?

Thanks

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

1

I'm almost positive that you need to setup two VLANs to support multiple PXE servers.

Answered 05/20/2013 by: chucksteel
Red Belt

  • I've read that you can filter clients via mac address, is that possible on the K2000? or is it possible to disable the PXE on the k2000?
Please log in to comment
1

I would put both PXE boot servers on a seperate vlan and configure your DHCP options 66 and 67 to point to the server you want on specific vlans

Answered 05/20/2013 by: SMal.tmcc
Red Belt

  • This is working for us, we have no vlans, just one subnet but it's extended so we have two ranges 192.168.1 and 192.168.0

    We're just changing option 66 and 67 as we need to in order to boot from kace or acronis. Once we've made the move to win7 we'll ditch acronis completely so this is a nice easy short term solution for us.
Please log in to comment
0

Not entirely necessary. We use two pxe servers accross all of our vlans. The trick is to use iPXE and configure your boot options appropriately in DHCP + a pxelinux install on your Ris/WDS server.
Checklist for configuring:
Create a new userclass in your dhcp options for iPXE

Create option 66 and 67 for both your k2000 and WDS/Ris box (screenshot attached)

Add appropriate files for pxelinux to the \\deployserver\reminst\boot folder
Edit your default file in pxelinux.cfg folder under the architectures you want to boot (in folder mentioned above) example code below:

DEFAULT      vesamenu.c32
PROMPT       0
NOESCAPE     0
ALLOWOPTIONS 0
# Timeout in units of 1/10 s
TIMEOUT 100
MENU WIDTH 40
MENU MARGIN 0
MENU ROWS 12
MENU TIMEOUTROW 14
MENU HSHIFT 5
MENU VSHIFT 5
MENU COLOR BORDER 30;44       #00000000 #00000000 none
MENU COLOR TABMSG 1;36;44     #00000000 #00000000 none
MENU COLOR TITLE 1;36;44     #00000000 #00000000 none
MENU COLOR SEL   30;47       #40000000 #20ffffff
MENU BACKGROUND DeploymentLogo.JPEG MENU TITLE PXE Boot menu
MENU WIDTH 80
MENU MARGIN 18
MENU ROWS 7 LABEL local
MENU       DEFAULT
MENU LABEL ^0 = Boot From Local Hard Disk
LOCALBOOT 0 LABEL wds
MENU PASSWD xxxxxxx
MENU LABEL ^W = Boot Windows Deployment Services
KERNEL     pxeboot.0 keeppxe LABEL kace
MENU PASSWD xxxxxx
MENU LABEL ^K = Boot KACE Deployment Services
KERNEL ipxe.0 keeppxe LABEL Session1
MENU PASSWD xxxxx
MENU LABEL ^1 = Autoboot GhostSession 1
kernel memdisk
APPEND keeppxe initrd=Session1.img

Configure your pxe boot options for wds to use the files you'll get with pxe linux, depending on the OS, ie you'll need to do this via command line in 2k8 or 2k8R2 I cant remember and 2k12 is gui.

After that boot away and off you go.  If you have any particular questions regarding it let me know and I can provide you with a copy of our build doco for this setup.




Answered 05/20/2013 by: Roonerspism
Second Degree Brown Belt

Please log in to comment
Answer this question or Comment on this question for clarity