WSUS maintenance and SCCM 2012 r2

[draker]

Hello,

 

I have read several articles on WSUS and SCCM. Many articles don't mention the fact that WSUS if not maintained will eventually slow to a grinding halt because it needs monthly maintenance ran on the DB.

 

This article actually describes what I am trying to avoid pretty well!

 

http://blog.coretech.dk/kea/house-of-cardsthe-configmgr-software-update-point-and-wsus/

 

I've also been told that no changes should be made to WSUS because SCCM controls the WSUS server.

 

 

 

 

At this point I have edited the membership on all expired and superseded updates. I would like to run the cleanup wizard on the WSUS server.. and if it fails I would like to run manual obsolete update queries on the DB as described in the linked article above. I have ran these on our standalone WSUS instances with great success.

 

My concern here is that somehow SUP will break because updates are missing or something.

 

I have read the articles on manual cleanups of the source directory etc, that's not what I am looking to do. I am looking to maintain WSUS so my nightly syncs don't start failing.. etc.

 

Can anyone speak to what is described in the linked article above? Is running the wsus cleanup wizards monthly safe?

 

 

 

[l.hv.yang]

I run the cleanup monthly and have no issues with SUP breaking. So far so good.

[Peter van der Woude]

Running the cleanup wizard should not harm your software update point.

[draker]

Thanks for the replies! I will give it a shot next week.

 

Do you run the wizard with all clean-up options selected?