1 of 1 people found this helpful
Well.. you can create a task to install the agent and then create a server task that runs a querry to find the computers with the up-to-date agent and move them to a subgroup where the client installation task is configured. Afterwars you'll have to manually move the clients back to their respective subgroups... so yes, there is a way to do this...kinda.
I thought about doing that, but we are georgraphically dispersed, so it might get a little dicey. I'll look in to this since it's really the only option I can see right now.
This really sucks though, it shouldn't require this much finagling to get this product properly installed.
This is the right approach, but I think tagging might be easier than moving systems between groups. I would go with a server task that identified systems with the up-to-date agent, then use that server task to tag the systems as "6.1 client ready". Then I'd create a deployment task that only target systems with that tag.