Update Rollup 3 is now available for Windows Server Solutions Best Practice Analyzer. 4 fixes and 49 new checks are included.
The new checks that are added in this update are:
- 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.