@george1421 Thanks for the reply, The hostname changer now works : It turns out it cannot rename PC like that and require “Rename > Image deployment > New Name is applied” but I have no idea if the Host product key has been changed and I’ve found no way to check.

Greetings, I am once again requesting support regarding FOG and it’s abilities.

I have (many) multiples PCs that I need to rename and put on Windows 10 so My goal is to sysprep and Image & deploy it. The Issue is that when I tried to change the Hostname with the FOG Web interface : nothing happen. How can I make it work ?

Im also wondering if I input a Host product Key after deploying my image, will it change the Windows key ? I wouldn’t like to have no or same key for each PC.

Thanks.

@george1421 It looks like it finally managed to update the database and proceed to the final moment of the capture. I did what you suggested and changed the FTP Path and I can’t believe it worked.
As you can see, my Image is there !

Many Thanks for the help, I was this close of giving up for another solution, I was stuck for so long !

@george1421 So I used CMD to connect to my NAS with ftp <nas ip> :

• Connection is successful with foguser
• pwd return “/”
• ls return the inside of my Shared folder FOG (@Recycle, snapins, images, tftpboot)

@Sebastian-Roth said in “could not complete tasking (/bin/fog.upload)”:

@DPR-SIO said in “could not complete tasking (/bin/fog.upload)”:

I Think I may have found the solution to my problem but I’m not sure

Would be interesting to hear what you found.

I’ll give a go to this in last. I’ll try others things first.

@george1421 said in “could not complete tasking (/bin/fog.upload)”:

@DPR-SIO Running the FOS Install script on a NAS probably will not work since the install script assumes your “NAS” is a linux computer.

Its possible to setup a NAS as a storage node as long as it has NFS and ftp capabilities. The NFS share directory and the FTP user directories need to point to the same location. In the storage node definition there is an FTP path field, that needs contain the actual path on the NAS where the files are located. The qnap and synology instructions do a good job of showing how things need to be configured. You need to make things configured in the correct location on the NAS, confirm that the ftp user can access both /images/dev and /images directory to move files.

I think my Storage node settings are wrong and Might be the issue. Anything that catch your attention ? My FOG server manage to save the image on my NAS but I still get an error in the end. “Failing to update database”.
Please understand I don’t like leaving IP and MAC address seen so Red is MAC, Green my NAS (Storage node then) and yellow my FOG Server.

The folders looks like this on my NAS : FOG/images snapins tftpboot
On My FOG it’s /mnt/FOG (I did “mount -t nfs <NAS IP>:/share/FOG /mnt”)

@george1421 Thanks for the reply and the guidance. I Think I may have found the solution to my problem but I’m not sure : do I need to Install FOG storage node script on NAS and use it as a Storage node for my FOG Server ?
More I think about it, More I think it is.

Greetings,

I have a FOG Server and Im using a QNAP NAS to store the images I capture. When I schedule a Capture, I successfully capture the image but after the 100%, I get errors such as :

• Error returned: Type: 2, File: /var/www/html/fog/lib/fog/fogftp.class.php, Line 714, Message: ftp_put(/share/FOG/images/dev/[MAC Adress]): failed to open stream: no such file or directory, Host: [My Host], Username: foguser

And finally, as title says : Could not complete tasking (/bin/fog.upload)

I don’t quite understand how and why this is happening. My Fog server is able to communicate and write on my NAS (My image is there) but after the capture, the task get stuck at ~68%.

Any idea how to fix ?