The problem was I had the Fog Server set up as the master storage node. In order to image & have it saved on the Fog storage I had to change Fog Storage to be the Master storage node( done within the Fog Server). Now all my problems are fixed…

it looks like you were hit with a big that was identified in 1.1.2, and was actually a large part of the 1.2.0 update. under certain conditions all of the settings could be blanked on the settings page. i’m afraid you’ll just have to set them back manually. but at least it won’t happen again…

Nobody has ever seen this before?

To add to this, if I set a task, it doesn’t restart the computer.

The Fog Service is running but the client isn’t responding.

What’s going on here?

Could the problem be there is only one partition (as seen in the screenshot)? My Thinkpad models show two partitions. The one partition GX755 running win7 works fine.

Hey Tom, I appreciate you following back up on this. Currently, I do have a drive that has failed in the LVM and am waiting on my boss for a replacement.

However, I don’t think that was the problem. As soon as I get a replacement drive, I’ll finish the upgrade process from Ubuntu 12.04 LTS to 14.04 LTS and from FOG 0.32 to 1.2.0. (The first one of these temporarily caused GRUB to break…)

Thanks again,
Chuck

[quote=“Junkhacker, post: 34899, member: 21583”]compression on 0.32 was hard coded to 3
if you’re uploading an image off of a slower computer, it will make a very big difference.
download speeds are typically faster then they were with 0.32, and isn’t that more important?[/quote]

Oh btw! We just tested it on the download and holy hell, you were not kidding about the improved download speeds. Excellent work!

I’m interested in the same documentation because I’m having issues with the new PXE setup and I thought it might be my old hardware.

Hey guys,

Thanks for the replies, I can give it a go sure thing, everything else by the way is working like a charm 🙂

Thank you, that solved the problem!

Kind regards,
CodeBarbarian

Thanks tom that’s great just made the change

thanks I will make the change and test.

I had the same issues the fix for me was using terminal to restart mysql server as well as the tftp server than it was all back to normal not sure if this is gonna happen everytime I reboot the server or not.

Also, just clear your browser cache, all should function if you run into issues again.

[quote=“Junkhacker, post: 34817, member: 21583”]if you don’t want to keep the data for logging purposes, a quick thing to try would be truncating the tasks, stapinTasks, and snapinJobs tables[/quote]
Junkhacker you rock 🙂
This advice solved the issue.
All snapins and single snapin smoothly installed.
Thanks a lot.

No, problem. I hope it works for you.

Ah, didn’t realize there was an update. I’ll give that a try. We have 3 new models of laptops and tablets and this is the only one that gave us trouble that’s what’s so strange. Even our older models worked like a charm all the way back to v.32.

I’ll update more when I update.

I had the clients in a group and when I managed the group to have the Host Name Changer Service run for some reason that didn’t take. Issue Resolved though
and Joining Domain I was using “Domain Name\Administrator” instead of just the username Oddly enough It automatically joined the workgroup “Domain Name” instead of just an error

This worked! Thanks Tom. From what I can tell the first time I downloaded this kernel something went awry although I got no error messages and the file was possibly corrupted, only 4655 bytes?. (I used a -no-certificate-check with wget, if i dont use the no cert, i get an SSL error) I noticed this a.m. it was much smaller than a kernel file should be. So this time I downloaded it in my Windows browser and pushed it up to my Fog box via FTP. Success. Thanks a gain Tom!

Windows Firewall is disabled. There are Windows 7 computers on the same subnet as the server which have working FOG services so the antivirus is not blocking the FOG service.

Unfortunately, the command recommended by Jose did not help, though I appreciate the ideas.

I’ve come across a few other threads where people have similar problems, but I haven’t seen any direct solutions related to this specific Windows 7 subnet issue. I’ll keep working on it though.