@Wayne-Workman Thank you for all your help.

@Wayne-Workman

Sorry for the delayed response, I have been busy at other locations. I think that moving to a freshly installed server is probably the best solution. I don’t have time to do it today, but it will be a separate machine (a better machine). What will be the best way to get those images and hosts transferred? I greatly appreciate the help. Also, be aware that due to the failed upgrading process, the web gui is no longer working.

I changed ip address of my server, removed /opt/fog/.fogsettings and reinstalled fog again. Now it works like a charm. May be, there was a compatibility issue between old fog settings and new fog version. Now, I don’t see any strange error like above.

Have you tried using sudo to copy using the second account?

Thanks. I’ll try that in the morning.

@Kleber Here’s a basic example that uses powershell with snapins - testing working on Win10. https://forums.fogproject.org/topic/8348/reset-local-windows-account-password-1-3-0

Yep, awesome that seemed to fix the issue.
just reset the encryption data for all hosts as it seemed to be happening on every client.

Thanks. 🙂

@kevinrigney
Did you change them in each of the folders to fog and root?

Mine had Me and root. I can’t upload an image.

@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 🙂