We have an SCCM 2012 environment with a Single Primary Site containing multiple Software Update Points (SUPs).
These SUPs are located in the same Central Site, are all sharing a single SUDSB database (as recommended by Microsoft), and this database is being synchronized from the external "Microsoft Update" location by the Master SUP (the
first one that we installed).
We have some large remote locations however, and we plan to install Secondary Site Servers in these sites. These Secondary Site Servers will have the SUP role installed on them, so all of the clients in each of these sites will use this
SUP rather than one of those at the Central Site.
We've set up one of these as a test, but have questions around the configuration...
We installed the WSUS role on this Secondary Site Server, configuring it to point to the single SUSDB database Server in the Central Site that all of the other SUPs share... We weren't certain whether this was correct, but it seemed the
most sensible option..?
Then when we configured the SUP in the Secondary Site, the options of where to synchronise from were greyed out, with the "Synchronize from an upstream data location (URL)" selected. This was reasonable we thought, as being a
Child Site that's what you'd expect it to do - and there seemed to be no option to change it in any case.
The question then is how this Secondary Site SUP will synchronise - if it does (which we're not sure of). Looking at the "Software Update Point Synchronization Status" window in the Monitoring workspace, the SUP on the Secondary
Site Server has a different icon to the others (a box with a green arrow and a blue circle with an exclamation mark in it, rather than a green circle with a tick in it for the Primary Site SUPs), and so far it doesn't seem to have attempted to synchronise,
and has no catalog version... This panel also indicates that it's Synchronisation Source is "Microsoft Update" - the only other SUP that has this is the Master SUP (which is reasonable as it is connecting to Microsoft Updates site); the other SUPs
in the Primary Site have the Master SUP as their Synchronisation Source, which is what I would have expected to see for the Secondary Site SUP as well..
Can anyone clarify how the Secondary Site SUP configuration should look, and where it should synchronise from? I've seen a couple of other items that suggest that a Secondary Site Server gets a replicated copy of the SUSDB Database from
the Primary Site and synchronises from this, but I can see no evidence of one in the Database instance on the Secondary Site Server - only the Replicated Site Database subset.
Thanks & Regards,
Alex Line