This is fixed, too, and can be marked as solved. The reason was stale WOL power action. I deleted those manually from the DB, and the CPU went back to normal.
I’m not sure about the SSH and replication issues, but I deleted my physical storage node, and I’m not seeing those anymore.
Here is a clearer forum version:
What I meant is this:
If a group is created but no hosts are added to that group, opening/clicking that empty group in the FOG dashboard throws an error in the browser.
I tested this on two separate FOG instances and got the same result on both.
Example: If the group sysprep-test-5002 is clicked in the screenshot below.
The browser shows this SQL error:
You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version
for the right syntax to use near ')' at line 8
Expected result:
FOG should open the empty group normally and show that it has no members, instead of generating a SQL syntax error.
@devle @Tom-Elliott This problem occurs when there are no hosts associated with the group (the group is empty). This can be closed, but I believe it should be moved to the BUG reports.
@lucamathuse No, I would not move the files manually yet.
If the capture reports “Cloned successfully” but the task remains In-Progress, then the capture itself may have finished, but the post-capture process is not completing correctly. Under normal conditions, the host should finish the task and then reboot or shut down automatically based on your settings.
So, before moving anything by hand, I would want to know whether the host is actually stuck there indefinitely or whether it is still finishing something in the background. If it never updates the task status, that could also explain why your image set ends up incomplete or inconsistent.
At this point, I would stop modifying the image files by hand and do one clean test from scratch.
Right now, the modified image is not a clean test anymore. The latest error shows Partclone is attempting to deploy p3 and then failing, which also explains why the restored partition shows as RAW.
This is how I have captured and deployed images on various HP models.
@lucamathuse From the metadata you posted, I do not see evidence that Partclone skipped the Windows partition.
d1.partitions shows p3 as the large Microsoft basic data partition, d1.original.fstypes shows p3 as ntfs, and d1p3.img.000 exists. That indicates the Windows partition was captured. That, by itself, does not prove that the deployed content is valid, but it does not support the claim that C:\ was simply left out.
So I think it is important to distinguish between these two cases:
Based on what you posted, this looks closer to the second case.
The reported behaviour also points more toward a Windows boot configuration issue than a Partclone omission. In particular, the manual changes you described on the Windows side — disabling WinRE, deleting/extending partitions, and editing BCD-related settings before capture — are much more likely to produce a recovery-only boot state than Partclone “skipping C:”.
If you want to prove that C is actually not being deployed, the correct test would be a debug deploy or checking the failed target from recovery/WinPE:
C:\Windows is presentIf those are present, then the problem is not that Partclone omitted C:, but that Windows cannot boot from the restored layout.
@kratkale said in Windows 11 | 65x HP Z2 Tower G1i:
Can I specify in FOG which hard drive to clone to? For example, using the serial number? That could be stored in the host entry
Hi, this is a known issue when using NVMe, as you’ve probably already discovered. I’m not sure whether FOG 1.5 supports using serial numbers to target disks, but someone from the team may be able to confirm that. FOG 1.6, however, does support targeting disks by serial number.
I ran into the same situation. As a workaround, I customized my init.xz to use the PCI path instead, since those appear to be more persistent.
@lucamathuse Hi. I have faced similar situation on HP. I think your computers are going into recovery because the BIOS hasn’t updated its boot entries. So it still thinks it should load the old OS.
From the steps, I saw you fiddling with the Boot entries. I’m not familiar with that method, but at least on my computers, I don’t need to change anything. Just a sysprep -> Shutdown and capture.
Have you actually tried investigating whether the data has been copied to your disk? Do you see the boot directory? You should be able to drop into the CMD from that recovery or advanced option and investigate that.
I have deployed Windows 11 while the image type was Windows 10, and never needed to change anything.
@Tom-Elliott Hi, has there been any development with this?
I’m facing a situation that’s not quite identical but very similar in my 1.6.0-beta.2297.
I already posted to the Forum with the details I thought were relevant, but noticed my FOG status is showing the same messages that are posted here.
Hello,
Recently, I noticed that I cannot run any snapins that were associated with the host. I also noticed the FOGScheduler was not working. After investigating, I found several issues.
FOG Version:
Upgraded from 1.15.10 → <several 1.6-beta in between> → currently running 1.6.0-beta.2297
Setup:
[04-07-26 9:28:10 am] # peruswin-audit-1.2: File does not exist d1.fixed_size_partitions(storage 1)
[04-07-26 9:28:10 am] # peruswin-audit-1.2: File does not exist d1.mbr(storage 1)
[04-07-26 9:28:10 am] # peruswin-audit-1.2: File does not exist d1.minimum.partitions(storage 1)
[04-07-26 9:28:10 am] # peruswin-audit-1.2: File does not exist d1.original.fstypes(storage 1)
[04-07-26 9:28:10 am] # peruswin-audit-1.2: File does not exist d1.original.swapuuids(storage 1)
[04-07-26 9:28:10 am] # peruswin-audit-1.2: File does not exist d1.partitions(storage 1)
[04-07-26 9:28:10 am] # peruswin-audit-1.2: File does not exist d1.shrunken.partitions(storage 1)
[04-07-26 9:28:10 am] # peruswin-audit-1.2: File does not exist d1p1.img(storage 1)
[04-07-26 9:28:10 am] # peruswin-audit-1.2: File does not exist d1p2.img(storage 1)
[04-07-26 9:28:10 am] # peruswin-audit-1.2: File does not exist d1p3.img(storage 1)
[04-07-26 9:28:10 am] # peruswin-audit-1.2: File does not exist d1p4.img(storage 1)
[04-07-26 9:28:10 am] # peruswin-audit-1.2: File does not exist on master node, deleting /images/peruswin-audit-1.2/d1.fixed_size_partitions on storage 1
[04-07-26 9:28:10 am] | peruswin-audit-1.2: No need to sync /images/peruswin-audit-1.2/d1.fixed_size_partitions file to storage 1
[04-07-26 9:28:10 am] # peruswin-audit-1.2: File does not exist on master node, deleting /images/peruswin-audit-1.2/d1.mbr on storage 1
[04-07-26 9:28:10 am] | peruswin-audit-1.2: No need to sync /images/peruswin-audit-1.2/d1.mbr file to storage 1
[04-07-26 9:28:10 am] # peruswin-audit-1.2: File does not exist on master node, deleting /images/peruswin-audit-1.2/d1.minimum.partitions on storage 1
[04-07-26 9:28:10 am] | peruswin-audit-1.2: No need to sync /images/peruswin-audit-1.2/d1.minimum.partitions file to storage 1
[04-07-26 9:28:10 am] # peruswin-audit-1.2: File does not exist on master node, deleting /images/peruswin-audit-1.2/d1.original.fstypes on storage 1
[04-07-26 9:28:10 am] | peruswin-audit-1.2: No need to sync /images/peruswin-audit-1.2/d1.original.fstypes file to storage 1
[04-07-26 9:28:10 am] # peruswin-audit-1.2: File does not exist on master node, deleting /images/peruswin-audit-1.2/d1.original.swapuuids on storage 1
[04-07-26 9:28:10 am] | peruswin-audit-1.2: No need to sync /images/peruswin-audit-1.2/d1.original.swapuuids file to storage 1
[04-07-26 9:28:10 am] # peruswin-audit-1.2: File does not exist on master node, deleting /images/peruswin-audit-1.2/d1.partitions on storage 1
[04-07-26 9:28:10 am] | peruswin-audit-1.2: No need to sync /images/peruswin-audit-1.2/d1.partitions file to storage 1
[04-07-26 9:28:10 am] # peruswin-audit-1.2: File does not exist on master node, deleting /images/peruswin-audit-1.2/d1.shrunken.partitions on storage 1
[04-07-26 9:28:10 am] | peruswin-audit-1.2: No need to sync /images/peruswin-audit-1.2/d1.shrunken.partitions file to storage 1
[04-07-26 9:28:10 am] # peruswin-audit-1.2: File does not exist on master node, deleting /images/peruswin-audit-1.2/d1p1.img on storage 1
[04-07-26 9:28:11 am] | peruswin-audit-1.2: No need to sync /images/peruswin-audit-1.2/d1p1.img file to storage 1
[04-07-26 9:28:11 am] # peruswin-audit-1.2: File does not exist on master node, deleting /images/peruswin-audit-1.2/d1p2.img on storage 1
[04-07-26 9:28:11 am] | peruswin-audit-1.2: No need to sync /images/peruswin-audit-1.2/d1p2.img file to storage 1
[04-07-26 9:28:11 am] # peruswin-audit-1.2: File does not exist on master node, deleting /images/peruswin-audit-1.2/d1p3.img on storage 1
[04-07-26 9:28:11 am] | peruswin-audit-1.2: No need to sync /images/peruswin-audit-1.2/d1p3.img file to storage 1
[04-07-26 9:28:11 am] # peruswin-audit-1.2: File does not exist on master node, deleting /images/peruswin-audit-1.2/d1p4.img on storage 1
[04-07-26 9:28:11 am] | peruswin-audit-1.2: No need to sync /images/peruswin-audit-1.2/d1p4.img file to storage 1
[04-07-26 9:28:11 am] | CMD: lftp -e 'set xfer:log 1; set xfer:log-file "/opt/fog/log/fogreplicator.peruswin-audit-1.2.transfer.storage 1.log";set ftp:list-options -a;set net:max-retries 10;set net:timeout 30; mirror -c --parallel=20 -R --ignore-time -vvv --exclude ".srvprivate" "/images/peruswin-audit-1.2" "/images/peruswin-audit-1.2";exit' -u fogproject,[redacted] 172.28.1.89
[04-07-26 9:28:11 am] * Started sync for Image peruswin-audit-1.2 - Resource id #1583
[04-07-26 9:28:11 am] | Sync finished - Resource id #602
Observed:
/images/<image>find and lftpApr 07 09:42:13 fog sshd[2483177]: error: kex_exchange_identification: Connection closed by remote host
Apr 07 09:42:13 fog sshd[2483177]: Connection closed by 172.28.1.89 port 55330
Apr 07 09:42:13 fog sshd[2483178]: error: kex_exchange_identification: Connection closed by remote host
Apr 07 09:42:13 fog sshd[2483178]: Connection closed by 172.28.1.89 port 55336
Apr 07 09:42:14 fog sshd[2483179]: error: kex_exchange_identification: Connection closed by remote host
Apr 07 09:42:14 fog sshd[2483179]: Connection closed by 172.28.1.80 port 34766
Apr 07 09:42:14 fog sshd[2483180]: error: kex_exchange_identification: Connection closed by remote host
Apr 07 09:42:14 fog sshd[2483180]: Connection closed by 172.28.1.80 port 34768
Observed:
Fix / Isolation:
FOGMulticastManager stops the SSH spamsession_start(): open(... Permission denied)
Observed:
/var/lib/php/sessions directory is correct:
drwx-wx-wt root:www-data
Session files are created as:
-rw------- 1 root root ...
Apache/PHP-FPM runs as www-data → cannot access them
Isolation:
Stop:
systemctl stop FOGScheduler FOGMulticastManager
Delete sessions:
find /var/lib/php/sessions -type f -name 'sess_*' -delete
Errors stop
Start only:
systemctl start FOGMulticastManager
Errors immediately return
Undefined array key "pmAction"
Observed:
powerManagement tableFix:
Observed:
FOGScheduler is restartedObserved:
php (root) ~100% CPU
Observed:
FOGSchedulerfogproject workslftp) can list image files correctly@Tom-Elliott Hi, sorry for the delayed response. I updated both the Fog server and storage node, but the same error is thrown at the end of multicasting.
@Tom-Elliott Absolutely. I will get back to you in a few hours.
Yes, it looks like multicast is working correctly. Thank you for the support.
I also want to add a few details to clarify our setup.
A few months ago, I was running version 1.15.10. Since we are developing an API-based solution, we decided to upgrade to the latest development branch.
During the upgrade, I noticed that when the message appeared telling me to visit /fog/management to update the database, no database update actually took place. Instead, the web interface took me straight to the FOG login page.
If I understood that correctly, it suggests there were no database schema changes between 1.15.10 and 1.6. However, that later led me to question my understanding, because several issues arose afterward, including the one mentioned in this post: “Database Update: Failed.”
I will add the other issues to the forum soon and link them here.
FOG version: 1.6.0-beta.2273
Let’s ignore the Snapin errors for now. The error is thrown at the end of the Multicasting image.
FOG version: working-1.6
commit: f61a90d97
The history of the days we noticed the issue. One thing I want to point out is that unicasting doesn’t throw that error.
| 2119 | [2026-03-05 09:22:52] Task ID: Name: Multiple Snapin -- orig Single has failed to save. Error: Required database field is empty: hostID | iina | 2026-03-05 09:22:52 | 10.24.193.157 |
| 2120 | [2026-03-05 09:23:03] Task ID: 3714 NAME: Wake-Up Task - 6037-GOLD 2026-03-05 09:23:03 has been successfully updated. | fog | 2026-03-05 09:23:03 | 172.28.172.92 |
| 2122 | [2026-03-05 09:23:04] Task ID: 3714 NAME: Wake-Up Task - 6037-GOLD 2026-03-05 09:23:03 has been successfully updated. | fog | 2026-03-05 09:23:04 | 172.28.172.92 |
| 2123 | [2026-03-05 09:23:54] Task ID: Name: Multiple Snapin -- orig Single has failed to save. Error: Required database field is empty: hostID | iina | 2026-03-05 09:23:54 | 10.24.193.157 |
| 2124 | [2026-03-05 10:27:19] ScheduledTask ID: 4 NAME: Multi-Cast Task has been successfully updated. | le.do | 2026-03-05 10:27:19 | 10.24.193.251 |
| 2125 | [2026-03-05 10:34:39] ScheduledTask ID: 5 NAME: Multi-Cast Task has been successfully updated. | le.do | 2026-03-05 10:34:39 | 10.24.193.251 |
| 2126 | [2026-03-05 14:26:47] Group ID: 42 NAME: sysprep-test-5004 has been successfully updated. | fog | 2026-03-05 14:26:47 | 172.28.171.22 |
| 2127 | [2026-03-05 14:27:16] Group ID: 42 NAME: sysprep-test-5004 has been successfully updated. | fog | 2026-03-05 14:27:16 | 172.28.171.22 |
| 2128 | [2026-03-05 14:58:43] Group ID: 42 NAME: sysprep-test-5004 has been successfully updated. | le.do | 2026-03-05 14:58:43 | 10.24.193.251 |
| 2129 | [2026-03-05 15:04:36] ScheduledTask ID: 10 NAME: Multi-Cast Task has been successfully updated. | le.do | 2026-03-05 15:04:36 | 10.24.193.251 |
| 2130 | [2026-03-05 15:08:03] Group ID: 42 NAME: sysprep-test-5004 has been successfully updated. | le.do | 2026-03-05 15:08:03 | 10.24.193.251 |
| 2131 | [2026-03-05 15:08:39] ScheduledTask ID: 11 NAME: Multi-Cast Task has been successfully updated. | le.do | 2026-03-05 15:08:39 | 10.24.193.251 |
| 2132 | [2026-03-05 15:13:38] Group ID: 42 NAME: sysprep-test-5004 has been successfully updated. | le.do | 2026-03-05 15:13:38 | 10.24.193.251 |
| 2133 | [2026-03-05 15:15:50] ScheduledTask ID: 12 NAME: Multi-Cast Task has been successfully updated. | le.do | 2026-03-05 15:15:50 | 10.24.193.251 |
| 2134 | [2026-03-05 15:49:11] Group ID: 42 NAME: sysprep-test-5004 has been successfully updated. | fog | 2026-03-05 15:49:11 | 172.28.172.92 |
| 2135 | [2026-03-05 16:13:34] Group ID: 42 NAME: sysprep-test-5004 has been successfully updated. | fog | 2026-03-05 16:13:34 | 172.28.171.193 |
| 2136 | [2026-03-05 16:13:47] MulticastSession ID: 141 NAME: Multi-Cast Task - sysprep-test-5004 2026-03-05 16:13:46 has been successfully updated. | fog | 2026-03-05 16:13:47 | 172.28.171.193 |
| 2137 | [2026-03-06 09:15:12] Group ID: 41 NAME: Le.Do (api-test) has been successfully updated. | le.do | 2026-03-06 09:15:12 | 10.24.193.251 |
| 2138 | [2026-03-06 09:15:27] ScheduledTask ID: 14 NAME: Multi-Cast Task has been successfully updated. | le.do | 2026-03-06 09:15:27 | 10.24.193.251 |
| 2139 | [2026-03-06 09:18:47] ScheduledTask ID: 15 NAME: Multi-Cast Task has been successfully updated. | le.do | 2026-03-06 09:18:47 | 10.24.193.251 |
| 2140 | [2026-03-06 09:45:04] Group ID: 42 NAME: sysprep-test-5004 has been successfully updated. | fog | 2026-03-06 09:45:04 | 172.28.172.92 |
| 2141 | [2026-03-06 09:45:21] MulticastSession ID: 142 NAME: Multi-Cast Task - sysprep-test-5004 2026-03-06 09:45:21 has been successfully updated. | fog | 2026-03-06 09:45:21 | 172.28.172.92 |
| 2142 | [2026-03-06 10:37:18] Group ID: 41 NAME: Le.Do (api-test) has been successfully updated. | le.do | 2026-03-06 10:37:18 | 10.24.193.251 |
| 2143 | [2026-03-06 10:37:32] ScheduledTask ID: 16 NAME: Multi-Cast Task has been successfully updated. | le.do | 2026-03-06 10:37:32 | 10.24.193.251 |
| 2144 | [2026-03-06 11:11:22] ScheduledTask ID: 17 NAME: Multi-Cast Task has been successfully updated. | fog | 2026-03-06 11:11:22 | 172.28.172.92 |
| 2145 | [2026-03-06 12:10:27] ScheduledTask ID: 18 NAME: Multi-Cast Task has been successfully updated. | fog | 2026-03-06 12:10:27 | 172.28.172.92 |
| 2146 | [2026-03-06 12:20:58] ScheduledTask ID: 19 NAME: Multi-Cast Task has been successfully updated. | fog | 2026-03-06 12:20:58 | 172.28.172.92 |
| 2147 | [2026-03-06 12:39:43] Group ID: 42 NAME: sysprep-test-5004 has been successfully updated. | fog | 2026-03-06 12:39:43 | 172.28.171.193 |
| 2148 | [2026-03-06 12:39:59] MulticastSession ID: 145 NAME: Multi-Cast Task - sysprep-test-5004 2026-03-06 12:39:58 has been successfully updated. | fog | 2026-03-06 12:39:59 | 172.28.171.193 |
| 2149 | [2026-03-06 15:50:17] ScheduledTask ID: 20 NAME: Multi-Cast Task has been successfully updated. | le.do | 2026-03-06 15:50:17 | 10.24.193.251 |
| 2150 | [2026-03-06 16:21:15] ScheduledTask ID: 22 NAME: Multi-Cast Task has been successfully updated. | le.do | 2026-03-06 16:21:15 | 10.24.193.251 |
| 2151 | [2026-03-09 09:19:06] Task ID: Name: Multiple Snapin -- orig Single has failed to save. Error: Required database field is empty: hostID | iina | 2026-03-09 09:19:06 | 10.24.193.58 |
| 2152 | [2026-03-09 09:19:14] Host ID: 66 NAME: 6037-GOLD has been successfully updated. | iina | 2026-03-09 09:19:14 | 10.24.193.58 |
| 2153 | [2026-03-09 09:19:25] Task ID: Name: Multiple Snapin -- orig Single has failed to save. Error: Required database field is empty: hostID | iina | 2026-03-09 09:19:25 | 10.24.193.58 |
+------+---------------------------------------------------------------------------------------------------------------------------------------------+----------+---------------------+----------------+
@Tom-Elliott Hi Tom, Sorry, my bad. I don’t get Login incorrect message. Mine is saying, No active task found for Host <Hostname>. But the error is the same, could not Update database. Also, I am using the latest working-1.6.
I don’t know if these errors are relevant, but my Multicast was around 12:30.
masih@fog:~$ sudo tail -n 200 /var/log/apache2/error.log
[Fri Mar 06 00:00:03.749336 2026] [mpm_prefork:notice] [pid 119135] AH00163: Apache/2.4.52 (Ubuntu) OpenSSL/3.0.2 configured -- resuming normal operations
[Fri Mar 06 00:00:03.749408 2026] [core:notice] [pid 119135] AH00094: Command line: '/usr/sbin/apache2'
[Fri Mar 06 09:45:22.809081 2026] [proxy_fcgi:error] [pid 188212] [client 172.28.172.92:11308] AH01071: Got error 'PHP message: PHP Warning: Undefined array key "hostID" in /var/www/html/fog/lib/router/route.class.php on line 2733PHP message: PHP Warning: Undefined array key "msaID" in /var/www/html/fog/lib/router/route.class.php on line 2515PHP message: PHP Warning: Undefined array key "hostID" in /var/www/html/fog/lib/router/route.class.php on line 2733PHP message: PHP Warning: Undefined variable $stat in /var/www/html/fog/lib/fog/group.class.php on line 772', referer: http://fog/fog/management/index.php?node=group&sub=edit&id=42
[Fri Mar 06 10:11:51.346904 2026] [proxy_fcgi:error] [pid 148942] [client 172.28.1.83:58320] AH01071: Got error 'PHP message: PHP Warning: Undefined array key "hostID" in /var/www/html/fog/lib/router/route.class.php on line 2733PHP message: PHP Warning: Undefined array key "msaID" in /var/www/html/fog/lib/router/route.class.php on line 2515PHP message: PHP Warning: Undefined array key "hostID" in /var/www/html/fog/lib/router/route.class.php on line 2733PHP message: PHP Warning: Undefined variable $stat in /var/www/html/fog/lib/fog/group.class.php on line 772'
[Fri Mar 06 11:00:16.168016 2026] [mpm_prefork:notice] [pid 119135] AH00170: caught SIGWINCH, shutting down gracefully
[Fri Mar 06 11:00:55.671950 2026] [mpm_prefork:notice] [pid 845] AH00163: Apache/2.4.52 (Ubuntu) OpenSSL/3.0.2 configured -- resuming normal operations
[Fri Mar 06 11:00:55.675999 2026] [core:notice] [pid 845] AH00094: Command line: '/usr/sbin/apache2'
[Fri Mar 06 11:27:39.854967 2026] [proxy_fcgi:error] [pid 895] [client 172.28.172.92:43525] AH01067: Failed to read FastCGI header, referer: http://fog/fog/management/index.php?node=task&sub=activescheduled
[Fri Mar 06 11:27:39.855265 2026] [proxy_fcgi:error] [pid 895] (104)Connection reset by peer: [client 172.28.172.92:43525] AH01075: Error dispatching request to : , referer: http://fog/fog/management/index.php?node=task&sub=activescheduled
[Fri Mar 06 11:27:39.907972 2026] [mpm_prefork:notice] [pid 845] AH00170: caught SIGWINCH, shutting down gracefully
[Fri Mar 06 11:27:49.405096 2026] [mpm_prefork:notice] [pid 4373] AH00163: Apache/2.4.52 (Ubuntu) OpenSSL/3.0.2 configured -- resuming normal operations
[Fri Mar 06 11:27:49.405283 2026] [core:notice] [pid 4373] AH00094: Command line: '/usr/sbin/apache2'
[Fri Mar 06 11:39:00.840026 2026] [mpm_prefork:notice] [pid 4373] AH00170: caught SIGWINCH, shutting down gracefully
[Fri Mar 06 11:39:35.371742 2026] [mpm_prefork:notice] [pid 840] AH00163: Apache/2.4.52 (Ubuntu) OpenSSL/3.0.2 configured -- resuming normal operations
[Fri Mar 06 11:39:35.372374 2026] [core:notice] [pid 840] AH00094: Command line: '/usr/sbin/apache2'
[Fri Mar 06 12:39:59.781079 2026] [proxy_fcgi:error] [pid 1514] [client 172.28.171.193:43267] AH01071: Got error 'PHP message: PHP Warning: Undefined array key "hostID" in /var/www/html/fog/lib/router/route.class.php on line 2733PHP message: PHP Warning: Undefined array key "msaID" in /var/www/html/fog/lib/router/route.class.php on line 2515PHP message: PHP Warning: Undefined array key "hostID" in /var/www/html/fog/lib/router/route.class.php on line 2733PHP message: PHP Warning: Undefined variable $stat in /var/www/html/fog/lib/fog/group.class.php on line 772', referer: http://fog/fog/management/index.php?node=group&sub=edit&id=42```@JGeear, I have the same problem. But I’m running the latest 1.6-working version.
@Tom-Elliott Hi Tom,
Thank you, that clarifies a lot. I now understand that hostSecTime represents the expiration time, not the creation time, which fully explains the consistent +30 minute offset I was seeing. That part now makes sense and resolves my question.
The only remaining actual issue I’m trying to understand is the snapin behavior: in several cases, snapins did not execute on some hosts. I don’t see any errors in the logs. Only that the snap-in task doesn’t start, but I will work on this and gather some more data. Thank you!