And Kent Agerlunds WSUS cleanup:
And Steve Thompson tip about Optimizing Your databases! Very good solution that I use alot:
Other tips I've pickup along the way:
- Set initial Database size to what its exptected and calculated to be before Configmgr goes into production. (To prevent fragmentet database disk file and lock files)
- Dont use too many Collections with Incremental Updates switched on. Maximum 200 pr hiearchy.
- Careful tuning and switching on to many hardware classes in inventory settings for clients. And dont schedule too often.
- Dont schedule Policy update for Clients for less than 30min, and use longer interval for server clients.
- And remember Antivirus Exclusion: http://www.systemcenterblog.nl/2012/05/09/anti-virus-scan-exclusions-for-configuration-manager-2012/ http://blogs.technet.com/b/systemcenterpfe/archive/2013/01/11/updated-system-center-2012-configuration-manager-antivirus-exclusions-with-more-details.aspx
- Antivirus Exclusion is important for all your systems: http://social.technet.microsoft.com/wiki/contents/articles/953.microsoft-anti-virus-exclusion-list.aspx
Keep things simple and supported.