@george1421 That is because the separate storage group has a master. It’s a “work around” to the “Images are always captured to the master node” because you, quite literally, are making the storage node, now, a master node. It works of course for this reason.

@madeyem said in FOG and UEFI/M.2 SSD:

Is it really necessary for you to have the PC run in raid on mode? If not, leave it at AHCI

If you have only a single disk in the computer OR you have multiple disks but have no plans on setting up a raid configuration there is no performance penalty to leave the disk controller in ahci mode.

@Brad-Schumann The short answer is it depends on what the laptop is doing. The bit longer answer is the config file for refind is in /var/www/html/service/ipxe and its called refind.conf.

Also make sure the firmware is up to date on this laptop because it could be flaky firmware that is causing refind to fail.

The last option is we may need to look into updating refind to a later version because the hardware drivers in refind may need updating.

So in the end it depends…

@Quazz Thanks, done: https://github.com/FOGProject/fos/issues/31

@martial said in button "Reset encryption Data" does not appear:

I guess the virtual mac address made by forticlient is the big problem as it is created on multiple clients?

Yes, most probably. Take a look at the option QUICKREG PENDING MAC FILTER in FOG Configuration -> FOG Settings -> FOG Client - Host Register!

@Sebastian-Roth No, i have changed the permissions to fogproject:root and delete the directories in /images/dev/ that looks like a MAC address.

It works now.

@Wayne-Workman said in Installation stops during setting up fogproject password:

own projects, I opt for very long passwords made from upper & lower case letters and numbers randomly. I’m talking 32, or 64 characters long. Typically I look up the maximum length supported password, and generate one of that length, just letters and numbers.

I tried another installation on an other, identical notebook fujitsu lifebook with fedora server 30, but allowed special characters in the function.sh and it works also.

do [[ -z $password || $ret -ne 999 ]] && password=$(head /dev/urandom | '0-9a-zA-Z!#$%&()*+,-./:;<=>?@[]^_{|}~' | fold -w12 | shuf -n1) echo -e "$password\n$password" | passwd $username >>$workingdir/error_logs/fog_error_${version}.log 2>&1 ret=$? let cnt+=1 done

@george1421 Thank you once again for great support!!!

Since the apache crashes did not correlate with the no directory or file errors I double checked everything attached to our workbench and…

Found out one of my engineers had a test box attached to our workbench that was set for no reply to ICMP so I did not catch it had been static’d to 10.0.0.250 as well. Flipped it over to DHCP and now PXE boot works consistently.

Sorry and thank you for your time!

Some options.

1º Use a snapin pack including the executable.
2º Put it in a ftp server and use a cmd ftp client to download it. (You can use the fog server/node as ftp and the built-in ftp client)

This two solutions works!!!

@Peter365 The only comment I can make is watch the permissions on the /images directory now. If you run into upload issues issue this command (note is a bit loose with the security, but its not too big of a risk) chmod -R 777 /images

@Wayne-Workman a bit late in the day but have just setup Fog Imaging server. Could get Realtek Nics to work. Your post solved the issue.

I have been paying with this for a bit now and was working through a scenario where the OS doesn’t get an IP so trying to statically assign one, at least temporarily. I wasn’t able to get it to work but I think it just needs a little more time to work on this scenario. Otherwise, this works quite well. I did some minor tweaks so that my end user only had to boot to the USB drive and after the cron job runs keep an eye on the screen for the IP of the FOG server which I echo’ed out at the end of the script using: printf “The IP of the FOG server is: $IP \N” > /dev/console

I sent it off to a co-worker in another location and asked them to just plug in the USB drive, boot to it, wait for the message then try another machine to see if he got the FOG menu. He did and was able to register the machine with FOG and pull an image down so I’m marking this:

SOLVED!!!

I may try to go back when I have some time to finish hashing through the statically assign an IP if you don’t get one scenario…

Current Solution set Kernel to 4.19.64 and set global option in Fog Configuration–> FOG Settings --> General Settings --> Kernel ARGS to tsc=unstable

Luckly this is the last year for these machines.

@oliver just so you know the linux user fog or fogproject should never be used for system administration. These accounts are owned by the fog program and will reset their passwords each time you install FOG.

We are glad you have it working now.

@Brad-Schumann From what you wrote so far I am fairly sure this is a different issue than we had before. Please open a new topic and post more details on when this is exactly happening. When there is a task scheduled or if you try to register the host or what?

@darkxeno In the dell firmware switch the disk controller from Raid-on to AHCI mode. Unless you have more than one disk connected in a raid configuration raid-on mode doesn’t help you. There is a document issues between linux and intel controllers in raid-on mode. Once you have imaged with fog you can switch back to raid-on mode or leave it in ahci mode. It doesn’t matter to windows.

@Celena said in I have a problems! I need your help:

he computer reboots before Windows has a chance to set up completely.

This is probably because you didn’t follow the guidance on the wiki about disabling the fog service on your reference image and then enabling it in your setupcomplete.cmd batch file.
https://wiki.fogproject.org/wiki/index.php/FOG_Client#FOG_Client_with_Sysprep (but that’s just a guess)

George,

I have another question, this time about sysprep. Why do we need to go through OOBE for an installation that is all in the same locale? Wouldn’t it be easier to just generalize and be done? And if doing that, do I still need to disable the Fog Client Service before doing it?

Thank you,
Dave

What device is your dhcp server. I’m going to guess it is a soho (home) router? The reason I think this is your gateway is 192.168.0.1 and your next server (from the picture) is also 192.168.0.1. Home (soho) routers will often say they are the pxe boot server and not the fog server.