locked
SCCM Client R2 CU3 in OSD RRS feed

  • Question

  • Our base image was created using SCCM build and capture. I created the base image using sccm client 2012 SP1 ( 5.00.7804.1300). Now, we recently upgraded to SCCM 2012 R2 CU3 and we would like to update our deployment production task sequence with the config manager client package so that the machine will pick up the new client version after the build. Upon testing, I always encounter an incomplete build. After the installation of the sccm client, the ts stops and will show the login window. The ccmsetup.log indicates a successful installation of the client as it  exits with a return code of 0. I have a gut feeling that the sccm client was upgraded and was not able to save the task sequence which caused the task sequence to stop. Any idea on why the build stops after the installation of the client and how to resolve the issue?
    Wednesday, December 17, 2014 8:46 AM

Answers

  • Have you modified the task sequence somehow? If so: how? The client package being used should automatically be updated and used in the task sequence so you will end up having an R2 client installed during the OSD task sequence. You only have to modify 'Setup Windows and ConfigMgr' in order to add CU3. 

    Torsten Meringer | http://www.mssccmfaq.de

    • Marked as answer by Daniel JiSun Monday, December 29, 2014 9:48 AM
    Wednesday, December 17, 2014 9:09 AM
  • You can follow this post to configure CU3 in OSD.

    http://sccmfaq.wordpress.com/2013/09/24/sccm-2012-include-cu-in-osd/


    Nick Pilon | Blog : System Center Dudes

    • Marked as answer by Daniel JiSun Monday, December 29, 2014 9:48 AM
    Wednesday, December 17, 2014 1:45 PM
  • Follow the guide to patch your client during the OSD but check your smsts.log file for any errors that cause the TS to bomb out after client install. You may get the same problem, even if patching the client, if there is something wrong with the underlying TS.

    Cheers

    Paul | sccmentor.wordpress.com

    • Marked as answer by Daniel JiSun Monday, December 29, 2014 9:48 AM
    Wednesday, December 17, 2014 2:41 PM

All replies

  • Have you modified the task sequence somehow? If so: how? The client package being used should automatically be updated and used in the task sequence so you will end up having an R2 client installed during the OSD task sequence. You only have to modify 'Setup Windows and ConfigMgr' in order to add CU3. 

    Torsten Meringer | http://www.mssccmfaq.de

    • Marked as answer by Daniel JiSun Monday, December 29, 2014 9:48 AM
    Wednesday, December 17, 2014 9:09 AM
  • You can follow this post to configure CU3 in OSD.

    http://sccmfaq.wordpress.com/2013/09/24/sccm-2012-include-cu-in-osd/


    Nick Pilon | Blog : System Center Dudes

    • Marked as answer by Daniel JiSun Monday, December 29, 2014 9:48 AM
    Wednesday, December 17, 2014 1:45 PM
  • Follow the guide to patch your client during the OSD but check your smsts.log file for any errors that cause the TS to bomb out after client install. You may get the same problem, even if patching the client, if there is something wrong with the underlying TS.

    Cheers

    Paul | sccmentor.wordpress.com

    • Marked as answer by Daniel JiSun Monday, December 29, 2014 9:48 AM
    Wednesday, December 17, 2014 2:41 PM