Hello all,

I am having trouble getting my SCCM2012 to connect to a WSUS Software Update Point (SUP) and have finally resorted to writing my own forum for help. I've searched dozens and dozens of forums but I haven't found any, step-by-step wise, guides for my environment specifically.

My environment is the following:

A disconnected Windows 2008 R2 server with SCCM 2012 installed (TEST domain)
A disconnected Windows 2008 R2 server with WSUS 3.0 SP2 installed (TEST domain)
A connected Windows 2008 R2 server with WSUS 3.0 SP2 installed and connected to Microsoft Updates (use the wsusutil.exe export command to sneakernet the WSUS metadata and then sneakernet it and the WSUSContent folder over to the disconnected WSUS server.)

I have tirelessly troubleshot this problem and am at the end of my rope. I've seen numerous errors but all the fixes that I have seen online have not been helpful for me. I will gladly give whatever information that you all experts need to help resolve this issue.

The first error that I'm seeing that I notice is from the WCM.log (C:\Program Files\Microsoft Configuration Manager\Logs):

3/31/2015 9:56:05 AM 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)

3/31/2015 9:56:05 AM Remote configuration failed on WSUS server.

3/31/2015 9:56:05 AM Setting new configuration state to 3 (WSUS_CONFIG_FAILED)

I don't know that any of that is helpful to anyone but I figure it's a start. Any help would be greatly appreciated.

Any chance that there's a proxy involved so so that http request to the WSUS will not be made directly, but via the proxy?

Have you also verified the ports configured in the SUP match those configured on the WSUS instance?

Have you launched the WSUS console on the system hosting WSUS to verify that it can connect to the WSUS instance?

I don't know how or why there would be a proxy involved since it's a disconnected network? This is just a test environment so I've never configure any proxies on it. There shouldn't be any proxy information needed in my type of environment is there?

