WSUS synchronization error - SCCM 2012

I have a virtual lab containing a WSUS server and an SCCM server.  I setup the WSUS server as the software update point in SCCM, but I am continuously having issues synchronizing.
 
As they are in a lab, they do not have internet access.  I gave the WSUS server access after install to download the latest updates, but after that, put it back on the lab network.  SCCM is only trying to synchronize the already-downloaded updates from WSUS, correct?  In other words, the lack of internet access should not adversely affect synchronization with the WSUS server?
 
The error is;
Type: Mileston
Severity: ERror
Message ID: 6703
Process ID: 2044
Thread ID: 1600
Description:
WSUS Synchronization failed.
Message: WSUS server not configured.  Please refer to WCM.log for configuration error deatils.
Source: CWSyncMgr::DoSync.
The operating system reported error 2147500037: Unspecified error
 
Any ideas?
 

Are there any errors in WCM.log?
 
Nash
 

It's trying to sync, not just for information on "already-downloaded updates" but for any new updates as well.  Possible updates for detection methods for current updates, plus anything new since it last checked.  So you can ignore that if it's your intent.

The only problem I have with that is that I have downloaded several updates with WSUS but in SCCM I am showing no items found on "All Software Updates."  So it doesn't know about any updates.
 

Downloaded with WSUS?  You mean in the CM console and not the WSUS console?

Probably best to post some of the WCM.log file so we can see the error but off the top of my head it appears that the integration between the two products isn't syncing up.  When you do a Configmgr installation all you need to do is a default WSUS install with Admin Console, utilizing whichever database functionality you want, then make sure the site role is installed within ConfigMgr.  ConfigMgr will then take care of pulling the strings of WSUS and generally there should be little to no interaction with WSUS on your part needed.  Judging by the error above it doesn't look like the integration between WSUS and ConfigMgr is properly configured though and that needs to be happy prior to trying a sync.
 
Other worthwhile logs to review are the ConfigMgr WSUSCtrl.log and WSyncMGR.log as they may help point you towards the likely configuration error you are seeing.
 

Well, I'm back.
I finally got everything reinstalled (dumped the CAS as you suggested), and I go to deploy updates and am still having a problem.  Everything looks perfect - it is detecting what computers need what patches, etc.  The computer I'm trying to patch (Win 7 x86), when I right click in Devices and go to properties, shows the deployments, but the patches aren't installing.  I removed all days from the maintenance window so it would install at any time, but for some reason it's showing that they still won't install.    It appears that it's finding the updates it needs, but then it's not installing for reasons unknown.  I've attached UpdatesDeployment.log from the client machine.  Any help, as always, is appreciated.

Attachment(s)

UpdatesDeployment.txt (47.28 KB) - downloaded 218 times

I should also note that on the information on the deployment it still says it is "in progress" (started yesterday at 4pm) and that it is still "downloading updates".

What's the CAS.log say?  Sounds like it isn't downloading.  

Well, one of the computers has CAS.log and the other doesn't, for some reason.
 
The one that does have it is attached.

Attachment(s)

CAS.txt (157.73 KB) - downloaded 69 times

The one without the CAS has a more serious issue as it must not be aware that it even needs to run something.  The one from the log above shows an HTTPS location available.  Do other applications install OK?  If not, I wonder if you should start by removing the HTTPS option to troubleshoot a PKI issue (assuming you even wanted to do cert based downloads).  Check all the client logs involved for windows updates like UpdatesDeployment.log and such.

Well, I actually disabled HTTPS/PKI for the site and only use HTTP.  Is the "CAS.log" referring to a Central Admin Site?  If so, I don't even have one of those any more (after I blew everything away and started over).

No, it's the Content Access Service.  http://technet.microsoft.com/en-us/library/bb892800.aspx
It's showing 2 sources in your log above and I'm wondering if the client can't get to the PKI based one.

Correct me if I'm wrong, but since I changed the entire primary site to HTTP rather than HTTPS, it shouldn't even be looking for an HTTPS site right?
 
Also, I just noticed that there was no "Software Update Connection Point Account".  So, I used my "SCCMBoss" account that is a domain admin.  Perhaps that will make a difference?  I dunno.  I only have one site, one SUP (a WSUS server), and 2 clients.

I'm still wondering why your clients are being offered anything but an HTTP option.  And your clients are talking to their SUP OK, it's that they aren't getting their content from the DP.

Ugh...me too.  Not sure where to go next.  Then I uninstalled the client on one of the clients and tried pushing it back out, no dice.  Awesome.

Well that's another issue altogether.  It might be just that CM12 is so different that there is something you missed.  Might want to hit the free labs to walk through setup scenarios: http://technet.microsoft.com/en-us/systemcenter/bb539977

12 is all I've ever used, as we've never had it before.  THis is all in a lab environment, installed on VMWorkstation.  The only thing I can think that would be different from a regular environment is that networking is handled by VMWorkstation, so no DHCP on the DC.  That's all that would be different.

Well for this thread, let's stick to the software update problem, which my guess is also a software distribution problem.  That something is left over telling CM12 to use HTTPS on the DPs since the log is offering both.

I guess I forgot to post my response, so I'm going to try to re-type it now.
I think I made *some* progress by removing all of my SUGs and deployment packages and starting over.  I have pushed 2 different SUGs to 2 different collections (both containing 1 computer each).  One of the collections has been stuck at "Downloading (0% complete)" on the first patch. 
The UpdatesDeployment.log looks a little better on one of them, saying "Progress received for assignment ({blahblahblah})" several times, and "EnumerateUPdates for action (UpdateActionInstall) - Total actionable updates = 6".  However, still stuck at 0% so it doesn't appear it is downloading. 
 
Will give you a progress update on the other collection's PC tomorrow.  As of right now it looks like it might be working (fingers crossed).