IT tutorials
 
Technology
 

SharePoint 2010 : Monitoring and Reporting - Editing rule definitions in the health analyzer

8/13/2013 11:30:52 AM
- Free product key for windows 10
- Free Product Key for Microsoft office 365
- Malwarebytes Premium 3.7.1 Serial Keys (LifeTime) 2019

SharePoint 2010 has a built-in health analyzer that acts as a best practice analyzer. The health analyzer will report whether or not the farm is compliant with each predefined health rule. The health analyzer builds upon the best practice analyzer from Microsoft Office SharePoint Server 2007.

There are roughly 65 rules that are categorized as follows:

  • Security

  • Performance

  • Configuration

  • Availability

Each rule is run by a timer job, and each rule has a specific purpose such as checking application pool memory, checking how security is configured on the farm, or checking drive space.

In Central Administration, it is possible to edit existing rules in order to meet the needs of your organization. Changes can be made to the scheduled execution of the job. On the ribbon, there is an option named Run Now that will execute the rule immediately. The rules are available out of the box and are meant to allow you to be proactive.

In this recipe, we will modify one of the existing health analyzer rules.

Getting ready

You must have farm-level administrative permissions to the Central Administration site.

How to do it...

  1. Open the SharePoint 2010 Central Administration website.

  2. Click Monitoring.

  3. Under the Health Analyzer section, click Review rule definitions.

  4. Under the category Security, click The server farm account should not be used for other services.

  5. A form pops up, which contains the parameter of the rule. The left-most ribbon button is Edit Item; click the button. The following screenshot appears:

  6. Change the Schedule to Daily, from the default value of Weekly.

  7. You must also manually change the value of the parameter Version. Change it to 2.0, from present 1.0.

  8. Click Save.

How it works...

The health analyzer rule definitions are run via the timer jobs. There are several parameters that the administrator can modify:

  • Title: This is the text description of the rule.

  • Scope: This is where the rule will run.

  • Schedule: This is how often the rules are employed.

  • Enabled: This designates the rule as active.

  • Repair Automatically: When the timer job kicks off, it will check the rules. If the rule can be checked and then corrected via SharePoint best practices, it will be.

  • Version: This is a manually edited text box that tracks versioning of the rules.

The page also notes who created the rule, and when the rule was last edited and by who.

There's more...

In addition to being able to edit the rule, there are several other parameters as shown by the following screenshot:

  • Version History: Shows all the versions

  • Alert Me: This notifies you when changes are made

  • Run Now: This executes the rule

More info — adding a new health rule

Every rule that a farm installation may need cannot be covered by the out of the box health rules. For instance, consider monitoring the number of tenants in the user profile social database. There may be a need for a governance rule that monitors this and flags the administrator when certain levels are reached; however, there is no out of the box rule available today that can help govern this.

In order to implement a new health rule, code must be written to utilize the Microsoft.SharePoint.Administration.Health namespace&;. Once the assembly is written, it must be placed in the Global Assembly Cache (GAC)&; on every machine. The new health rule must then be registered with the SharePoint Health Analyzer. The best way to do this is to create a SharePoint feature that can be activated and deactivated.
 
Others
 
- SharePoint 2010 : Monitoring and Reporting - Configuring what gets logged
- SharePoint 2010 : Monitoring and Reporting - Accessing the SharePoint 2010 logging database
- Windows Server 2012 : Using Event Viewer for Hyper-V troubleshooting
- Windows Server 2012 : Tuning your Hyper-V server
- Windows Server 2012 : Using Resource Metering
- Windows Server 2012 : Monitoring Hyper-V Replica
- Windows Phone 8 : Other Ways of Launching Your App (part 2) - Using a File Association
- Windows Phone 8 : Other Ways of Launching Your App (part 1) - Using a Custom Protocol
- Windows Phone 8 : Phone Integration - Live Tiles (part 2)
- Windows Phone 8 : Phone Integration - Live Tiles (part 1)
 
 
Top 10
 
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
Technology FAQ
- Is possible to just to use a wireless router to extend wireless access to wireless access points?
- Ruby - Insert Struct to MySql
- how to find my Symantec pcAnywhere serial number
- About direct X / Open GL issue
- How to determine eclipse version?
- What SAN cert Exchange 2010 for UM, OA?
- How do I populate a SQL Express table from Excel file?
- code for express check out with Paypal.
- Problem with Templated User Control
- ShellExecute SW_HIDE
programming4us programming4us