Error P2V with UEFI Secure Boot to Hyper-V

%3CLINGO-SUB%20id%3D%22lingo-sub-181210%22%20slang%3D%22en-US%22%3EError%20P2V%20with%20UEFI%20Secure%20Boot%20to%20Hyper-V%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-181210%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRONG%3ENEED%20YOUR%20HELP!%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20failing%20to%20convert%20a%20few%20physical%20machine%20to%20Hyper-V%20(W2012%20R2)%20due%20to%20%3CU%3EUEFI%20Secure%20Boot%20on%20the%20physical%20machine.%3CBR%20%2F%3EThe%20physical%20machines%20are%20running%20Windows%202008%20R2%20Server%20or%20Windows%202012%20Server.%20During%20the%20conversion%20process%2C%20we%20got%20the%20error%20showed%20in%20the%20attached%20image.%3C%2FU%3E%3C%2FP%3E%3CP%3E--%20Could%20someone%20help%20us%20to%20resolve%20this%20issue%3F%3CBR%20%2F%3E--%20How%20can%20the%20secure%20boot%20be%20disabled%3F%3CBR%20%2F%3E--%20How%20can%20we%20convert%20the%20physical%20machines%20to%20Hyper-V%20based%20on%20Generation%202%3F%3C%2FP%3E%3CP%3E--%20Any%20converter%20tool%20that%20support%20the%20convertion%20to%20Hyper-V%20on%20Windows%202012%20R2%20or%202016%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-181210%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EP2V%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESecure%20Boot%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EUEFI%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
Deleted
Not applicable

NEED YOUR HELP!

 

We are failing to convert a few physical machine to Hyper-V (W2012 R2) due to UEFI Secure Boot on the physical machine.
The physical machines are running Windows 2008 R2 Server or Windows 2012 Server. During the conversion process, we got the error showed in the attached image.

-- Could someone help us to resolve this issue?
-- How can the secure boot be disabled?
-- How can we convert the physical machines to Hyper-V based on Generation 2?

-- Any converter tool that support the convertion to Hyper-V on Windows 2012 R2 or 2016?

 

 

0 Replies