localzuk Posted July 31, 2012 Posted July 31, 2012 (edited) I'm still getting my head around SCCM and would find it useful if someone could confirm the following for me. I can use WSUS as normal if I want - just tell it to deploy updates to machines per the rules within it, or I can use SCCM and create the following: A deployment package (ie. a share somewhere) (DP) An automatic deployment rule (ADR) So then on the schedule, the WSUS server synchronises itself, and then on its own schedule the ADR evaluates the updates and automatically marks those that apply to it for deployment, marking superseded ones as not for deployment etc... It then copies the files into the DP, which the machines in the Device Collection then use to update themselves. Is this all correct? Does this mean that you potentially end up with 2 copies of the updates on a server - one in WSUS and one in SCCM? On a related note, in WSUS I can run the Server Cleanup Wizard to get rid of old stuff. Is there something similar in SCCM? Or a way to automatically delete old/superseded updates? For example, my SCEP definitions DP now has 300MB+ of definitions in it, and it only needs be the latest one. Edited July 31, 2012 by localzuk
FN-GM Posted July 31, 2012 Posted July 31, 2012 On my SCCM course they said dont touch WSUS once you have linked it with SCCM. Do everything in SCCM, it should be manageable.
localzuk Posted August 1, 2012 Author Posted August 1, 2012 Seems the only way to do this is by creating a script, or manually deleting updates from a deployment package (and then refreshing that package, which deletes the physical files from the share).
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now