as the title states, I was wondering wether this is intended or some kind of bug.
When associating a new snapin to a host or group via the “Snapins” tab it queues all previously already associated snapins, even though they were already deployed and succesfully installed. It also seems to always create a new imaging task for the client when doing this, even though the client has long been imaged already. When this happens the imaging task starts but wont run by itself and blocks any further deploying of all kinds of snapins until manually cancelled. Which of course makes sense because we’re not starting a network boot again for an already productive client but in reverse as mentioned blocks all further deployment of snapins or tasks.
Is my understanding of that feature wrong? Should associating only be used for imaging tasks? We tried using it so hosts would automatically get the missing snapins associated to them, not a completey new imaging with all associated snapins.