/build/static/layout/Breadcrumb_cap_w.png

KACE Product Support Question


PXE/iPXE, Vlans, Oh My...

06/13/2017 1209 views
Good morning all,

Last year, we got in a pickle when our NOC was able to see our K2 on their network and determined it vulnerable. As a result, we moved our K2 off our primary vlan and onto a secondary vlan. Deployments worked fine, but in order to capture, I had to plug a target system into a different wallport that was on the 2nd vlan. All was good....

The pickle got bigger when we were tasked with virtualizing our K2. We got the installer from Quest, spun up the VM, got the version equal between the physical and the virtual appliance, migrated all my KBE's, images, packages, etc to the VM, and then continued the upgrade process. We are on 4.1.182 currently.

I've been asked to create a new image for Win10_1703. I built and sysprepped, enabled DHCP on my K2, boot to NIC (using a Dell 990) and get a 'No configuration methods succeeded' message.

Did some searching and realized what we apparently didn't realize before: the change to PXE booting that occurred in the 4.0 update.

I contacted Quest. They advised me, as in the KKE video, to update my DHCP server with the new settings for PXE and iPXE. We don't have DHCP on this vlan, and I don't think I can configure this in the K2.

Does this make sense and does anyone have any suggestions?

Thanks,

-- Ray


2 Comments   [ + ] Show comments

Comments

  • Kind of..

    First, 4.0 is NOT PXE booting anymore technically speaking, is it iPXE booting, it's the evolution of PXE booting and it allows you to PXE boot both Legacy and UEFI BIOS systems.

    See: https://en.wikipedia.org/wiki/IPXE for more details.

    I believe depending on the DHCP you're using, the configuration varies. For example, Win Server 2008 R2 has a different DHCP setup than Win 2012 or Win 2016 domain controllers....

    If the K2 is being used as DHCP, no setting needs to be done, just make sure they can ping each other and all needed ports are open:
    See: https://support.quest.com/kb/129799
  • Another option might be to create a hard coded USB key to boot the system to capture the image. This would use the KBE manipulator so set the K2 IP, then install onto a USB Key and choose that to load the files into the RamDisk of the target system.

Be the first to answer this question

 
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