Hi David,

The command for setting the forcepxeonnmextboot is

cctk.exe --forcepxeonnextboot=enable

The description for the items in UEFI boot order is shown in CLI, with the following command.

cctk bootorder --bootlisttype=uefi

The command for disabling IPv6 device in the given system is

cctk bootorder --bootlisttype=uefi --disabledevice=

Hope this helps.

Thanks, but I'm afraid that doesn't really help as this needs to run as an automated process, so no interaction. i.e. required to determine which uefi boot option refers to which.

I guess this may be a failing with uefi boot option presentation generally?!?  I don't have any other manufacturers UEFI based hardware on which to confirm this....

It would be nice if they had standard 'tags' for the various options e.g. uefi.ipv4 so we could reference by what it does...

Has anyone any further suggestions/experience on automating manipulation uefi bootorder with cctk?

Our current requirements are to enable the uefi network stack (--uefinwstack=enable) so that it is available via the F12 boot menu BUT disable/remove the "Onboard NIC(IPV4)" and "Onboard NIC(IPV6)" from the activebootlist 

Thanks

David

I am attempting to do the same thing, just disable Onboard NIC (IPV6) from Boot Order Sequence with Dell Command | Configure. Any thoughts would be appreciated.

Outside of a script (maybe powershell) that looks up the device ID numbers would not work consistently for enabling IPV6 PXE.  Select-String works wonders on exe output in PowerShell.

I cannot use UEFI at all on Dell computers for these reasons: (testing on Latitude 3340 BIOS: A11)

1.  A UEFI enabled flash drive is bootable without entering a setup password.  This is not the case when in Legacy mode.
2. I cannot prevent newly added devices in general from being bootable since CCTK cannot disable a UEFI device that is not connected.
3. ForcePXEONNextBoot sounds good in theory, but is difficult to get out of if you cannot boot to the network for some reason.  We have lots of issues with students plugging the power cord into the network jack and breaking pins.  

I've found the "Enable Boot Support" under "System Configuration", but it doesn't seem to be a CCTK supported option and we don't have the manpower to configure the 7000 Latitudes personally.  Even if we could, it breaks the convenient option to boot to a "disabled" device if you know the setup password.  

We have same requirement and the CCTK seems to only to be usefull in the insecure legacy mode.

@Dell Please fix it.

Dell do we have any one who can update this thread with their valuable feedback , I have been chasing from everywhere but no response and I see a lot of people are struggling with the same issue.

Friends anyone if able to resolve this problem with any workarounds please let me know.4

After enable Thunderbolt Boot Support under System Configuration, my 7390 2-in-1 using a DA300 can boot from PXE.

I had the same problem, just setup both uefi.1 and uefi.2 to be first, if one fails the other will run next and it will get there for my purposes.  But if you look at the log after running the package it will tell you which one is which:

2019/03/21 20:01:06 cctk -  DeviceStatus DeviceNumber     DeviceType    Shortform  DeviceDescription
2019/03/21 20:01:06 cctk -  -------------------------------------------------------------------------
  Enabled         2           UEFI Device       uefi.1  Onboard NIC(IPV4)
  Enabled         3           UEFI Device       uefi.2  Onboard NIC(IPV6)
  Enabled         0             Hard Disk          hdd  Windows Boot Manager
2019/03/21 20:01:06 cctk -  -------------------------------------------------------------------------
2019/03/21 20:01:06 cctk - You can use DeviceNumber or shortform to set the boot order.