Today, I was fortunate enough to attend Shane Young, Microsoft MVP’s “Its Flu Season – How is your SharePoint Server Feeling?” webcast organized by the Ted Pattison Group. Shane’s Webcast was about the auditing the MOSS farm and how to do the health check on the MOSS farm.
Being a MOSS consultant, I have worked on many different SharePoint projects and I wanted find out how the experts perform the initial audit of the SharePoint farm. Most of the health checks tasks I typically perform were demonstrated by the Shane Young. Unfortunately there was no recording of the web cast but here is the quick recap of the check list, one might want to perform on the MOSS Servers for the initial health check. Hopefully Shane won’t mind having them documented here.
Web Front End Servers
- Check Installed Software through Add/Remove Software and make sure there is no unwanted software installed on the server.
- Check “My Computer” for number of drives, partitions, and used/available space. Add more space if it there is hard disk space problem. Make sure there are additional drives configured for the logs and index files.
- Go to “Task Manager” and check for CPUs, Resource Usage, Network Performance.
- Go to “System” in control panel and check for hardware profiles (RAM, Processor Speed, etc.), Automatic Updates (Make sure its disabled), and Networking Capabilities
- Check IIS Manager – Check for host headers and IP address bindings, SSL settings, App Pool Settings, and App Pool Service Accounts. Put the IIS Logs on the drive other than C.
- Check Event Log for any MOSS errors. Resolve all the critical errors.
Central Administration Site – Operations Tab
- Check Servers in farm page – Check for all the SharePoint servers with the same version and patch level
- Check the search service accounts on MOSS Search and WSS Search page, it should be dedicated account, shouldn’t be farm admin account
- On the MOSS Search Service for Index role, check for Indexer Performance based on the Number of CPUs on the machine. At minimum, use Partially Reduced
- On the MOSS Search Service for Index role, check WFE Crawling setting – Use all WFE servers for crawling. Do not use Dedicated WFE.
- Make sure only one server is running Index Role in the farm for each SSP
- Make sure WSS Search Service runs only once a day and only one instance of WSS Search Service runs on the farm
- Make sure Outgoing Email Settings are set to the valid exchange/SMTP server
- Check the Timer Job Status page – Check for any failed jobs
- Diagnostic Logging and Usage Analysis Logging – Change the default location to the drive other than C (e.g. F:\logs) and make sure all servers in the farm has a defined drive (e.g. F in this case).
- Check Current License Type – Verify what license is and make sure farm is not running on trial version. This is very crucial to understand what MOSS services are running on the farm.
Central Administration Site – Applications Tab
- “Check the Services Enabled in the Farm” section to see any farm configuration errors
- Make sure Web Application URLs and Content Databases has a meaningful name.
- Check the number of Content Databases per web application, site collection created per content databases, and verify round-robin allocations.
Content Databases on the SQL Server
- Check the DB size – Shouldn’t be more than 100 GB.
- DB Files Properties – Check the Auto Growth Settings – it should be minimum 500 MB or 1 GB.
- Transaction Log Files Properties – Check the log file size. It shouldn’t be large. Shouldn’t be more than 4-5 GB. If it’s too large, backup and shrink the logs, set the Auto Growth settings to reasonable settings.
- SSP Edit Page – Index files location other than C drive, Check for the SSP service accounts, and shouldn’t be farm admin accounts
- Search – Check Crawl Schedules and Crawl Log Errors. Make sure Crawl Schedules won’t overlap.
- User Profiles – Verify the Profile Source and Check the Crawl Schedules
Hopefully this will help auditing the next SharePoint farm you come across.