firstcom Posted November 19, 2015 Report post Posted November 19, 2015 I'd love to hear from those of you that have a similar set up as our environment. We have an external WSUS server and two SUPs -- one as a primary and a disaster recovery SUP. Best practice suggests using one database for multiple SUPs, but obviously in a DR situation we'd want a completely separate database in our DR datacenter - so that can't apply in that scenario. I was told it was a best practice to let SCCM handle all WSUS administration, but I've also read articles stating that WSUS needs to be pruned and cleaned up regularly. I don't think these articles were users that utilized SCCM in combination with WSUS, however. Within SCCM, I have set it to expire superseded updates after one month. Our WSUS server has around 14,000 total updates. In SCCM, I have divided our update groups into OS or product, as recommended by best practice guides. We fall within guidelines of having 1000 or less updates per update group, with the largest having around 600-700. However, I'm curious if the WSUS side of things is being kept to best practice with this scenario/environment. Should I be pruning it and performing clean ups, or should I let SCCM handle it entirely? Thank you! Quote Share this post Link to post Share on other sites More sharing options...
