I found a 6.0 document that said to schedule them both on the same client task but make sure EEAGENT is first. I did this. It ran, EEAGENT Completed. EEPC did not. User gets reboot prompt reboots , EEPC instals, user gets prompted again. Reboots. Now 6.21 is installed too.
Is this how its supposed to work ? Anyway to get it down to one prompt one reboot ?
I guess there is no other way...I've done it like you.
One client task to deploy both the 1.2.1 agent and the 6.2.1 eepc software.
2 reboots are required as described in the migration guide
we use the following settings within the client taks for the EEPC Agent update:
With this setting it is only needed one reboot.
And we do work with tags and queries. Create 2 tags: e.g. ee_agent1.2.1-update and ee_eepc6.2.1-update
Create a query which filter all systems where the ee agent is version 184.108.40.2065 or 1.2.1 and it has tag ee_agent1.2.1-update and not tag ee_eepc6.2.1-update
The query should run every 15 minutes (server task). Systems which are in the query then are tagged with tag ee_eepc6.2.1-update.
Create 2 client tasks:
1) one with ee agent 220.127.116.115 which runs only if the client system has tag ee_agent1.2.1-update
2) one with ee eepc 18.104.22.1685 which runs only if the client system has tag ee_eepc6.2.1-update and ee agent versions is 22.214.171.1245
So basically that should be everything in short words.