Update information
How to obtain this update
To obtain this update if you are running SBS 2011 Standard, use one of the following methods:
- By default, Microsoft Update points to the WSUS service in SBS 2011 Standard. This update is displayed in the Update tab of the Admin Console. After you deploy this update, it is displayed as available for installation in Microsoft Update.
- In SBS 2011 Standard, this update can also be installed directly by using Microsoft Update. To do this, start Windows Update and select the Check online for updates from Windows Update option. Then, click the Get updates for other Microsoft products option, and complete the process to opt in to Microsoft Updates. Then, click Check for updates in Microsoft Update to obtain the update.
To obtain this update if you are running SBS 2011 Essentials, Windows Storage Server 2008 R2 Essentials, or Windows Multipoint Server 2011, follow these steps:
- In Windows Update, click Click here for details next to Find out more about free software from Microsoft Update, and then follow the steps to obtain updates from Microsoft Update. If you have already opted in to Microsoft Updates, you can safely ignore this step.
- In Windows Update, click Check for updates.
Prerequisites
To apply this update, you must be running one of the following operating systems:
- Windows Small Business Server 2011 Standard
- Windows Small Business Server 2011 Essentials
- Windows Storage Server 2008 R2 Essentials
- Windows Multipoint Server 2011 Standard
- Windows Multipoint Server 2011 Premium
Additionally, you must have Windows Server Solutions BPA 1.0 installed.
Registry information
To apply the update in this package, you do not have to make any changes to the registry.
Restart requirement
You do not have to restart the computer after you apply this update.Update replacement information
This update replaces the following update:2600333 An update for Windows Server Solutions Best Practices Analyzer 1.0 is available
2652984 Update 2 for Windows Server Solutions Best Practices Analyzer 1.0 is available
Fixed issues that are included in this update
Issue 1
Symptom
Windows Server Solutions BPA is installed on Windows Multipoint Server, and then a shortcut to the tool is added to the desktop. This shortcut is visible to all the users for Windows Multipoint Server. All the client users can see this shortcut in their sessions.
Notes
- After you apply this update, this shortcut will be removed for all the users, even the administrator. This shortcut will not be displayed on anyone's desktop. The administrator has to go to the Start menu to manually start a BPA check.
- This change applies only to Windows Multipoint Server.
Issue 2
Symptom
Consider the following scenario:
- You Install Windows Server Solutions BPA and then select Yes to updates and integration.
- You run Windows Server Solutions BPA and wait until Windows Server Solutions BPA detects an update. However, you do not install the update.
- You run Windows Server Solutions BPA Schedule task manually in the following path:
Task scheduler\Task Scheduler Library\Microsoft\Windows server solutions BPA\Daily BPA check
In this scenario, you may receive the following errors in the Application log:
Log Name: Application
Source: Application Error
Date: 10/11/2011 10:04:16 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: computer name
Description:
Faulting application name: BPAUpdate.exe, version: 6.1.7900.2, time stamp: 0x4d4876b4
Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdfe0
Exception code: 0xe0434352
Fault offset: 0x000000000000aa7d
Faulting process id: 0x24c8
Faulting application start time: 0x01cc88270adadba8
Faulting application path: C:\Program Files\Windows Server Solutions BPA\Bin\BPAUpdate.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Log Name: Application
Source: .NET Runtime
Date: 10/11/2011 10:04:15 AM
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: computer name
Description:
Application: BPAUpdate.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.IOException
Issue 3
Symptom
You receive the following error messages after you configure a Best Practices Analyzer scheduled task:
Error message 1Log Name: Application
Source: MSExchange Common
Date: 12/26/2011 2:05:50 AM
Event ID: 4999 Task
Category: General
Level: Error
Keywords: Classic
User: N/A
Computer: computer name
Description: Watson report about to be sent for process id: 544, with parameters: E12, c-buddy-RTL-AMD64, 14.01.0355.001, BPA, M.E.Data.Directory, M.E.D.D.DSAccessTopologyProvider..ctor, S.IO.FileLoadException, 72f, 14.01.0355.001. ErrorReportingEnabled: False
Error message 2Log Name: MSExchange Management
Source: MSExchange CmdletLogs
Date: 12/26/2011 2:05:50 AM
Event ID: 8
Task Category: General
Level: Error
Keywords: Classic
User: N/A
Computer: <computer name>
Description:
(PID 544, Thread 5) Task Get-AcceptedDomain throwing unhandled exception: System.IO.FileLoadException: Mixed mode assembly is built against version 'v2.0.50727' of the runtime and cannot be loaded in the 4.0 runtime without additional configuration information. at
Microsoft.Exchange.Data.Directory.DSAccessTopologyProvider..ctor(String machineName) at
Microsoft.Exchange.Data.Directory.DirectoryServicesTopologyProvider.DiscoverConfigDC() at
Microsoft.Exchange.Data.Directory.DirectoryServicesTopologyProvider..ctor() at
Microsoft.Exchange.Data.Directory.TopologyProvider.InitializeInstance() at
Microsoft.Exchange.Data.Directory.ADServerSettingsHelper.set_ViewEntireForest(Boolean value) at
Microsoft.Exchange.Data.Directory.RunspaceServerSettings..ctor() at
Microsoft.Exchange.Configuration.Tasks.Task.InitializeRunspaceServerSettings() at
Microsoft.Exchange.Configuration.Tasks.Task.BeginProcessing().
{16434477-0a8d-4ef3-8e5b-104fb1cbcb6e}
Issue 4
Symptom
After you install Windows Server Solutions BPA on Windows Small Business Server Essentials or Windows Server Storage Essentials, the clients on the network start throwing the following alerts.
On the Windows 7 clients:
Computer Monitoring Error. Can only partially assess the health of this computer
On the Windows XP clients:
Cannot access the health of this computer because a component that is required to assess health is not available. Install the latest version of Windows PowerShell available from the Microsoft Web site
New checks that are added in this update
After you install this update, the Windows Server Solutions BPA adds the following new checks:
- Check whether backup fails because of a hidden partition.
- Check whether backup fails because the Exchange transaction log is missing or corrupted.
- Check whether backup fails because of SQL writer issue.
- Check whether last backup attempt failed.
- Check whether OWA app pool identity is not running under the default setting.
- Check whether OWA app pool .NET Framework is not using the default setting.
- Check whether OWA app pool pipeline is not using the default setting.
- Check whether OWA app pool bitness option is not set to the default.
- Check whether Exchange transport start mode is not set to the default.
- Check whether Exchange Transport service is not running.
- Check whether Exchange Transport service account is not using the default account.
- Check whether OnlyUseLatestCLR registry value is set incorrectly to 1.
- Check whether NT Backup is installed.
- Check whether IIS does not own port 80 (0.0.0.0:80) or port 443 (0.0.0.0:443).
- Check whether default website is not running in Microsoft Small Business Server 2011.
- Check whether start mode for NTFRS File Replication is not using default setting.
- Check whether NTFRS File Replication Service is not running.
- Check whether the NTFRS account is not using the default setting.
- Check whether Read and Script permissions on the /remote virtual directory are incorrect.
- Check whether on the /remote virtual directory, HTTP Redirect is set or inherited.
- Check whether host header on default website for port 80.
- Check whether Windows PowerShell virtual directory is not using the default SSL settings.
- Check whether start mode for the DFSR File Replication Service is not set to the default.
- Check whether DFSR File Replication Service is not running.
- Check whether DFSR File Replication account is not using the default setting.
- Check whether Office 365 Provider service is not using default account.
- Check whether Office 365 Provider service is not started.
- Check whether Office 365 Provider service is not using the default start mode.
- Check whether one or more WSUS Group Policies are missing.
- Check whether website registry value under RpcProxy set to Default Web Site.
- Check whether default website has the KerbAuth module enabled.
- Check whether default website has the WSMan module enabled on it.
- Check whether the account that is used as the Microsoft SharePoint Farm account is missing one or more group memberships.
- Check whether the account that is used as the SharePoint Web Application account is missing one or more group memberships.
- Check whether the account that is used as the SharePoint Search account is missing one or more group memberships.
- Check whether the account that is used as the SharePoint Farm account is missing one or more Microsoft SQL Server roles.
- Check whether the Web.config file is in the default website's physical directory.
- Check whether one or more receive connectors' MaxMessageSize does not match the get-transportconfig MaxReceiveSize.
- Check whether one or more send connectors' MaxMEssageSize does not match the get-transportconfig MaxSendSize.
- Check whether the /EWS virtual directories maxRequestLength does not match the get-transportconfig MaxSendSize.
- Check whether MultiPoint Server 2011 is a beta version.
- Check whether one or more of the default WSUS groups are missing.
- Check whether the Block Level Backup Engine Services service is not using the default start mode.
- Check whether the Block Level Backup Engine Services service is not set to the default startup account.
- Check whether the common name on the certificate that is bound to the WSS Certificate Web Service website does not match the server name.
- Check whether the certificate for the Remote Desktop Gateway service seems to be bound incorrectly.
- Check whether one or more email-enabled document libraries exist but the Windows SBS Company Web Domain remote domain does not exist.
- Check whether the Windows SBS Company Web Domain remote domain does not have TNEFEnabled set to $false.
- Check whether the .NET Framework v1.1 is installed.
Known issues
After you install Update Rollup 3 for Windows Server Solutions BPA, and start Windows Server Solutions BPA in Small Business Server 2011 Standard, you receive the following error message:
The /EWS virtual directories maxRequestLength doesn't match the get-transportconfig MaxSendSize
The checking logic of this rule is incorrect. If you change the value in the rule after the resolutions, Microsoft Exchange Web Services users are affected. Additionally, some Outlook Web Access scenarios are broken.
This issue does not occur if the
maxRequestLength value is set to the default value of 2097151 (2GB).
You can safely ignore this warning on Small Business Server 2011 Standard servers.For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: 824684 Description of the standard terminology that is used to describe Microsoft software updates