Something i don't understand in the BIOS vs UEFI subject
Hello,
Like a lot a people i've met the BIOS vs UEFI issue. If i understand well, i can't use my old image who has been made for legacy mode on a UEFI system (i'm using K2000)?
I have the last version of K2000 (6.1) with the new preinstall and midlevel UEFI tassk.
Is it possible to continue using my old image or will i have to rebuild everything?
If the answer is yes, how can i do? It seems that it is almost impossible to Install Windows 10 in VirtualBox in UEFI mode.
Basically my question is: is there a way to deploy the image i have on my Appliance (legacy) on a UEFI system?
Regards,
David.
Answers (3)
I do not use VM to make my master. I use a dell 5050 barebones setup to create my masters on(both legacy and UEFI). I copy the admin profile to default when syspreping. This method has work for 13 years that we had Kace and we have HP, Lenovo, and Dell desktops and laptops plus surfaces I send this image to and it has never been a problem using a physical box.
I use this command to sysprep:
sysprep /generalize /oobe /shutdown /unattend:c:\windows\system32\sysprep\adminw10x64.xml
I do not recommend this but I did this at first:
This requires advanced knowledge of both Kace SDA and Windows
You create a UEFI master, delete the files on the OS capture those drives. Create a deployment for this and as a mid level task you manually deploy your old legacy OS wim.
Now with custom deployments you can do this by making a hybrid deployment of both the UEFI system partitions and the legacy OS partition.
The short answer is, yes you can. You will need to go into the system settings and set it back to legacy BIOS mode however. Depending on the make, Dell also has a checkbox for allowing legacy ROMs, I usually will also check this.
Yes, you can still use a bios captured image. The big caveat here, is you should only be capturing a single partition image, not both.
My image is captured from a clean VMWare virtual machine, Windows partition only (C:)
I deploy this to both legacy and uefi enabled machines by utilizing DHCP to determine the vendor class. This boots the KBE in either BIOS or UEFI, and the pre and mid level tasks lay down the appropriate boot code.
