@Wayne-Workman Thanks Wayne! I appreciate the help and patience! You’re the man!

@Joe-Gill
I currently update from an external source and have no experience yet how it affects the Sophos console.

k got it working @Wayne-Workman sorry about the confusion, i didn’t pull correctly
thanks

@noelpd If you are using the FOG Client, please follow documentation in the FOG Wiki:
https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep

This issue only appears to happen on windows 10 installations. It would seem the legacy client uninstaller is not fully compatible (of sorts) with windows 10.

@Wayne-Workman I think what he is saying is basically, the timeout default was timing out faster than the display could keep up with. So by the time the OP started seeing anything, it was already loading into Windows rather than giving a menu they could work with.

By upping the timeout value, it gave the system enough time to display the menu and allow the OP to perform the necessary actions.

Of course, if I’m wrong please let me know.

@MarkP said in What should I expect speed wise from multicast?:

If I remember correctly Unicast decompression is done on the client and Multicast decompression is done on the server.
We run all our images uncompressed for multicast purposes.

If you’re setting your compression down to 1, that’s probably your problem. Leave compression at the default, 6. You’ll need to re-upload after you change this value.

@jamesb Well, if you have ruled out the patch cable, gunk in the chips, RAM, and know that all the other exact-same models work fine, you’re left with just the problematic computer. It could be a bad power supply, giving out too much or too little voltage, or unsteady voltage. Or it could be a bad motherboard.

You could try to update the firmware on the motherboard to see if it helps.

@Joe-Schmitt said in Hostname is correct:

Just try disabling it, and re-imaging.

Works !

You probably made a bad situation worse when you upgraded to a newer OS. I have no idea what is wrong, I’m just going to give you some commands to run and give us the output. This is just a starting point.

df -h
service apache2 status
service mysql status
mysql -u root fog

@Gary-Kulovics said in Amount Fog can image:

Any answer on how to change at the main fog menu boot to hard drive from 5 seconds to a different time

Web Interface -> FOG Configuration -> iPXE Boot Menu -> Menu timeout

And, You never responded to me from your Multicast problem thread:
https://forums.fogproject.org/topic/8106/multicast

I can confirm that updating to fog 1.3 helped 🙂

@Wayne-Workman sure! Thanks for your help!

@Wayne-Workman said in Which table to check in db to see if there are pending wakeup entrys:

quote

How is the payment and which country is it? I have attachment with me 😄

@Stilty Re-downloaded cleanly??

@Wayne-Workman

Ah, so that’s what you were basing that question on. I was really just very confused about why you were on about disk space, now that makes sense.

@Tom-Elliott

Interesting. I am fairly sure it was working before the latest git pull, so I’m not sure where the init image I’m looking at came from. I will update the init image, but I do wonder now what else might not have taken since the update. Perhaps it is time to rebuild that server.

Thank you all for your help.

Thanks, Wayne!

@Tom-Elliott Thanks! this did the trick. WOL to groups is now working, but the apache log is spitting out this error now.

[Thu Aug 11 07:17:07.370532 2016] [:error] [pid 32376] [client 10.100.150.44:64341] PHP Warning: array_count_values(): Can only count STRING and INTEGER values! in /var/www/html/fog/lib/fog/fogmanagercontroller.class.php on line 111, referer: http://fog/fog/management/index.php?node=group&sub=edit&id=1532

Fairly sure this is fixed now. I don’t know why the hashes were all sorts of strange, but I believe this was partially related to the timeout as seen https://forums.fogproject.org/topic/8278/rc6-snapins-no-longer-working/13.

With any luck, this was all it was, and I’m just going to guess what was seen from the start was from a download that timed timed out, while the hashing mechanism was able to run much faster and return within its own allotted time.