Best posts made by bluenix

It would be great if the storage node to use for imaging / snapins could automatically be determined based on the subnet of the requesting client.

This would be useful in a situation where computers are physically roaming between locations. If e.g. a snapin/image for that host is queued, it would make sense to download the snapin/image from the storage node that is in the current subnet.

In RC5, when you deploy a single snapin to a host, and deploy a second single snapin directly afterwards to the same host (before the first one is processed by the client), Active Snapin Tasks only shows the last deployed snapin as a task.

The following happens step by step:

1. Deploy single snapin A to host 1
2. Snapin A shows up in both Active Tasks and Active Snapin Tasks
3. Deploy snapin B to host 1
4. Snapin B shows up alongside snapin A in Active tasks, but replaced Snapin A in Active tasks
5. The client will install Snapin B and remove it from Active Snapin Tasks
6. Snapin A remains indefinitely queued in Active Tasks, never appears in Active Snapin tasks and never gets installed by the client (client logs no snapins found in c:\fog.log)