Seeing issues with svchost spiking the cpu on SBS 2008 servers?

http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/a0903c99-cf2b-4877-b494-2ef202348afa

http://social.technet.microsoft.com/Forums/en-US/exchangesoftwareupdate/thread/80bcd162-8eee-445d-84c2-6118d62c39b4/

http://social.microsoft.com/Forums/en-US/partnermsgexchange/thread/ba988ad0-59c4-46d7-b242-29ad00049649

http://social.microsoft.com/Forums/en-US/partnerwinserversbs/thread/0d5304c0-3fbe-41ff-8fec-4f9ae843e7cd/

At an Exchange powershell command window (open up the Exchange shell with a runas admin) type in Disable-antispamupdates  and say Yes to disable antispam updates for now.

Then go into services, stop Windows Update service and restart it.  You’ll see the svchost spike problem go away.

When the issue resolves, I’ll tell you to flip them back on.  If you temp disable them now, you won’t spike the cpu on the box.

The issue has been resolved.  If you disabled antispam updates, turn them back on.

So during migrations some people are installing the ntbackup code on their SBS 2011 boxes.  This allows you to restore data from your SBS 2003.  <Unconfirmed at this time> It appears that on some hardware configurations or setups if you leave this ntbackup code in the server and then attempt to do a bare metal install, you’ll end up with a blinking cursor on a black screen. 

Hyper-V – SBS 2011 – Black Screen:
http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/be28b0a1-9cad-45aa-ad4c-b9e85e3128d2/

The moral of this story is, when you complete the process of migration, uninstall KB974674.

I’m thankful for my friends and family.

I’m thankful for the folks behind the SBS blog

I’m thankful for Brian Krebs and his blog..and I just donated to ensure his blog keeps going.

And of course, I’m thankful for all of you that read the blog and inspire me.

Thanks.