FOG Won't finish capturing a windows 10 image

[tom.langenfeld]

Thank you guys so much. I am going to test that idea right now.

[tom.langenfeld]

I set the password to all 3 places in the settings as well as the web login and the server user to the same password to be sure but am still getting the same error message at the same time.

[george1421]

@tom.langenfeld

Can you log into the fog server linux console with the fog user ID and password? If not you will have to login back in as root and key in passwd fog to reset the fog user’s password. I’m not ready to rule out other issues but this is the most common one that gets messed up.

[tom.langenfeld]

Yes I can. And I understand you need to start with common errors and I appreciate the assistance.

[Wayne Workman]

@tom.langenfeld I still think it’s credentials, check the storage node management password, be careful of browser auto fill.

[tom.langenfeld]

Nope the login and the password for that step are identical.

[Tom Elliott]

@tom.langenfeld can you show us your troubleshooting steps?

[tom.langenfeld]

I have gone in through the settings to check the password and username all match in the fog settings. I am able to connect and successfully go to pxe boot. I also have done a fresh install of everything on the server as well.

[tom.langenfeld]

I am looking for advice on the next steps to test.

[Wayne Workman]

I am trying to message you.

[tom.langenfeld]

@Wayne-Workman I am not getting any thing from you.

[Wayne Workman]

@tom.langenfeld Top right, the talk bubble.

[tom.langenfeld]

@Wayne-Workman Thanks I will keep an eye for you or others in that location

[tom.langenfeld]

I have done a clean install of FOG leaving the sql option blank during installation.

I have one password to login to the web gui
one password for the storage node management and tftp server( all the same user)
Another password and username are both different for sql user

However none of these passwords work for logging into

[tom.langenfeld]

@tom.langenfeld to the kunbuntu server

[coco65]

I am having exactly the same issue, after updating to 8347. Will a clean install help?

[Tom Elliott]

@coco65 https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP

Please try these steps out. Make sure to update your /opt/fog/.fogsettings file for the password variable.

[coco65]

@Tom-Elliott :

Make sure to update your /opt/fog/.fogsettings file for the password variable.

As a distribution platform I used a laptop as fog server, Fog in virtual Debian 8 running inside Hyper-V in Windows 10, and a switch to connect a bundle of laptops as clients. The laptop hd ran out of space for images so I used a NAS as Fog storage node. All way to complicated and a laptop hd is just too slow, so now I invested in a Gigabyte BRIX micro PC with a 1 TB Intel M.2 SSD inside as Fog server. Smaller and lighter then a laptop. Did a fresh install, Debian 8 and it works great and super fast. No more FTP password errors. Only some problems getting DHCP server to auto-start, the Network-manager in gnome was in the way. Solved that. Did an image pull, an image deploy and an image multicast (Windows 10 image). All works great. Next on my list is to test the Fog client in Win10. Just for fun tried a ClamAV virus scan job, that did not work. Maybe I have to install ClamAV first? Time to read the manual/wiki again, maybe that’s not implemented yet…

[Tom Elliott]

@coco65 ClamAV, I’m afraid, I’m preparing to do away with.

This is because it’s “use” was not exactly useful. If you have to “ClamAV” it, chances are it’s safer (and potentially faster) to just reimage the system. The reporting was basic at best and every time you ran it, chances were great that you’d hit a snag in getting the signature files updated.

[Wayne Workman]

@Tom-Elliott said in FOG Won't finish capturing a windows 10 image:

@coco65 ClamAV, I’m afraid, I’m preparing to do away with.

This is because it’s “use” was not exactly useful. If you have to “ClamAV” it, chances are it’s safer (and potentially faster) to just reimage the system. The reporting was basic at best and every time you ran it, chances were great that you’d hit a snag in getting the signature files updated.

I’ve dealt with (and victoriously defeated) crypto - wall many many times with a 5 minute image deployment.

Of course I deleted the users profile and deleted their redirected app data as well.

Fog puts crypto wall into obsolescence.