@Sebastian-Roth Ok so I found a fix for single boot. By a chance several of the devices worked after a complete reimage and have no issues. The other devices that still had issues had a slightly more strenuous issue.

Install Iso Image Via USB:
Windows 11 and Windows 10 (Version 1709 and newer):
Rebuild the BCD store.

First run the command below to back up the old BCD:

ren BCD BCD.bak

Now re-create it using this command:

bcdboot c:\Windows /s <boot letter>: /f ALL (You can add a switch before /s for the computer locale: /l <language code>. By default, /l en-us English USA is used.)

bootrec /rebuildbcd

@george1421 I’ll be damned, pardon my french.

So I guess I was just not patient enough. You guys were right, the acpi error has nothing to do with this other than distracting it from the real process.

After changing the log to level 7, I noticed at some point it says its resizing right before the acpi errors take over. I realized its not stuck, its just taking a while to proceed bc resizing always takes a little longer when capturing image.

So I just let it sit there and eventually it proceeds on capturing the image. It doesn’t look pretty with all the acpi errors but it still does what it suppose to do.

Thank you @george1421 and @Sebastian-Roth for helping on this.

@Sebastian-Roth said in Windows Keys Management Plugin:

overwrite each others settings

Yess…this was the cause …i’ve uninstalled the plugin and now all seems ok 🙂
10x dude 💪

@pauleb Intriguing. So you didn’t need to create a EFI entry for the drive? I wonder if it was already there for that drive from the previous image or something.

I guess mine did not work because I first imaged my test machine with an MBR image, which made the EFI entry no longer show up.

Good luck, and thanks for the info.

@Flyer I create users in the setupcomplete.cmd batch file. That gets executed at the end of the WinSetup process and before the first login.

You can also with the unattend.xml file define an auto admin login process for a specific user. You can set up a counter so the auto login process only executes X times then reverts to login required. This is configured in the unattend.xml file. There is also a first run section where you can do things to update the user’s current profile.

So the idea would be to have the setupcomplete.cmd file create the user with a predefined secure password, then in the unattend.xml file have this user account setup to auto login once or twice depending on what you need, then have the first run section do what is needed to the user’s profile.

One of the last steps in the unattend.xml file is to delete the setupcomplete.cmd and the unattend.xml to erase any clear text passwords that might be contained within. Finally reboot the computer.

These are just ideas on alternate ways to go about solving this problem. I agree that accounts you create before should still exist after winsetup, but M$ typically has other ideas for us.

@itmod This piece of information still has not made it to the official docs (which are under work anyway). So here you go with a forum link: https://forums.fogproject.org/topic/16703/dual-boot-2-disks-unable-to-boot-grub

@kalafina Thanks for the update.

Nevertheless I opened an issue on github to look into making the fog-client a 64 bit application at some point.

@RTOadmin Are those topics related? https://forums.fogproject.org/topic/16715/printer-assignment-problem

May I ask you to not do double/cross posts? I know we have not answered in more than a week but opening another topic is not going to help. No offense! Just want to give you a heads up.

@lukebarone Thank you very much.It worked!

@kalafina I don’t know how to mark the topic as solved…

@kansukee I have never used Intune/Autopilot but from what I read about it I guess you can image using FOG and manage the devices with Intune/Autopilot. Give it a go and let us know here!

Searching the forums I can find a few hints on it here and there.

Hello, had the same problem. Try this, it’ wil fix your problem normally. Run the command : “manage-bde-status” many times until you see 0.0% .
Then try again to capture your image.

fog image .png

@sebastian-roth Thanks Sebasian I appreciate the input and had a feeling you would say that. Was worth the ask though! Hats off to ya! Cheers

@rogercrf Ok great (well not really, but now we know where to look). The PXE booting bits are all fine.

The issue here is that its possible that FOS Linux doesn’t have the driver for this network adapter.

What I want you to do is cancel this deployment task in the FOG web ui.

Lets first make sure the kernel actually got updated like we need.

from the fog server linux command prompt key in the following
file /var/www/html/fog/service/ipxe/bzImage (case is important). Hopefully it reports the kernel version is 5.15.x (where x is something larger than 50). If yes then we need to debug this kernel driver issue.

