@Tom-Elliott Thx! I will try it out when RC9 comes!

@Tom-Elliott Sending an ‘All snapins’ task every time is not a solution for us, because some installers don’t react well if they’re already installed on the host

@Tom-Elliott We are running the latest RC8. I understand what you mean in terms of tasking, i’m just saying that it used to work like that from versions 0.32 till 1.20 (before we updated to the RC’s). I often sent two or more single snapins, they each had their own task in ‘Active snapins’ and they got executed one after another in the order that I had sent them. Now, only the last one gets executed, the other keeps hanging in the active tasks and stays ‘Queued’

When deploying two single snapins to a host only the last snapin gets executed. The first one disappears from the Active Snapin Tasks and remains indefinitely in the Active Tasks list.

However when you make a ‘Send all snapins’ task on a host every snapin appears as it’s own task in ‘Active snapin tasks’

I think it makes sense that every snapin I send creates a seperate task that needs to be executed. This is especially true if you have multiple admins that may be responsible for different snapins. Why would one of the snapins be cancelled like that? Doesn’t make sense to me.

It used to work like that before we upgraded to the RC’s