Posts made by greichelt

@FGeyer

I know this is an old topic, but it looks like you don’t have a solution. I have this exact problem. It looks like @Tom-Elliott may consider this unnecessary (which may very well be true for other use cases), but for the sake of using @george1421 's awesome driver injection solution, it would be really nice to have. My workaround was to utilize OS type 4 for Windows 11 as I am not using it for anything. I updated the following line in “fog.custominstall”

case $osid in
5|6|7|9)

to

case $osid in
4|5|6|7|9)

Then I updated the following line in “fog.copydrivers”

case $osid in
5) osn=“win7” ;;
6) osn=“win8” ;;
7) osn=“win8.1” ;;
9) osn=“win10” ;;

to

case $osid in
4) osn=“win11” ;;
5) osn=“win7” ;;
6) osn=“win8” ;;
7) osn=“win8.1” ;;
9) osn=“win10” ;;

Mark you image as OS type 4 and it works as it should. Hope this helps.

Finally figured it out. The packet capture was key. Apparently the file were looking for is when pxe booting with this particular version of dnsmasq is undionly,kpxe.0. This is the file that could not be found. I created a symlink like this - sudo ln -s undionly.kpxe undionly.kpxe.0 and it resolved the problem. Hopefully this will help future, non-Linux inclined users of FOG.

I have been running a FOG server for several years now. Configuration took a while, but once I had it up and running, it’s been bullet proof. Recently, we had a former employee “try to update” the server without permission. He was not able to tell us what he actually did to it, but it broke our ability to PXE boot. I’m certainly not a Linux guru by any stretch of the imagination, but I’ve been using my Google-fu to attempt to fix this to no avail. Here is everything I can think of that’s relevant:

1. I have updated FOG to the latest version with no issues
2. dnsmasq seems to be functioning fine
3. I am able to tftp -i 172.31.0.2 get undionly.kpxe
4. I can successfully logon to the fog web interface
5. I have attached a packet capture and screenshot of the PXE boot error

I’m sure there is a lot more I should include, so please let me know what you need and I’ll provide. Any help is greatly appreciated.

traffic-of-interest.pcap

@george1421 Thank you so much for the quick reply. I figured this part out. I ran sudo apt-get install dnsmasq and didn’t really pay attention to what was going on. It told me the latest version for LTS 16.04 was already installed, so I was still on 2.75. After a bunch of googlefoo, I check the version with dnsmasq -v and saw my error. I followed this - https://wiki.fogproject.org/wiki/index.php?title=ProxyDHCP_with_dnsmasq and installed 2.76. Now, it’s working! This unfortunately broke DNS lookups on my FOG server and I’m not sure how to fix it. I can ping 8.8.8.8 and get a response, but can’t nslookup.

@george1421 I setup dnsmasq as you have suggested as I was not able to get my VMware VMs to EFI PXE; however, I am getting the as shown in the screenshot below when I legacy boot. EFI no longer functions on my working Dells. I am using Ubuntu 16.04. My FOG server is 172.31.0.2 (I updated all 5 entries in the script in the link you provided). I’m not sure where to go from here.

@george1421 Thanks, George. I think I’ve got it from here. You can mark this as solved. If I have further unforeseen questions or problems regarding this same issue, should I reply to this post, or open a new one?

@george1421 Looks like I got a horrible driver pack from Dell. I got several prompts titled “Windows can’t verify the publisher of this driver software.” Manual install of the drivers from this folder using device manager throws the error, “Windows encountered a problem installing the drivers for your device. Windows found drivers for your device but encountered an error while attempting to install them. The has for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering.” I’ve been getting my drivers from here - https://www.dell.com/support/article/us/en/19/sln312414/dell-command-deploy-driver-packs-for-enterprise-client-os-deployment?lang=en and, so far, have never had an issue. This has been an awesome resource up until now. The pack I downloaded was the Latitude 5500 Windows 10 Driver Pack A05 (11/26/2019).

