@lucjayjay said in FOG does not copy NVRAM/EFI Bootorder:

First is ipxe.efi that points to fog and the other being the windows bootloader. Btw do u see any problem with this approach instead of configuring every machine to network boot ?

Good point! I have to admit that I have not tested this myself yet and I don’t know anyone who has. Possibly there are some advanced users here in the forums who have done this?! Most people just use standard UEFI PXE boot I think. The FOG iPXE menu chainloads your machines back to disk by default in case there is no task scheduled for it.

Maybe im overseeing something but I think recreating the NVRAM from the efi-nvram.dat file would be much easier especially when ur cloning to machines of the same type.

This sounds like a straight forward solution. Though I am not sure is it might cause a lot of trouble if you deploy to a (slightly) different machine. We need testing and it’s really great you are pushing this forward!!

Leading to my next question, is there any way to run custom scripts when cloning (to create a nvram copy) ? And how do I distinguish which Image is being deployed to my machine in the post deploy script ?

You should be able to use the so called post init scripts for now. We will work on adding this to the official scripts as soon as we have a nice solution.

@Duncan What kind of network card is in your machine? Please check out Windows device management for the PCI device IDs.

@ziolucione While you are on the CLI please run the following commands, take pictures (!) and post her:

lspci -nn
dmesg | grep -i -e eth -e wifi -e 80211

@vic60400 There might be a way to remove the old CA cert and deploy new one via remote powershell commands. I have never done this and can’t promise this will work. Play with it and let us know what you get.

You’ll find two FOG related certs in the Windows cert store. You don’t need to worry about the one called FOG Project. This is for verifying the signature of the fog-client software components (needed as we provide auto update in SYSTEM context). The one called FOG Server CA you need to swap out.

@sgoodman I have not tested PHP 7.4 yet. Which Linxu OS do you use and what repo do you pull the packages from?

@amc123 Not exactly sure which version of FOG you run. The init version and ramdisk_size make me think this should be 1.5.7 but Username: fog tells me it’s 1.5.6 or older. If you really use FOG 1.5.7 then something went wrong and you need to manually set the username (web UI -> Storage node settings -> Management Username) to fogproject. This was changed from version 1.5.6 to 1.5.7…

Usually not something you should have to mess around yourself. The installer should take care of this. But seems like it didn’t or someone messed with it.

@thennessey What size is the destination disk? From the partition table it needs to be at least 17.64 GB and I am fairly sure it’s big enough, right?

Last time we had this kind of issue it turned out to be caused by converting the partition table using mbr2gpt. Did you use that by any chance? I ended up modifying the users d1.mbr using a hex editor to fix that and make it deploy properly. But we never found a proper solution that would make a fresh captured d1.mbr work.

https://forums.fogproject.org/topic/13220/error-trying-to-restore-gpt-partition-deploying-an-image-to-smaller-disk

@thennessey Ok, little different than what I had expected. Can you please post the contents of the text file /images/Win10UEFITest/d1.fixed_size_partitions too?

@Greg-Plamondon said in snapin hash does not match on storage node (1.5.7.55):

After doing some more investigating I found that the file sizes are indeed not the same. I was getting the information 2nd hand. I checked the "C:\Program Files(x86)\FOG\tmp folder for the snapin and it is only 1kb in size.

Please see if you can open that file (e.g. using Notepad++ or some other good editor) to see what the file looks like. Possibly this might give us a clue what’s going on here.

@jeremyvdv In the pictures you posted we see that Image Path is set to /volume1/images2 while FTP Path is set to /images. Change FTP Path to the same you have in Image Path and the error should go away.