@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!
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_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?
Could it have to do with some authentication issue?
I updated my FOG server from 1.5.4 to 1.5.8 a couple of weeks ago to be able to image some new laptops (HP Elitebook 850 G6) that were not imaging with the older version. After some google-ing all the answers pointed to the latest version supporting that laptop’s NVMe drive.
I installed version 1.5.8 and was able to image the laptops. However, now I have an even bigger problem. All my lab computers that have the newer version of HP’s BIOS (the one that you can use the mouse on) get stuck at a
rEFInd Initializing... screen. All those computers were working fine with FOG and rEFInd before upgrading to 1.5.8. The computers with the older BIOS type work fine. I am using UEFI for all my computers so my DHCP is setup to use ipxe.efi.
HP EliteDesk 800 G1 - Works
HP EliteDesk 800 G2 - Doesn’t Work
I have googled for a couple of weeks now trying different things but still no luck. I have tried everything from these links and more (I didn’t save all the links):
I have tried downloading the newest version of refind_x64.efi and changing the
Exit to Hard Drive Type(EFI) option in FOG’s
iPXE Menu Settings.
Maybe I just didn’t type the right combination of search terms and there is already a solution for this, if so, sorry for the duplicate.
Thanks in advance!
Updated from 1.5.4 to 1.5.8 now computers with newer BIOS getting stuck at
@george1421 So I am pretty sure it is fixed now. I looked at the logs for php and found this error
[20-Aug-2019 17:28:19] WARNING: [pool www] server reached pm.max_children setting (5), consider raising it
So I changed the pm.max_children setting to 150, just to be sure, and it is now working perfectly!
I re-imaged the same lab with 20 computers and monitored the server to see how many php-fpm services ran and I found that at one point I had 10 instances so bringing that up from 5 did help for sure.
@Sebastian-Roth I restarted the service and the server too just to be sure.