I’m fairly sure this is fixed. Could use confirmation though, but i’ve not been seeing an issue for quite some time.

@Tom-Elliott Just HDD exit types need a wiki article in and of themselves. Right now, I have the exit types for all my equipment only in my head… If I slip and hit my head on the sink, it’s all gone!

This should be fixed. I know it’s been a while in the making, but hey, trying to catch up on bugs and report their solved states more accurately.

Sorry for not responding earlier, Yes this is solved. Thanks again for all the hard work @Developers and everyone else.

Pushed schema update to fix the text for this.

@Tom-Elliott I installed in storage node mode at home last week and it worked - but I had to manually get the ftp credentials from the storage node’s .fogsettings file and then plug those into the main server.

I don’t remember exactly what but I had to do some messing around to get replication to start - but I think it was minor and my fault concerning that. I haven’t tried it any more recently than mid-last week I think.

I learned what the issue is and have fixed it. While you may have to remove the erroneous entries in the fogsettings file, this should now be fixed and no more of the expression errors.

I’ve updated the code that handles the duration information and this should now be displayed in simple text format.

@Wayne-Workman Added, as well as to many other fields.

Was just updating, not a new install. No idea why, no idea if it’s still happening, I rolled my snapshot back and haven’t tried again.

@Tom-Elliott It is enabled, yes. We don’t do hardware independent images (ugh), so we haven’t run into any issues where the client interrupts sysprep. After talking to @Jbob a bit, I have a better understanding of what’s happening and a workaround to correct it.

I’m informed that upload/capture task types are not counted in the queue by default due to their minimal bandwidth requirements.

Found, confirmed, and fixed.

Looks good now. Thanks for the speedy fix.

@Tom-Elliott Should now be corrected for.

I just looked through what was happening with this in the installer files.

and I decided it just wasn’t important enough to even bother with.

I’m just that one weird guy that was trying to build a config file for DHCP without actually using DHCP.

Please disregard, sorry.

@Wayne-Workman @Jbob

Push set for updated Client Version.

This issue is solved in version 6150

It is solved with the last version 6150

@Wayne-Workman yes. This is because the Storage Nodes can also be responsible for the “Checking in/Completion” of tasks.