locked
SCCM 2012 WSUS some updates are not installed RRS feed

  • Question

  • Wsyncmgr.log
    sync: SMS synchronizing updates, processed 1899 out of 1899 items (100%) SMS_WSUS_SYNC_MANAGER 8/7/2014 3:17:02 PM 6892 (0x1AEC)
    sync: SMS performing cleanup SMS_WSUS_SYNC_MANAGER 8/7/2014 3:17:02 PM 6892 (0x1AEC)
    Done synchronizing SMS with WSUS Server ad.sccm.local SMS_WSUS_SYNC_MANAGER 8/7/2014 3:17:04 PM 6892 (0x1AEC)
    Set content version of update source {EA8258B6-64BB-4FC7-BEDC-0F677823FA36} for site P01 to 1 SMS_WSUS_SYNC_MANAGER 8/7/2014 3:17:04 PM 4844 (0x12EC)
    STATMSG: ID=6702 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=ad.SCCM.local SITE=P01 PID=2020 TID=4844 GMTDATE=Thu Aug 07 19:17:04.433 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 8/7/2014 3:17:04 PM 4844 (0x12EC)
    Sync succeeded. Setting sync alert to canceled state on site P01 SMS_WSUS_SYNC_MANAGER 8/7/2014 3:17:04 PM 4844 (0x12EC)
    No changes made to the SMS database, content version remains 1 SMS_WSUS_SYNC_MANAGER 8/7/2014 3:17:04 PM 4844 (0x12EC)
    Sync time: 0d00h05m27s SMS_WSUS_SYNC_MANAGER 8/7/2014 3:17:04 PM 4844 (0x12EC)

    I tried to resync the software lib and nothing changed tried to redeploy

    My issue some software updates make it to the client but not all.

    Server2008r2
    SCCM2012 Standalone
    WSUS 3.2.7600.226

    I dont have the foggiest where to start to trouble shoot.

    I also ran Wsusutil.exe reset

           

    • Moved by Lawrence Garvin Friday, August 8, 2014 2:47 AM another CM2012 SU question
    Thursday, August 7, 2014 8:52 PM

