locked
Broke WSUS Sync after attempting to install MBAM on SCCM2012 server RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I attempted to install the new MBAM 2 on our SCCM2012 SP1 server and after which I broke client communications and the WSUS sync.  I believe it broke because I installs the MBAM website on port 80 which is the same port as the SCCM communicates.

    We noticed it when we first went to deploy an update for Java and the update didn't work and after I removed the MBAM website from the SCCM server software deployments began to work again.  Regretfully this did not seem to fix our WSUS sync issues.  Below is an excerpt from the WCM.log file.  I have marked the two lines which appear in RED on the log viewer as BOLD.  WSUS has been configured on port 80 since we installed SCCM 2012 SP1 and has worked just fine until yesterday when I installed MBAM at which time it broke and remains broke even after removing the MBAM web site which corrected our other client communication issues.

    Wait timed out after 60 minutes while waiting for at least one trigger event.    SMS_WSUS_CONFIGURATION_MANAGER    4/18/2013 8:01:33 AM    6944 (0x1B20)
    Timed Out...    SMS_WSUS_CONFIGURATION_MANAGER    4/18/2013 8:01:43 AM    6944 (0x1B20)
    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)    SMS_WSUS_CONFIGURATION_MANAGER    4/18/2013 8:01:43 AM    6944 (0x1B20)
    Checking runtime v2.0.50727...    SMS_WSUS_CONFIGURATION_MANAGER    4/18/2013 8:01:43 AM    6944 (0x1B20)
    Found supported assembly Microsoft.UpdateServices.Administration version 3.1.6001.1, file version 3.1.7600.256    SMS_WSUS_CONFIGURATION_MANAGER    4/18/2013 8:01:43 AM    6944 (0x1B20)
    Found supported assembly Microsoft.UpdateServices.BaseApi version 3.1.6001.1, file version 3.1.7600.256    SMS_WSUS_CONFIGURATION_MANAGER    4/18/2013 8:01:43 AM    6944 (0x1B20)
    Supported WSUS version found    SMS_WSUS_CONFIGURATION_MANAGER    4/18/2013 8:01:43 AM    6944 (0x1B20)
    Attempting connection to WSUS server: IMAGESERVER2.Bridgewater.local, port: 80, useSSL: False    SMS_WSUS_CONFIGURATION_MANAGER    4/18/2013 8:01:43 AM    6944 (0x1B20)

    System.Net.WebException: The request failed with HTTP status 404: Not Found.~~   at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)    SMS_WSUS_CONFIGURATION_MANAGER    4/18/2013 8:01:43 AM    6944 (0x1B20)

    Remote configuration failed on WSUS Server.    SMS_WSUS_CONFIGURATION_MANAGER    4/18/2013 8:01:43 AM    6944 (0x1B20)
    STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=IMAGESERVER2.Bridgewater.local SITE=BWC PID=4124 TID=6944 GMTDATE=Thu Apr 18 12:01:43.217 2013 ISTR0="IMAGESERVER2.Bridgewater.local" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0    SMS_WSUS_CONFIGURATION_MANAGER    4/18/2013 8:01:43 AM    6944 (0x1B20)
    Waiting for changes for 60 minutes    SMS_WSUS_CONFIGURATION_MANAGER    4/18/2013 8:01:43 AM    6944 (0x1B20)


    • Edited by AKlein Thursday, April 18, 2013 3:04 PM
    Thursday, April 18, 2013 2:07 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    You may be able to make it work but I wouldn't expect to get support from MS if it breaks. MBAM docs specifically say to use their own two servers. I'm not disagreeing that's silly to require a server to do nothing more than host a webservice but that's what MS says we should do.

    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

    • Proposed as answer by Garth JonesMVP Saturday, February 7, 2015 2:50 AM
    • Marked as answer by Garth JonesMVP Tuesday, October 27, 2015 4:29 PM
    Thursday, April 18, 2013 4:32 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    MBAM should be on it's on servers, that's two at a minimum. You should NOT be installing it on the ConfigMgr (or SCOM as your title says) server.

    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

    Thursday, April 18, 2013 3:02 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    To fix WSUS after you've removed MBAM reinstall WSUS.

    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

    Thursday, April 18, 2013 3:03 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Sorry I mistyped in my title.  Its an old internal joke here but I did fit the title going forward.

    The WSUS syncing seems to have 'fixed' itself as it just started to work again at some point since I posted the first message.  I had performed a full sync which worked correctly and the error messages in the log did not reoccur at the next scheduled update at 10:01 or 11:01.

    I was wondering why I couldn't install the MBAM web components on the SCCM server if I put it on a different port.  It seems a bit redicilous to isntall it on a different server when its just the web components.  The database is on our SQL server and I have already done the SCCM intergration components to install MBAM in a SCCM environment.

    Thursday, April 18, 2013 3:07 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    You may be able to make it work but I wouldn't expect to get support from MS if it breaks. MBAM docs specifically say to use their own two servers. I'm not disagreeing that's silly to require a server to do nothing more than host a webservice but that's what MS says we should do.

    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

    • Proposed as answer by Garth JonesMVP Saturday, February 7, 2015 2:50 AM
    • Marked as answer by Garth JonesMVP Tuesday, October 27, 2015 4:29 PM
    Thursday, April 18, 2013 4:32 PM