@sebastian-roth Hi, I can take a look if you have another suggestion. Thanks,

@sebastian-roth omg, just “Create New Host” and then create a task to deploy the image you want - I was playing with the last week!

@GEORGE1421 I tried to deploy images to 6 more PCs. The ones that have the keyboard problem (5/6) has bios “J01 v02.15” and the one that worked is “J01 v02.06”. It works, if the bios is older.

@george1421 I’ll check that the next time. I just rebooted one 10x and the keyboard finally worked on the FOG screen.

@sebastian-roth I know, that’s why this is SO weird…

@sebastian-roth @GEORGE1421 the kb is usb. all ports are usb 2. I tried different ports and keyboard, too. It is just strange that the kb works later.

@george1421 it is stuck on the screen the has …this host is NOT registered… They are HP elite 8200.

Server

• FOG Version: 1.4.4
• OS: ubuntu 16.04 LTS

Client

• Service Version:
• OS:

Description

I have deployed FOG images on 9 PCs. However, I found that on 3 of them, the keyboard is not working on the FOG screen after the keyboard worked in bios to select the pxe boot. The 3 worked after either waiting overnight (since it was quitting time and trying the next morning) or going into the bios>computer settings>exiting without saving changes. However, these 2 workarounds are not working on the 10th PC.

The PC is on the list as OK/works with FOG. The keyboard has been changed and are simple/generic ones. I did not see any special keyboard settings in the bios.

Thanks,

Thanks for all the suggestions. I will have to move this to the back burner and concentrate on physical PCs, now.

@george1421 no joy yet

@wayne-workman

I did your suggestion “If I had this issue, I’d reinstall the OS on the VM from vanilla ISO, and then see if it can netowork boot via FOG and then sent to the HDD to boot the OS via the fog menu.”

This VM will boot from the FOG menu if the BIOS Exit Type is set to boot grub_first_hdd. It will boot to Windows if the BIOS is set to boot from IDE first.

However, my original VM created from a FOG captured image gives “Launching GRUB… begin pxe scan… Starting cmain()…” when the Exit Types for BIOS and EFI are set to grub_first_hdd. Also, if I set the BIOS to boot from the IDE first, I just get a blinking underscore (cursor).

I’m not sure where this leaves me since the ISO is a trial from Microsoft and the PCs from the vendor do not come with the ISO.

Thanks,

@wayne-workman I am changing the Exit Type for BIOS and UEFI.

@wayne-workman I’m trying this, now.

@tom-elliott First, I changed the Exit Types globally in the iPXE boot menu. Now, I am changing them on the Host. Thanks,

@tom-elliott It is gen 1. I tried Refind_efi and it did not work.

@sebastian-roth but I listed the “messages” I got on my post “…I get a blinking cursor or “starting cmain()”, “chainloading failed…”, iPXE>, grub>, etc.”

@sebastian-roth I did this before posting. I even tried every GRUB Exit Type.

Server

• FOG Version: 1.4.4
• OS: ubuntu 16.04 LTS

Client

• Service Version:
• OS:

Description

I have a FOG image that has been deployed ~5 times to physical PCs successfully, BIOS ones.
I created a new vm in hyper-v and set it to network boot and create. After the FOG image deploys and the vm reboots, I get “Booting from SAN device 0x80”. The host is registered in FOG and I changed the Exit Types to “Exit” and the various "GRUB"s but Windows 10 on the vm still does not boot - I get a blinking cursor or “starting cmain()”, “chainloading failed…”, iPXE>, grub>, etc. I also changed these Exit Types globally in the iPXE Boot Menu. When I iPXE boot and look at Client System Information, I see the 3 partitions, as on the physical PCs, and another one. I know the guys at PDQ were talking about FOG deploying images to VMs, but I do not know if they were using Hyper-V.

Thanks,