/build/static/layout/Breadcrumb_cap_w.png

Virtualised Capture and Deploy of an EFI Image

Hello all,

I am trying to change the way we do a few things in our build process and I would like to start incorporating VMware virtual machines as the platform in which we build our base images, but I am hitting a stumbling block.

For a standard BIOS image, I think I have a good idea of how to do it, although have not followed through with a deployment of my capture with standard C: MBR and D: OS partitions.

An UEFI image is where I am having the most trouble. We are trying to create a gold image that can be used on our Dell Latitude 10's and I need to have the VM running in EFI mode. I have got it to EFI mode, I have followed steps I have found to add a manual boot entry for the .EFI file on my KACE x86 boot stick, yet when I try and boot to it I get "unsuccessful", which I also get if I try to boot from the ISO. I am performing this by passing through the USB stick from my laptop through the VM's console window. I have not yet tried plugging the USB directly into the VM host and passing it to the VM, but am not sure if this will make the difference as the EFI boot manager can see the contents of the stick.

So the questions I have really are:

Can you boot to a KBE stick in VMware ESXI?

Is creating a UEFI image through VMware going to work on the Dell Latitude 10?

If you have any other suggestions on managing the imaging process through VMware I would appreciate any feedback.

Please do ask if I need to provide any more info on the environment.

Thank you in advance for your replies.

Kind regards,

-- Danny


0 Comments   [ + ] Show comments

Answers (1)

Posted by: nlieschke 9 years ago
Yellow Belt
0
Hi,

You can certainly capture and deploy for both legacy and UEFI. You can do this in vmware workstation or ESXI. I now use several VM's I have created in our ESXi environment. 

Like you, I attempted to boot to my USB connected through my local machine. It seemed to start to boot into the KBE okay, however, eventually it fails or freezes on the windows logo.

What I ended up doing was putting the USB into the back of the host. I then created a DRS rule which prevents my image development VM's from moving to other hosts. 

Also, you need to make sure you have the correct drivers in your KBE. I would suggest using LSI Logic SAS for your VM, although if you like you can add the VMware Paravirtual driver into your K2000, reacache drivers upload relevant WIN PE etc. 

Apart from the VMware paravirtual driver, as long as you are running the latest winPE driver pack you will be fine. 

Once you have done this, you can "Force EFI Setup" under the VM Properties in the vcenter (web gui or vSphere). 

It's then a simple matter of selecting the USB from the boot options.

For legacy, you can just set a boot action on the MAC ADDDRESS which you can get from the VM properties also, the boot to NIC.  

Let me know if you have issues I can add screenshots etc if you like. 








 

Comments:
  • Hi, that's great advice, thank you very much. I shall take another look today and see if I can get any further!

    Thanks,

    -- Danny - danleesmith 9 years ago
  • Hi can I see the screenshots if you still have them? Thanks - mrposada3326 7 years ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