Marking this thread solved since the request in the opening post is not possible.

@Ph3noM Please schedule a debug deploy task (normal deploy task but tick the option “Schedule task as a debug task”), start the machine up and wait till you get to the shell. Then start cloning (command fog) and step through the tasking. When you get back to the shell run the following commands to see if the registry changes were done correctly - make sure to choose the correct windows (7/10 - won’t work for XP!) system partition for /dev/sdaX, e.g. /dev/sda2:

shell> mkdir -p /ntfs shell> ntfs-3g -o force,rw /dev/sdaX /ntfs shell> reged -e /ntfs/Windows/System32/config/SYSTEM ... reged> cd ControlSet001\Services\Tcpip\Parameters reged> ls ... <Hostname> ... reged> cd ControlSet001\Control\ComputerName\ComputerName reged> ls ... <ComputerName> ... reged> q shell> umount /ntfs

See what you get for <Hostname> and <ComputerName>…

Moving thread to solved.

@Ph3noM said:

No it’s ok now, i just made a mistake.
I am very happy!
Thanks all for the help!

What was the mistake?

@Ph3noM Fog doesn’t set a DB password - if fog sets up the DB on a new server, it’s left blank. The installer (at least in FOG 1.3.0 beta) asks you for a DB password just in case you set one in the back end. And of course if that’s the case (and 99% of the time it is) then the field in /opt/fog/.fogsettings would be blank as well.