the /images location that is hardcoded in fog.upload is just the name of where it has mounted the storage location to in fog.checkin

I’m telling you, it’s already setup in 1.2.0.

Looks like the problem was PEBKAC (seriously I feel like an idiot haha). I had so many Ethernet cables across my desk and didn’t realize one of them was hooked through a 10/100 interface. When I took the original image I was connected to the 10/100 but when I swapped with the HDD I plugged it back into a GigE port. My bad on that.

For what it’s worth it’s blazing fast across the board again 😄

[quote=“TonyB.2871, post: 40293, member: 26980”]Just curious as we were able to image fine on 1.2.0 for quite some time up until recently. I know there was a minor network infrastructure change, but nothing that should have affected the Fog server’s functionality. Given I can access it via HTTP, TFTP, etc… and that it worked before, Im slightly confused why we need to upgrade.[/quote]

Hi,

No new hardware ? : switchs, computers, …
Your server is virtual ?

Regards,
Ch3i.

that worked. i had it set to partimage and switching it to partclone fixed the issue. thanks.

Issue resolved.
Dont ask me how but I tried with two different systems and Ive been able to restore them

I started from scratch this morning, paying extra attention to the proxy dhcp setup process, and it now seems to be working as it should. Have successfully uploaded and multicasted an image. Thanks for your help.

yes it is.

Thanks tried that first part as fix but not the second. Just updated. Thanks, hopefully do the trick. :_)

I’ll see if I can borrow one of our school’s raspberry pi, and see if I can sort this out.

That said, all I’d be testing is the installer and the services to get started, but I would not recommend using it to actually image systems. This is just my thoughts. The Pi is not a very powerful system. While I’m sure it will do what you want, it wouldn’t necessarily be the “best” method to do a “mobile” solution either.

Same thing happens on Lenovo R500’s and Lenovo R61’s. Changed AHCI to compatibility. Its a known issue and its related directly with the hardware and BIOS. This will affect any install of Windows, ghosting, Acronis True Image and FOG. Sorry but not a FOG issue.

[quote=“Thomas Rucker, post: 40196, member: 1970”]So, it’s not the GPT or MBR, but FOG has a limitation, because of how Lenovo loads their machines.

I guess I have to live with the RAW image then, correct.

I have to say, it works very well, but it’s very slow, thank you for your thoughts.[/quote]

If you have 6 primary partitions it’s GPT.

[url]http://en.wikipedia.org/wiki/GUID_Partition_Table[/url]

Still did not work. What is odd is that the image was working just fine until I set up fog correctly for renaming the computer and joining it to the domain. Kaspersky is not even attempting to install. It just skips right over it and goes straight into windows. I am at a loss. Need a day to think.

Thanks, that seems to have fixed it.

Since Fog uses several servers and other components that use usernames and passwords, and since it seems that the installation script doesn’t set them all correctly, is there any documentation for Fog that explains how to set them all up correctly?

Hah! I tried your command and got the error Host is blocked because of many connection errors; unblock with ‘mysqladmin flush-hosts’.

We ran that and voila! Our FOG server is back.

You guys are truly wonderful.

Tom, sorry if this confused you. The initial set up was already tested on local (Ubuntu 13.10 VM) and was working. nothing really has changed besides putting the master Node on a freenas (with FTP & NFS) and giving full control of the loaction to the fog user (which was put as the user to use in the node management on the GUI)

Since then, everything is still working fine, comunication between Fog and the node is fine, image uploads are going to the dev folder then after upload is finished it’s being transfered to the main /images folder. the ONLY issue is whenever we try to proceed a download from the host management page, it fails automatically giving out the error I posted above. BUT using the quick download from the host list in task management works.

Do you need more information?

Linux beginner here; While I have been using FOG for about 3 years now, messed up and fixed several things using your forums, I have what appears to be the same issue mentioned above. I can go into the webpage and force the images to happen and they work just fine, otherwise even though no other images are actually in progress they will sit and display “Waiting for a slot, 0 PCs are in front of me. (x min)”

What do I need to do to look at the mysql database and check these entries? I apologize for my newbiness ahead of time. Just can’t seem to find the answer to editing the database, and appreciate wonderful UBUNTU commands and ideas to add to my ever growing understanding of UBUNTU.

Running .32 still on UBUNTU 14.04

Thank you.

Because the OOBE experience is actually required for windows to properly adjust to a machine’s hardware, if you want to add software to a windows machine fresh out of the box without even going through with OOBE (which keeps your re-arm count from going to high) I HIGHLY suggest going through with the windows install until asked for a computer name and username, at this point if you hit CTRL+SHIFT+F3 your system will reboot into AUDIT mode, Sysprep will pop up when windows logs in. At this point choose “Enter system audit mode” for the first option and “quit” for the second and hit OK, Sysprep will take a few moments to close and once it’s gone you can do with the system what you will (Drivers, Software, even populating C:/Users/Default/Desktop with any shortcuts the client may need). At this point you can run windows updates (IT IS OK IF YOU NEED TO RESTART YOUR PC FOR UPDATES THIS WILL NOT DAMAGE ANYTHING AS LONG AS YOU CHOSE QUIT IN SYSPREP AS I STATED ABOVE, YOU WILL ONLY HAVE TO REPEAT CHOOSING AUDIT MODE AND QUIT EVERY TIME THE PC RESTARTS) after finishing with EVERYTHING you would like to exist on the computer restart once more, now that we have everything we need we can set it to run OOBE at last, Sysprep will pop up as always under System cleanup action choose “Enter System out-of-box-experience”, and check the generalize box, and for the second option choose reboot and hit OK, the computer will now reboot when the BIOS starts hit whatever key you need to access the boot menu, queue your host to upload the image in the FOG web GUI and boot it to the NIC, this SHOULD pull the image just fine and negate MOST issues everyone seems to be having! Apologies for the multipost…

Since it’s a VM, take a snapshot. Then issue the dnsmasq removal command:

[code]sudo apt-get remove dnsmasq[/code]

See if you can Ping internally, if so test the internet. Reboot the VM, turn off your dhcp service again and see if internet is still available. If any of this breaks your ability to connect to the network, then you need to restore your snapshot and disable both the dhcp and dnsmasq services on boot when you need to connect to your home network.

Junkhacker, thank you! I didn’t even think about this. I had it bound to the 10.x.x.x address. Changed to the 192.168.x.x and the FOG menu is now booting.

I swear i had switched this earlier and tested, but apparently it did not save the change (please read: [U]I[/U] failed to save the change)