Disableing a Kace server



  • Hey all, got my fog server installed but un-known to me there is a kace imaging box which will automatically boot to under pxe mode on my optiplex 380’s. my question is does any one know how to take down the kace server without messing with the ticketing system? or can i use the image server boot in my dell bios to run fog?

    thanks in advance


  • Developer

    I can tell you from personal experience that FOG and Kace can coexist. Look into the ITNinja forums for setting the 244 option for DHCP for the K2000 and leave DHCP option 66 for FOG. Then look into PXE chaining to the IP address of the K2000 if you still want to use it for imaging. The K1000 and K2000 are completely separate so you shouldn’t have to worry about the ticketing/inventory system at all.

    Our FOG installation works similarly to the K2000 Dell drivers feed where it uses DPInst to install hardware-specific drivers after sysprep based on Dell model number. (You may also need to rebuild your KBE ISO to tell it to use option 244.)


  • Senior Developer

    Also, the latest (2811) has default support for ${fog-ip} ${fog-webroot} ${boot-url} syntax calling that works across all of iPXE. So it should be good to use on your own custom menus as needed. Also, remember, native ipxe calls still work (i.e. ${next-server} ${filename} etc…)


  • Developer

    [quote=“Malfunctioning Eddie, post: 39987, member: 27496”]
    As an interesting and somewhat related aside, I have looked at this option for supporting multiple PXE servers on on network. I haven’t had a chance to fully explore it, but it could prove useful in scenarios like ours where an existing PXE solution exists.
    [/quote]

    with the latest svn version of fog, it is possible to change the default ipxe menu boot option for systems that do not have a scheduled task. this could be set to chainboot to a second pxe server. all systems would first boot to Fog, then if there were no scheduled task, it would go to the next pxe server, and assuming there is nothing for it there, it would continue to boot normally.



  • This sounds familiar. We use KACE in our environment here. We actually have two KACE appliances…the 1000 and the 2000. The 2000 is the actual deployment box that machines PXE boot to. The 1000 runs our ticketing system and other tasks such as inventory tracking, package deployment, etc. The 1000 doesn’t PXE boot as far as I’m aware.

    Once upon a time, we (well, me) tried to use FOG here and I had to beg and plead to our network team to change a couple of DHCP options to PXE to FOG instead of KACE. I don’t recall the options, but I’m sure there are others here that can point you in the right direction. In any event, the KACE appliance remained active but would no longer allow systems to PXE from them.

    As an interesting and somewhat related aside, I have looked at this option for supporting multiple PXE servers on on network. I haven’t had a chance to fully explore it, but it could prove useful in scenarios like ours where an existing PXE solution exists.

    [url]http://www.vcritical.com/2011/06/peaceful-coexistence-wds-and-linux-pxe-servers/[/url]


  • Developer

    i don’t know anything about Kace in particular, but pxe booting requires that the DHCP server serve out the server and filename to boot. so that will need to be changed on your DHCP server


Log in to reply
 

417
Online

39184
Users

10832
Topics

103133
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.