@george1421 I am going to attempt #2 now as i have to run out to a customer’s site now to do a VMware install. #1 will take more time than I have now. To provide some additional insight into what happens before and after I hard reset (because I just did it after letting the 5500 sit all night), when I came in this morning, the notebook display was black. Gesturing on the touchpad wakes up the display “Just a moment…”, so it’s not a freeze; it is responsive. Holding the power button for 15 seconds does a hard shutdown. After powering back on, I get “Just a moment…” for a few seconds then the annoying “Hi” and all the M$ crap that follows. I am then presented with a desktop (no request to logon, just the desktop with the expected icons). Trying #2 now.

I forgot to mention, a hard reboot allows the machine to boot into the OS, but SetupComplete.cmd does not run, so no drivers are actually installed (SetupComplete.cmd installs the drivers injected to C:\Drivers) and the workstation rename does not happen (a PowerShell script that gets called by SetupComplete.cmd).

We just received a new batch of Dell Latitude 5500 notebooks. We currently have an array of other Dell notebooks and desktops (17 in all) that we image with various golden images all cloned from the same base image built in VMware. This image is in audit mode with no preinstalled software or drivers. We clone the image, boot the clone (the clone boots in audit mode), install software (no drivers or VMware tools are installed), sysprep with an unattend.xml file, and image the workstations. Drivers are injected at the end of the Partclone process using @george1421 's post install script - https://forums.fogproject.org/topic/11126/using-fog-postinstall-scripts-for-windows-driver-injection-2017-ed. We have found that keeping all drivers out of our images allows us to never have problems with deploying a workstation, until now.

The new Latitude 5500 notebooks hang at “Just a moment…” upon first boot (just after Partclone and the driver injection). We have never seen Windows 10 do this before. They seem to image just fine (after some UEFI PXE tweaking that @george1421 and @Sebastian-Roth helped me through on a previous topic), so we are not sure where to go from here. Any suggestions would be greatly appreciated.

@george1421 George, at @Sebastian-Roth 's request, I am opening a new topic for this. To answer your question, we install no drivers in our golden image, not even VMware tools. Whatever drivers are installed are included in the Windows 10 1803 base install.

@Sebastian-Roth Doing it now. Thanks again.

@george1421 @Sebastian-Roth Well, I used all of the reboot= options and they all had the same results; HOWEVER, it lead me to remove acpi=off from KERNEL ARGS and it fixed the problem with it hanging after the post install script! So that one is fixed.

I am still having a problem with the 5500 stopping at the blue “Just a moment…” screen with the hula-hoop of circles spinning around. So far none of my other machines are doing this. After about 15 minutes, the screen goes black, so I thought it rebooted, but it turns out the laptop display just went to sleep. Gesturing on the touch pad wakes it up to “Just a moment…”. Alt+Tab produces no results. If I hard power off from here, the workstation does boot into the OS, but SetupComplete.cmd never runs. I don’t have anything other than a network cable and a power adapter plugged in (non-USB-C) Any thoughts?

@george1421 Let me start off by offering my apologies for sending you down a rabbit hole regarding BIOS/UEFI image capture. I looked through the procedure and found the images are being created in VMWare as UEFI, then the sysprep, shutdown, boot to BIOS, change to Legacy boot then capture. From there, we deploy to the physical workstation with legacy enabled, then switch to UEFI on first boot. So you are absolutely correct; our images are being created as UEFI. I was going by memory from a year ago and should not have wasted your time.

@george1421 @Sebastian-Roth I have begun toggling through the reboot= options because I won’t sleep tonight unless I have tried each one. So far reboot=warm and reboot=hard leaves the system hung at restarting system and reboot=efi giving an actual error as shown in the previous post.

@george1421 @Sebastian-Roth thank you both so much. I am heading home for the night and will pick this up again tomorrow and report back. I have started toggling through the reboot= options, though I put them in the universal Kernel Args settings under FOG Configuration > FOG Settings > General Settings > KERNEL ARGS since the hang is happening to all of our active models. reboot=efi made the screen vomit and ended in “Fixing recursive fault but reboot is needed!” I’ll try some more options tomorrow to see what I get. I have provided a screenshot to better flesh out what I mean by vomit

