Update of my posting:
I killed my system and made all new:
W10 Pro - VirtualBox - Linux Mint - Fogserver
all the same as I did it several times before

Result: capture works WITHOUT any failure

Dear FOG-Guys: please reorganize the generation of this random password, make it easyer, no one takes care of this password !!

My Host OS ist Windows 10 Pro, running VirtualBox.
My FOG Server ist Linux Mint.
I am an experianced user in Windows and VirtualBox, but not in Linux, but no matter of this.
A few days ago I made the same System (W10-VB-Mint) with a vdi-disk of 100 GB. This system worked well with capturing and deploying images. I made a mistake and captured too many images which filled up my vdi. Therefore I made my system completely new with vdi of 1000 GB. I did all the same steps and now I have this problem.
Seems to be an issue in installation with this random password.

wrong password for user “fogproject” ???

I get this after capture an image, client tries a little time and then reboots within 1 Minute.

I am not a linux user. I only installed Linux Mint on VirtualBox, changed IP to fixed and made a download of fog project software + installing without any specials.

Many Users do so and there is often this issue but NO SOLUTION !!! Every expert says to harmonize the passwords, but I did not set any password for user “fogproject” while installation.

What the hell is the solution for this problem ???

there are to many issus, I was testing the whole last week to get a workflow for production Environment (School), but one time this Does not work, the other time that does not work and so on.
I have lots of experience in Computers, Servers , Network PXE and so on but I have not the time to test so hard with no effort.

Sorry for that, I wish you good luck and I will try FOG later next year again.

@WalterT
ok
now i have TWO hosts and also two physical maschines, one captured the image from and one deployed on it.

Hosstname on both machines different to the database. How to change? Client Service not installed.

@WalterT
ok:
after Windows initial install, windows uses the Microsoft basic graphic adapter, but shows 1920x1080 on the monitor with hdmi cable.
this happens also after a few restarts.
after touched by fog the first time even without doing any task, windows sets 800x600 as resolution that cannot be changed

after installing a correct graphic driver, this problem is gone. Seems to be an issue of the Intel NUC mini PCs which use a graphic driver that is not contained in windows 10 basic installation.

@george1421 I also didnt believe, but it happend always when I tried to make my workflow as described.

I will test again and report

all Host settings are enabled…

I am beginning from the start today and try to find a workflow for production evironment

when you make a host ready to use, then you want to register it within the servers database. you can you use quick register out of the fog menue, the host is registered and reboots.
At this moment the graphic driver is removed and windows 10 uses a basic driver with 800x600 and begins searching for a proper vga driver.

FAZIT: DO NOT USE Quick register, use manual register instead

Hi
my goal is to avoid this MS sysprep shit when deploying serveral pc`s and to do minor actions on the machine itself.
I have a FOG Server running on Hyper-V (Server 2016), Ubuntu Mate … works
my "Master"Host is w10Pro6 fully installed with FOG Service instaled, PXE works

My steps:
Starting MasterHost and make a quick registration (the only time work on the host)
Hostname in dadabast is the MAC, Hostname of MasterHost is a unique windows name (not changed)
at this moment the hostname in database and on the host is different and I would expect the FOG Service to to his work and make a hostname change and reboot. It does not.
Even after another reboot, the hostname is not changed.

that means also a red icon instead of a green one because my DNS Server does not know the hostname written in database and cannot ping.

Now I deploy the image I captured before to the same machine hoping for a changed hostname (erasing MBR/GPT tables wait wait wait , there is a thread about this problem, but I didnt do anything yet)
HEUREKA ! Hostname changed ! the icon is already red, but the dns-server can ping the hostname.

is this the solution for changing a hostname? by deploying a whole image?