As we have had so many requests about this topic I have tried to sort this out and properly fix it. Turned out to be quite hard but I hope I got it now without causing any other harm.

@Tom-Elliott Can you please take a look at this commit and let me know if something jumps at you that could cause us trouble. I mean I have tested things a bit but as I had to change code right in the FOGController class I am unsure about side effects this might cause. What do you think?

@vmesuria FOG does something I call “early host rename” - which happens just after a host is being imaged by adjusting registry keys in the Windows partition. I am not exactly sure how well this works in Windows 10 but it certainly worked for Win 7!

If you want to go beyond this and also join the hosts to your domain you need to use the fog-client software… It does the hostname change after the host was imaged and booted to the installed OS. As well it can to the domain join for you.

@george1421 Yes, the setting is there but can you PXE boot (to ipxe.efi)??

@George Upgrading from 8 to 10 is quite a step. Probably something we have not tested. Please take a look at the settings file in /opt/fog/.fogsettings - find the line starting with packages=... and remove that from the file (good idea to make a backup copy of the file before you do this). Then re-run the installer.

@george1421 said in image deploy works to virtual machines but not on working on actual machines:

I don’t think you can create a uefi based VM in virtual box,

I am not exactly sure about this but I think you can create UEFI based VM and install an OS from an ISO just fine. But the issue is that you cannot properly PXE boot that UEFI based VM to capture the image. Search our forums and the web to see if this is still the case even in the latest version of VirtualBox.

@TBuzaTechnician The default is to not make FOG the DHCP…

@loutrage said in IPXE Boot Problem - No such file or directory after installation of SSL:

We tried a lot of things and we have always the same problem.

This is not going to help any. Give us more details on what exactly you have tried and what happened. Otherwise we can’t help you properly.

Is there a way to see if our CA is correctly import in the binaries

Yes there is but it’s a bit of work:

cd /path/to/fogproject
mv src/ipxe/src/ipxescript src/ipxe/src/ipxescript.orig
mv src/ipxe/src-efi/ipxescript src/ipxe/src-efi/ipxescript.orig
echo -e '#!ipxe\nshell' > src/ipxe/src/ipxescript
echo -e '#!ipxe\nshell' > src/ipxe/src-efi/ipxescript
cd utils/FOGiPXE/
./buildipxe.sh
cd ../..
sudo cp packages/tftp/*.* /tftboot

Now when you boot a client it won’t go to the menu but drop to the iPXE shell.

iPXE> certstat
...

This should give you the certificate it has embedded in it’s store within the binary.

@TBuzaTechnician By the way, we use this so called auto answer mode of the installer too. Thanks to @Wayne-Workman we have an automated installer test running: http://fogtesting.theworkmans.us/

@TBuzaTechnician Have you tried running the installer like this yet? ./installfog.sh -y

This will just run through using all settings as default. If you need to modify specific settings there are command line switches for a lot of things and we could even add more if there is need to. Just run ./installfog.sh --help to show the command line switches. Be aware, there is an issue with the long form command line switches like --ssl-path ... - they simply don’t work but the short form -c ... should do.

@davidka said in image deploy works to virtual machines but not on working on actual machines:

I can boot and start the restore process from a networked computer, and it looks good, starts the restore process, goes through the motions, reboots, and then just keeps rebooting.

What exactly do you see on screen when it “just does the reboot”. Without detailed information we can’t really help.

I used a Linux mint USB stick to check the partitions and it shows the boot and windows partitions. Shouldn’t there be 4 partitions?

Have you checked the partitions on your master VM yet? Is this a legacy BIOS or UEFI install? You can’t deploy a legacy BIOS image to a UEFI machine or vice versa - well you can deploy it but it won’t boot properly.