Ok this is resolved. I was able to unbox another new machine and build out the image and capture it from that machine. I then deployed the image to the other 11e that would not capture without error. Thanks All for the help

I would be glad to help with that.

I found it and increase to 512 and is working fine. Thanks

This has been resolved with latest revisions and some other work by Tom

@Arrowhead-IT
The “reset encryption data” button is not there

I uninstalled the fog client and reinstalled the new version. This is not just one host, this is all hosts

This has been resolved by Tom.

It was a php version issue he had me run
rm -rf /etc/apache* /etc/php*
apt-get purge ‘libphp’ ‘apache*’ ‘php*’

then reinstall and it worked perfectly.

@george1421 I was able to edit the Grub.cfg and add our Fog server IP in and then boot with USB and register and capture and deploy. Thank you again for all the help.

Figured it out. The old database was using the wrong bzImage file. Thank you again for all the help.

@george1421 Worked Great thank you sir. It was the Storage node password was incorrect.

@george1421 Thank you, That worked.

@Ced58 We had the same issue with the L`3W and now we have L13 Gen5 that are doing the same thing. Were you ever able to get this resoled? The L13W we had to roll back the bios to a known working bios. The new ones are still not working. Thanks

@JJ-Fullmer We are using FOG 1.5.9 I have tried turning on the Mac passthough. I have tried all of the .efi bootfiles i have. We did get a machine back from Lenovo where they rolled back the biois and that one machine is working fine

@Tom-Elliott !

This is what i get with each of them.

We have been using the ipxe.efi boot file and that one would not even get this far. So i changed to the intel.efi and got it to boot to this screen.

This is what i get to after changing the boot file. I have updated the kernel and still can not get past this. We have about 200 of these Yogas and when the bios gets updated we are no longer able to boot to fog. I have verified secure boot is disabled and the MAC pass through is disabled.

@george1421 When I mean it works, After replacing the mac in FOG after registration and boot to FOG again it then shows it is registered. If I don’t replace the mac it shows it is not registered.

@george1421 When I do a full host registration it has the mac address of the dongle. When it boots to windows it uses the system mac. I am able to edit the mac in the FOG gui and it works. We have 2 machines we are looking at right now but are looking at buying 150 more.

@george1421 I have pass through enabled. I tried to upload an image of the bios settings but it keeps giving errors.

We are able to boot to FOG and it shows that the host is not registered. The mac address at boot shows the System mac. When we try to register the host it gives the error that the host is already registered in fog. The mac address that it shows there is the mac address of the dongle. Why isn’t it using the mac address that it boots with?

@george1421 Ok I have found with the MAC passthrough in the Bios turned on we are not able to boot to FOG unless we were on the same subnet. With it turned off i was able to boot to FOG on other subnets. So this is not good for us as when you register the machine you have to keep the dongle with the device. Thank you all again for the help.