At the moment, that's the way it works, I'm afraid. Update tasks take their branches from the agent policy. Unfortunately it looks like this is the same in ePO 4.6...
I guess the good news is that I wasn't missing something. Even if the bad news is that this was actually the design.
I think I'll submit a FMR around it. Even if it's by design and looks like it's the same way in 4.6, I think it can be done easier and more obviously. Just take the product update client task, and add an extra column to it to allow you to choose the desired branch. Who knows? Maybe someone else will agree with me
Maybe better would be wait for VSE 8.7 P4 repost and then install whole product form evaluation branch...
As far as I can tell, a client task to do a full install will not actually update machines that already have the product installed.
If I have a machine that is VSE 8.7p2 and I set up a product deployment task with VSE 8.7p3 this is what happens:InfoSchedulerScheduler: Invoking task [VSE 8.7i Product Deployment Task]...InfoUpdaterChecking update packages from repository ePOSA_PACHQCIS01.InfoUpdaterInitializing update...InfoUpdaterVerifying catalog.z.InfoUpdaterExtracting catalog.z.InfoUpdaterLoading update configuration from: catalog.xmlInfoUpdaterVerifying VSE870Det.McS.InfoUpdaterVerifying VSE870Det.McS.InfoUpdaterUpdate FinishedInfoSchedulerThe task VSE 8.7i Product Deployment Task is successfulInfoSchedulerScheduler: Task [VSE 8.7i Product Deployment Task] is finished
It just checks to see if VSE 8.7 is installed, then ends the task. It doesn't verify the patch level of the product. You have to have a seperate task to perform patch updates. In my perfect world, that task would allow you to select branches, but currently, you need to use the patch updater task in conjunction with an agent policy modification to do that.