Microsoft release Rollup update for System Center Configuration manager and they will normally also include a client update.
But if you do nothing and just use a standard task sequence your client version will be the one released together with SCCM 2012 R2.
As shown her (all versions are 5.00.7958.1000):
There are a lot of ways around this problem but lets take a closer look on a fairly simple one using OSD:
I our Task Sequence, just before Setup Windows and Configuration Manager, we can copy the current MSP patch from the latest Rollup to a local folder.
xcopy configmgr2012ac-r2-kb3054451-x64.msp C:WindowsSCCMHotfix /E /H /C /I /Q /Y
You will be able to find the name of the MSP file in the latest update in the hotfix folder of your SCCM 2012 R2 installation:
You can see the KB number needed on the source folder on the latest RollUP package – if in doubt:
Now use the PATCH property with the local path to the MSP file:
And when trying the Task Sequence again the client is updated as shown her:
In the above I used the x64 version, you must of course use the correct file name, matching your version (x64 or x86).
Using hardcoded c: might not always be the best solution, so if you experience problems you could go for the OSDISK variable to control the destination: