Interesting detail in passing: With another computer series (Lenovo M900) this problem does not occur !!

Hello!
I have a weird problem after deploying Windows 10 (or Windows Server 2016). Fog Server 1.5.5, kernel 4.19.6.
All client machines (Dell Optiplex 7010) currently have Windows 7 or Windows 8 installed on an SSD (rolled out without problems last year with FOG).
Now we have a new Windows 10 image created (on a Dell Optiplex 7010 …, exactly the same hardware as all other PCs), captured (without sysprep) and wanted to roll out the image.
The deployment is error free, but Windows does not boot (error 0xc0000225), indicating a bad boot loader.
Maybe someone has the same problem and maybe a solution for it?

EDIT: Additional Info: BIOS-config (legacy) is the same on all PCs
best regards
BB

@tom-elliott Hello Tom! I know that. But you misunderstand me!
What I do is the following:
I change an entry under “Active Directory” and press “Update” in this section -> Feedback: “successfully saved”.
If I then go to any other menu item in the FOG (e.g., Dashboard) and back to the “FOG Settings” to “Active Directory”, the changes made will still be there!
If I now change another item in the settings (for example, PXE MENU TIMEOUT and change the value 5 to 3) and press Update under this section, appears again “successfully saved”.
But if I switch to the dashboard and go back to the FOG settings under “Achtive Directory”, the entries made there have disappeared and also the change in the section above it (in PXE MENU TIMEOUT is again stored 5 instead of 3!)!
Printscreens:
First Change in Active Directory:

Press update:

Going to dashboard and back to FOG-Settings changing “PXE MENU TIMEOUT from 5 to 3” and press update:

Going to dashboard and back to Fog-Settings, all changes are gone!!:

@tom-elliott Ubuntu 16.04.4 LTS and Fog Server 1.5.4

@quazz hmmm., sorry, no such log, neither in the Web-Gui, nor in the /var/log/ and subdirectories…

@quazz I do the “sudo mysqlcheck -r fog”
With this reply:
0_1528900646611_check-database.txt

but it did not solve the problem unfortunately!

@tom-elliott Hy Tom! I understand! Will the new logfile again have the “wrong” permission when logrotate starts? Where can I set with which permissions the new logfile will be created?

But back to the main problem:

My problem is not the wrong permissions on the logfiles, but that settings in the fog settings are not saved.
For this I have new findings:
If I enter something in the fog settings under “Active Directory”, these entries are saved. But if I change something in the “FOG System Settings” afterwards (for example the menu timeout from 5 to 3) the entries in “Active Directory” will be deleted! That is reproducible.

@quazz I changed the pm.max_children entry in /etc/php/7.1/fpm/pool.d/www.conf to 50
new PHP-Log:
0_1528889085857_FOG-PHP71-fpm_2.txt

I also changed permissions to 755, so now I can see the apache-log-files in the GUI!! (but I do not know how this permissions could change, nobody has ever changed them??)

Here the mysql log:
0_1528889995333_sql-log.txt

and actual Apache log:
0_1528890400238_FOG-APACHE2_2.txt

@quazz Thanks for reply!
How or where do I change the PHP-FPM settings?

here are the current permission-settings of the Apache2-logfolder:
0_1528886769897_FOG-APACHE2_log_permissions.txt

Where do I find the mariadb-logs? Here are the files and folders in LOG:
0_1528887322547_log-folder.txt

Strangely enough, the other described problems (kernel update and version information) have been done as if by magic (I have not changed anything, but these two things are working again!) !?

@quazz I really would if I could…, Apache ErrorLogfile says: “Unable to open file for reading”
So I connected to FOG via SSH and open the logfiles PHP-FMP and apache errorlog.
You will find the copied content attached

0_1528816009808_FOG-APACHE2.txt

0_1528816020869_FOG-PHP71-fpm.txt