FOG Won't finish capturing a windows 10 image

[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.

[coco65]

@Tom-Elliott : Before starting with a fresh install, in my previous Hyper-V version of Fog;,

At the end of ./installfog.sh you get this:

#################################################################
   FOG has adjusted to using a login system to protect what can/cannot be downloaded
   We have detected that you don't have credentials defined to perform the backup
   If you would like the database to be backed up during install please define
   in your /opt/fog/.fogsettings file

   fogguiuser='usernameOfFOGGUI'
   fogguipass='passwordOfFOGGUIUser'

   You can also re-run this installer as:

   fogguiuser='usernameOfFOGGUI' fogguipass='passwordOfFOGGUIUser' ././installfog.sh
############################################################

So I copied and pasted

fogguiuser='usernameOfFOGGUI'
fogguipass='passwordOfFOGGUIUser'

into the fogsettings file.

Maybe it should have been:

fogguiuser='fog'
fogguipass='password' 

???

Remember as a normal user I am not so smart, just good at Ctrl-C and Ctrl-V.

[Wayne Workman]

@coco65 the credentials must be a valid web interface account. The purpose is for further lockdown of DB backups - defining them in the fogsettings file will allow fog to authenticate said user and use it to do the DB backup during installation or update.

[tom.langenfeld]

Is there a tutorial how to edit the password and user fields? I have tried using vi but do not know how to edit the fields.

[Tom Elliott]

@tom.langenfeld type the i key and then make your edits. When done press the ESC key and type :wq

[Wayne Workman]

@tom.langenfeld said in FOG Won't finish capturing a windows 10 image:

Is there a tutorial how to edit the password and user fields? I have tried using vi but do not know how to edit the fields.

Tom’s stuff is good, but for further help and for future readers, we do have a basic Vi tutorial which includes a video.
https://wiki.fogproject.org/wiki/index.php?title=Vi

[tom.langenfeld]

Hey Tom, When you added that information into the .fogsettings file did you change the existing username and password fields to match the info from the installer or did you just add the two lines that you mentioned?

[Tom Elliott]

@tom.langenfeld Your fogguiuser and fogguipass fields are completely separate from the username/password fields as defined in the fogsettings file. Those new fields are ONLY relevant to the GUI itself.