Link to home
Start Free TrialLog in
Avatar of Chris Millard
Chris MillardFlag for United Kingdom of Great Britain and Northern Ireland

asked on

SCCM 2012 won't perform initial sync, and Java update from SCUP not showing.

I have a brand new install of System Center 2012 and System Center Updates Publisher 2011. I am setting this up so that product updates from 3rd parties such Java, Acrobat Reader etc., can be pushed out to client PCs without user intervention.

I have successfully created a package in SCUP for Java (under a new vendor called Oracle), and I have successfully published this.

However, this update is not appearing in SCCM 2012 - but then again, SCCM 2012 is not showing ANY available updates - including from Microsoft.

The sync settings are set to Microsoft Update. I have followed suggestions to clear the product categories then re-select some in order to start the initial synchronisation, but I can't seem to get it working.
Avatar of Steve Whitcher
Steve Whitcher

Check your settings for the software update point.   In the Administration section, under Site Configuration, Sites, right click on your Site and select "Configure Site Components".  You said you're set to synchronize from Microsoft update, so it sounds like the Sync Settings tab is good.  What about the Classifications tab, do you have everything selected there?  And on the Products tab, have you selected which products you want updates for?

One tricky little thing - the Products tab will update and list new products after you publish 3rd party updates from SCUP for the first time.  For example, if you have updates from Oracle for Java listed in SCUP, the first time you publish one for that company and application, you'll need to wait until after a software updates synchronization has completed in configmgr, THEN go in to the Software update Point Component Properties screen and select the new checkboxes for Oracle and/or Java.
Avatar of Chris Millard

ASKER

The first sync isn't taking place though. I do have products and classifications selected.
Under the Monitoring section, if you select "Software Update Point Synchronization Status", what does it show on the right?

Also under monitoring, look under "System Status", "Component Status".  What is the status of the "SMS_WSUS_SYNC_MANAGER", "SMS_WSUS_CONFIGURATION_MANAGER", and "SMS_WSUS_CONTROL_MANAGER"?

If any of those are showing a status other than OK, right click on them and select "Show Messages", "All".  What errors are in the logs?
Steve, under the Monitoring section - the "Software Update Point Synchronization Status" shows an icon of a software box with a blue icon. Site Code, Software Update Point and Synchronization Source are the only populated fields (Sync Source shows as Microsoft Update).

SMS_WSUS_SYNC_MANAGER is at Critical - error messages (id 6703) reads:-

WSUS Synchronization failed.   Message: WSUS update source not found on site TUC. Please refer to WCM.log for configuration error details..

SMS_WSUS_CONFIGURATION_MANAGER is at critical - error message reads:-

WSUS Configuration Manager failed to configure upstream server settings on WSUS Server "SRV-AD-01.tuc.local".    Possible cause: WSUS Server version 3.0 SP2 or above is not installed or cannot be contacted.

SMS_WSUS_CONTROL_MANAGER is showing as OK.

WSUS was installed through the Server Manager on Server 2012 and I assume is version 4.0.
WCM.log
WSUS console opens just fine. I have just looked at that article, but it refers to a 503 error in the WCM log file. I don't have a 503 error in mine.
ASKER CERTIFIED SOLUTION
Avatar of Chris Millard
Chris Millard
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Sorry, I didn't see the WCM.log file when I replied earlier.  That does make a difference.  It sounds like you've likely found the issue with the incorrect port setting, hopefully everything will go smoothly for you from here.
Found the problem myself.