Answers

  • I don't see errors in the screenshots. After creating software update group you have to deploy it. In the first screenshot seems that you have downloaded updates but not deployed.
    http://myitforum.com/cs2/blogs/nbrady/archive/2011/11/06/using-sccm-2012-rc-in-a-lab-part-6-deploying-software-updates.aspx
    Friday, August 8, 2014 7:58 AM
  • You should never go into the WSUS admin console and perform any administrative actions whatsoever. Approvals in WSUS have nothing to do with ConfigMgr deploying updates. WSUS integrated into ConfigMgr serves one purpose only: the download and distribution of the update catalog in it entirety (OK, that's two actually).

    To deploy updates using ConfigMgr, you need to create Software Update Groups and deploy them.


    Jason | http://blog.configmgrftw.com

    • Marked as answer by Daniel JiSun Wednesday, September 10, 2014 3:11 AM
    Monday, August 11, 2014 2:25 PM

All replies

  • Thursday, August 7, 2014 8:52 PM
  • Thursday, August 7, 2014 8:53 PM
  • I don't see errors in the screenshots. After creating software update group you have to deploy it. In the first screenshot seems that you have downloaded updates but not deployed.
    http://myitforum.com/cs2/blogs/nbrady/archive/2011/11/06/using-sccm-2012-rc-in-a-lab-part-6-deploying-software-updates.aspx
    Friday, August 8, 2014 7:58 AM
  • The odd thing is i created a software group and deployed it well tried to but all of them dont make it to the client PC. I will follow your suggestion on the link and report back thanks. 

    PS Correct I have no errors. 


    • Edited by Khloro Friday, August 8, 2014 1:27 PM spelling
    Friday, August 8, 2014 1:10 PM
  • I only see this once i followed directions

    Friday, August 8, 2014 2:24 PM
  • I then reboot
    • Edited by Khloro Friday, August 8, 2014 2:25 PM
    Friday, August 8, 2014 2:25 PM
  • Friday, August 8, 2014 2:29 PM
  • What's your search criteria when creating the SU Group? Check against what is in the group and what is actually required for that device. The client will only install what is relevant.

    Cheers

    Paul | sccmentor.wordpress.com

    Friday, August 8, 2014 2:35 PM
  • Only updates that are applicable to the system will be shown and installed. Also, the client must refresh its machine policy to learn of new deployments -- by default this happens every 60 minutes.

    Jason | http://blog.configmgrftw.com

    Friday, August 8, 2014 2:40 PM
  • Question I might of found the issue. I noticed that yes i did filter windows 7 updates; but i noticed that in my software group i have windows 7 and 64 do i need to separate them?
    Friday, August 8, 2014 2:56 PM
  • No you can not separate by architecture.

    TBH I don't even separate out by O/S as the client device will only install updates applicable to itself. 


    Cheers

    Paul | sccmentor.wordpress.com


    Friday, August 8, 2014 2:57 PM
  • I got it working but I have a few questions to ask.

    When I went to my WSUS i approved the downloads they all did get install Via SCCM. I thought SCCM would deploy them as it should but do i always have to manual select approved download updates in order for SCCM to push out the updates? 

    Is there a setting that i need to change for sccm to download without approval via WSUS?

    Monday, August 11, 2014 2:07 PM
  • You should never go into the WSUS admin console and perform any administrative actions whatsoever. Approvals in WSUS have nothing to do with ConfigMgr deploying updates. WSUS integrated into ConfigMgr serves one purpose only: the download and distribution of the update catalog in it entirety (OK, that's two actually).

    To deploy updates using ConfigMgr, you need to create Software Update Groups and deploy them.


    Jason | http://blog.configmgrftw.com

    • Marked as answer by Daniel JiSun Wednesday, September 10, 2014 3:11 AM
    Monday, August 11, 2014 2:25 PM
  • WSUS should not be configured when running with SCCM. SCCM manages the WSUS component. How was WSUS set up when installed?

    Cheers

    Paul | sccmentor.wordpress.com

    Monday, August 11, 2014 2:25 PM
  • Thank you for the clerification

    Here is how i configured my WSUS 

    http://www.windows-noob.com/forums/index.php?/topic/4427-using-sccm-2012-rc-in-a-lab-part-2-add-sup-and-wds/

    If my WSUS is forcing me to do approvals. How would I change it to have WSUS get approval from SCCM ?

    Would I need to reinstall WSUS?

    Thank you all again trying to learn as much as i can before going to a class @ new horizons.

    Monday, August 11, 2014 2:54 PM
  • Not sure what you mean by "forcing you to do approvals". Is it twisting your arm? As mentioned, you should never go into the WSUS console in the first place.

    Also as mentioned, WSUS is used only for its ability to download and distribute the update catalog, nothing more. It does not in any way actually distribute or deploy updates themselves. Thus, there's no need for WSUS to get "approvals" from ConfigMgr (there's actually no such thing in ConfigMgr).

    Also as mentioned, to deploy updates in ConfigMgr, you need to create Software Update Groups and deploy them.

    At this point, if you have approved updates in WSUS, yes, you should just completely uninstall it and reinstall it. You should remove your software update point first though. You do have a software update point in ConfigMgr, correct?


    Jason | http://blog.configmgrftw.com

    Monday, August 11, 2014 3:27 PM
  • Jason,

    Thanks I will reinstall WSUS and I do have a Distribution point. As for Forcing you to do approvals. I was trying to explain that i found it odd that not all updates are getting installed even after I created the Software Group. I went into WSUS and approved the updates and they got installed Via SCCM. I will uninstall WSUS and try again.

    Monday, August 11, 2014 3:36 PM
  • Uninstall the SUP first then WSUS. Do not run any admin from within the WSUS console. Use ConfigMgr for all SU related activity.

    Cheers

    Paul | sccmentor.wordpress.com

    Monday, August 11, 2014 3:46 PM
  •  I went into WSUS and approved the updates and they got installed Via SCCM.

    This is coincidental (unless of course you had previously gone into WSUS and declined those updates). The two are completely unrelated.

    Jason | http://blog.configmgrftw.com

    Monday, August 11, 2014 4:09 PM
  • Thank you all for your advice. Ill report in once i have reinstalled my WSUS.
    Monday, August 11, 2014 5:51 PM