We are seeing a persistent encryption/token issue in FOG 1.5.10.16. There is also a consistent timestamp anomaly, and while both occur together, I do not know if they are directly related.

Problem 1:

Every time the FOG Client authenticates (for example, after a reboot), a new token is generated, and shortly after that, the “Reset Encryption Data” button reappears automatically in the UI.
I am not sure if this is expected behavior by design, but I have observed that some snapin tasks do not execute unless the encryption data is manually reset first.

Problem 2:

Separately, there is a consistent +30 minute offset between the database value hosts.hostSecTime and all real system clocks. The offset is always exactly +30 minutes ahead of:

hosts.hostSecTime in MariaDB is always written exactly +30 minutes ahead of: FOG server time (date), MariaDB NOW(), Windows client time (Get-Date), token.dat LastWriteTime on the client.

Example data from Host with ID 66:

PS C:\Users\Administrator> Get-Item "C:\Program Files (x86)\FOG\token.dat" | Select LastWriteTime

LastWriteTime
-------------
03/12/2025 9.45.58

And

MariaDB [fog]> SELECT hostSecTime FROM hosts WHERE hostID = 66;
+---------------------+
| hostSecTime         |
+---------------------+
| 2025-12-03 10:15:58 |
+---------------------+
1 row in set (0.000 sec)

All systems (FOG server, storage node, Windows clients) are correctly NTP-synchronized.

Questions

Is it normal for “Reset Encryption Data” to reappear after every reboot?
Is the +30 minute offset in hostSecTime expected or a known issue in 1.5.10?
Could either of these independently explain intermittent snapin failures?

Cheers!