How does a change in SCCM architecture affect WSUS?
We haven't used WSUS until we got into SCCM, and use it now only under SCCM auspices.
A recent rearchitecting of our SCCM infrastructure (replaced central site, de-parented and re-parented its children) appears to have affected parts of WSUS.  Some clients are not taking any updates, apparently due to synchronization issues between their WSUS server and the WSUS server's parent.  The WSUS consoles indicate there are now some patches the WSUS child servers know about that their parent does not -- probably not the way it's supposed to be.
I'm looking for guidance or best practice on how we *should* have gone about handling WSUS in our SCCM re-architecting, and how to fix sync issues now among the WSUS servers.  I did download the (150pp!!) WSUS Ops Guide, but it doesn't mention managing in an SCCM environment.  And the SCCM guidance is to stay away from the WSUS consoles anyway, let SCCM handle it.
So where do we go from here?  Any best practices from the field?

TIA.

Jeff Kantner
January 21st, 2010 1:32am

Yes, I know this is an old post, but Im trying to clean them up. Did you solve this problem, if so what was the solution?

Free Windows Admin Tool Kit Click here and download it now
May 22nd, 2015 3:22pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics