@kevinnew22 said in Error trying to restore GPT partition tables (restorePartition TablesAndBootLoaders):

understood, the release of the new version will be when more or less? I can help with something?

Can’t give you a date as we don’t have a fixed plan for new releases. Not great but that’s the way it is right now. Hardly anyone has time to work much on FOG and so things are going very slowly. You are more than welcome to join in an help us push this forward. See my post in the forums. Please send me a private message if you are keen to get involved and I am sure we have something for you! Looking forward to hear from you.

@lucycle Take a look at the first couple of lines of this script: https://github.com/FOGProject/fogproject/blob/master/utils/FOGiPXE/buildipxe.sh

@pevecg said in Fog Deploy stuck on "rebooting system as task is complete":

The interesting part is that when setting this setting, we had to once fully power cycle the PC before the setting was applied/started to work.

I’m not sure I understand. I get the idea that this setting “ahci=off reboot=warm” is causing problems after the system is imaged?? If that is what you say its not possible. These are instructions to the FOS Linux kernel. Once the kernel reboots and/or the computer is repowered there is no way those settings would still impact the computer.

@pamadmax Which version of the fog-client do you use?

Try using this installer to hopefully fix the issue: https://github.com/FOGProject/fog-client/releases/download/0.12.0/FOGService_fixed-tls.msi

This has been discussed in the forums before…

@richard-wise Do you use the FOG server to manage the target computers post deployment or do you just load and go with imaging?

@rhodesj2314

Thank you. I figured it out and added the tftp server to the dhcpd.conf file on mu Ubuntu server.

@amher17 Yes and no but maybe.

What you need to do is place the files from the iso image on a windows network share. Then share that directory out to your network.

Next you need to make a bootable WinPE disk that connects to the network share then launched the windows setup.

You can deploy that WinPE image using fog or a usb drive for that matter.

Now reading your post I see a disagreement when your statements. Is your goal here to deploy an iso image or capture it with FOG?

What is the purpose for what you are trying to do? Explaining that might give you a better answer.

@yeet TBH I would not use fog for this. There are better/cheaper solutions out there, specifically Veeam Backup Agent (free). You can have it take nightly backups to where you can do a bare metal restore if the system fails. You can setup a retention period for each backup (i.e. 14 days before rewriting the oldest backup).

The target of your veeam backup can be a nas, san, another CIFS based computer, or a Veeam B&R server. I use the Veeam backup agent at home for my windows and linux computers backing up to a Synology NAS. Works perfect.

@sebastian-roth The error with chkconfig is still here and I dnd’t found any topic about it in the forum, is any alternativ possible to this package ?

So it seems the list “_configuredPrinters” contains the printer that I want to install.
Is it the host’s printers list configured through the fog server web ?
And the “installedPrinters” list will be the printers already installed on the host ?

@mrp When we struggled with this I didn’t think as far as only using identifiers for deployment. I will see what I can do when I get back from my holiday in a couple of days.

@EduardoTSeoane Please test on dev-branch as well and let us know.

@louvet-christophe Can you please take a picture of the error on screen and post that here in the forums?

https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_NFS
Creating & verifying .mntcheck files
.mntcheck is a hidden and empty file that a FOG client uses during image capture and image download/deployment to verify an NFS share is mounted correctly.

To create these files, on the FOG server:

touch /images/.mntcheck
touch /images/dev/.mntcheck
Verify these files with:

ls -laR /images | grep .mntcheck

I forgot to isntall the client it’s working now sorry !

@turtle331 I would like to get a solution for the installer error

@george1421 When I renamed refind.efi to refind_x64.efi, it worked as intended. Thank you for your help, I really appreciate it.

@sebastian-roth

This is how I install it manually. I browse to it and right click and click connect. I will uninstall it on my computer and try it your way. Thanks

@sebastian-roth
I tried this solution with Windows 21H1 the image capture and deploy works without any problems from a 1 TB NVMe SSD to the 500 GB SATA SSD.

d1.minimum.partitions

cat d1.minimum.partitions label: gpt label-id: 32D055B8-40FD-4110-9551-5794A08735E8 device: /dev/nvme0n1 unit: sectors first-lba: 34 last-lba: 2000409230 sector-size: 512 /dev/nvme0n1p1 : start= 2048, size= 204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=28F8CABB-959B-4C15-986E-0F8640E4F0C7, name="EFI system partition", attrs="GUID:63" /dev/nvme0n1p2 : start= 206848, size= 32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=ED9F8F39-E265-428D-8BE1-C2B7E4304D52, name="Microsoft reserved partition", attrs="GUID:63" /dev/nvme0n1p3 : start= 239616, size= 291316922, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=05966690-06CD-4A69-BF88-376CC3EBFAC0, name="Basic data partition" /dev/nvme0n1p4 : start= 291556864, size= 5639168, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=49569B35-41CE-42F5-82CB-6F68BA36C239, attrs="RequiredPartition GUID:63"

d1.partitions

cat d1.partitions label: gpt label-id: 32D055B8-40FD-4110-9551-5794A08735E8 device: /dev/nvme0n1 unit: sectors first-lba: 34 last-lba: 2000409230 sector-size: 512 /dev/nvme0n1p1 : start= 2048, size= 204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=28F8CABB-959B-4C15-986E-0F8640E4F0C7, name="EFI system partition", attrs="GUID:63" /dev/nvme0n1p2 : start= 206848, size= 32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=ED9F8F39-E265-428D-8BE1-C2B7E4304D52, name="Microsoft reserved partition", attrs="GUID:63" /dev/nvme0n1p3 : start= 239616, size= 1994530304, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=05966690-06CD-4A69-BF88-376CC3EBFAC0, name="Basic data partition" /dev/nvme0n1p4 : start= 1994769920, size= 5639168, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=49569B35-41CE-42F5-82CB-6F68BA36C239, attrs="RequiredPartition GUID:63"