@Sebastian-Roth I know this thread is a bit old, but my question is exactly this thread.

I am having the same issue as @jtappen. In my case, all of my hosts had the enforce checkbox selected on my prior FOG server. After I moved everything to a new server for some reason the checkboxes got unchecked.
I tested with a few computers by clicking the checkbox and it works perfectly fine. My problem is that I have over 200 hosts so I would like to “checking ALL the checkboxes” by updating the database.

Would anything break if I run UPDATE hosts SET hostEnforce='1'; to update all hosts in one blow?

@george1421 Ahh okay thank you!

@george1421 Thank you so much that helps a lot! I’ll have to modify a few things and test it out.

One question. What does the dots command do? I’ve tried to search what that command does in bash but I can’t find anything about it.

EDIT: Also does the file have to be a .rek filetype or can it just be a txt?

@george1421 I didn’t think of having a text file on the image itself, that is so simple to implement.
I’ll try both things out next week when I am back at the office.

Thank you so much!

Hello, I am trying to create a post download script to add drivers to my image.
I have read many forum posts about this and have created my script. Most of those posts reference the $osid variable that can be used in these scripts.

I have different drivers for different versions of Windows 10 (1909, 2004, 20H2, …) but I don’t see a way of figuring out what version I am imaging on a computer.
So, I am thinking I could add the version number in the image name and add the logic to the script.
That being said, is there a variable for the image name?
I know that the images table in the database has and imageName field, but is there a variable for it that can be used in the post download scripts?

Also, is there a link/file where I can see what other variables are available to the FOS at that moment?

Thanks for the help!

@Sebastian-Roth Thank you so much for telling me about the Reset Encryption Data, that worked!

If you could please let me know the way to do that for all the computers en mass, I would greatly appreciate it!

@Sebastian-Roth @george1421 Thank you for your reply. I did do that from the link provided before submitting my last reply.

This make me think that the issue I had with my old FOG server may have been a certificate issue.

Since I copied the ssl certificate from the old FOG server and this still doesn’t work, does this mean I just have to redeploy the fog client from the new server on all the computers?

If so, is there anything I must remove from the computer before doing that? (e.g. registry data)

Once again, thank you so much for all your help!

@george1421 Hello once again!
I just finished setting up my new FOG server following the links that you provided.

I am getting a RSA ERROR: Certificate validation failed on the computer I am using to test snapins. Also, the host’s status is unknown for all my computers. What would be the best way to fix this issue?
My thought was to write a script to reinstall the FOG client on the computers through a GPO but maybe there is something easier to fix this?

Once again thank you so much for all your help!

@george1421 Hello once again.
I have decided to just recreate my imaging server. I was able to get newer hardware so now is probably the best time.

Would you be able to guide me in the right direction (with links) on how to setup my new server with FOG correctly and move over hosts, groups, images, and snapins?

Thank you again for all your help!

@george1421 Hello again. Thank you for your help.
I tried both suggestions and sadly still no luck.

I decided to install FOG 1.5.5 using a clean Ubuntu install on another computer just to see what happens. When changing the DHCP to use the IP of the fresh install machine, the rEFInd Initializing... screen goes away after 3 seconds (how it should work). Since that worked, I used the refind.conf and refind.efi files and copied them to my FOG server running 1.5.8 and it still didn’t work.

Then, I installed FOG 1.5.8 to see if I get the same issue on the clean machine and I do. The rEFInd Initializing... screen doesn’t go away.

I then replaced all the files in /var/www/fog/service/ipxe/ to use the ones from the 1.5.5 install and it still didn’t work but I saw an error saying that it was looking for a refind_x64.efi file. I renamed the refind.efi to refind_x64.efi and it now works.

Since that worked, I did the exact same thing on my production FOG server (using the files from the clean install computer that did work) and I am still stuck on the same screen.

Other than reinstalling the OS and FOG on my server, what else could I try to check since I guess the issue isn’t the actual refind.efi or refind.conf files?

EDIT:
Could it have to do with some authentication issue?