I have both set to port 80 (but I've read where that can be an issue when connecting to the database.) I have everything set to 80 as far as I can tell. Where exactly would I verify those ports?

Which system are you referring to? I don't think I'm reading your question correctly, sorry.

Update *** - I can connect from the WIN-SCCM server to the WIN-WSUS server via the WSUS console.

• Edited by Nicklesss 17 hours 8 minutes ago

You can verify the SUP's ports in the ConfigMgr console on software update point properties page and you can verify the WSUS ports in IIS on the system hosting the WSUS instance.

Can you post the entire, unedited snippet of the log file where the errors occur as the log line before errors are just as important as the lines showing the errors?

I will do that as soon as I get the chance! I'll report back with that.

So you want the entire WCM.log file? Any other log files needed?

No, generally the entire log file is not needed. Just the relevant portion showing the activity that failed and what happened right before that activity. Reading log files is an art though and deciding what is relevant is not always straight-forward. Too much = bad, too little = bad (kind of like the three bears).

I have both set to port 80 (but I've read where that can be an issue when connecting to the database.) I have everything set to 80 as far as I can tell. Where exactly would I verify those ports?

Which system are you referring to? I don't think I'm reading your question correctly, sorry.

Update *** - I can connect from the WIN-SCCM server to the WIN-WSUS server via the WSUS console.

• Edited by Nicklesss Tuesday, March 31, 2015 2:34 PM

Here is the last few lines before the errors and the relevant errors as well:

3/31/2015 2:46:28 PM	SMS_EXECUTIVE started SMS_WSUS_CONFIGURATION_MANAGER as thread ID 4724 (0x1274).	SMS_WSUS_CONFIGURATION_MANAGER	2596 (0x0A24)
3/31/2015 2:46:31 PM	This WIN-SCCM.PMMI.local system is the SMS Site Server.	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 2:46:31 PM	Populating config from SCF	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 2:46:31 PM	Setting new configuration state to 1 (WSUS_CONFIG_PENDING)	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 2:46:31 PM	Changes in active SUP list detected. New active SUP List is:	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 2:46:31 PM	    SUP0: WIN-SCCM.PMMI.local, group = , nlb =	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 2:46:31 PM	Updating active SUP groups...	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 2:46:31 PM	Waiting for changes for 1 minutes	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 2:46:32 PM	Wait timed out after 0 minutes while waiting for at least one trigger event.	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 2:46:42 PM	Timed Out...	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 2:46:43 PM	Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 2:46:43 PM	Checking runtime v2.0.50727...	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 2:46:43 PM	Found supported assembly Microsoft.UpdateServices.Administration version 3.1.6001.1, file version 3.1.7600.256	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 2:46:43 PM	Found supported assembly Microsoft.UpdateServices.BaseApi version 3.1.6001.1, file version 3.1.7600.256	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 2:46:43 PM	Supported WSUS version found	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 2:46:43 PM	Using PMMI\sccmadmin credentials for network connections	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 2:46:43 PM	Attempting connection to WSUS server: WIN-SCCM.PMMI.local, port: 80, useSSL: False	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 2:48:04 PM	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	4724 (0x1274)
3/31/2015 2:48:04 PM	Done using PMMI\sccmadmin credentials	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 2:48:04 PM	Remote configuration failed on WSUS Server.	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 2:48:04 PM	STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=WIN-SCCM.PMMI.local SITE=CSR PID=2572 TID=4724 GMTDATE=Tue Mar 31 18:48:04.582 2015 ISTR0="WIN-SCCM.PMMI.local" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 2:48:04 PM	Setting new configuration state to 3 (WSUS_CONFIG_FAILED)	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 2:48:04 PM	Waiting for changes for 58 minutes	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 2:48:04 PM	Trigger event array index 0 ended.	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 2:48:09 PM	SCF change notification triggered.	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 2:48:09 PM	Populating config from SCF	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 2:48:09 PM	Waiting for changes for 58 minutes	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)

Inside of the ConfigMgr inside of the Software Update Point properties page, the port is set to:

Port Number: 80
SSL Port Number: 443

Inside of IIS, there is a little bit of a discrepancy.

For Default Web Site:
Bindings: net.tcp:808:*,net.pipe:*,net.msmq:localhost,msmq.formatname:localhost,http::80:,https::443:

For WSUS Administration:
Bindings: http::8530:,https::8531:

Does that help at all?

After changing the Port Number to 8530 and SSL Port Number to 8531 inside of ConfigMgr --> Software Update Point --> Properties, the log looks as if it connected successfully...

3/31/2015 3:16:30 PM	Trigger event array index 0 ended.	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:16:35 PM	SCF change notification triggered.	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:16:35 PM	Populating config from SCF	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:16:35 PM	Setting new configuration state to 1 (WSUS_CONFIG_PENDING)	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:16:35 PM	Changes in active SUP list detected. New active SUP List is:	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:16:35 PM	    SUP0: WIN-SCCM.PMMI.local, group = , nlb =	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:16:35 PM	Updating active SUP groups...	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:16:35 PM	Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:16:35 PM	Checking runtime v2.0.50727...	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:16:35 PM	Found supported assembly Microsoft.UpdateServices.Administration version 3.1.6001.1, file version 3.1.7600.256	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:16:35 PM	Found supported assembly Microsoft.UpdateServices.BaseApi version 3.1.6001.1, file version 3.1.7600.256	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:16:35 PM	Supported WSUS version found	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:16:35 PM	Using PMMI\sccmadmin credentials for network connections	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:16:35 PM	Attempting connection to WSUS server: WIN-SCCM.PMMI.local, port: 8530, useSSL: False	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:17:01 PM	Successfully connected to server: WIN-SCCM.PMMI.local, port: 8530, useSSL: False	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:17:01 PM	Verify Upstream Server settings on the Active WSUS Server	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:17:04 PM	Successfully configured WSUS Server settings and Upstream Server to win-wsus.pmmi.local	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:17:04 PM	Done using PMMI\sccmadmin credentials	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:17:04 PM	WSUS Server configuration has been updated. Updating Group Info.	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:17:04 PM	Updating Group Info for WSUS.	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:17:04 PM	Set DBServerName property in SCF to 'WIN-SCCM\SCCM2012' on this site for WIN-SCCM.PMMI.local.	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:17:04 PM	user(NT AUTHORITY\SYSTEM) runing application(SMS_WSUS_CONFIGURATION_MANAGER) from machine (WIN-SCCM.PMMI.local) is submitting SDK changes from site(CSR)	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:17:10 PM	Using PMMI\sccmadmin credentials for network connections	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:17:10 PM	Attempting connection to WSUS server: WIN-SCCM.PMMI.local, port: 8530, useSSL: False	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:17:10 PM	Successfully connected to server: WIN-SCCM.PMMI.local, port: 8530, useSSL: False	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:17:11 PM	Subscribed Update Categories <?xml version="1.0" ?>~~<Categories>~~	<Category Id="Product:041e4f9f-3a3d-4f58-8b2f-5e6fe95c4591"><![CDATA[Office 2007]]></Category>~~	<Category Id="Product:84f5f325-30d7-41c4-81d1-87a0e6535b66"><![CDATA[Office 2010]]></Category>~~	<Category Id="UpdateClassification:0fa1201d-4330-4fa8-8ae9-b877473b6441"><![CDATA[Security Updates]]></Category>~~	<Category Id="UpdateClassification:28bc880e-0592-4cbf-8f95-c79b17911d5f"><![CDATA[Update Rollups]]></Category>~~	<Category Id="UpdateClassification:68c5b0a3-d1a6-4553-ae49-01d3a7827828"><![CDATA[Service Packs]]></Category>~~	<Category Id="UpdateClassification:e0789628-ce08-4437-be74-2495b842f43b"><![CDATA[Definition Updates]]></Category>~~</Categories>	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:17:11 PM	Done using PMMI\sccmadmin credentials	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:17:11 PM	Using PMMI\sccmadmin credentials for network connections	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:17:11 PM	Attempting connection to WSUS server: WIN-SCCM.PMMI.local, port: 8530, useSSL: False	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:17:11 PM	Successfully connected to server: WIN-SCCM.PMMI.local, port: 8530, useSSL: False	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:17:12 PM	Done using PMMI\sccmadmin credentials	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:17:14 PM	Successfully inserted WSUS Enterprise Update Source object {23160195-24D8-4B6D-8DDD-52176DC89E41}	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:17:14 PM	Configuration successful. Will wait for 1 minute for any subscription or proxy changes	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:18:14 PM	Setting new configuration state to 2 (WSUS_CONFIG_SUCCESS)	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:18:14 PM	Waiting for changes for 28 minutes	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:18:14 PM	Trigger event array index 0 ended.	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:18:19 PM	SCF change notification triggered.	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:18:19 PM	Populating config from SCF	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:18:19 PM	Waiting for changes for 28 minutes	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:18:19 PM	Trigger event array index 1 ended.	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:18:19 PM	File notification triggered.	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:18:24 PM	File notification triggered WCM Inbox.	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:18:24 PM	Waiting for changes for 28 minutes	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:18:24 PM	Trigger event array index 1 ended.	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:18:24 PM	File notification triggered.	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:18:29 PM	File notification triggered WCM Inbox.	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)
3/31/2015 3:18:29 PM	Waiting for changes for 28 minutes	SMS_WSUS_CONFIGURATION_MANAGER	4724 (0x1274)

