locked
Endpoint Protection stopped updating RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I was migrating to SCCM 2012 and things seemed to be ok. Then Endpoint Protection stopped updating.

    I found the below errors on one computers. I am not convinced this is from Endpoint Protection. However, these are the only errors on that computer.

    11759 Updates advance download job completed with failure for assignment {9f38c41c-bce0-4fb3-9ea7-43aefbceaaed}.

    11713 SMS internal error occurred for the update b8cc8f0b-3610-4f41-bfe8-38f99635f2f2.

    11713 SMS internal error occurred for the update 264567f6-aa54-4006-b79f-2634e45cdae2.

    11713 SMS internal error occurred for the update 000a432a-3dab-4384-8348-9bb52ed2361d.

    Endpoint Protection agents are now using Windows update.

    Anyone have an idea as to what is going on?

    Thursday, July 5, 2012 10:24 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Tha; this turned out to be a problem with the update policy.

    In terms of what? This doesn't help others that might find this thread. Please add details so other can benefit, too.

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

    • Marked as answer by Carl M5646813 Thursday, January 31, 2013 7:15 PM
    Wednesday, July 18, 2012 7:13 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    That can be related to a BITS issue.

    1# Verify BITS for queued jobs or backlogs:
    bitsadmin.exe /list /allusers
    bitsadmin.exe /reset /allusers

    Or repair WU components http://support.microsoft.com/kb/971058/en-us

    2# Then reinstall the ConfigMgr 2012 client.

    Bechir Gharbi | My blog: @myITforum.com | Twitter: @Bechir_Gharbi | Linkedin: Bechir Gharbi | Time zone: GMT + 1

    Monday, July 16, 2012 12:40 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks for the information, however; this turned out to be a problem with the update policy.

    Wednesday, July 18, 2012 12:48 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Tha; this turned out to be a problem with the update policy.

    In terms of what? This doesn't help others that might find this thread. Please add details so other can benefit, too.

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

    • Marked as answer by Carl M5646813 Thursday, January 31, 2013 7:15 PM
    Wednesday, July 18, 2012 7:13 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    the problem with the update policy was an error in the path to the updates.

    Thursday, January 31, 2013 7:15 PM