SBS (and WHS?) if not dcpromo'd will, after seven days, shut down every hour.  The process sbscrexe.exe is created by the SBCore service.  If terminated it will immediately restart and it cannot be stopped.  The service SBCore cannot be set to "disabled".

There are two (three?) ways to work around this.  All will likely violate the MS EULA.

• Use Process Explorer to 'suspend' sbscrexe.exe
• Give Administrators permissions to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SBCore (and child nodes) and change the 'Start' DWORD from 2 to 4
• Deny the Everyone group all access to C:\WINDOWS\system32\sbscrexe.exe
• In Process Explorer kill sbscrexe.exe - it shouldn't restart
• services.msc should now show SBS Core Services as disabled

• An alternative approach is to disable the 'SBS Core Services' service in a particular hardware profile (ie can't do a outright disable) assuming there is only one hardware profile.

• Finally, repeated kills of the sbscrexe.exe process might completely kill it for a single session.

Edit - having an ntbackup process running in the background seems to stop sbcore from shutting down.
   

"The Microsoft Exchange Information Store service terminated with service-specific error 0 (0x0)."

AVG AntiVirus had expired which caused the Exchange AV module to fail:

"Error code -2147467259 returned from virus scanner initialization routine. Virus scanner was not loaded. " (Event ID 9581)

and

"Error 0x80004005 starting the Microsoft Exchange Information Store.

Failed to init VSERVER. " (Event ID 9564)

SOLUTION

Set "HKLM\system\Currentcontrolset\services\MsexchangeIS\Virusscan" to "0" and start service.  Renew AV subscription

After DS restore WSUS, SQL Reporting Services and SSEE failed to start.

For SSEE first extract ssee_10.msi from WSUSSetup*.msi\wYukon and then run the following command:

msiexec /i ssee_10.msi CALLERID=OCSetup.exe REINSTALL=ALL RINSTALLMODE=omus /qn REBOOT=ReallySupress /l*v c:\ssee_repair.log

Update Services (WSUS) wouldn't reinstall complaining about a lack of .NET Framework 2.0 and .NET Framework 2.0 wouldn't reinstall due to "... incompatible with a previously installed one" (ie NET2.0 SP1).  Solution is to change/repair from add/remove programs and reboot.

Reporting services is fixed by this, too.

Finally, for any EVENT IDs 1309s to run %WINDOWS%\Microsoft.NET\Framework\V2.0.50727\aspnet_regiis.exe -i

Can't install Service Pack (or some/all other updates) directly, from Windows Update or by WSUS.  See http://support.microsoft.com/default.aspx?scid=kb;en-us;822798 for solutions.

This worked for me:

create batch file (catroot2.cmd)

net stop cryptsvc
ren %systemroot%\System32\Catroot2 oldcatroot2
net start cryptsvc
cd %systemroot%\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
del /Q tmp*.cat
exit

Then delete all tmp*.cat files from %systemroot%\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE} (or add to batch file, as above)

Trying to run the Group Policy Results Wizard in SBS 2003 from the server to a remote PC gives the following error message:

Group Policy Error

Failed to connect to <computername> due to the error listed

below. Ensure that the Windows Management

Instrumentation (WMI) service is enabled on the

target computer, and consult the event log of the

target computer for further details.

Details: the RPC server is unavailable.

Needless to say, WMI and RPC server are both running on the target computer and the event log contains no entries.

The Microsoft solution is to enable "Allow Remote Administration Exceptions" in the Small Business Server Windows Firewall GPO (Computer Configuration | Administrative Templates | Network | Network
Connections | Windows Firewall | Domain Profile).

Naturally this doesn't help any.  A helpful post by DonL on Microsoft's public SBS newsgroup gives the fix:

The RPC port 135 is being blocked - by the Microsoft Firewall Client for ISA
2004. To unblock, do the following:

Go to ISA Server Management
Browse to "Firewall Policy"
Select "Edit System Policy"
Browse to "Active Directory" under "Authentication Services"
Uncheck the box titled "Enforce strict RPC compliance"
Click OK
Apply the new settings