There is still no software update information inside of SCCM though.

Yep, you just pointed out the ports above which don't match:

WSUS: 8530

SUP: 80

You should reconfigure your SUP to use 8530/8531.

Thank you very much. I changed the SUP to 8530 and as you can see in the WCM.log file from above, it says it "Successfully connected" but I opened the WSYNCMGR.log file and got this:

3/31/2015 3:24:26 PM	Sync time: 0d00h01m30s	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:33:40 PM	Wakeup by inbox drop	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:33:46 PM	Found local sync request file	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:33:46 PM	Starting Sync	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:33:46 PM	Performing sync on local request	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:33:46 PM	Full sync required due to changes in main WSUS server location.	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:33:46 PM	Read SUPs from SCF for WIN-SCCM.PMMI.local	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:33:46 PM	Found 1 SUPs	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:33:46 PM	Found active SUP WIN-SCCM.PMMI.local from SCF File.	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:33:46 PM	STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=WIN-SCCM.PMMI.local SITE=CSR PID=2572 TID=4784 GMTDATE=Tue Mar 31 19:33:46.034 2015 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:33:47 PM	Synchronizing WSUS server WIN-SCCM.PMMI.local	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:33:47 PM	STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=WIN-SCCM.PMMI.local SITE=CSR PID=2572 TID=4784 GMTDATE=Tue Mar 31 19:33:47.042 2015 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:33:47 PM	Using account PMMI\sccmadmin to connect to WSUS Server	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:33:47 PM	Synchronizing WSUS server win-sccm.pmmi.local ...	SMS_WSUS_SYNC_MANAGER	2992 (0x0BB0)
3/31/2015 3:33:47 PM	sync: Starting WSUS synchronization	SMS_WSUS_SYNC_MANAGER	2992 (0x0BB0)
3/31/2015 3:35:17 PM	Sync failed: UssCommunicationError: WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.1.101:80~~at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context). Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:35:17 PM	STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=WIN-SCCM.PMMI.local SITE=CSR PID=2572 TID=4784 GMTDATE=Tue Mar 31 19:35:17.077 2015 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS" ISTR1="UssCommunicationError: WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.1.101:80~~at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:35:17 PM	Sync failed. Will retry in 60 minutes	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:35:17 PM	Setting sync alert to active state on site CSR	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:35:17 PM	Sync time: 0d00h01m31s	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)

