Topics created by nerdstburns

@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 thank you for the quickest reply on a forum I’ve ever seen lol. Disabling hibernation mode fixed the issue. I appreciate your help!

@nerdstburns Adjusting compression ratio with Zstd might help to speed it up.

@nerdstburns There is one important thing I have to add. If you select a single partition in the image definition it won’t touch the partition table on deploy/capture at all!! So I would advice you create two image defintions, one full image where the option Partitions is unselected and another one with Partitions set as suggested by George. Now capture the full image an deploy that to all your hosts once. Then when you want to update C:\ you capture that to the other image definition “Partition 1 only” and deploy that to the hosts again.

If you ever try to deploy the “Partition 1 only” to an empty disk (no or not the correct partition layout deployed before) then it will fail!

@nerdstburns Just want to add a question to what George already said. Are both your disks NVMe drives by any chance? Just asking because they are special and need different parameters.

Which version of FOG do you use?

@nerdstburns If the host is turned off and wake on LAN (WOL) works in your environment, then it will just be started automatically and do the image deployment. You can have it reboot after the task (default) or let it do a shutdown via adding shutdown=1 as Kernel parameter (general FOG settings or individual host settings).

When you use the FOG web UI to schedule a normal deployment task you see the selection:

Schedule instant (default selection) Schedule delayed (one shot at a certain time) Schedule cron-style (repeating task as often as you like it to happen, once a day or every other hour or whatever)

@nerdstburns Please take a picture of the error in screen and post that here. The notice on space is only a general message and does not necessarily apply in this case.

@nerdstburns Since the pxe booting computers are on a different subnet than the fog server, you will have to go the wireshark route.

Install wireshark on a 2nd computer on the gamers vlan. Setup a capture filter of port 67 or port 68 and then pxe boot a computer until you get the error.

The stop the wireshark capture. You should see a dhcp DISCOVER from the target computer and then one or more OFFERS from dhcp servers that heard the DISCOVER packet. Make sure you know these responding dhcp servers if you have more than one answer.

Look at the OFFER packet (in the center section) and expand it there should be an ethernet header section where you would have …

It may be just easier to post the pcap here or to a file share site and IM me the link. It would take me twice as long to type out what to look for than for me to just look at it.

@nerdstburns said in Updating Fog Server 1.x.x:

will I have problems updating to a stable version if I have 1.5.9RC2?

No you will not have issue the only thing you will need to do to switch back is this

git checkout master git pull cd bin ./installfog.sh

The current 1.5.9RC2 is very stable and there will (probably) be no (true) difference between 1.5.9RC2 and 1.5.9 GA other than the name change.

@nerdstburns said in Minimum Server Specs:

unicast images on up to 100-200 computers

Is there any good reason you don’t want to use multicast? That would take a huge load off the disk subsystem and network of your FOG server!

@george1421 so far it’s only 2 out of the 12 I’ve done. If I hit boot from hard disk it will go to the drive, but otherwise nothing happens. Tried it multiple times.