Windows 8 Boot fail MBR related.

So I have having a little trouble getting my deployment to complete.  I get as far as the first reboot after installing the drivers from the driver feed.  Upon the first boot, which is then meant to continue back into the Kace installation for post deploy tasks to run. I am getting the below error.  This has happened on a Latitude E7440 notebook at a Remote Site as well as a VM local to the main K2000 server.  

For reference, here are the Pre Install tasks.  


I am capturing Win 8.1 Enterprise.  I used the Dell sysprep Creator tool to create the sysprep and ran before capturing my image which was created using a VM (ESXi hosted).  I have build and deployed many WDS servers and clients over the years and am getting my feet wet with KACE.  Has anyone seen anything like this and have any possible solutions? 

0 Comments   [ + ] Show comments

Answers (1)

Posted by: SMal.tmcc 5 years ago
Red Belt
look at your source capture, does it also have a small system partition

  • Looks like my source was UEFI. I have been doing everything UEFI for the past few years using WDS and deploying over the network, but Dell are saying that Kace currently not support UEFI network deploys. So I am recreating my capture image using a BIOS MBR. - Vivalo 5 years ago
    • you can do uefi images, just not pxe boot uefi with Kace - SMal.tmcc 5 years ago
      • Yeah, that's why I said Kace currently doesn't support UEFI network deploys. Not the biggest problem in the world, but means i have to choose between WDS and UEFI..... - Vivalo 5 years ago
      • if your current machines are uefi you can boot them by placing the boot on the drives current image and call that, or use a boot stick - SMal.tmcc 5 years ago
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