I feel like I'm close but there is something, probably in IIS or how I'm doing something in WSUS, that isn't correct.

Inside the Administration tab, with Sites selected and getting to the Software Update Point Component Properties, where should the "Select the synchronization source for this software update point" be pointed?
Synchronize from Microsoft Update
Synchronize from an upstream data source location (URL) -- currently what I have chosen
Do not synchronize from Microsoft Update or upstream data source

• Edited by Nicklesss 11 hours 59 minutes ago

After changing the "Select the synchronization source for this software update point" to "Do not synchronize from Microsoft Update or upstream data source", it appears to be syncing! I now have patches in my Software Updates tab inside of All Software Updates!

Thank you VERY much for the help!

My next question would be, since I'm in a closed enclave and all of them say, "Downloaded" no, how do I go about downloading the patches? Is that something I need to do from my internet connected WSUS server? Do I choose what patches that I want to use and approve them and wait for them to download then airgap over the WSUSContent folder and export the metadata from that server?

I knew that I was getting close but could not figure out the missing piece.

After changing the "Select the synchronization source for this software update point" to "Do not synchronize from Microsoft Update or upstream data source", it appears to be syncing! I now have patches in my Software Updates tab inside of All Software Updates!

Thank you VERY much for the help!

My next question would be, since I'm in a closed enclave and all of them say, "Downloaded" no, how do I go about downloading the patches? Is that something I need to do from my internet connected WSUS server? Do I choose what patches that I want to use and approve them and wait for them to download then airgap over the WSUSContent folder and export the metadata from that server?

I knew that I was getting close but could not figure out the missing piece.

"Disconnected WSUS" reference: https://technet.microsoft.com/en-us/library/cc720486(v=ws.10).aspx

Although, your earlier post suggests you already know about wsusutil export etc...

Have you applied the latest set of WSUS updates to both WSUS servers ? (there are a couple of updates which fixup the export files, by using different compression)

Thank you very much. I changed the SUP to 8530 and as you can see in the WCM.log file from above, it says it "Successfully connected" but I opened the WSYNCMGR.log file and got this:

