/build/static/layout/Breadcrumb_cap_w.png
04/09/2019 169 views

Hello,

I have created a customized Win 10 1809 image on VMWare workstation and am now trying to capture it. On trying to boot to KBE I see DHCP address being assigned and it seems to try to get to KBE screen but all I see is a black screen. I see the same behaviour on a Win 10 technician machine on the same VMWare workstation that I am trying to PXE boot, it also has apps already installed. However on a brand new VM with no OS on it when I try to boot to same KBE it does and it allows me to capture imageĀ and all other menu items. A new KBE was built with Windows 10 ADK and is being used by both VM with OS and apps configured as well as a VM with no apps

I am hoping I don't have to recreate the VM and was wondering if anyone has come across this issue

Many thanks



Answer Summary:
1 Comment   [ + ] Show comment

Comments

  • Update - the new VM that I had created for which the KBE was working once I modified that VM to increase disk size I again started seeing the black screen post acquiring IP address from DHCP. Wondering if it has something to do with VMWare?

Answer Chosen by the Author

0

I was able to boot into KBE now, had to for whatever reason change the vCPU from 2 to 1 which seems to have fixed the issue

Thanks

Answered 04/09/2019 by: kace_admin
Orange Belt

  • See:

    https://support.quest.com/kace-systems-deployment-appliance/kb/232911/unable-to-pxe-boot-vmware-vms-to-legacy-ipxe-with-more-than-one-vcpu