/build/static/layout/Breadcrumb_cap_w.png

Start KACE 2000 (KBE) from another iPXE Environment - Fails cause of wrong IP from Startserver. Any Ideas?

Hello everyone,

we use the KACE 2000 for deploying Systems. Now we have new requirement which I am actualiy testing. Our normal procedure for iPXE boot for Kace is controlled on the DCHP server by the appropriate options for the startup file and startup host. This works!

However, in the future we want to use another iPXE boot environment (as a new starting point) to start different virtual machines from there (IP: XXX.XXX.XXX.32). This new boot environment also offers the possibility to boot into other iPXE environments via script. From this point I would like to boot into KACE 2000.

Reason: A local operating system with the corresponding software should also be available on the clients.

The Skript to boot into the KACE 2000 iPXE looks like this:

cpuid --ext 29 && set arch x86_64 || set arch i386

chain http://XXX.XXX.XXX.52/boot/boot.php?mac=${mac}&platform=${platform}&arch=${arch}&client_ip=${ip}

The correct KBE is started and with it the underlying Windows PE. The problem now:

When trying to mount the KBOX share the IP address of the first used start server (XXX.XXX.XXX.32) is used. This fails, because the directory does not exist here (XXX.XXX.XXX.32\peinst). In my opinion the problem will occur with the CMD command: set /p KBOX_IP=<X:\windows\temp\kbox-ip-address. After that there is a ping to the address XXX.XXX.XXX.32 - which is of course wrong.

If our new boot environment is not used and the KACE start server is passed via the DHCP server, everything works as it should.

I would be very happy if someone had an idea how we could solve this problem. Thanks a lot for your help.

 

 

 

 


0 Comments   [ + ] Show comments

Answers (1)

Posted by: IT-MP 1 week ago
White Belt
0

Hello all,

I just found out that in the KBE a DHCP query is started again and thus the start server of the new boot environment is passed again. Does anyone have an idea what conditions I could set up on the DHCP to prevent this?


Comments:
  • Scopes

    Create a separate scope\range of IPs, and they're going to have their own scope options.

    So the same DHCP will be able to offer different option values for 66 and 67. - Channeler 1 week ago
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