@george1421 Thank you for your reply, an update caused the fog server to no longer be able to run the mysql service. It has been fixed! Thank the lord lol!

@pep said in Using a separate NIC for multicast:

web = http: //192.168.1.100/fog/ ftp = 192.168.1.100 storage = 192.168.1.100: / images / dev / storageip = 192.168.1.100

Thanks! That works. I can leave my storage settings as default and Multticast will use eno2, then for anything not multicast I can set the correct parameters for eno3.

Just a note that for deployment the storage variable needs to be ip.address:/images/ (without the dev/)

Hi, so I did change to version refind version 0.10.4 worked with my HP models, and capture new image, on only UEFI bios, and its working. @EduardoTSeoane made me think that I have only legacy compatible images so I tried to fix that. Thank you guys for help!

*UPDATE: It is not the FOG server as I was able to boot an OLDER (Legacy) Lenovo to the FOG Main menu screen. SO this appears to be an issue with the newer BIOS/Secure boot or even possibly a NIC incompatibility. I will search elsewhere.

@Tom-Elliott @Wayne-Workman In this case here the installer error was actually helpful to prevent from later issues with two IPs on an interface that were not intentionally configured.

I don’t think it’s worth the effort changing the scripts but feel free to go ahead.

@mesaman0182 From the picture we see that you are using a very old version of FOG. Is this a fresh install? Why did you choose to use that?

Now to answer your question: The one important field you need to set is Host Image. But as we see in the picture you don’t have an image defined yet. So go to the images in the FOG web UI and create one. All the other fields in the host settings can be left as default or empty for now.

@enrico-fazio This is a known issue with Ubuntu 21.04. You need to use the latest dev-branch version with that.

@jbandy
I ran into the same issue myself and did a bit of research. It appears it is a problem with the .Net Framework not using more secure SSL/TLS protocols, which can be enabled.

So, after enabling them, the very issue you have encountered above was fixed.
You have to add two registry key value in windows:

Using Powershell:

Set-ItemProperty -Path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Value '1' -Type DWord Set-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Value '1' -Type DWord

Or manually using regedit find:

HKey_Local_Machine\SOFTWARE\Wow6432Node\Microsoft\.NetFramework\v4.0.30319

Add a 32-bit DWord, called

SchUseStrongCrypto

Modify its value to 1.

Then repeat the same for:

HKey_Local_Machine\SOFTWARE\Microsoft\.NetFramework\v4.0.30319

After those values are set, you can restart the Fog service on the Windows machine, and it should work.

I hope this helps; apologies for the janky post, first time posting here. @Sebastian-Roth You may find this useful for your erratia and troubleshooting section regarding the client. It might also be possible to check and set these values via the client installer in the future.

@quazz said in Fog/dnsmasq and EFI booting:

SecureBoot must be disabled for EFI

i…

That was it. I feel like an idiot! thank you!

@sebastian-roth Checked on the storage node that was giving issues and it done fine i am going to just move everything to new master SN and test

fog@Fog-Main-Storage:/images$ cp Win1064Bit4-15-21/d1p2.img test_extract.img.gz fog@Fog-Main-Storage:/images$ file test_extract.img.gz test_extract.img.gz: gzip compressed data, last modified: Thu Apr 15 12:45:14 2021, from Unix, original size modulo 2^32 3448112244 gzip compressed data, reserved method, ASCII, has CRC, extra field, has comment, encrypted, from FAT filesystem (MS-DOS, OS/2, NT), original size modulo 2^32 3448112244 fog@Fog-Main-Storage:/images$ gunzip test_extract.img.gz

@sebastian-roth
Yes one of the storage nodes is the master
But i am working on changing that as we speak and creating a new master 64bit then the others will be changed to 64 bit also

as of right now i have
server 64 bit 16.04 xubuntu not storage node
1 Ubuntu 16.04 32bit storage node master
1 Ubuntu 16.04 32bit storage node
1 ubuntu 20.04 64 bit storage node

I am going to just use the 64bit as master after i get the images all copied over, then disable the other 2 32 bit nodes, upgrade them to 64 bit and re-enable them to see if that fixes some of the issues i am having since the 1.5.9 upgrade

@sebastian-roth I resolved this issue by changing the boot file to ipxe.efi on my DHCP server scope configuration. Thank you!

@nerdstburns said in Reset fog dashboard login password:

I have tried the 1.5.0 steps on this page

So what was the outcome if trying this? Were you able to login to the database? What happens when you send the SQL query? Please provide more details on what exactly you tried and what happened and we should be able to help.

@Tom-Elliott
Dude, I was able to integrate the LDAP with the fog, now I need to manage the access levels, how can I do with LDAP enabled? I thank your previous answers.

Looks like @John-L-Clark has a huge setup with many hosts. Talked in chat and figured that increasing the value of php_admin_value[memory_limit] in /etc/php/7.4/fpm/pool.d/www.conf fixed the issue.

Possibly moving to InnoDB could help here as well. Though this is not supported in an official release yet. Take a look at those topics:
https://forums.fogproject.org/topic/15162/the-list-all-hosts-tab-takes-a-long-time
https://forums.fogproject.org/topic/14254/high-cpu-usage
https://forums.fogproject.org/topic/14689/high-cpu-usage-on-fog-server/9

@sebastian-roth
All the laptops we have are HP Probook x360 435 G7 model,

thanks

@sebastian-roth Moving it to 12 did the trick! Is there anything else I should change or do? Thank you guys for the help!