Hey Sebastian, thanks for the response. Some external vendors nuked our network over the weekend while performing some kind of maintenance in the data center, so I’m without access to the FOG server until the pieces can be mended. I’ll get back to you with the info once I can.

@Sebastian-Roth My apologizes for the confusion. I meant I cleared them only today to eliminate the possibility of looking at stale logs entries. I do get new log entries every time I run a capture. I continue getting the same error every time. Update database failed with the same ftp_put failure. Would you like me to re-run the capture? Since I have not changed anything I am not why the problem would go away? Do you think it is a version issue? I am running 1.5.6? Does updating the database process depend upon DNS or a default gateway by chance?

@Chris-Whiteley Ok, this partition layout looks fine as well. In the pictures we see that it seems to try to expand the partitions and doesn’t hit any obvious error but the outcome is not what we expect. So we need to dive into this even more. Please add the following as Kernel Parameters to this hosts’ settings and run another debug deploy: isdebug=yes ismajordebug=1 When you get to the “Attempting to expand/file partitions” (that’s before the blue partclone screens) pay attention and take pictures again. It should give us more details this time.

@jlthompsonpsd said in Image capture issues: There are no error messages to forward. It just hangs indefinitely at Reading Partition tables. How long have you waited? Please schedule a fresh task for this host but this time tick the check box for debug! Boot up the client, hit ENTER twice to get to the shell. Now run the following command to find out which disk is being recognized: lsblk Now with that run the following commands as well to see which one is the one that hangs: udevadm settle blockdev --rereadpt /dev/... lsblk -I 3,8,9,179,202,253,259 -lpno KNAME,TYPE /dev/... For the blockdev command you need to put in the correct disk device name that you got from the initial lsblk. Maybe it’s /dev/sda or /dev/nvme0n1 or …

@quinniedid Whoops, just saw that we’ve lost track of this. Did you ever solve this. Might give it a try in the next days when I find the time.

@jemerson93 Thanks for bumping this topic. Must have gone unseen in the last busy week, sorry. Is it one particular image that you see this “random” issue with? Please post the contents of the text files p1.partitions, p1.minimum.partitions and p1.fixed_size_partitions of that image here in the forums.

@Jonathan-Cool I find it very interesting that a SYSTEM account will work on Windows 7 but not Windows 10. One thing I would like to see is doing the same thing with PSExec running as the SYSTEM account and once you have that command window open change the directory to where you usually have the drivers dumped to. Run the xcopy from the NAS. I would be curious to see the behavior difference between Windows 7 and Windows 10. Also, can you capture a screenshot of the security permissions of the folder specially on Windows 10 that the drivers are dropped into? Something like this:

Weird, disregard. It just suddenly started working now. No idea what fixed it. Maybe it took a while for something to register.

@khalid Problem might be that the fog-client runs as System Service. Maybe installing updates like this is not allowed by MS security.

@Junkhacker and @Sebastian-Roth Junk was right. Fresh install taking almost all defaults fixed it for me. Thanks!

@cmurray139 i’m not sure. I don’t have much experience with devices that don’t have Ethernet built in. if you search the forums, you might find someone who’s already solved the problem though.

@Onirix May I ask you to use the most current version 1.5.6 as of now. There was a bug in an earlier version that prevented an install on latest Debian…

We have managed to fix this for some reason the username needs the domain name in front of it and it then works fine so in AD default user we have now white_spire\fog and then password and appears to be working now

@Sebastian-Roth I did not found the option in FOG configuration -> fog settings , but I just found the faulty host had as primary MAC the Windows vNIC mac. I put the MAC of the physical NIC as primary and then everything back to normal. I don’t have a idea to make the research better as I just had to search in the host section of FOG the MAC addresses found in the client log to see what was going on.

@Tom-Elliott I try the fix and its ok. Thanks for your works

Hey, I downloaded the ISO file of Windows 10 Home from third party source and I am also stuck in proceeding further. Any help will be appreciated.Thanks in Advance.

@Miodog Please let us know if we can improve the Multicast address thing within FOG even more. We are open for any kind of suggestion on this.

It’s probably going to be two weeks or longer before I can adjust the daily tests - I’m super busy this weekend, next week, and vacation is the week after. But I’m pretty confident I can test upgrades. At least upgrading from the last release.

@Alois Please try the following commands: sudo su - apt-get install php7.2-mysql phpenmod mysqli systemctl restart apache2 systemctl restart php7.2-fpm

@JB2019 please paste the contents of your install log. it should be located, from the base directory of the install files, in /bin/error_logs/foginstall.log