@george1421 I’d put money on you being right. If your theory is correct and it “internally switched it self back to bios mode”, there is no evidence of this in the BIOS; BIOS shows UEFI with legacy boot options disabled. I have an E5450 and a 5590 in front of me and both show UEFI yet they were imaged with the method I described. Furthermore, what lends credence to me thinking these are booting UEFI, we don’t see the Windows logo on boot like you do with a BIOS boot, we get the Dell logo with the hula-hoop of circles then the logon screen.

@Sebastian-Roth Got it. What’s the formatting for adding more than one arg?

acpi=off,reboot=cold
acpi=off, reboot=cold
acpi=off;reboot=cold

etc…

@Sebastian-Roth This one is a bit over my head. Where do I go to find and edit this file?

@george1421 Regarding dnsmasq, you’ve talked me into it. My only question is on step 1 where you have us “remove pxe boot information from your router”. Under the Advanced tab, my SonicWALL has 3 fields (screenshot below). Which field should I remove?

Regarding the post install script, you kickstarted my memory. I built this setup a year ago, so I forgot. I thought the driver install portion was built-in to FOG, but I remember following one of your posts to get driver injection working (this one - https://forums.fogproject.org/topic/11126/using-fog-postinstall-scripts-for-windows-driver-injection-2017-ed). This has been working flawlessly for all of our 17 laptop desktop models using legacy boot and undionly.kpxe. The issue with it hanging at “Restarting system” only started today when I updated the Boot File line on my SonicWALL DHCP serverr from undionly.kpxe to ipxe.efi. I bet if I switch it back I will not have a problem with it hanging. With that said, I will dig into the post install script and see what I can find.

Regarding your lack of belief , before you said anything, I had no idea it was a known issue switching from legacy to UEFI after my imaging process. This is the process we came up with a year ago when we setup FOG. It always worked, so I never questioned it. I’m absolutely dumbfounded that we have never had an issue with it until now. I’m certainly not dismissing your recommendation, in fact, after setting up dnsmasq, I am going to switch my VMware VM to UEFI, recapture, and test.

@george1421 thank you so much for quick reply. My apologies for the blurry picture. I have added a new one below. The error in the picture happens just after the drivers are detected and pulled. This is not a post install script, it happens just after FOG’s built-in driver detection that runs just after Partclone finishes.

If I have a problem getting my other laptops that support legacy boot to work, I may setup dnsmasq as my SonicWALL does not support dynamic boot files, but I would like to switch everything over to UEFI since it saves me from having to go into every BIOS and changing from UEFI to Legacy and back after the deployment is finished.

All of my images are BIOS captured (from a VMware VM) and BIOS deployed. After deployment, I access BIOS, disable legacy, enable Secure Boot, and boot UEFI with no issues. We have 17 different models of laptops/desktops we do this with (the 5500 would make 18 if it worked - model list below image). This time, I BIOS captured the image then deployed with UEFI on and Secure Boot off to 3 different models and had mixed results. All laptops hung at “Restarting systems” (screenshot below). The 7212 deployed without issue, the E5450 deployed and booted to OS, but SetupComplete.cmd didn’t run, and the 5500 hung at Just a Moment with a hard reboot allowing it to boot to OS, but SetupComplete.cmd didn’t run.

Several of my laptops get imaged using Legacy deploy with RAID-On enabled and get switch to UEFI when imaging is complete. Any laptop that we get the no HDD error on we switch to AHCI to get around this, image using Legacy and switch to UEFI when imaging is complete.

With all this said, can you please clarify …" you can not install (and expect it to boot) a bios captured image onto a uefi based computer." Are you saying I can’t legacy capture and legacy deploy then switch to UEFI? If so, this has been working great for me for a year on all 17 models. OR, are you saying that I can’t legacy capture and UEFI deploy? If so, this is likely my problem as I am getting mixed results as described in my 3rd paragraph.

Latitude
3500
5480
5491
5500 (not working)
5580
5590
7212 Rugged
7490
E5450
E5470
E5540
E5550
E6440

OptiPlex
3050
3060
5050
7060

Precision
3510