locked
SCCM Client 5.00.8239.1000 on Windows 10 RRS feed

  • Question

  • Hi People,<o:p></o:p>

    We are starting to install windows 10 in de company and working with SCCM 2012 R2 SP1 5.00.8239.1000. Installing windows 10 goes fine but the client is unable to retrieve the available software software. The corporate name on the top right is also not visible. <o:p></o:p>

    Is there an update for a new Windows 10, or is something misconfigured?<o:p></o:p>

    Thanks

    Michael<o:p></o:p>

    <o:p></o:p>

    Thursday, October 27, 2016 12:41 PM

Answers

  • What version of Windows 10? 

    2012 R2 SP1 only supports 2015 LTSB, 1507, and 1511. Anything beyond those requires ConfigMgr Current Branch (CB) 1606.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Marked as answer by Michael Hgend Thursday, October 27, 2016 3:11 PM
    Thursday, October 27, 2016 1:56 PM

All replies

  • That indicates that the Client did not receive (yet) policies from the Management Point. You'd have to check the Client logs why this is happening. Also Keep in mind that Win10 Anniversary Update is oficially not supported with CM12.

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

    Thursday, October 27, 2016 12:46 PM
  • Torsten,

    Thanks for the reply, have been checking the logs multiple times. Can you guide me to the right one? I was looking in the PolicyEvaluator and it is booming, he keeps adding records. But after more the two hours no result.

    Thursday, October 27, 2016 1:18 PM
  • locationservices and clientlocation if an MP is found. ccmmessaging if communication to the MP is fine.

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

    Thursday, October 27, 2016 1:21 PM
  • Just checked the ClientLocation log, and there he sais"Current Assigned Management Point...." so he is connect to the MP.

    The Commmessaging log show's 

    Initialized queue processor 'mp_mp_ddrendpoint'. Enabled=true Concurrency=1

    CcmMessaging 10/27/2016 3:14:10 PM

    1260 (0x04EC)

    Initializing queue 'mp_mp_relayendpoint'...

    CcmMessaging 10/27/2016 3:14:10 PM

    1260 (0x04EC)

    Queue 'mp_mp_relayendpoint' initialized with 0 messages.

    CcmMessaging 10/27/2016 3:14:10 PM

    1260 (0x04EC)

    Initialized queue processor 'mp_mp_relayendpoint'. Enabled=true Concurrency=1

    CcmMessaging 10/27/2016 3:14:10 PM

    1260 (0x04EC)

    Initializing queue 'mp_statusreceiver'...

    CcmMessaging 10/27/2016 3:14:10 PM

    1260 (0x04EC)

    Queue 'mp_statusreceiver' initialized with 0 messages.

    CcmMessaging 10/27/2016 3:14:10 PM

    1260 (0x04EC)

    Initialized queue processor 'mp_statusreceiver'. Enabled=true Concurrency=1

    CcmMessaging 10/27/2016 3:14:10 PM

    1260 (0x04EC)

    Initializing queue 'mp_[http]mp_locationmanager'...

    CcmMessaging 10/27/2016 3:14:10 PM

    1260 (0x04EC)

    Queue 'mp_[http]mp_locationmanager' initialized with 0 messages.

    CcmMessaging 10/27/2016 3:14:10 PM

    1260 (0x04EC)

    Initialized queue processor 'mp_[http]mp_locationmanager'. Enabled=true Concurrency=1

    CcmMessaging 10/27/2016 3:14:10 PM

    1260 (0x04EC)

    Initializing queue 'mp_[http]mp_policymanager'...

    CcmMessaging 10/27/2016 3:14:10 PM

    1260 (0x04EC)

    Queue 'mp_[http]mp_policymanager' initialized with 0 messages.

    CcmMessaging 10/27/2016 3:14:10 PM

    1260 (0x04EC)

    Is the 0 message part wrong ?


    Thursday, October 27, 2016 1:49 PM
  • What version of Windows 10? 

    2012 R2 SP1 only supports 2015 LTSB, 1507, and 1511. Anything beyond those requires ConfigMgr Current Branch (CB) 1606.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Marked as answer by Michael Hgend Thursday, October 27, 2016 3:11 PM
    Thursday, October 27, 2016 1:56 PM
  • Well that did the trick. Just updated windows 10 to 1607. Will stop trying then. 

    Earlier this morning  i updated SCCM to 1511 just returned to a snapshot because of time, but there we had an issue that the software center wound load in software after 2 hours. He did manage to load some policy’s because I saw the corporate name but still no software.

    Any clue’s , or log files i can check ? 

    Thanks

    Michael

    Thursday, October 27, 2016 2:05 PM
  • Reverted to a snapshot? Please explain this as this is totally unsupported and could cause you further issues.

    This sounds like a new issue though for which you should open a new forum thread.

    Also, as noted, for full Win 10 1607 support, you need to be on CB 1606, not 1511. You can directly upgrade to 1606 using the new baseline media made available recently.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Thursday, October 27, 2016 2:39 PM
  • Before I update the live environment I do the upgrade on the test environment.  Normally the snapshot won’t give us any problem because the sql en app are on the same server. I will create another topic for those issue’s. Thanks for the help

    Thursday, October 27, 2016 3:11 PM