Hey Jason,
for some background and ammo for you, we have an environment with thousands of distribution points spread across Australia servicing their local subnets.
Our links are so bad to these sites, that in SCCM 2007, client push was not feasible except in one off type remediation scenarios, because the client package always came from the site server.
In SCCM 2012, one of the changes that is really great for us is that client push will leverage the local DP for the client package files, so I've been testing this.
Adding the PATCH= property to the client push command line means hardcoding the location of the patch file. Thats fine if you're pushing from the site server ala 2007, but that means it wont leverage the patch files on the local DP.
I know there are other supported methods, we can use a dynamic collection with a query based on client version and a mandatory deployement of the patch etc, but this seemed like a solution that would cater for the local DP requirement, work for client push,
and work for OSD task sequences without modifying command lines or using scripts.
Essentially, if it works, this is a perfect "out of the box" type scenario.
*Edit* - also, if you review the ccmsetup log, the patches are applied last. They dont get appended to the client.msi cmd line. I'm not sure if thats different to how 2007 worked, but if it is, then maybe it wont affect cmd line switches anymore ?
Cheers,
Matt
