Client push deployment and CU / hotfix install

Question

I'm trying to figure out a way to do a push install of the 2012 client, CU update, and hotfixes all in one go.  I know using the ClientPatch folder method is not supported, but I'm wondering if another way would work.
1) When you do a client push install from the console, does it use BITS?
2) Does it directly use the files in Program Files\Microsoft Configuration Manager\Client on the site server, or the SCCM client package?
3) Could you create a Hotfixes folder under the Client folder, put the CU / hotfixes in there, then use the PATCHES property to point to C:\Windows\ccmsetup\hotfixes\%PROCESSOR_ARCHITECHTURE%\hotfixname.msp?
I know you can use SCUP or packages to do the updates, but it would be much easier to do it all at once.  Hence the reason why so many people still use the ClientPatch folder, I guess.  I really wish they'd make that a supported option.

Answer 1

1. No, the initial push portion is a straight SMB copy to the target client. However, that only copies a bootstrapper, ccmsetup, which in turn kicks off on the client to download the rest of the necessary files. The download by ccmsetup does use BITS though.
2. ccmsetup downloads the necessary files from the package on the proper distribution point (although it will fallback to the MP where it would be ultimately pulling from the client folder location.
3. Yes, you could create the folder but that would not cause it to be copied to target client. The files it downloads are a fixed list.
The most you could do is add it to the client push properties but that is problematic because the patches are architecture specific. Thus, there really is no good way to do this using client push.
A client startup script however offers many advantages including being able to do this.
Jason | http://blog.configmgrftw.com | @jasonsandys