@Tom-Elliott no problem, thank you for helping me ! We hope this will be useful to users reading this post.

I edited the line in /etc/ssh/sshd_config
I restarted the capture, here is the error, directly when I boot on IPV4:

@Tom-Elliott

FYI

@Tom-Elliott

So I launched a task to capture my image and it was in principle a success, here is the screen:

BUT… once the download is complete, this is the error I receive:

Here again, the “second task” remains stuck at 1%

My capture is still stuck in \images\dev with my computer’s macadress

I’m helpless (I’m in production at the moment)

@Tom-Elliott Here is…

I typed these commands:

apt-get -y install git -y
apt install wget

cd/root
git clone https://github.com/fogproject/fogproject.git --branch=working-1.6

fog project cd
git pull
CD bin
./installfog.sh -y

I got this error when loading packages:

error: Installing package: php-mysql…………Failed! (Will try later)

The interface changes a little but I get the hang of it.
I’ll capture an image and get back to you

@Tom-Elliott I can’t find the installation of FOG working-1.6

@Tom-Elliott said in Mounting /images/dev on /images failed - permissions denied:

sudo chmod 777 -R /images/Nuc7i5BNKSDC-AC001-C000-win11

I moved it manually, gave rights etc. The problem continues

@Tom-Elliott at the point where I am, no problem starting over with a new installation.

Could you give me a link to install this version? that I am sure to do what you asked me

@El-Fogito

always same error when trying to deploy

my image is stored in image\dev with another name (mac address of the PC captured)

Hello,

I’m reviving the topic, my problem is still not resolved (I am deploying on 180 computers this week)…

I captured an image this morning, my PC restarts as if the image had been captured successfully

I also see the size of the image in the management console:

But here’s the problem:
In active tasks, a second loading (I imagine moving from images\dev to \images) is blocked. This is the crux of my problem. Database problem? what to do ? Here is a screen

@george1421the correct server is 10.10.10.38, the bad one is 10.20.10.38

they are in the same network yes, only different Vlans but with the same rules