@djgalloway In the fog settings -> fog configuration page there is a field called “log level” or something close to that. The default is 4, set it to 7 to see if we can get some of the prestartup error logs. It should not just hang.
@rocksteve69 Well, lets start by collecting some details on this target hardware. Lets do the following.
Manually register a target computer into FOG (you may have already done this because you are having issues deploying).
Schedule a capture/deploy to this target system, but before you schedule the task, tick the debug checkbox.
PXE boot the target computer
After several screens of text that you need to clear by pressing enter, you will be dropped to the FOS Linux command prompt.
Key in ip addr show and collect the IP address of the FOS LInux client
Set root's password to something simple like *hello with passwd Don’t worry this password will be reset the next time FOS boots.
Now with the information you set in steps 5 and 6, use putty or a remote window shell from a second computer by connecting to ssh on the FOS LInux system using info you previously collected. This remote connection will help you copy and paste commands into the FOS Linux shell.
Key in lspci -nn -k and post the results here. If you get an error drop the -k from the command. This command will print out the hardware ID and the kernel driver being used for that device.
@Daniel-Miller Hmm, making progress!
It’s strange you get the Middleware::Response Invalid host when starting as root. Is this host registered with FOG yet? If not, manually register it. If it is, then reset encryption data in the FOG web UI settings for this particular host.
I actually don’t see where those service loads happen during install.
I think this is what you are looking for: https://github.com/FOGProject/fog-client/blob/master/UniversalInstaller/UniversalInstaller.cs#L418 (called here I suppose)
@jester805 For Windows 2012+ dhcp server there is guidance on how to set it up here: https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy
The instructions are for 2012 dhcp server, but I can tell you they work well for 2016 dhcp server too.
A couple of deviations from the tutorial.
I would setup these classes
Type Architecture Name
---- -----------------
6 EFI IA32
7 EFI BC (EFI Byte Code)
9 EFI x86-64
Set your default dhcp option 67 to undionly.kpxe.
Set dhcp option 66 to the IP address of your fog server
In the custom filters only set dhcp option 67. Don’t set option 66 like in the instructions\
The idea is if one of the filters don’t match then it will pick the default values which will be for bios computers (undionly.kpxe)
