@tneuber The unattend.xml thing, is a windows thing and not a fog thing.

For example I don’t use the FOG client in my environment but I use the unattend.xml file to configure the target computer and connect it to AD. Here is an example of a sanitized version of my unattend.xml file: https://forums.fogproject.org/topic/11920/windows-10-1803-sysprep-problem/7

hey folks,
the thread is old, but we had also a fight with all the certificates.
after installation of fog 1.5.6 all the clients we imaged bevor stopped communicating with this fog server, they had certificate issues.
we created a gpo that deletes all the installed fog certificates with 3 powershell commands:
Get-Childitem Cert:LocalMachine\root | where-object Thumbprint -eq “4737f594b54cb9fe1103e3c325d9c6963e57c911” | remove-item -force

Get-Childitem Cert:LocalMachine\root | where-object Thumbprint -eq “c84f54d1f654e2f9f04d3c2bf99b3a36371856d4” | remove-item -force

Get-Childitem Cert:LocalMachine\root | where-object Thumbprint -eq “CBE3E738F63C3B1BB93A296F70E73E527D12C637” | remove-item -force

then it worked…

@tneuber What server OS is this? Did you change php.ini settings? Are you able to use the Web UI without issue? The message seen on screen is a PHP message. Take a look at the PHP ini file on your system an set an appropriate timezone. Depending on your OS the INI can be in different locations. On my debian server I have it in /etc/php/7.0/apache2/php.ini. Should be somewhere along this line on yours as well.

@sebastian-roth The issue was changing the LAN boot selection from UEFI to CSM Boot. Thanks all!