locked
System Center Configuration Manager 2012 R2 CU3 Client stop to work RRS feed

  • Question

  • Hi Everyone,

    I've a strange problem with my SCCM 2012R2 cu3 environment.

    When I deploy my OSD TS, the client install itself with the version 1000.

    After the TS finish, the CU3 arrive and install itself.

    The strange thing, is that after 10-15min the client stop working.
    Under Actions you find only two options, and in the Software Center instead of having "MY COMPANY NAME" on the right corner, it's written: IT Organization.

    What could the problem be?

    Thanks

    Update: I've tryied to "push" the client to the faulty computer, and it worked.
    The strange thing is that after the OSD and cu3 update the client stop working.
    But if you reinstall it , it works.

    So what can the problem be?

    • Edited by TDA90 Wednesday, November 12, 2014 3:02 PM
    Wednesday, November 12, 2014 2:12 PM

Answers

  • Now is working again ... no clue what happend. :o
    • Marked as answer by TDA90 Friday, November 14, 2014 3:03 PM
    Friday, November 14, 2014 3:03 PM

All replies

  • Are you supplying the PATCH property in the task sequence to install the CU3 update directly?

    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

    Wednesday, November 12, 2014 7:35 PM
  • I've seen this behaviour before. It sounds like you are deploying an 'old' client in the TS and then when that build is done SCCM is upgrading the client afterwards which can display this in my experience. It should come good eventually though. As per Peters response that's one way around it by putting in the patch with the TS.

    See this for a bit more info too - http://blogs.technet.com/b/configmgr_geek_speak/archive/2013/09/09/using-configuration-manager-automatic-client-upgrade-to-upgrade-to-the-latest-system-center-endpoint-protection-client.aspx 

    Wednesday, November 12, 2014 8:36 PM
  • Hi,

    I deploy the CU3 after the TS has finished, not directly inside the OSD TS.

    That's because I have also old SCCM2007 client in my environment, that I will upgrade and they need the CU3 too.

    Thursday, November 13, 2014 7:05 AM
  • Hi,

    I deploy the CU3 after the TS has finished, not directly inside the OSD TS.

    That's because I have also old SCCM2007 client in my environment, that I will upgrade and they need the CU3 too.

    Thursday, November 13, 2014 7:05 AM
  • I do not see a connection between CM07 and CM12 here. Could you add some details please?
    Are there overlapping boundaries/groups for site assignment? Are you using distinct sitecodes?

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

    Thursday, November 13, 2014 11:22 AM
  • Now is working again ... no clue what happend. :o
    • Marked as answer by TDA90 Friday, November 14, 2014 3:03 PM
    Friday, November 14, 2014 3:03 PM