I clicked edit on his post because sometimes the triple tics when done wrong hide text, and he did post a line of code, I fixed it so we can see it now.

But it still makes no sense to me. It looks like he’s trying to use VB.NET.

BASH is easier.

Awesome, that answers my question. Thank you!

I took a look at the code and I don’t remember why I added that. The same likely happens for “routeraddress” and “plainaddress” as well.

I’ve republished RC-15 to have the code changes in effect to correct the installer issues in regards to these four fields. I also re-tagged the RC-15 as RC.2 is just a tag, it’s not the “version” applied to the installation.

@Wayne-Workman I’m not saying you all are.

I’m saying how I might approach the situation from a personal mindset.

Just confirmed and sharing - FOG 1.3.0 RC-11 also works just fine on Fresh Ubuntu 16 Server without any special commands.

I feel I should add all Enabled nodes will send wol. Non enabled won’t cause they’re not enabled lol.

If you have a spare machine laying around, I’d ask you to try FOG 1.3.0 RC, and see how it goes. Leave your old fog server alone for this.

Bad HDDs don’t act uniformly. Just because an error was thrown in Clonezilla doesn’t mean the same one will be thrown in FOG, and vice-versa. Of course people on the forums here have posted pictures of very strange errors in partclone before, and of course those were sometimes due to bad HDDs.

My recommendation is to not assume an old drive is good. If it’s older, do a health-check on the drive before you ever start building your image on it. This should prevent a lot of problems.

My fault - I was ssh’d into the wrong server… 😕

Tom has done his best to ensure all of it’s features work. But for instance, Directory cleaner on the legacy client ONLY worked on Windows XP. All the core functionality works - up to Windows 8.1. The legacy client is not supported on Win10 - can you blame it though? The legacy client was developed when XP was the latest - and it’s designed to do stuff to the OS, to the registry, etc. OSs Change. The new fog client should be good for many future versions of Windows, plus Joe is keeping on top of it also.

Sorry to pop this bubble… Due to communication issues, I thought PortFast was turned off for this case. I’ve found out that PortFast was in fact turned on.

@Wayne-Workman Thanks. Fog has become a critical piece server system for our engineering school’s loaner laptop program. We require students to have tablet PCs for the engineering program, and if for some reason their PC can be used, either because it is out for repair or other situations, we will loan them a system preloaded with the most used engineering applications.
When the system is returned, it gets immediately wiped and refreshed with a new copy using fog. Usually it takes less than 8min per system. Nothing works better. Also, Tom, all the developers and moderators have done an excellent job with the code, patches and suggestions. They deserve all of the praise.

@Joe-Schmitt Does this change only apply to scheduled shutdown tasks, or to all power management tasks including reboot? Just asking.

Ok, cool.

I can’t tell you what version I’m running at home. But I am able to use FF on Zorin (ubuntu based). That is my primary browser I use for the fog forums. I can confirm when I get home. As for right now I’m using FF 47.0 on my windows computer and it is fine.

@Lee-Rowlett I’ll be expanding on that article soon to cover image sharing. The video was meant to be an introduction.

Fedora 23, 24, and CentOS 7 articles updated to allow UDP ports 49152 through 65532.

I now remember this being corrected for in a later RC, this was the line 23 issue.

I’ve deleted that massive log, and updated.

ALSO - many folks here I’ve seen their root partition fill up recently - this is most certainly the culprit.

I also foresee more posts about it. We need them to just delete that big log and update.