using FOG 1.5.5. On my Windows 10 Education images only I am having a problem. On any Dell computer, laptop or desktop. If Onboard NIC is first boot device, it will boot to FOG, at the FOG screen it will try to boot to hard drive after 3 seconds, but goes to a black screen and will never boot. If I change boot order in BIOS so that onboard NIC is not the first option it will boot fine. Even if I go to F12 boot menu options manually and choose onboard NIC and it boots to FOG, from there it will go on and boot from the hard drive after 3 seconds just fine. It’s only when I have onboard NIC as first boot device, it will not boot from hard drive after it boots to FOG. I do not have this problem on my Windows 10 LTSB or LTSC Images. BIOS booting. Not UEFI. Any ideas?Help!
Latest posts made by dmoseley
-
With NIC 1st boot device, won't boot to hard drive from FOG menu. Blinking cursor
-
Password protect Partic Magic iPXE menu item
I created a menu item for Parted Magic and it’s working great. I even added the parameters to password protect it. Thought it was working great. Turns out you can leave username and password fields blank and get to Parted Magic. Any idea what I’m doing wrong. FOG 1.5.5 on Ubuntu 16.04.
This is my parameters and it is set to show on all hosts. TIA.
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
kernel http://${fog-ip}/pmagic/bzImage64
initrd http://${fog-ip}/pmagic/initrd.img
initrd http://${fog-ip}/pmagic/files.cgz
imgargs bzImage64 boot=live ip=dhcp edd=on noapic load_ramdisk=1 prompt_ramdisk=0 rw vga=normal sleep=0 loglevel=0 keymap=us splash quiet - || read void
boot || read void -
RE: FOG Client Failing after recent W10 update
@george1421 thank you, @george1421. I will try that. Although, I haven’t been syspreping my fog images in the past and they’ve always worked fine. I used to use fogprep, but haven’t since Windows 7. I’ll give it a go.
-
RE: FOG Client Failing after recent W10 update
Matthew, I’m in the same situation, did you find a solution to error code 2725? I’m getting the same error. I know it has something to do with not being able to change the hostname, because if I manually change the hostname, but don’t bind to AD, and reboot, the fog service binds to AD just fine. Any input very much appreciated. Thanks.