@jonathanho92 said in Help in deleting image in fog server:

When i try to click delete they prompt me for credential i am not sure which credentials to key in to delete the image

That’s the same credentials you use to login to the FOG web UI. It’s just a safety thing to prevent people from deleting image files in a rush.

@jbandy Edit C:\Program Files (x86)\FOG\settings.json on the client machine. Then restart the service called “FOGService” or the computer.

@tom-elliott
@Sebastian-Roth

Thank you all. It is solved now in 1.5.9.78 with HTTPS on.

/var/log/apache2/other_vhosts_access.log

80 "POST /fog/management/index.php?node=client&sub=wakeEmUp HTTP/1.1" 302 599 443 "GET //fog/management/index.php?node=client&sub=wakeEmUp HTTP/1.1" 200 9111 443 "POST /fog/management/index.php?node=client&sub=wakeEmUp HTTP/1.1" 200 9111

/opt/fog/log/fogscheduler.log for Power Management Task

[04-29-21 6:16:25 am] * 1 task found. [04-29-21 6:16:25 am] * 0 scheduled task(s) to run. [04-29-21 6:16:25 am] * 1 power management task(s) to run. [04-29-21 6:16:25 am] * Power Management Task run time: Thu, 29 Apr 2021 06:16:00 +0000 [04-29-21 6:16:25 am] * This is a cron style task that should run at: 1619676960. [04-29-21 6:16:25 am] * Found a wake on lan task that should run. [04-29-21 6:16:25 am] | Task sent to fcaa-https

/opt/fog/log/fogscheduler.log for Scheduled Task:

[04-29-21 6:22:26 am] * 1 task found. [04-29-21 6:22:26 am] * 1 scheduled task(s) to run. [04-29-21 6:22:26 am] * 0 power management task(s) to run. [04-29-21 6:22:26 am] * Scheduled Task run time: Thu, 29 Apr 2021 06:22:00 +0000 [04-29-21 6:22:26 am] * This is a cron style task that should run at: 1619677320 [04-29-21 6:22:26 am] * Found a scheduled task that should run. [04-29-21 6:22:26 am] - Is a host based task. [04-29-21 6:22:26 am] - Unicaset task found! [04-29-21 6:22:26 am] - Host fcaa-https [04-29-21 6:22:26 am] - Task started for host fcaa-https!

Thank you again! Now our school can wake-up on Schedule 😉

Peter

@tom-elliott So to clarify that last point Tom, the SQL should reflect under ngName both the Storage group name AND the Storage node name? DCSTORAGE in this case is the name of the Storage node master server for the Storage Group 3 storage group.

I’ve compared to the other image(s) which are only hosted on (and are being replicated from) the Master node and they only reflect the main storage group under ngName.

I’ve made note of the replicator service restart command, cheers. I went a bit neanderthal and just rebooted all my servers just now to see if that kicked things into life.

Checking the Image Replicator logs under FOG Configuration > Log Viewer it only references DCMASTER and the 2 nodes in its storage group. Does replication from the Storage master of the other storage group show in these logs? Or do we need to check local log files on the server itself?

cheers Tom

@sebastian-roth In the back of my mind I was knowing that its something at a lower layer … I am the only admin on this network so I dont know how it self destructed from 1 day to the next, might consider a windows update, but moving dhcp off windows would rule that out. Will try a pcap.

@stephane The directory listing and settings look fine. No idea why it shows “No such file or directory”. What kind of DHCP server do you use? Settings?

Can you please capture a packet dump and upload a PCAP to a fileshare and post link here? https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

@sebastian-roth

It was just a hiccup. Running the installer again without git pull there weren’t any errors.

foginstall.log

Update!

So I upgraded to Ubuntu 18.04 which did not resolve the issue. I then updated FOG to 1.5.9.71 which must have been release today 🙂 . After completing the FOG update, the services are running and I was able to successfully deploy 2 machines using multicast. I rebooted the server and verified that the services started after a reboot. Thanks for your help and working on this awesome software!

@robertkwild “better” is a relative term. I suggest following the command because we know it will do what it needs to do properly.

@d2freak82 said in Error on first PXE boot:

later popped an error that the drive was unclean on 2 different laptops

This is expected if you did not shutdown the computer properly before image capture. The shutdown command from the start menu is not sufficient.

You have the following options to properly power off the computer for image capture.

Run the following command from a command prompt shutdown -s -t 0 Use sysprep to power off the computer using the proper command line switch. Turn off fast startup in windows.

The kernel version I’m referencing is for FOS Linux (what get downloaded to the target computer), not the host OS kernel version. You can see the kernel version using the web ui FOG Configuration->Kernel update.

i have resolved this issue. I am not sure but when i was looking into ubuntu it did not update the images correctly. I moved them again and this time it was working correctly

i used FTP software , filezilla , to see the files where not on the ubuntu server but the gui was saying it was there .

@mmoore5553 Good to hear you were able to make it work. Just a few comments on what you said:

I ran the setup again in the vm and finally go the error setting up and starting dhcp server - no router address found - no dns address found.

The router and DNS addresses are only used by the FOG installer to set those in the DHCP configuration to be sent to clients requesting IP (and router/DNS information) from the DHCP server.

if i want a VM to connect I have to change my VM to Nat and not bridged.

Hmm, I would think you can set all VMs to bridged and should be able to PXE boot VMs and physical machines then.

@mmoore5553 said in drive not expanding fog 1.5.9:

@scott-b yes it is . Windows 20h2 . I finally got it resolved by the moderator. I had to go into my image and delete the recovery drive. Then it acted correctly.

Just wanted to put that out there if someone else had the same issue

Thank you for letting me know. I’m having the same issue so I’ll give that a shot.

@jonathanho92 Upgrade your FOS kernel version to 5.6.X or later. I would go to 5.10.12 or later to get the latest hardware support.

@george1421 Hello !
Thanks you so mush ! It worked ! 🤗 🤗

Have a good day,
Pinki

@thor_egil Just to add to what George said, find information on this in the docs: https://docs.fogproject.org/en/latest/reference/change_fog_server_ip_address.html

@robertkwild said in is it ok to make new dir in /images:

OK to create /images/backup

Yes it is OK. FOG don’t care or will ever see it.

@robertkwild Yes, it’s perfectly safe for you to manually deleted the image directory/files. You are the administrator.

@sebastian-roth

Update…
It appears updating the init.xy file AND adjusting the KERNEL RAMDISK SIZE setting was the key to get it working. Only have tested with 1 of the images created on the new 1.5.9 server, deploying on the 1.5.5 server. Looks like we can limp along doing this until we can get the other sites updated, which is in motion now.

I owe you guys a beer! Thank you again!

@robertkwild said in syspreping a vanilla windows golden image:

i found this, you can sysprep win10 up to 1001 times

Just to be a bit snarky, if you have to sysprep your image 1000 times, I think you might be doing something wrong or IT should not be your field of work.

But on the less snarky side its good to know the number and hopefully I’ll never personally need it. As I said we use MDT to build the golden image so I get a fresh from DVD image (with current windows updates) each time the golden image is recreated.