We are attempting to migrate from Deploy Studio to the Kace 2000.  I am able to netboot a mac client while on the same vlan as the server.  However I can not netboot from another mac client on a different Vlan.  

I am able to PXE boot a windows client both on the same Vlan, as well as a different Vlan without issue.

I have added the IP Helper of our DHCP server, as well as the Kace 2000 to the Enterasys K Series (Layer 3) switches.

Our DHCP Server is running on a Microsoft Windows 2008 R2 Server (Stock DHCP Server).

Has anyone else figured this one out?


Thank you,

 

lk

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

3

Apple protocol prevents the traffic from hopping subnets unless the Mac has been blessed or ip helpers have been put in place on the network to pass the traffic. Run this tool on a Mac and try to netboot: http://mac.softpedia.com/progDownload/NetBoot-Across-Subnets-Download-10838.html

http://www.kace.com/support/resources/kb/article/discussion-on-booting-using-macboot-from-a-subnet-other-than-where-the-k2000-appliance-resides

Answered 06/03/2013 by: mpace
Red Belt

  • I have the appropriate IP Helpers in place. I am able to boot windows computers from either our Ghost, Windows Deployment Server, the Kace2000 box (windows OS only), and Macs using Deploy Studio. The only issue I am experiencing is attempting to boot Mac clients from the Kace2000.

    I was able to bless an OSX7.5 client, and then netboot to the Kace2000 box. I attempted to do the same on a OSX6.8 machine. Looks like the bless command went through ok (no errors), but it still would not netboot. I tried both a OSX6.3 and OSX8.3 netboot set.

    It's so very odd that I can netboot a Mac client from any Vlan using deploy studio, but not the Kace2000 box.

    Any other idea's? (thank you for the input).
  • Just spoke to the Kace Management and Developer Team. They do not fully support netbooting across subnets using iphelper. They also do NOT have it in the que for a future feature release. They believe that using an RSA on every vlan is adequate. The only way they will consider this important is based on votes. I found out we have to vote on things like this. I can't believe they consider booting outside of your imaging servers vlan as a "feature". Oh well, it's their rules, we just pay for them....

    Please vote here: http://kace.uservoice.com/forums/82717-k2000/suggestions/1687565-mac-netbooting-across-subnets

    Without the votes, it WILL NOT happen.
Please log in to comment

Answers

1

Possibly one port is closed:

http://www.kace.com/support/resources/kb/article/network-ports-needed-for-k2000-appliance-operation

Answered 06/01/2013 by: Nico_K
Red Belt

  • Thank you, but there is not a firewall in the middle with our network configuration.
  • Just spoke to the Kace Management and Developer Team. They do not fully support netbooting across subnets using iphelper. They also do NOT have it in the que for a future feature release. They believe that using an RSA on every vlan is adequate. The only way they will consider this important is based on votes. I found out we have to vote on things like this. I can't believe they consider booting outside of your imaging servers vlan as a "feature". Oh well, it's their rules, we just pay for them....

    Please vote here: http://kace.uservoice.com/forums/82717-k2000/suggestions/1687565-mac-netbooting-across-subnets

    Without the votes, it WILL NOT happen.
Please log in to comment
Answer this question or Comment on this question for clarity

Share