@Tom-Elliott Regarding the snapin issue: you mentioned that I would not be able to deploy a snapin to a host unless that snapin is associated with the host.
I may be misunderstanding how these settings work, so here is how I am interpreting them:
For example, the 5002-PC01 is not associated with any snapin, yet I can still deploy a snapin to the group where this host belongs, and that host successfully applies the snapin.
Screenshot 2026-03-10 095309.png
For the group, however, I do not see those association checkboxes. This is a bit confusing because the snapin deployment anyways, is successful for most hosts in that group. Only a few fail.
Screenshot 2026-03-10 095415.png
The reason I have not associated the hosts with the snapin is that, in the past, whenever we deployed an image, those snapins would run automatically, even when we did not need them at that time.
The log on the host with faild snapin deployment:
---------------------------------SnapinClient--------------------------------- ------------------------------------------------------------------------------ 10/03/2026 10.07.27 Client-Info Client Version: 0.13.0 10/03/2026 10.07.27 Client-Info Client OS: Windows 10/03/2026 10.07.27 Client-Info Server Version: 1.6.0-beta.2273 10/03/2026 10.07.27 Middleware::Response ERROR: Unable to get subsection 10/03/2026 10.07.27 Middleware::Response ERROR: Object reference not set to an instance of an object.