Deployment Solution

Hello, 

Currently I used HyperV Gen 2 (UEFI) to create our corporate images. Before when using HyperV Gen 1 (Reg Bios) I could boot off the boot iso i created with Boot Disk Creator *:\Program Files\Altiris\Deployment\BDC\bootwiz\Bootwiz.exe.

Now since i went to Gen 2 with is secure boot i can no longer boot from this iso, so i'm wondering how I can go about creating a boot iso the is efi enabled? or converting my current one to be EFI bootable?

Any help would be appreciated.

What version of DS?  DS 7.5 supports UEFI via WinPE 4.  DS 6.9 SP6 supports UEFI via WinPE4 as well.  Earlier versions did not support it well.  Not 100% sure of the ISO build and how that affects this, but I'm guessing what you need is PE4 instead of PE 2.1.  My first guess anyway...

I'm on DS7.5 HF3

I hope you meant 7.5 SP1 HF something.  HF3 is broken on the initial release.  HF4/HF5 is where we started recommending things.  HF3 is really old.

Unless you're on SP1 that is.  That's really new.  :D  You might want to get an updated version up in a lab and try again.  It just a lab - free license - you know.  Then see if it works.  If not, let us know.

Yeah were on the latest... 

AFAIK, UEFI secure boot is not yet supported.

Please try with non secure boot option

Regards,
Anil

@hmh_it -do you need anymore assistance here?

I guess not as Anil says its not supported

UEFI booting is a mine field as every element in the process has to be 64-bit. This is not an Altiris constraint, but one that is implicit in the technology itself. When you add secure boot to this, you also add another constraint that your DVD drive's storage controller firmware needs to be both signed and authenticated.

In short, you are going to have a lot of trouble with UEFI and secure boot I think in general until this technology area matures. Microsoft's angle with secure boot is that it is intended to help secure the machine after the OS is installed. This is why a lot of advice from Microsoft on this topic is to disable secure boot prior to the OS install, and then enable it again afterwards.

Kind Regards,
Ian./