To debug this issue manually register this computer with the FOG server web ui. You will need to know the mac address of the computer. Once you manually register this computer with the FOG server, schedule a caputer/deploy task. Doesn’t matter, but before you hit the deploy task button tick the debug checkbox. Now schedule the task and pxe boot the target computer. It should immediately jump to imaging and not present the iPXE menu. You will still see the ip error message but it will drop you to the FOS Linux command prompt. Key in the following commands.
uname -a
ip a s
lspci -nn | grep -i net
grep -i firmware /var/log/messages

Take a clear picture of the output and we can debug more. But lets hope the kernel didn’t get updated and just an update will fix it.

@taylorcockrell Well there is no easy answer here. If you need secure boot enabled in your environment then you can create a self signed key and apply it to each workstation. Then you can sign both ipxe.efi and bzImage with the same key. Once that is done you can secure boot using FOG. I created a tutorial on this on the steps needed. For an opensource project its a bit impractical to get microsoft signed kernels and efi boot loaders to do it any other way. I wish there was a better solution.

In the case of the hardware, I know for Dell hardware you can use a Dell offered utility to modify the firmware from within the host OS. Thinking that you can turn off secure boot (which will break bitlocker, but you will reimage the computer anyway) then reboot the computer into PXE booting with FOG.

If you require an IT tech to sit in front of the computer to image it, then they can simply turn off secure boot and then boot into pxe booting via the uefi boot manager. The imaging tech would have the access and capabilities to disable secure boot prior to imaging.

@castelon The quick answers are yes, yes and no.

Ideally you will have the answer file on the windows golden image before you run the sysprep command because when calling sysprep you will point to the exact location of the answer file. Then shut down and capture with FOG.

While I was developing my golden image I wrote a post download script to open the windows disk and replace the answer file. I did it this way to avoid having to restore, update teh answer file then sysprep and recapture with fog.

While yes you can deploy it with a snapin, it won’t do you any good because winsetup needs that answer file BEFORE snapins would run. Its a chicken and egg situation.

Hi,
I force computers (with UEFI) to boot from HDD (Windows bootloader) with this command in snapin:

#Booot from HDD
#Snapin works only with Powershell x64 Snapin Template?
#Use at your own risk! No warranty!
c:\windows\system32\bcdedit.exe /set “{fwbootmgr}” displayorder “{bootmgr}”

We use it after imaging because PXE boot is too slow.
Peter

@multipass ok would you follow this tutorial to capture a pcap of the pxe booting process. https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

Upload that pcap to a file share site and DM me the link using FOG chat. I’ll take a look at it for the next steps. The capture filter will only collect the dhcp process and no other traffic on your network.

@rtarr said in Boot Loop after Sysprepping a Golden Image VM:

It then boots to the login page for the local admin where install packages are located on the desktop.

I’m glad you have it worked out.

To extend what you have done just a bit more (if needed). Look at my unattend.xml script there are sections where to add local keyboard support (if you are not in the US) as well as it should have autoadmin login with a login count number that will cancel the auto admin login after X number of logins. If not you can add it to your unattend.xml file. That in conjunction with the run firstlogincommands where you can install any applications in an unattended manner as the local admin. The last firstlogincommand should be shutdown -r -t 0 that will reboot the computer leaving it at the login window.

I just looked and my posted unattend.xml file in the link does not included this section. I must have removed that before posting. But above is enough info for you to google it.

Thank you @george1421 .
It was really perfect.

Since I have some issues with Sysprep, I changed my way. So let’s forget the previous story for imaging.

What is my scenario?
My clients (coffeeshop) every day login to the systems. I need to reimage machines every time they log out from systems. So that they can get fresh installed windows after turning machine on.

So what I did do for machines?
I installed windows 11 on my workstation which is Dell 3420 Precision Tower. Then, I installed a few apps like chrome, pdf reader, vlc. Finally, I put this script to the windows task scheduler in order to execute it right after the computer boot up or shut down. this script helps me to keep network boot as the first boot order (Since windows manipulate the first option to itself while it should be pxe because of the next boot). This script will run on every boot and every shutdown(just making sure pxe is first order).

What is my issue?
I simply captured the image without anything else llike sysprep. I deployed this image on the original machine which I installed windows 11 from scratch. Now Windows 11 can not boot up. First, it goes to a blue screen and it says “BAD CONFIG SYSTEM INFO”, and then it goes to the automatic recovery page and SrtTrail.txt says: “Check for installed LCU Error code: 0x3f1”

It seems fog can not capture windows 11 images correctly or can not restore the same image on the same machine.

If fog is fine, what is my mistake? :))