locked
SCCM Restore RRS feed

  • Question

  • I would like to setup WSUS fresh after SCCM restore. Is this possible?  I noticed on the server that I can't install .Net 3.5 and 4.0 Http option is this needed? It's greyed out.  Will I need to reconfigure settings for IIS after the restore?  Thanks.
    Friday, December 23, 2016 3:10 PM

All replies

  • Yes this is possible.

    Define "can't install .Net 3.5 and 4.0 Http"? Greyed out where?

    Yes, these are needed.

    No, nothing to configure or reconfigure in IIS.


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

    Friday, December 23, 2016 6:16 PM
  • Under roles and features it's greyed out. 3.5 & 4 are installed but the option to check http is greyed out. I can provide screen shot if needed
    Friday, December 23, 2016 7:30 PM
  • Do you have any WSUS documentation for fresh install after SCCM restore?
    • Edited by Tech191405 Friday, December 23, 2016 7:33 PM
    Friday, December 23, 2016 7:32 PM
  • It's no different than a normal install.

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

    Friday, December 23, 2016 7:52 PM
  • Yeah, screenshots would be helpful please.

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

    Friday, December 23, 2016 7:53 PM
  • This is the area that's greyed out this is just a picture: https://goo.gl/images/9IH5az
    It's HTTP activation
    • Edited by Tech191405 Friday, December 23, 2016 8:38 PM
    Friday, December 23, 2016 8:35 PM
  • The reason why I ask for documentation is because it seems I have to remove old WSUS configuration from SCCM to install it new. Is that correct?
    Friday, December 23, 2016 8:40 PM
  • Removing the SUP removes any WSUS configuration.

    I don't see what's greyed out, just click the checkbox next to HTTP activation.


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

    Friday, December 23, 2016 9:59 PM
  • This is just an example of the setting I'm talking about. I'm not able to provide a screen shot from my server
    Friday, December 23, 2016 10:01 PM
  • I got that fixed.  Thanks.
    Friday, December 23, 2016 10:40 PM
  • So I guess I should remove the wsus role for sccm because I am installing a fresh wsus correct?
    Friday, December 23, 2016 10:41 PM
  • That depends upon exactly what you are doing which isn't exactly clear. Are you planning on installing WSUS n another server?

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

    Friday, December 23, 2016 11:47 PM
  • I installed on the same server I did the restore of SCCM.  I can't get the wsus content folder to sync with sccm.  I am getting the following errors:

    Wsyncmgr.log

    Performing sync on local request  $$<SMS_WSUS_SYNC_MANAGER><12-24-2016 16:48:35.293+300><thread=9164 (0x23CC)>
    Read SUPs from SCF for server.  $$<SMS_WSUS_SYNC_MANAGER><12-24-2016 16:48:35.310+300><thread=9164 (0x23CC)>
    Found 1 SUPs  $$<SMS_WSUS_SYNC_MANAGER><12-24-2016 16:48:35.314+300><thread=9164 (0x23CC)>
    Found active SUP server. from SCF File.~  $$<SMS_WSUS_SYNC_MANAGER><12-24-2016 16:48:35.314+300><thread=9164 (0x23CC)>
    Sync failed: WSUS update source not found on site *. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource  $$<SMS_WSUS_SYNC_MANAGER><12-24-2016 16:48:35.315+300><thread=9164 (0x23CC)>
    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=server. SITE=* PID=3872 TID=9164 GMTDATE=Sat Dec 24 21:48:35.316 2016 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found on site *. Please refer to WCM.log for configuration error details." ISTR2="" IS*="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_SYNC_MANAGER><12-24-2016 16:48:35.319+300><thread=9164 (0x23CC)>
    Sync failed. Will retry in 60 minutes  $$<SMS_WSUS_SYNC_MANAGER><12-24-2016 16:48:35.320+300><thread=9164 (0x23CC)>
    Setting sync alert to active state on site *  $$<SMS_WSUS_SYNC_MANAGER><12-24-2016 16:48:35.320+300><thread=9164 (0x23CC)>
    Sync time: 0d00h00m00s  $$<SMS_WSUS_SYNC_MANAGER><12-24-2016 16:48:35.325+300><thread=9164 (0x23CC)>
    Wakeup by inbox drop  $$<SMS_WSUS_SYNC_MANAGER><12-24-2016 16:52:05.395+300><thread=9164 (0x23CC)>
    Found local sync request file  $$<SMS_WSUS_SYNC_MANAGER><12-24-2016 16:52:10.417+300><thread=9164 (0x23CC)>
    Starting Sync  $$<SMS_WSUS_SYNC_MANAGER><12-24-2016 16:52:10.418+300><thread=9164 (0x23CC)>
    Performing sync on local request  $$<SMS_WSUS_SYNC_MANAGER><12-24-2016 16:52:10.418+300><thread=9164 (0x23CC)>
    Read SUPs from SCF for server.  $$<SMS_WSUS_SYNC_MANAGER><12-24-2016 16:52:10.432+300><thread=9164 (0x23CC)>
    Found 1 SUPs  $$<SMS_WSUS_SYNC_MANAGER><12-24-2016 16:52:10.444+300><thread=9164 (0x23CC)>
    Found active SUP server. from SCF File.~  $$<SMS_WSUS_SYNC_MANAGER><12-24-2016 16:52:10.445+300><thread=9164 (0x23CC)>
    Sync failed: WSUS update source not found on site *. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource  $$<SMS_WSUS_SYNC_MANAGER><12-24-2016 16:52:10.446+300><thread=9164 (0x23CC)>
    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=server. SITE=* PID=3872 TID=9164 GMTDATE=Sat Dec 24 21:52:10.446 2016 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found on site *. Please refer to WCM.log for configuration error details." ISTR2="" IS*="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_SYNC_MANAGER><12-24-2016 16:52:10.446+300><thread=9164 (0x23CC)>
    Sync failed. Will retry in 60 minutes  $$<SMS_WSUS_SYNC_MANAGER><12-24-2016 16:52:10.447+300><thread=9164 (0x23CC)>
    Setting sync alert to active state on site *  $$<SMS_WSUS_SYNC_MANAGER><12-24-2016 16:52:10.447+300><thread=9164 (0x23CC)>
    Sync time: 0d00h00m00s  $$<SMS_WSUS_SYNC_MANAGER><12-24-2016 16:52:10.452+300><thread=9164 (0x23CC)>

    WCM Log

    Subscription contains categories unknown to WSUS.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:45:10.529+300><thread=9160 (0x23C8)>
    Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified error~  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:45:10.530+300><thread=9160 (0x23C8)>
    STATMSG: ID=6603 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=server SITE=* PID=3872 TID=9160 GMTDATE=Sat Dec 24 21:45:10.530 2016 ISTR0="server" ISTR1="" ISTR2="" IS*="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:45:10.530+300><thread=9160 (0x23C8)>
    Setting new configuration state to 4 (WSUS_CONFIG_SUBSCRIPTION_PENDING)~  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:45:10.532+300><thread=9160 (0x23C8)>
    Waiting for changes for 13 minutes  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:45:10.533+300><thread=9160 (0x23C8)>
    Trigger event array index 0 ended.  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:48:30.262+300><thread=9160 (0x23C8)>
    SCF change notification triggered.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:48:35.264+300><thread=9160 (0x23C8)>
    Populating config from SCF  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:48:35.264+300><thread=9160 (0x23C8)>
    Setting new configuration state to 1 (WSUS_CONFIG_PENDING)~  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:48:35.282+300><thread=9160 (0x23C8)>
    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)~  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:48:35.283+300><thread=9160 (0x23C8)>
    Checking runtime v2.0.50727...~  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:48:35.284+300><thread=9160 (0x23C8)>
    Failed to create assembly name object for Microsoft.UpdateServices.Administration. Error = 0x80131701.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:48:35.285+300><thread=9160 (0x23C8)>
    Checking runtime v4.0.30319...~  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:48:35.286+300><thread=9160 (0x23C8)>
    Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.3.9600.16384~  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:48:35.288+300><thread=9160 (0x23C8)>
    Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.3.9600.18324~  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:48:35.289+300><thread=9160 (0x23C8)>
    Supported WSUS version found~  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:48:35.289+300><thread=9160 (0x23C8)>
    Attempting connection to WSUS server: server, port: 8530, useSSL: False  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:48:35.290+300><thread=9160 (0x23C8)>
    Successfully connected to server: server, port: 8530, useSSL: False  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:48:35.296+300><thread=9160 (0x23C8)>
    Verify Upstream Server settings on the Active WSUS Server~  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:48:35.296+300><thread=9160 (0x23C8)>
    Successfully configured WSUS Server settings and Upstream Server to server  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:48:35.327+300><thread=9160 (0x23C8)>
    Attempting connection to WSUS server: server, port: 8530, useSSL: False  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:48:40.341+300><thread=9160 (0x23C8)>
    Successfully connected to server: server, port: 8530, useSSL: False  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:48:40.346+300><thread=9160 (0x23C8)>
    Category Company:94d731de-22a6-4458-dc4d-b5267de026fc (Adobe Systems, Inc.) not found on WSUS  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:48:40.353+300><thread=9160 (0x23C8)>
    Category Product:b1d1a5ca-37c4-5805-b271-367467ef10f5 (Java JRE Client) not found on WSUS  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:48:40.427+300><thread=9160 (0x23C8)>
    Starting WSUS category sync from upstream...  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:48:40.498+300><thread=9160 (0x23C8)>
    Microsoft.SystemsManagementServer.WSUS.WSUSMSPException: WSUS sync failed with UssNotFound: ~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.IsSyncRunning()  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:48:45.541+300><thread=9160 (0x23C8)>
    Failed to set Subscriptions on the WSUS Server. Error:(-2146233088)Unknown error 0x80131500~  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:48:45.551+300><thread=9160 (0x23C8)>
    STATMSG: ID=6603 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=server SITE=* PID=3872 TID=9160 GMTDATE=Sat Dec 24 21:48:45.551 2016 ISTR0="server" ISTR1="" ISTR2="" IS*="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:48:45.551+300><thread=9160 (0x23C8)>
    Setting new configuration state to 4 (WSUS_CONFIG_SUBSCRIPTION_PENDING)~  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:48:45.553+300><thread=9160 (0x23C8)>
    Waiting for changes for 10 minutes  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:48:45.554+300><thread=9160 (0x23C8)>
    Wait timed out after 10 minutes while waiting for at least one trigger event.  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:58:20.835+300><thread=9160 (0x23C8)>
    Timed Out...~  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:58:30.841+300><thread=9160 (0x23C8)>
    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)~  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:58:30.841+300><thread=9160 (0x23C8)>
    Checking runtime v2.0.50727...~  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:58:30.842+300><thread=9160 (0x23C8)>
    Failed to create assembly name object for Microsoft.UpdateServices.Administration. Error = 0x80131701.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:58:30.843+300><thread=9160 (0x23C8)>
    Checking runtime v4.0.30319...~  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:58:30.844+300><thread=9160 (0x23C8)>
    Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.3.9600.16384~  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:58:30.845+300><thread=9160 (0x23C8)>
    Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.3.9600.18324~  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:58:30.847+300><thread=9160 (0x23C8)>
    Supported WSUS version found~  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:58:30.847+300><thread=9160 (0x23C8)>
    Attempting connection to WSUS server: server, port: 8530, useSSL: False  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:58:30.847+300><thread=9160 (0x23C8)>
    Successfully connected to server: server, port: 8530, useSSL: False  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:58:30.853+300><thread=9160 (0x23C8)>
    Verify Upstream Server settings on the Active WSUS Server~  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:58:30.854+300><thread=9160 (0x23C8)>
    Successfully configured WSUS Server settings and Upstream Server to server  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:58:30.901+300><thread=9160 (0x23C8)>
    Setting new configuration state to 4 (WSUS_CONFIG_SUBSCRIPTION_PENDING)~  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:58:30.903+300><thread=9160 (0x23C8)>
    Refreshing categories from WSUS server~  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:58:30.903+300><thread=9160 (0x23C8)>
    Attempting connection to WSUS server: server, port: 8530, useSSL: False  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:58:30.904+300><thread=9160 (0x23C8)>
    Successfully connected to server: server, port: 8530, useSSL: False  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:58:30.908+300><thread=9160 (0x23C8)>
    Successfully refreshed categories from WSUS server~  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:58:40.433+300><thread=9160 (0x23C8)>
    Attempting connection to WSUS server: server, port: 8530, useSSL: False  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:58:45.447+300><thread=9160 (0x23C8)>
    Successfully connected to server: server, port: 8530, useSSL: False  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:58:45.452+300><thread=9160 (0x23C8)>
    Category Company:94d731de-22a6-4458-dc4d-b5267de026fc (Adobe Systems, Inc.) not found on WSUS  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:58:45.459+300><thread=9160 (0x23C8)>
    Category Product:b1d1a5ca-37c4-5805-b271-367467ef10f5 (Java JRE Client) not found on WSUS  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:58:45.528+300><thread=9160 (0x23C8)>
    Starting WSUS category sync from upstream...  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:58:45.598+300><thread=9160 (0x23C8)>
    Microsoft.SystemsManagementServer.WSUS.WSUSMSPException: WSUS sync failed with UssNotFound: ~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.IsSyncRunning()  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:58:50.638+300><thread=9160 (0x23C8)>
    Failed to set Subscriptions on the WSUS Server. Error:(-2146233088)Unknown error 0x80131500~  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:58:50.646+300><thread=9160 (0x23C8)>
    STATMSG: ID=6603 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=server SITE=* PID=3872 TID=9160 GMTDATE=Sat Dec 24 21:58:50.646 2016 ISTR0="server" ISTR1="" ISTR2="" IS*="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:58:50.649+300><thread=9160 (0x23C8)>
    Waiting for changes for 60 minutes  $$<SMS_WSUS_CONFIGURATION_MANAGER><12-24-2016 16:58:50.651+300><thread=9160 (0x23C8)>

    Saturday, December 24, 2016 10:40 PM
  • Hi,

    You could take a look at this thread: https://social.technet.microsoft.com/Forums/en-US/6bbf3aad-45c5-4181-a89d-ea7585f2ca11/failed-to-set-subscriptions-on-the-wsus-server-error2146233088unknown-error-0x80131500-in-sccm?forum=configmanagersecurity

    You may have a test in your lab.

    Best Regards,

    Ray


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    • Edited by Ant_G Tuesday, December 27, 2016 8:15 AM
    Tuesday, December 27, 2016 8:12 AM