Thanks for that. But I am a little confused, so please forgive me.
You said “Vendor Class Identifiers. We have an article written just for this” but there is nothing in there about Cisco configuration for multiple vendor class identifiers.
“I’d strongly advise you to upgrade to FOG Trunk” but then later “I would advise against it.”. I am not sure if I should or shouldn’t.
From what I can gather, Windows server DHCP is the most flexible way, and seems like you can inject multiple boot files (undi / ipxe / snponly etc). Perhaps I should move from Cisco DHCP to Server 2012, as its easier to manage.
Question, if I go to Windows Server DHCP, am I correct in assuming it allow multiple boot files automatically depending on device.
So if UEFI device is trying to boot, it will boot the ipxe and if we have older devices, it will boot same old undionly file?
I will go and do some research on Cisco multiple Vendor Class Identifiers and see if its possible, and will post back if successful and with steps.