Known Issues and Expected Situations with Patching on SBS 2008 and SBS 2011
SBS 2011


1.  SharePoint 2010

After the install of SharePoint update http://support.microsoft.com/kb/2345322 you may see an error message in the log files

Log Name: Application
Source: Microsoft-SharePoint Products-SharePoint Foundation
Date: 1/5/2011 6:00:00 PM
Event ID: 6398
Task Category: Timer
Level: Critical Keywords:
User: OFFICE\spfarm
Computer: DC01.office.lan
Description: The Execute method of job definition Microsoft.SharePoint.Administration.
SPUsageImportJobDefinition (ID 8a337ec2-bb36-4b3c-9d45-31a2edef6920) threw an exception.

More information is included below. Access to the path 'C:\Program Files\Common Files\
Microsoft Shared\Web Server Extensions\14\LOGS' is denied.

 Please review this blog post for resolution:

MPECS Inc. Blog: SBS 2011 – SharePoint Foundation Event ID 6398 – Access Denied Every 30 Minutes:
http://blog.mpecsinc.ca/2011/01/sbs-2011-sharepoint-foundation-event-id.html


     2.  Exchange 2010

a.  Issue with IE9 and Exchange 2010
The EXPTA {blog}: Issue with IE9 and the Exchange 2010 Management Console:
http://www.expta.com/2011/04/issue-with-ie9-and-exchange-2010.html
The workarounds are to end task mmc.exe every time or uninstall IE9.

b.  Disabled services 

Both Exchange 2010 and 2008 totally disable the services during any update, rollup or service pack and then reenable them at the end of the install. Thus you can find yourself after a reboot where email is not working and Exchange is not functioning.  Don’t panic, merely review the Exchange setup log file.  If it looks like everything completed correctly,  merely go back into the server and reenable the disabled services. 

For Exchange 2010 these are:

SharePoint unfortunately has a bad reputation of not updating well.  Keep in mind that in large server farms they update SharePoint BY HAND due to the fact that they need to have all servers get updates at the same time.  If you decide that you want to update SharePoint manually, install the update and be prepared to either run the SharePoint configuration wizard or run the psconfig command manually.

SBS 2008

     I.  Exchange 2007

Both Exchange 2010 and 2007 totally disable the services during any update, rollup or service pack and then reenable them at the end of the install. Thus you can find yourself after a reboot where email is not working and Exchange is not functioning.  Don’t panic, merely review the Exchange setup log file.  If it looks like everything completed correctly,  merely go back into the server and reenable the disabled services. 

For Exchange 2007 these are: 

     II.  Exchange updates for SBS.

Post SP3 on Exchange 2007, all Exchange service packs are SBS aware and do not need any special wrappers to install.

     III.  SharePoint Services

SharePoint unfortunately has a bad reputation of not updating well.  Keep in mind that in large server farms they update SharePoint BY HAND due to the fact that they need to have all servers get updates at the same time.  If you decide that you want to update SharePoint manually, install the update and be prepared to either run the SharePoint configuration wizard or run the psconfig command manually.