Wsus on Secondary Site

[DimStam]

Hello , i have a simple question maybe for the most of you . I have an SCCM 2012 infra with SUP :

 

Site 100 - Primary Site , WSUS ( Sync with MS updates )

Site 200 - Secondary Site , WSUS (Downstream from Site 100)

Site 300 - Secondary , WSUS (Downstream from Site 100)

Site 120 - Secondary Site , WSUS (Downstream from Site 100)

 

All secondary sites are with low bandwidth network connectivityto Primary and for this i installed the WSUS's . I would like to ask what is the diference between distribute software updates from Primary site - > secondary sites via SCCM distribution points , does need to have WSUS's on every Secondary ? When i deploy software updates to clients on secondary sites , the primary site create a package with all the selected updates and send it to distribution points in secondary sites , Right ? So the selected updates are into the package that i distribute . Why to have WSUS's on secondary sites ?

 

Thanks a lot !

[LawrenceGarvin]

The WSUS servers are not required on the secondary sites. The sole purpose of the WSUS server is to allow the Software Updates Agent to obtain the update metadata (detection logic) to determine the compliance state of an update. This compliance state is then reported by the CMAgent to the Management Point (MP).

 

All updates are obtained from a Distribution Point. Your concern with bandwidth connectivity is a strong case for having Distribution Points in your remote sites.

 

Whether a WSUS server in the Secondary Site will be of notable benefit really depends on the number of clients in those remote sites. The value in having a downstream SUP in Configuration Manager is to support sites with a large number of clients. If your sites have less than a hundred clients, you probably will not see sufficient value in the deployment of the downstream SUP to justify the expense of maintaining and administering it.