Update Rollup 3 for Windows Server Solutions Best Practices Analyzer 1.0 is available

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:

  1. Check whether backup fails because of a hidden partition.
  2. Check whether backup fails because the Exchange transaction log is missing or corrupted.
  3. Check whether backup fails because of SQL writer issue.
  4. Check whether last backup attempt failed.
  5. Check whether OWA app pool identity is not running under the default setting.
  6. Check whether OWA app pool .NET Framework is not using the default setting.
  7. Check whether OWA app pool pipeline is not using the default setting.
  8. Check whether OWA app pool bitness option is not set to the default.
  9. Check whether Exchange transport start mode is not set to the default.
  10. Check whether Exchange Transport service is not running.
  11. Check whether Exchange Transport service account is not using the default account.
  12. Check whether OnlyUseLatestCLR registry value is set incorrectly to 1.
  13. Check whether NT Backup is installed.
  14. Check whether IIS does not own port 80 (0.0.0.0:80) or port 443 (0.0.0.0:443).
  15. Check whether default website is not running in Microsoft Small Business Server 2011.
  16. Check whether start mode for NTFRS File Replication is not using default setting.
  17. Check whether NTFRS File Replication Service is not running.
  18. Check whether the NTFRS account is not using the default setting.
  19. Check whether Read and Script permissions on the /remote virtual directory are incorrect.
  20. Check whether on the /remote virtual directory, HTTP Redirect is set or inherited.
  21. Check whether host header on default website for port 80.
  22. Check whether Windows PowerShell virtual directory is not using the default SSL settings.
  23. Check whether start mode for the DFSR File Replication Service is not set to the default.
  24. Check whether DFSR File Replication Service is not running.
  25. Check whether DFSR File Replication account is not using the default setting.
  26. Check whether Office 365 Provider service is not using default account.
  27. Check whether Office 365 Provider service is not started.
  28. Check whether Office 365 Provider service is not using the default start mode.
  29. Check whether one or more WSUS Group Policies are missing.
  30. Check whether website registry value under RpcProxy set to Default Web Site.
  31. Check whether default website has the KerbAuth module enabled.
  32. Check whether default website has the WSMan module enabled on it.
  33. Check whether the account that is used as the Microsoft SharePoint Farm account is missing one or more group memberships.
  34. Check whether the account that is used as the SharePoint Web Application account is missing one or more group memberships.
  35. Check whether the account that is used as the SharePoint Search account is missing one or more group memberships.
  36. Check whether the account that is used as the SharePoint Farm account is missing one or more Microsoft SQL Server roles.
  37. Check whether the Web.config file is in the default website’s physical directory.
  38. Check whether one or more receive connectors’ MaxMessageSize does not match the get-transportconfig MaxReceiveSize.
  39. Check whether one or more send connectors’ MaxMEssageSize does not match the get-transportconfig MaxSendSize.
  40. Check whether the /EWS virtual directories maxRequestLength does not match the get-transportconfig MaxSendSize.
  41. Check whether MultiPoint Server 2011 is a beta version.
  42. Check whether one or more of the default WSUS groups are missing.
  43. Check whether the Block Level Backup Engine Services service is not using the default start mode.
  44. Check whether the Block Level Backup Engine Services service is not set to the default startup account.
  45. Check whether the common name on the certificate that is bound to the WSS Certificate Web Service website does not match the server name.
  46. Check whether the certificate for the Remote Desktop Gateway service seems to be bound incorrectly.
  47. Check whether one or more email-enabled document libraries exist but the Windows SBS Company Web Domain remote domain does not exist.
  48. Check whether the Windows SBS Company Web Domain remote domain does not have TNEFEnabled set to $false.
  49. Check whether the .NET Framework v1.1 is installed.

http://support.microsoft.com/KB/2699813

Leave a Reply

Your email address will not be published. Required fields are marked *