3/31/2015 3:24:26 PM	Sync time: 0d00h01m30s	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:33:40 PM	Wakeup by inbox drop	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:33:46 PM	Found local sync request file	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:33:46 PM	Starting Sync	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:33:46 PM	Performing sync on local request	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:33:46 PM	Full sync required due to changes in main WSUS server location.	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:33:46 PM	Read SUPs from SCF for WIN-SCCM.PMMI.local	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:33:46 PM	Found 1 SUPs	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:33:46 PM	Found active SUP WIN-SCCM.PMMI.local from SCF File.	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:33:46 PM	STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=WIN-SCCM.PMMI.local SITE=CSR PID=2572 TID=4784 GMTDATE=Tue Mar 31 19:33:46.034 2015 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:33:47 PM	Synchronizing WSUS server WIN-SCCM.PMMI.local	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:33:47 PM	STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=WIN-SCCM.PMMI.local SITE=CSR PID=2572 TID=4784 GMTDATE=Tue Mar 31 19:33:47.042 2015 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:33:47 PM	Using account PMMI\sccmadmin to connect to WSUS Server	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:33:47 PM	Synchronizing WSUS server win-sccm.pmmi.local ...	SMS_WSUS_SYNC_MANAGER	2992 (0x0BB0)
3/31/2015 3:33:47 PM	sync: Starting WSUS synchronization	SMS_WSUS_SYNC_MANAGER	2992 (0x0BB0)
3/31/2015 3:35:17 PM	Sync failed: UssCommunicationError: WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.1.101:80~~at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context). Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:35:17 PM	STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=WIN-SCCM.PMMI.local SITE=CSR PID=2572 TID=4784 GMTDATE=Tue Mar 31 19:35:17.077 2015 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS" ISTR1="UssCommunicationError: WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.1.101:80~~at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:35:17 PM	Sync failed. Will retry in 60 minutes	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:35:17 PM	Setting sync alert to active state on site CSR	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)
3/31/2015 3:35:17 PM	Sync time: 0d00h01m31s	SMS_WSUS_SYNC_MANAGER	4784 (0x12B0)

I feel like I'm close but there is something, probably in IIS or how I'm doing something in WSUS, that isn't correct.

Inside the Administration tab, with Sites selected and getting to the Software Update Point Component Properties, where should the "Select the synchronization source for this software update point" be pointed?
Synchronize from Microsoft Update
Synchronize from an upstream data source location (URL) -- currently what I have chosen
Do not synchronize from Microsoft Update or upstream data source

• Edited by Nicklesss Tuesday, March 31, 2015 7:43 PM

My next question would be, since I'm in a closed enclave and all of them say, "Downloaded" no, how do I go about downloading the patches? Is that something I need to do from my internet connected WSUS server? Do I choose what patches that I want to use and approve them and wait for them to download then airgap over the WSUSContent folder and export the metadata from that server?

That's a bit of a manual chore I'm afraid and is not perfect.

Yes, you can approve the updates on the Internet connected WSUS instance. From there, you can copy over the WSUS content folder to an internal location. Then, within the ConfigMgr console, when downloading the updates (by right-clicking on a single update or an update group and selecting download), the last page of the download wizard will as you for a source location. You can then specify the location where you copied the WSUS content folder from the Internet facing WSUS instance. It will look in subfolders (or at least it is supposed to to my knowledge).

If the Internet facing WSUS instance is specified as the upstream server of the WSUS instance being used by the ConfigMgr SUP, make sure that you disable Automatic Updates on your clients also otherwise the approvals will flow down to the SUP's WSUS instance and the clients will begin using these approvals outside of ConfigMgr. You should disable Automatic Updates (via a domain group policy) regardless though to prevent the WUA from doing anything on its own.

Yeah, I know about the WSUS import/export tool but what I'm unfamiliar with is how it works as far as downloading the patches itself. I assume that all the patches I need to be downloaded need to be "approved" on the internet-connected WSUS server?

I have applied two WSUS patches (KB2720211-x64.exe and KB2734608-x64.exe). I know there is one more that is used if your files are more than a certain size but I don't have that KB off the top of my head.