locked
SCCM 2012 R2 and WSUS Configuration RRS feed

  • Question

  • I am fairly new to ConfigMgr in general. I have recently installed Configuration Manger 2012 R2 in our office setting. I am using the existing WSUS infrastructure. I have downloaded the console on the SCCM server and i have populated the software updates with the updates but when I try to manually download updates to deploy manually i get nothing but errors. The WCM and wsyncmgr logs have no errors. The errors I am getting are in the WSUSCtrl log and the compmon log.

    The WSUSCtrl log show the following:

    Failed to read the required Operations Management component registry key values on SCCM.gccoop.local; error = 6 (0x6). SMS_WSUS_CONTROL_MANAGER 4/28/2014 2:14:52 PM 5948 (0x173C)
    Failed to read in current property values and initialize COpsMgmtComponent object; error = 6 (0x6). SMS_WSUS_CONTROL_MANAGER 4/28/2014 2:14:52 PM 5948 (0x173C)
    Failed to generate heartbeat for component 'SMS_WSUS_CONTROL_MANAGER' because the COpsMgmtComponent object is uninitialized. SMS_WSUS_CONTROL_MANAGER 4/28/2014 2:14:52 PM 5948 (0x173C)

    The compmon log shows the following:


    Failed to read the required Operations Management component registry key values on local computer; error = 6 (0x6). SMS_COMPONENT_MONITOR 4/30/2014 11:04:37 AM 3168 (0x0C60)
    Failed to read in current property values and initialize COpsMgmtComponent object; error = 6 (0x6). SMS_COMPONENT_MONITOR 4/30/2014 11:04:37 AM 3168 (0x0C60)


    I haven't had much luck looking for answers so any little bit of help would be greatly appreciated! Thanks.

    Monday, May 5, 2014 1:37 PM

Answers

  • I was able to download updates manually by uninstalling the WSUS Console and re-installing it, but WSUSCtlr.log is still showing the same error message. I am honestly disappointed in help I received from the "expert" the whole point of new versions of ConfigMgr is to make it more convenient, such as using an existing WSUS structure and I feel as there isn't enough information out here on how to configure it and such.  
    • Marked as answer by x-25 Tuesday, May 6, 2014 4:15 PM
    Tuesday, May 6, 2014 4:14 PM

All replies

  • What does supsetup.log tell? Was the installation of the SUP successful at all? (You should not use an existing WSUS BTW)

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

    Monday, May 5, 2014 2:01 PM
  • The SUP installation was successful and I am receiving all the metadata that populates the software library. The supsetup.log shows no errors what so ever and I am able to communicate with the WSUS server so I can't figure out where my issue lies.
    Monday, May 5, 2014 4:00 PM
  • I was recently told that WSUS 3.0 SP2 isn't compatible with Windows Server 2012 and i have installed the WSUS 3.0 SP2 console on a Windows Server 2012. Could that be the reason I can't get ConfigMgr to deploy updates the way it should? 
    Monday, May 5, 2014 4:55 PM
  • I was able to download updates manually by uninstalling the WSUS Console and re-installing it, but WSUSCtlr.log is still showing the same error message. I am honestly disappointed in help I received from the "expert" the whole point of new versions of ConfigMgr is to make it more convenient, such as using an existing WSUS structure and I feel as there isn't enough information out here on how to configure it and such.  
    • Marked as answer by x-25 Tuesday, May 6, 2014 4:15 PM
    Tuesday, May 6, 2014 4:14 PM