I implemented the fix in my setup. It works HOWEVER just copying refind.conf and renaming it WILL NOT WORK!
rEFInd seems to hardcoded look for refind.conf and WILL NOT ACCEPT a file named differently. I worked around this by naming both files refind.conf and putting them in different folders.

Thanks again for your help!

Thanks to @Tywyn who provided the initial password I was able to figure out why this happened. The installer uses the password to update the storage node setting in a way that is prone to a URL encoding issue. I have to admit I didn’t know base64 encoding can actually produce strings that can cause such a problem:

$ echo -n 'as~ja$j2niau83j2' | base64 YXN+amEkajJuaWF1ODNqMg==

The + character is then miss-interpreted by the PHP code as space character and therefore breaking the base64 decoding of that string.

I just pushed a fix to dev-branch in hope if this fixing all cases that special characters could cause in that part of the code.

@george1421

Thank you, perfect followup…
worked well as well L13 Yoga success.

Thanks to all.

@joanmarzo Only a real FOG Server can run the fog replicator service. Marking the nas as a master node allows it to capture and deploy images. If you want image replications to other servers you will need to setup something outside FOG to move the images. Remember I said this configuration is NOT supported by FOG but can kind of work.

@phm2000 said in Error trying to restore GPT partition tables:

I have same problem with fog 1.5.7, is there a solution ?

Sorry but with this kind of problem there is no general solution that works for everyone. Please open your own topic in the forums and post all your own details: full contents of the file d1.partitions, d1.minimum.partitions and d1.fixed_size_partitions.

@JYost said in Remotely imaging a laptop using FOG:

Now that I’m looking at it I see exactly what you mean about going in and pre-creating the HOST.

This is referred to as manually registering the host. The only bit of information that may be problematic is the target computer’s MAC address. If you have the mac address then you an just go into the web ui and add a new host and enter its name, image, mac address via the web ui. You won’t get the full inventory right away, but there will be enough information to pxe boot the target computer. If the fog client is already running on the target computer, when you create a deploy task the target computer will reboot, or power on if WOL is enabled on the target computer. But to do this, the target computer needs to be configured to boot through PXE to the FOG menu every time. If there is nothing to do the target computer will continue on booting from the local hard drive.

ALSO, if the fog client is installed on the target computer BUT the target computer is not registered in FOG the target computer will be added to the FOG server in the pending state. You will need to approve the target computer to have it added to the inventory. You will still need to set the image name but you should have a near hands off registration.

@Sebastian-Roth

fogadmin@fogimaging:~$ ls -al /var/www && ls -al /var/www/html total 16 drwxr-xr-x 4 root root 4096 Feb 13 10:53 . drwxr-xr-x 14 root root 4096 Sep 11 2017 .. drwxr-xr-x 10 www-data www-data 4096 Feb 13 11:04 fog drwxr-xr-x 2 root root 4096 Sep 11 2017 html total 20 drwxr-xr-x 2 root root 4096 Sep 11 2017 . drwxr-xr-x 4 root root 4096 Feb 13 10:53 .. lrwxrwxrwx 1 root root 13 Sep 11 2017 fog -> /var/www/fog/ -rw-r--r-- 1 root root 10701 Sep 11 2017 index.html

Yes text alternatif

@george1421 , obrigado! Agora entendo como o fog funciona!

@george1421

Looked through the guide and everything matched, it was just the tftp server password that was wrong.

@george1421 I received my fixed IP from the sysadmin and I redid the installation. Everything is working perfectly now. I really thought the error was coming from mysql

I really appreciate the help you have given me. Thanks!

@george1421

From the chat session as well as the pcap here is what we found. The bootp information in the dhcp offer packet is set correctly but the dhcp options values were incorrectly set. The OP is using a route to supply the dhcp and pxe boot information for his network. The red outlined text is the problem with the dhcp offer packet.

pxe_boot.png

@Pikmin Understand it only needs to be in ahci mode for imaging, once the image is laid down just switch it back to raid-on mode before the first boot of windows. Or if you are not using any raid function, just leave it in ahci mode. There isn’t much of a performance penalty for leaving it in ahci mode.

@Sckendall With pfsense make sure both the bios and uefi fields are filled out to support dynamic booting between bios and uefi clients. Then pfsense will work fine for network booting.

@Sckendall Yes start a new topic, they are free and keep problems and solutions together with the subject of the thread.

@Sebastian-Roth , @george1421

Thanx for your help.
I set up a new virtual host with ubuntu 18.04.03 LTS server with fog and dnsmasq and everything went fine for the installation part now.
The ubuntu 18.04.03 provides apparmor by default, so I assume, that apparmor was not the reason for the install-issues I had before.
Maybe the fact, that I have had mysql installed manually, tried installation of fog and removed mysql after noticing, that fog wants to install mariadb, gave us the troubles we had.

Now another problem arose, but I opened another thread for that: https://forums.fogproject.org/topic/14197/1-5-7-does-not-capture-correctly

@Sebastian-Roth - I will try these things when I get into the office on Monday morning. I believe that I have the 1903 image that was working prior to this last batch of windows/software updates that I can get the data from.

@Fog_Newb Send me your email address in a direct message (it’s the talk bubble in the top right), and I’ll get a wiki user created for you.

@dclark I ended up just redoing my image for my Latitude 3500s with a clean install of latest W10 from USB. I gave up trying to fix the partitions/issue.

No issue with new image and deployed a bunch so far (single disk resizable)