SBS Monitoring with high CPU load

Just encountered an issue with an SBS 2008 server. High CPU load was caused by the SBSMonitoring SQL instance. Eventually narrow it down and applied the fix described here:

http://social.technet.microsoft.com/Forums/en/smallbusinessserver/thread/d195baac-da8b-4387-9079-c55d5e1879b4

Whilst checking the event log afterwards, I also noted these information events. Another Google search promised resolution by using this fix:

http://social.msdn.microsoft.com/Forums/en/sqldatabaseengine/thread/0b3a2163-929f-4ba6-8e74-3d683aea19f1

Resolving Common SBS Event Log Entries

This message used to appear on most of my clients weekly "Network Reports":

Windows SharePoint Services 3 Search
Event ID: 2424
Event Details:
The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again. Context: Application "Search", Catalog "index file on the search server Search"

There are quite a few references out there on how to resolve this issue, but equally enough reports that the presented solution did not work. First up I checked this MS KB article to see if it fixed the issue. The problem persisted and eventually I found this SBS blog post, which looks credible and explains what happens. I implemented the suggestion they refer to - yet another blog posting which resolved the issue.

Another message frequently encountered is:

DCOM
Event ID: 10016
Event Details:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {61738644-F196-11D0-9953-00C04FD919C1} to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

This one is easier to fix, using this blog post as a guide.