@alexh Hi, please create another topic about you problem. First time look at that : https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP

We were able to get the stuff figured out. YAY!

The connection is now operational. FOG Interface displays properly.

You are welcome! 🙂 As well I learned to pay even more attention to what I see in the PCAP file. Would have saved us at least an hour or two… When testing with the command line client Scott didn’t know about the important -i option for Windows tftp command line client as described here. When looking at the PCAP file Scott sent me I didn’t notice that it tried to request the file in ‘netascii’ mode instead of ‘binary’.

So everything is working now and it was just the upper case filename option in the DHCP config…

@Satya because this is a consumer grade router is there any special configurations on it doing special things? If not there usually is a reset button on the router that will allow you to reset to the factory defaults. What the sequence of doing so is would require the manual of the device which you can find online.

@MagicLink Correct, they are compressed.

@fredlwal Why did you enable it? It should remain disabled.

sudo ufw disable

I am amazed typed in /dev/sda and I am now in the process of uploading. You guys rock.

Yep, @Tom-Elliott helped me realize that over chat. Reboot, rinse, repeat. Thanks @Wayne-Workman for having a look-see. You can mark this is as solved.

Thank you Wayne. That did the trick.

Seems like people from the same place maybe? Posting at the same time about the same issue. https://forums.fogproject.org/topic/7000/image-cloning-fails

You can mark this is as solved. This was a case of good old SE linux set to enforce. Can’t believe it. Thanks @Tom-Elliott!!

@J3ff
The only way I’ve solved the problem was to upgrade to svn 6889.
After that the web ui kernel update has let me upgrade to this kernel

Official Published Kernels
Kernel - 4.5.0 TomElliott
Date : March 14, 2016
Version : 4.5.0
FOG Type: TomElliott
Arch Type: (x86_64)

Marking as solved (not directly a FOG issue)

@george1421 Thanks for testing and letting us know. Seams to work with the latest trunk so I am marking this solved now. Please let us know if you feel images are not moved properly (please check FTP first!).

@george1421 You know I usually do a full wipe on all of my images. This was the only image I did not enforce a full wipe of the drive. I can see why it should be standard practice even though my other images are done as full wipes and installing os on raw partition.

As for the initial chainload issue, it was probably trying to load images from a non-existent storage node. After removing the location plugin and the decommissioned storage node, the chainload issue disappeared. I was informed a storage node died (mobo crapped out).

@Sebastian-Roth thanks I figured it out .

@Ph3noM Please schedule a debug deploy task (normal deploy task but tick the option “Schedule task as a debug task”), start the machine up and wait till you get to the shell. Then start cloning (command fog) and step through the tasking. When you get back to the shell run the following commands to see if the registry changes were done correctly - make sure to choose the correct windows (7/10 - won’t work for XP!) system partition for /dev/sdaX, e.g. /dev/sda2:

shell> mkdir -p /ntfs shell> ntfs-3g -o force,rw /dev/sdaX /ntfs shell> reged -e /ntfs/Windows/System32/config/SYSTEM ... reged> cd ControlSet001\Services\Tcpip\Parameters reged> ls ... <Hostname> ... reged> cd ControlSet001\Control\ComputerName\ComputerName reged> ls ... <ComputerName> ... reged> q shell> umount /ntfs

See what you get for <Hostname> and <ComputerName>…

@Sebastian-Roth said:

Marking this solved for now as we didn’t hear back from anyone. If you have printer issues please follow the link Wayne posted below. If you still think there is an issue within FOG please let us know!

I apologize for the delay, been swamped. It does seem the issue has been resolved. I have not seen it after the past several SVNs. Thank you very much for your help.

@cotec I am pretty sure this issue was solved: https://forums.fogproject.org/topic/5990/printer-issues-continue

Please make sure you update to the latest version (FOG and FOG client) and try again.

@mxc bumping this…