Chapter 13
Monitoring the SharePoint Environment
Microsoft Exam Objective Covered in This Chapter:
- Maintaining a SharePoint Environment
- Monitor and Analyze a SharePoint Environment
Once you have the SharePoint Server 2010 environment configured and operating as you desire, you are responsible for monitoring SharePoint, not only to determine when errors occur and when corrective action is required but to review and analyze the long-term operation of SharePoint. This allows you to see trends and to decide when changes to SharePoint, such as adding additional servers, are required based on those trends.
Understanding Monitoring Tools
In general, monitoring involves a collection of tools that lets you view the actions of various features and activities in SharePoint in order to establish a baseline of systems operations, determine when problems occur, and note trends that may require changes in the SharePoint hardware, deployment, and configuration settings.
Monitoring features are enabled in SharePoint by default using a collection of standard settings. As a SharePoint administrator, you may determine that monitoring settings need to be adjusted to meet your technical or business requirements. You have the ability to modify the settings for diagnostic logging and health and usage data collection.
Diagnostic Logging
Diagnostic logging is composed of a series of logs that collect data typically used in troubleshooting errors in SharePoint. Although the default settings are sufficient for most SharePoint deployment scenarios, you can adjust the configuration for diagnostic logging to more closely match your company’s requirements. Changes to diagnostic logging settings are sometimes made when you require the system to collect more data more often such as when making a significant hardware or configuration change to the SharePoint environment.
Health and Usage Data Collection
Health and usage data collection is a set of monitoring tools that gather different types of data including event log data, performance counter data, and timer service metrics data. These tools use specific timer jobs to perform their tasks, and once the information has been collected, it is used to create various reports, such as administrative, health, and web analysis reports. Adjustments you can make to these features include changing the schedule for the timer job, controlling data collection, manually triggering timer jobs, and disabling timer jobs.
SharePoint Health Analyzer
The SharePoint Health Analyzer runs a set of predefined health rules against servers in the SharePoint farm to monitor any potential configuration and performance issues. When a rule is run and fails, the result is written to the Health Analyzer Reports list and Windows event log. The failure also triggers an alert that is sent to the Health Analyzer Reports live found on the Review Problems And Solutions page in Central Administration, so you have multiple avenues for locating and reviewing this data. If you suspect that the rule itself may be poorly configured in relation to your purposes, you can also modify the rule to result in more accurate readings.
The Health Analyzer Reports list is just like any other list in SharePoint and can be configured and modified the way you would any other list. You can also export list items to an Excel spreadsheet for further analysis or to send via email.
Actions you can modify in relation to this tool are enabling or disabling rules, modifying the schedule by which rules run, defining the scope of rules, triggering rules manually, and having an email alert sent when a rule fails.
This section of the chapter will provide you with the necessary information for configuring and editing all monitoring tools in SharePoint. This includes the configuration of diagnostic logging, usage and health data collection, and the SharePoint Health Analyzer.
Configuring Diagnostic Logging
Although diagnostic logging is enabled by default when you install SharePoint, you can control a number of features regarding this utility including event throttling and event log flood protection. Exercise 13-1 shows you what’s involved. You will need to be a member of the Farm Administrators group to successfully complete this task.
Exercise 13-1: Configuring Diagnostic Logging
1. Go to the Central Administration home page and click Monitoring.
2. On the Monitoring page, click Configure Diagnostic Logging under Reporting.
3. On the Diagnostic Logging page, under Event Throttling, to configure event throttling for all categories, click the All Categories check box, select the desired event log level in the Least Critical Event To Report To Event Log list, and then select the desired trace log level from the Least Critical Event To Report To The Trace Log list.
4. To configure event throttling for one or more categories, select the check boxes next to the desired categories and then select the desired event and trace log levels from the lists mentioned in the previous step, as shown here.
5. To configure event throttling for one or more subcategories of a category, expand the plus (+) sign next to the desired category, select the check box next to the desired subcategory, and then select the desired event and trace log levels from the lists mentioned in step 3.
6. To set event throttling for all categories back to their default levels, select the All Categories check box and then select Reset to default in both the Least Critical Event To Report To The Event Log list and the Least Critical Event To Report To The Trace Log list.
7. Under Event Log Flood Protection, select the Enable Event Log Flood Protection check box.
8. Under Trace Log, type the path to the folder where you want the logs written in the Path field.
9. In the Number Of Days To Store Log Files field, type the number of days you want logs retained, from 1 to 366, before the files are deleted.
10. If you want to limit how much disk space the logs can use, select the Restrict Trace Log disk space Usage check box and then type the number in gigabytes (GB) that you want to be the disk space limit for log files.
11. When finished, click OK.
For step 10, once the disk space limit has been reached, older logs will be deleted to make room for newer logs.
You can perform the same task using Windows PowerShell. To do so, open PowerShell as an administrator, type the following cmdlet string at the prompt, and then press Enter, selecting the desired parameters and substituting your production values for the sample values:
Set-SPLogLevel -TraceSeverity {None | Unexpected | Monitorable | Medium | High | Verbose} -EventSeverity {None | Information | Warning | Error | Critical | Verbose} [-Identity <Category name...>] -Verbose
Going through Exercise 13-1 will help you understand the options available with the Set-SPLogLevel cmdlet. You want to select one option for -TraceSeverity such as Medium, one option for -EventSeverity such as Error, and you can use the Identity parameter to select one or more categories to change, such as Administration. If you want to view current settings, use Get-SPLogLevel, and to reset categories back to the default levels, use Clear-SPLogLevel.
Configuring Usage and Health Data Collection
As mentioned earlier in this chapter, the usage and health data collection system uses specific timer jobs to perform monitoring tasks and collect monitoring data and then writes data to the logging folder and logging database. Exercise 13-2 shows you how to configure this logging tool. You need to be a member of the Farm Administrators group to perform this task. Also, any settings you make are applied to the entire farm and cannot specify a smaller group of servers.
Exercise 13-2: Configuring Usage and Health Data Collection
1. Go to the Central Administration home page and click Monitoring.
2. On the Monitoring page, click Configure Usage And Health Data Collection under Reporting.
3. On the Usage And Health Data Collection page, select the Enable Usage Data Collection check box under Usage Data Collection.
4. Under Event Selection, select the check boxes for the events you want to be logged in the Events To Log list.
5. Under Usage Data Collection Settings, type the path to the logging folder in the Log File Location field, which is a location that must exist on all servers in the server farm.
6. Type the maximum disk space in gigabytes (GB) that the logs may use in the Maximum Log File Size field.
7. Under Health Data Collection, select the Enable Health Data Collection check box.
8. To change the health data collection schedules, click Health Logging Schedule, and in the list of timer jobs that appears, click the desired timer jobs and then either change the schedules or disable the timer jobs.
9. Under Log Collection Schedule, to change the schedules for log data collection, click Log Collection Schedule. In the list of timer jobs that appears, click the desired timer jobs and then either change the schedules or disable the timer jobs as seen here.
10. Under Logging Database Server, select either Windows Authentication or SQL Authentication to change the authentication option or accept the default setting.
11. Click OK when you’re finished.
When selecting the events to log, keep in mind that the more selections you make, the more resources the logging system will consume. Choose to log only those events for which you need regular reports. If you are making a specific change in your system and need additional reports for those events, enable logging for them only as long as you need the information. Afterward, go back in and disable logging for the added events.
In the last step before exiting, you selected the authentication method for the logging database server; however, you cannot change the name of the database server or the name of the database used for logging. That modification can be made only using Windows PowerShell. This task will be subsequently presented in this portion of the chapter.
You can perform a number of tasks on the usage and health data collection system using Windows PowerShell, including configuring the system as a whole, as you just did with Central Administration. To do so, open Windows PowerShell as an administrator, type the following string at the prompt, and then press Enter, selecting the desired parameters and substituting your production values for the sample values:
Set-SPUsageService [-LoggingEnabled {1 | 0}] [-UsageLogLocation <Path>] [-UsageLogMaxSpaceGB <1-20>] [-Verbose]
For the -LoggingEnabled switch, select 1 to enable logging and 0 to disable logging. For the -UsageLogLocation, type the path to the logging folder. For the -UsageLogMaxSpaceGB switch, enter a value from 1 to 20 to indicate the amount of disk space to be allowed by the logs.
Using PowerShell, you can specify a specific type of event to be logged and the number of days it will be kept before deletion. At the prompt, type the following string and then press Enter, using the desired parameter values and substituting your production values for the sample values:
Set-SPUsageDefinition -Identity <GUID> [-Enable] [-DaysRetained <1-30>] [-Verbose]
The -Enable switch turns on usage logging for the specified event, and the GUID used with the -Identity switch specifies the event to be logged. Enter a value from 1 to 30 for the number of days you want the log retained.
If you choose to log usage data to a different database than the one used by default, you must use Windows PowerShell to make the specification. At the command prompt, type the following string and then press Enter, indicating the actual name of the database server,the database, and a username and password that has rights to the server and database:
Set-SPUsageApplication -DatabaseServer <Database server name> -DatabaseName <Database name> [-DatabaseUsername <User name>] [-DatabasePassword <Password>] [-Verbose]
You do not have to add the username and password if the account you’re already logged in with has access to the relevant database server and database.
Configuring the SharePoint Health Analyzer
A SharePoint administrator can be expected to configure both the timer jobs for the Health Analyzer as well as the rules. Exercise 13-3 shows you how to perform the timer jobs task using Central Administration. You must belong to the Farm Administrators group to complete this task. Also be aware that this configuration has a farm-wide scope. You cannot configure Health Analyzer timer jobs for just a few servers in the farm.
Exercise 13-3: Editing Health Data Collection Timer Jobs
1. Go to the Central Administration home page and click Monitoring.
2. On the Monitoring page, click Configure Usage And Health Data Collectionunder Reporting.
3. On the Configure Usage And Health Data Collection page, click Health Logging Schedule under Health Logging.
4. When the Job Definitions page opens, click the desired timer job.
5. On the Edit Timer Job page, modify the timer job schedule to the desired parameters under Recurring Schedule and then click OK.
This task is substantially similar to Exercise 13-2, which shows you how to go in and edit or disable a timer job after initially configuring it.
The same task can be performed in Windows PowerShell using a series of command strings. To begin, open PowerShell as an administrator. At the prompt, type this cmdlet using the desired values and parameters and then press Enter:
Set-SPTimerJob [-Identity <name>] [-Schedule <Schedule string>]
For the -Identity parameter, type the name of the timer job. If you do not specify a name for Identity, all timer jobs will be affected by the schedule change. If you don’t know the name of the specific timer job you are looking for, type the following at the prompt and then press Enter:
Get-SPTimerJob | Format-Table -property id,title
To see a list of the current timer jobs and their schedules, type the following at the prompt and then press Enter:
Get-SPTimerJob | Format-Table -property id,title,schedule
There are a large number of specific values you can type at the -Schedule switch. Use one of the following lines of code to set the timer job schedule you want to apply:
every <1-60> seconds
every <1-60> minutes at <1-60>
every <1-60> minutes between <1-60> and <1-60>
hourly between <1-59> minutes past the hour and <1-59> minutes past the hour
daily between starting from <hh:mm:ss> and starting no later than <hh:mm:ss>
weekly between starting on <day of the week hh:mm:ss> and starting no later than <day of the week hh:mm:ss>
monthly between starting on < day number hh:mm:ss> and starting no later than < day number hh:mm:ss>
monthly by <hh:mm:ss> on <week number> <day of week>
You can edit the rules for the Health Analyzer in Central Administration. You must be a member of the Farm Administrators group to complete the task. Exercise 13-4 shows you how.
When you modify a health rule, you can edit Configurable Fields and Read-Only Fields.
Configurable Fields are Title, which is the name of the health rule; Scope, which indicates which server or servers the rule runs against; Schedule, which defines the schedule for the rule; Enabled, which shows whether the rule is on or off; Repair Automatically, which if on, tries to fix any errors the rule encounters; and Version, which tracks the version history of the rule.
Read-Only Fields include Version, which only lists the version number for the rule; Created At, which shows the date and time that the rule was made; and Last Modified, which shows the date and time the rule was last edited.
Exercise 13-4: Configuring Health Data Collection Rules
1. Go to the Central Administration home page and click Monitoring.
2. On the Monitoring page, click Review Rule Definitions under Health Analyzer.
3. On the Health Rule Definitions page, click the desired rule under the desired category.
4. When the Health Analyzer Rule Definitions dialog box opens, click Edit Item.
5. Edit any of the rules as you desire. When you’re done, click Save or click Cancel to close without saving any changes, as shown here.
Now that you have your environment set up to gather information, once sufficient data is collected, you are responsible for reviewing the various logs and reports that are available in SharePoint. You can review administrative reports, diagnostic logs, health reports, timer jobs, and health reports.
Reviewing Reports Using Central Administration and Windows PowerShell
Most of the report review tasks you perform are done in Central Administration, but a few can be done using Windows PowerShell. Exercise 13-5 illustrates the steps for reviewing administrative reports in Central Administration. You must be a member of the Farm Administrators group to perform the following steps.
Exercise 13-5: Reviewing Administrative Reports
1. Go to the Central Administration home page and click Monitoring.
2. On the Monitoring page, click View Administrative Reports under Reporting.
3. On the Administrative Report Library page, click the name of the desired report folder.
4. On the Report Folder page, click the name of the desired report.
5. If you want to filter the results on the page, make the desired filter changes and then click Apply Settings.
Filtering can help you narrow down the scope of the data you are exploring so that you can focus on the information that’s most important to you.
Viewing Log Events with Windows PowerShell
Interestingly enough, you can filter diagnostic logs in a number of ways using Windows PowerShell. PowerShell can access the Universal Logging System (ULS) logs in SharePoint and, depending on the parameters used, view the raw data and apply specific filters to your views. To do so, open PowerShell as an administrator, and to view all trace events, type the following at the prompt without any parameters and then press Enter:
Get-SPLogEvent
You can use a number of parameters and values to filter your view of the event logsas follows.
To view an event log by area, type the following at the prompt and then press Enter, inserting your production value for Area at the appropriate switch:
Get-SPLogEvent | Where-Object {$_.Area -eq <Area>}
To view event logs by category, type the following string at the prompt and then press Enter, putting in the production value for Category at the Category switch:
Get-SPLogEvent | Where-Object {$_.Category -eq <Category>
To view an event log by event ID, type the following string at the prompt and press Enter, replacing the sample value with the actual event identifier at the EventID switch:
Get-SPLogEvent | Where-Object {$_.EventID -eq <EventID>}
To view an event by level, type the following string at the prompt and press Enter, entering the desired level such as warning or error at the Level switch:
Get-SPLogEvent | Where-Object {$_.Level -eq [Information | Warning | Error | Critical | Verbose | Unexpected | Monitorable | High | Medium]}
To filter event log content by a specific text string, enter the following command at the prompt and press Enter, replacing the sample value with the actual string of text by which you want to filter:
Get-SPLogEvent | Where-Object {$_.Message -like "*<string>*"}
To filter event logs by process, type the following command at the prompt and then press Enter, replacing the process sample value with the value of the actual process property:
Get-SPLogEvent | Where-Object {$_.Process -like "*<Process>*"}
You can use Central Administration to view SharePoint health reports. Exercise 13-6 gives you the steps. You must be a member of the Farm Administrators group to perform this task.
Exercise 13-6: Reviewing Health Reports in Central Administration
1. Go to the Central Administration home page and click Monitoring.
2. On the Monitoring page, click View Health Reports under Reporting.
3. On the Report page, click the name of the desired report.
4. When reviewing the report, click the desired data criteria and then click Go.
5. Click the desired column name to sort data rows.
Timer jobs run specific services in SharePoint defining the schedule for these services including monitoring. You can view the status of timer jobs using either Central Administration or Windows PowerShell. Exercise 13-6 shows you the Central Administration method. You must be a member of the Farm Administrators group to perform this task.
Exercise 13-7: Reviewing Timer Jobs in Central Administration
1. Go to the Central Administration home page and click Monitoring.
2. On the Monitoring page, click Check Job Status under Timer Jobs.
3. On the Check Job Status page, use the paging arrows at the bottom of the desired groups such as Scheduled, Running, and History.
4. To view the timer job status for a particular group, click the name of the group.
To view the status of a specific timer job using Windows PowerShell, type the following at the command prompt and then press Enter, specifying the timer job name at the -Identity switch:
Get-SPTimerJob [-Identity <Timer job name...>] | Format-Table -PropertyDisplayName,Id,LastRunTime,Status
You can also view the history for a particular job by using the following command:
(Get-SPTimerJob [-Identity <Timer job name...>]).HistoryEntries | Format-Table -Property Status,StartTime,EndTime,ErrorMessage
You can view web analytics, which is a collection of reports regarding site and site collection usage, in Central Administration. Exercise 13-7 provides the instructions. You will need to belong to the Farm Administrators group to perform this task.
Exercise 13-8: Reviewing Web Analytics in Central Administration
1. Go to the Central Administration home page and click Monitoring.
2. On the Monitoring page, click View Web Analytics Reports under Reporting.
3. On the Web Analytics Reports page, click the desired web application.
4. On the Web Analytics Reports – Summary page, click the name of the desired report in Quick Launch, and depending on the type of report, you may or may not be able to change the report settings by clicking Analyze on the Ribbon.
5. Click the desired column name to sort the rows in the data grid.
Options for modifying the settings of a report type when you click Analyze in the Ribbon are Date Range, Export To Spreadsheet, Filter, and Paging Size. You can modify Date Range and export reports to a spreadsheets for all report types. You cannot edit filter or paging size for Summary, Number Of Page Views, Number Of Daily Unique Visitors, Number Of Referrers, Number Of Collections, and Top Site Collection Templates.
Collecting Data from SharePoint Monitoring
You are a SharePoint administrator for your company, and you implemented a SharePoint 2010 Server farm solution in your organization several months ago. At that time, you configured the various SharePoint logging and monitoring tools to gather information including diagnostic logging, health and usage data collection, and SharePoint Health Analyzer. Now you must gather information from these various tools as part of a report you are going to present to the CIO and the rest of the management staff regarding SharePoint’s effectiveness.
To review these logs and reports, you will need to use a combination of Central Administration and Windows PowerShell because no one interface can access everything. You pull information from the administrative reports, health reports, timer jobs, and web analytics sections in Central Administration, but you also use PowerShell to display different views of the event logs.
You will still need to compile all this data so that it can be presented to the management team in a more narrative form supported by various graphs, but you will be able to demonstrate both the baseline performance of the server farm and any changes and trends in usage over time.
In this chapter, you learned the specifics about the different monitoring and analysis tools in SharePoint:
- The differences between diagnostic logging, health and usage data collection, and the SharePoint Health Analyzer
- How the different monitoring tools are configured
- How to access and review reports in SharePoint
Understanding How to Enable and Configure Monitoring and Analysis Tools Understand the practices involved in setting up and configuring diagnostic logging, health and usage data collection, and the SharePoint Health Analyzer.
Demonstrating the Ability to Review Reports Know how to access each monitoring tool and the reports it generates in SharePoint using Central Administration and Windows PowerShell.
1. You are a SharePoint administrator for your company, and you are currently managing the monitoring and analysis tools in SharePoint. As you perform these tasks, what do you find is true about SharePoint monitoring?
A. All monitoring tools in SharePoint are enabled by default.
B. All monitoring tools managed by Central Administration are enabled by default, but you must manually enable those tools managed with Windows PowerShell.
C. All monitoring tools managed by Windows PowerShell are enabled by default, but you must manually enable those tools managed by Central Administration.
D. All monitoring tools in SharePoint are disabled by default.
2. You are a SharePoint administrator for your company, and you are currently managing the monitoring and analysis tools in SharePoint. You want to gather different kinds of information including event log data, performance counter data, and timer service metrics data. Which of the following tools should you use?
A. Diagnostic logging.
B. Health and usage data collection.
C. SharePoint Health Analyzer.
D. Any of the available monitoring tools gathers that data together.
3. You are a SharePoint administrator for your company, and you are currently managing the monitoring and analysis tools in SharePoint. Of the following, which tool should you typically use to troubleshoot errors in SharePoint?
A. Diagnostic logging.
B. Health and usage data collection.
C. SharePoint Health Analyzer.
D. Any of the available monitoring tools can be used equally well to troubleshoot errors.
4. You are a SharePoint administrator for your company, and you are currently managing the monitoring and analysis tools in SharePoint. You are currently configuring diagnostic logging using Central Administration. Of the following, which features can you manage for diagnostic logging? (Choose all that apply.)
A. Event Backwash
B. Event Log Flood Protection
C. Event Failure Control
D. Event Throttling
5. You are a SharePoint administrator for your company, and you are currently managing the monitoring and analysis tools in SharePoint. You are currently configuring Diagnostic Logging using Windows PowerShell. Of the following, which PowerShell cmdlet should you use?
A. SPDiagLog
B. SPDiagnosticLog
C. SPLogLevel
D. SPLogSet
6. You are a SharePoint administrator for your company, and you are currently managing the monitoring and analysis tools in SharePoint. You are currently configuring usage and health data collection using Central Administration. Of the following, what is true about configuring this utility?
A. You can configure this data collection tool to apply to a web application, a single server, a collection of servers, or the server farm.
B. You can configure this data collection tool to apply to a single server, a collection of servers, or the server farm.
C. You can configure this data collection tool to apply to a group of three servers or more including the entire server farm.
D. You can configure this data collection tool to apply to the entire server farm only.
7. You are a SharePoint administrator for your company, and you are currently managing the monitoring and analysis tools in SharePoint. You are currently configuring diagnostic logging using Central Administration and want to limit the amount of disk space that can be used by the logs. When the disk space limit has been reached, what happens?
A. You receive an error that no further information can be written to the log files until you delete currently existing files.
B. You receive a notice that you have exceeded the disk space limit but information will still be written to the log files.
C. The most recent log files are overwritten by the current log files.
D. The oldest log files are overwritten by the current log files.
8. You are a SharePoint administrator for your company, and you are currently managing the monitoring and analysis tools in SharePoint. You are currently configuring usage and health data collection using Central Administration. Of the following, which task or tasks can you not perform for usage and health data collection in Central Administration? (Choose two.)
A. You cannot change the name of the database server.
B. You cannot change the name of the database on the database server.
C. You cannot change the authentication method for the database server.
D. You cannot change the schedule for timer jobs.
9. You are a SharePoint administrator for your company, and you are currently managing the monitoring and analysis tools in SharePoint. You are currently configuring usage and health data collection using Windows PowerShell. You want to specify a specific type of event to be logged. Of the following, which is the correct cmdlet to use?
A. SPUsageService
B. SPUsageIdentity
C. SPUsageEvent
D. SPUsageDefinition
10. You are a SharePoint administrator for your company, and you are currently managing the monitoring and analysis tools in SharePoint. You are currently configuring usage and health data collection using Windows PowerShell. You want to change the database used to log usage data to one different from the default. Of the following, which cmdlet should you use?
A. SPUsageApplication
B. SPUsageDatabase
C. SPUsageDatabaseName
D. SPUsageService
11. You are a SharePoint administrator for your company, and you are currently configuring the SharePoint Health Analyzer. You want to configure health data collection rules in Windows PowerShell. Of the following, which is the most correct statement?
A. You can only manage Configurable Fields for health rules in PowerShell.
B. You can only manage Read-Only Fields for health rules in PowerShell.
C. You can manage Configurable and Read-Only Fields for health rules in PowerShell.
D. You cannot manage health rules in PowerShell. You must use Central Administration.
12. You are a SharePoint administrator for your company, and you want to view log events using Windows PowerShell. There are a number of ways you can filter log event views in PowerShell, and they all begin with the same command. Of the following, which is the correct command?
A. Find -SPLogEvent
B. Get -SPLogEvent
C. Set -SPLogEvent
D. View- SPLogEvent
13. You are a SharePoint administrator for your company, and you want to view log events using Windows PowerShell. There are a number of different ways you can filter event views in PowerShell. Of the following, which are correct methods? (Choose all that apply.)
A. You can view by Area.
B. You can view by Category.
C. You can view by EventID.
D. You can view by Server Name.
14. You are a SharePoint administrator for your company, and you want to view the timer jobs for health reports using Windows PowerShell. Of the following, which is the correct command you must use to achieve your goal?
A. Find -SPTimerJob
B. Get -SPTimerJob
C. Set -SPTimerJob
D. View- SPTimerJob
15. You are a SharePoint administrator for your company, and you are currently reviewing web analytics using Central Administration. You are changing the settings for the report type. Of the following, what are valid options for this task? (Choose all that apply.)
A. Data Range
B. Export To Spreadsheet
C. Filter
D. Paging Size
16. You are a SharePoint administrator for your company, and you are currently reviewing web analytics using Central Administration. After you click Analyze on the Ribbon, you are presented with a number of editing options, but not all of these options work with all report types. Of the following, which options work with all report types? (Choose two.)
A. Date Range
B. Export To Spreadsheet
C. Filter
D. Paging Size
17. You are a SharePoint administrator for your company, and you are currently reviewing health report information in Central Administration. On the Central Administration home page, you click Monitoring. What must you click next to review timer jobs?
A. Health Reporting.
B. Reporting.
C. Timer Jobs.
D. You must perform this task in Windows PowerShell.
18. You are a SharePoint administrator, and you currently want to review administrative reports in Central Administration. You can find administrative reports on which of the following pages?
A. A library page
B. A list page
C. A reports page
D. A web part page
19. You are a SharePoint administrator for your company, and you are currently configuring the rules for the Health Data Collection tool in Central Administration. You want to set a rule that, when it encounters an error, will attempt to correct the error. Of the following, what rule applies to this task?
A. Error Repair
B. Fix Error
C. Repair Automatically
D. No rule applies
20. You are a SharePoint administrator for your company, and you are currently setting up the schedule for timer jobs as they apply to the Health Data Collection utility. Of the following, what schedule types or frequencies can you configure for timer jobs in PowerShell? (Choose all that apply.)
A. Every <1–60> seconds
B. Every <1–60> minutes at <1–60>
C. Hourly between <1–59> minutes past the hour
D. Annually between <1–366> days
1. A. Monitoring features are enabled in SharePoint by default using a collection of standard settings.
2. B. The health and usage data collection is a set of monitoring tools that gather together different types of data including event log data, performance counter data, and timerservice metrics data.
3. A. Diagnostic logging is comprised of a series of logs that collect data typically used in troubleshooting errors in SharePoint.
4. B, D. You can configure and manage Event Throttling and Event Log Flood Protection for diagnostic logging. The other two options are bogus.
5. C. Use the SPLogLevel cmdlet and appropriate parameters to configure diagnostic logging in Windows PowerShell. The other cmdlets are bogus.
6. D. Any usage and health data collection tool settings you make are applied to the entire farm and cannot specify a smaller group of servers.
7. D. Once the disk space limit has been reached, older logs will be deleted to make room for newer logs.
8. A, B. You can select an authentication method, but you cannot change the database on the default database server or change the database server using Central Administration. You can only change the database and the name of the database server used by the usage and health data collection tool using Windows PowerShell. You can change the schedule for a timer job in Central Administration.
9. D. SPUsageService is the Windows PowerShell cmdlet used to generally configure the usage and health data collection system as a whole. The other cmdlets are bogus.
10. D. SPUsageService is the Windows PowerShell cmdlet used to generally configure the usage and health data collection system as a whole. The other cmdlets are bogus.
11. D. You can only manage health rules for health data collection using Central Administration.
12. B. Get -SPLogEvent is the correct command. All the other options are bogus.
13. A, B, C. You can view event log information by Area, Category, EventID, Level, andProcess but not by Server Name.
14. B. Get -SPTimerJob is the correct command. All the other options are bogus.
15. B, C, D. The correct option is Date Range, not Data Range. All other options are correct.
16. A, B. Only the options for editing a date range and exporting information to a spreadsheet work with all types of reports in web analytics. You can use filtering and edit paging size for only some report types.
17. C. You can click Reporting to view health reports but must click Timer Jobs to view the timer jobs for health reports. The Health Reporting option is bogus, and you can perform this task in both Central Administration and Windows PowerShell.
18. A. Administrative reports are found on the Administrative Report Library page.
19. C. For Health Rules under Configurable Fields, select Repair Automatically so that the rule will try to fix any errors it encounters.
20. A, B, C. The option for setting the schedule annually is bogus. All other options are correct.