Microsoft Virtual Labs: Monitoring Windows Server 2008, SQL Server 2008 and Exchange 2007

Microsoft Virtual Labs
Monitoring Windows Server

2008, SQL Server 2008 and
Exchange 2007
Monitoring Windows Server 2008, SQL Server 2008 and Exchange 2007
Table of Contents
Monitoring Windows Server 2008, SQL Server 2008 and Exchange 2007 ............................. 1
Exercise 1 Understanding the Windows Server Operating System Management Pack .................................................2
Exercise 2 Understanding the Microsoft SQL Server Management Pack .....................................................................7
Exercise 3 Understanding and Tuning the Exchange 2007 Management Pack ........................................................... 11
Monitoring Windows Server 2008, SQL

Server 2008 and Exchange 2007
The “Monitoring Windows Server 2008, SQL Server 2008 and Exchange 2007”
Objectives lab provides an opportunity for you to explore many of the existing and new
features of these three MP, which are the most commonly deployed and used
MPs for System Center Operations Manager.
Due to breadth of these MPs and the limited amount of time available the labs
will not exhaust all of the MPs’ capabilities. However, during this lab you will be
introduced to many key concepts, including:
• Navigating the management packs imported into a management group
• Browsing the management pack components such as discoveries, rules
and monitors
• Customizing management packs with overrides
• Key views provided in the Windows Server Operating System, SQL
Server and Exchange 2007 management packs
Estimated Time to
Complete This Lab 75 Minutes
Computers used in this

Lab DC
RMS
EXCH
WEB
SLES
The password for the Administrator account on all computers in this lab is:
P@ssword
Page 1 of 16
Exercise 1
Understanding the Windows Server Operating System
Management Pack
Scenario
In our environment are a collection of servers running the Windows Server 2008 Operating System, which you want
to monitor for the condition of their OS and its supporting hardware resources. In this exercise, you will go through
a set of key tasks that are required to understand and use the Windows Server Operating System management packs,
which provide these monitoring capabilities.
Tasks Detailed Steps

Complete the following Note: Right-click the background and select Personalize. Click Display Settings and
tasks on: select the resolution to1024 by 768. Click OK then close Personalization.
a. If you are not already logged into the system, log in as the user
RMS CONTOSO\Administrator with the password P@ssword.
1. Start the Operations b. Start the Operations Manager console by double-clicking the Operations
Manager console Console shortcut on the desktop.
2. Search for the a. In the tree pane, click the Administration button to open the Administration
view.
Windows Server
Operating System b. In the tree pane, select Management Packs.
management packs c. In the results pane, in the Look for box, type Windows Server, and press
Enter.
Note: The list of imported Windows Server Operating System management packs will
appear.
Examining the properties of each management pack listed will show a description of
the imported MPs. The management packs imported in the lab are the following:
File Description
Displayed as “Windows Server Operating System
Microsoft.Window
Library,” this management pack is the library
s.Server.Library
management pack that defines all of the features and
components that are common to all versions of the
Windows Server operating systems. This
management pack contains no monitoring
configuration and is a prerequisite for all other
Windows Server operating system management
packs. Therefore, this management pack must be
imported at the same time or prior to the version-
specific management packs.
Page 2 of 16

Displayed as “Windows Server 2008 Operating
Microsoft.Window
System (Discovery),” this management pack
s.Server.2008.
discovers Windows Server 2008. It contains the
Discovery
version-specific classes used for monitoring and
provides the means by which instances of those
classes will be discovered. This management pack is a
prerequisite for the Windows Server 2008 monitoring
management pack and is required by other
management packs that focus their monitoring on
systems running Windows Server 2008 specifically
Microsoft.Window
System (Monitoring),” this management pack defines
s.Server.2008.
the rules, monitors, views, tasks, and reports that are
Monitoring
used for monitoring the Windows Server 2008
operating system.
Note: While only the Server 2008 specific management packs are imported into the
lab environment, the following MPs exist as well for monitoring prior versions of the
Windows Server operating system:
File Description
Microsoft.Window
System,” this management pack provides both
s.Server.2003
discovery and monitoring for the Windows Server
2003 operating system.
Microsoft.Window
System,” this management pack provides both
s.Server.2000
discovery and monitoring for the Windows 2000
Server operating system.
Note: There are several reasons why the MP files are divided the way that they are.
The first reason has to do with dividing the MPs up by the OS version. This allows
administrators to limit the amount of monitoring to just the operating system version
they have deployed.
The second reason has to do with the fact that, starting with the Server 2008 specific
MPs, the discovery and monitoring functionality are separated. This allows
administrators the ability to phase in monitoring as they see fit, and it makes it
easier for other management packs to take a dependency on the objects discovered
by the Windows Server OS MPs without requiring the monitoring to be deployed.
Note: There are a number of discoveries provided as a part of the Windows Server
3. Examine the
Operating System management packs and all of them can be customized via
Windows Server overrides. While most discoveries are enabled by default, some are not. The
Operating System following steps walk through viewing the various discoveries and shows how to
management pack customize them with overrides:
Page 3 of 16

discoveries a. In the tree pane, click the Authoring button to open the Authoring view.
b. In the tree pane, expand Authoring | Management Pack Objects, and select
Object Discoveries.
c. In the toolbar, click Scope.
d. In the Look for box, select View all targets, click Select All, and click OK.
Note: At this point, the view of discoveries is scoped to show only those discoveries
that are a part of the Windows Server 2008 Operating System management pack.
e. In the Look for box, type Discover Windows 2008 Servers, and press Enter.
Note: We just narrowed the view even further to show you the discovery responsible
for discovering the various computer classes related to Windows 2008 Server.
f. Right-click any of the rows with the name Discover Windows 2008 Servers,
point to Overrides | Override the Object Discovery, and click For all objects
of class: Windows Server.
g. Examine the Parameter Name column.
Note: You can see that this discovery is enabled by default. Disabling this discovery
would effectively prevent the entire Windows Server operating system management
pack from running.
h. Examine the Interval Seconds parameter.
Note: You can see that the default value is 3605 seconds, which is the equivalent of
about once per half-hour. If you want to change how Windows 2008 Servers are
discovered or “undiscovered” in your environment, change this discovery script.
i. Click Cancel.
j. Using the Look For tool, review the following discoveries which are disabled
by default:
Discover Windows Disk Partitions
Discover Network Adapters (Both Enabled and Disabled)
Discover Windows Physical Disks
Discover Windows CPUs
k. In the toolbar, click Scope.
Note: You can use overrides in your environment to enable these discoveries if this
level of monitoring suits your needs.
Note: Very commonly, people need to quickly identify what monitoring is provided
4. Examine the
with a specific management pack. The following steps walk through how to use the
Windows Server scoping capabilities of the Operations Console to view the rules and monitors that
Operating System are available in the Windows Server 2008 Operating System management pack.
management pack These steps could be reused for any other management pack by replacing the
Rules and Monitors management pack name used in steps 3-4.
a. In the tree pane under Management Pack Objects, select Rules.
b. In the toolbar, click Scope.
c. In the Look for box, type Windows Server 2008 Operating System
(Discovery).
d. Click Select All, and click OK.
Note: The resulting view shows all rules that are targeted at classes provided in the
“Windows Server 2008 Operating System (Discovery)” management pack.
e. In the Look for box, type Logical Disk, and press Enter.
Page 4 of 16

f. Repeat step e in the Monitors node.
g. In the toolbar, click Scope.
5. Examine the Note: As a final step to reviewing the Windows Server Operating System
management pack, there are a number of views that are provided by this MP which
Windows Server
allow users to understand Windows Server state at a very high level and then drill
Operating System
into state and performance more specifically. The following steps walk through these
management pack
views and how to use them.
views
a. In the tree pane, click the Monitoring button to open the Monitoring view.
b. In the tree pane, expand Microsoft Windows Server, and select Windows
Server State.
Note: In the state view you will see an entry for every Windows Server Computer
that has been discovered.
c. In the results pane, select EXCH.contoso.com computer, and look at the Detail
View towards the bottom of the console.
Note: From the state view you can drill into the state of the Windows Server in a
couple of key ways.
d. In the results pane, right-click RMS.contoso.com, point to Open, and click
Diagram View.
Note: A separate window opens with a diagram view that shows the Windows Server
class for RMS.contoso.com and the immediately related classes that have been
discovered.
e. Drill down into each of the classes in the view and review the information that
is show in the Detail View as you select different types of classes.
f. Close the Diagram View.
g. In the results pane, right-click EXCH.contoso.com, point to Open, and click
Health Explorer for EXCH.contoso.com.
Note: Again a separate window will open with the Health Explorer view for the
EXCH.contoso.com computer.
This view shows the hierarchical structure of the monitors that is applied to the
computer and their corresponding states. If one or more monitors are in a non-green
state then they are automatically expanded to those monitors allowing you to quickly
identify the root cause and it’s affect on the overall health model for the computer.
h. Close the Health Explorer.
i. In the Microsoft Windows Server folder, browse through the various views
provided by the Windows Server Operating System management pack.
j. In the tree pane, expand the Performance folder, and select the Processor
Performance dashboard view.
Note: By default all tiles in the view are empty (we have added the
RMS.contoso.com server). For each tile you need to select the check mark in the
Show column for the rows that you wish to see in the chart.
k. Click the empty field in the top view labeled Processor\% Processor
Time\_Total Performance.
l. In the Legend, select Show for EXCH.contoso.com.
m. Repeat step l for the System\Processor Queue Length Performance (bottom
left) and System\Context\Switches/sec Performance (bottom right) views.
Note: Now if you switch away from this view, and back again later your Show settings
Page 5 of 16

will be saved.
Page 6 of 16
Exercise 2
Understanding the Microsoft SQL Server Management Pack
Scenario
On some of the servers in our environment, SQL Server 2008 is installed, and we want to monitor the condition of
their various SQL Server roles such as the DB Engine and Reporting Services. In this exercise, you will go through
a set of steps that show key tasks required to understand and use the SQL Server management packs, providing these
monitoring capabilities.

Complete the following a. In the tree pane, click the Administration button to open the Administration
tasks on: view.
b. In the tree pane, ensure that Management Packs is selected.
RMS c. In the Look for box, type SQL Server, and press Enter.
1. Search for the SQL Note: A list of Microsoft SQL Server management packs will appear. Examining the
Server management properties of each management pack listed will show a description of the imported
packs MPs. The management packs imported for the lab are the following:
File Description
Contains the object types and groups that are common
Microsoft.
to SQL Server 2000, SQL Server 2005, and SQL
SQLServer.Library
Server 2008.
Contains definitions for object types and groups that

Microsoft.
are specific to SQL Server 2008. It contains the
SQLServer.2008.
discovery logic to detect all objects of the type
Discovery
defined on servers running SQL Server 2008.
Provides all monitoring for SQL Server 2008.

Microsoft.
SQLServer.2008. Note
Monitoring
SQL Server 2008 will not be monitored until you
import this management pack.
Note: While only the SQL Server 2008 specific management packs are imported into
the lab environment, the following MPs exist as well for monitoring prior versions of
the SQL Server:
File Description
Microsoft.
SQLServer.2000.
Discovery
Page 7 of 16

Microsoft.
Monitoring
Microsoft.
SQLServer.2005.
Discovery
Microsoft.
Monitoring
Note: The reasoning behind dividing these files as they are is very similar to the
Windows Server Operating System management packs. First, by dividing them into
version specific MPs the Operations Manager administrator has more granular
control over the MPs they have deployed and how they are customized. Secondly,
partially due to the size of the SQL MPs and also for administrative purposes, the
SQL MPs are further split into discovery and monitoring MPs.
Note: There are a number of discoveries provided as a part of the SQL Server
2. Examine the SQL
management packs and all of them can be customized via overrides. While most
Server management discoveries are enabled by default there are some which are not. The following steps
pack discoveries walk through viewing the various discoveries and shows how to customize them with
overrides.
a. In the tree pane, click the Authoring button to open the Authoring view.
b. In the tree pane, under Management Pack Objects, select Object Discoveries.
c. In the toolbar, click Scope.
d. In the Look for box, select View all targets, click Select All, and click OK.
Note: At this point the view of discoveries is scoped to show only those discoveries
that are a part of the SQL Server 2008 management pack.
e. In the Look for box, type Discover SQL 2008 Database Engines, and press
Enter.
Note: This will narrow the view even further to show you the discovery that is
responsible for discovering where the SQL 2008 Database Engine role has been
installed.
f. Right-click any of the rows with the name Discover SQL 2008 Database
Engines (Windows Server), point to Overrides | Override the Object
Discovery, and click For all objects of class: Windows Server.
g. Examine the Parameter Name column.
Note: You can see that the discovery is enabled by default. Disabling this discovery
would effectively prevent all discovery or monitoring of the DB Engine, SQL agent
or databases from running.
In addition to the common parameters that all discoveries have notice that this
discovery includes the Exclude List parameter.
h. Click on the Exclude List parameter and review its description shown in the
Page 8 of 16

Details box.
Note: This parameter accepts a comma-delimited list of strings. When the discovery
runs it will compare the name of the DB Engine discovered with the list of strings
and if a match is found then the discovery will not submit the discovery for that DB
Engine.
i. Click Cancel.
j. Using the Look For tool, review the following discoveries which are disabled
by default:
Discover SQL 2008 Agent Jobs
Discover File Groups and Files
Discover Replication Components
SQL 2008 Replication Publications and Subscriptions Discovery
Provider
k. In the toolbar, click Scope.
Note: The SQL Server management pack includes views which are oriented around
3. Use the SQL Server
the state of the various SQL Server roles, Databases, the SQL Agent, Performance,
management pack and more. The following steps walk through using these views.
views
b. In the tree pane, expand Microsoft SQL Server, and click Computers.
Note: In the state view you will see an entry for every computer that hosts a
discovered instance of SQL Server.
c. In the results pane, click RMS.contoso.com, and look at the Detail View.
d. In the results pane, click on the SQL 2008 DB Engine cell for
RMS.contoso.com.
Note: Notice now that the detail view changes to show the instances that have been
discovered on the computer, its state and related classes.
e. Right-click the SQL 2008 DB Engine cell for RMS.contoso.com, and click
Properties.
Note: The Object Properties dialog will open up and you can resize it to view all of
the details about the SQL 2008 DB Engine that has been discovered.
f. Click OK.
g. In the tree pane, under Microsoft SQL Server, expand Databases, and select
Database State.
Note: In the Database State view a list is shown of all of the databases that have
been discovered, properties of each and their corresponding state.
h. Click on the row for the OperationsManager database and review the
properties list that is shown in the Detail View.
i. Right-click the OperationsManager row, point to Open, and click Health
Explorer for OperationsManager.
j. Expand the Availability, Configuration, and Performance monitors to view
the list of all of the monitors which contribute to the overall state of the
database.
k. To view the properties of the monitors right-click on any of the monitors list
and select Monitor Properties.
l. Close the Health Explorer for OperationsManager.
Page 9 of 16

Note: As a final step in reviewing the SQL Server management pack, we will go over
4. Using reports in the
the reports that are available to provide information about SQL Servers over the
SQL Server longer-term for things like problem management and capacity planning.
management pack
Given that the lab machines are not running for long periods of time, the data we
have to work with is limited. The purpose of this task is to demonstrate the reports
that exist and how to run them.
a. In the tree pane, click the Reporting button to open the Reporting view.
b. In the tree pane, under Reporting, select SQL Server 2008 (Monitoring).
Note: By clicking on each of the reports, you are provided with information about
the reports purpose and how to use it within the Report Details window.
c. In the results pane, right-click SQL Server Configuration, and click Open.
d. From the From drop-down, select Advanced.
e. Change the no offset to minus, change the day(s) to 7, and click the green
check mark.
f. In the Objects area, click Add Object.
Note: When the Add Object dialog comes up notice the warning that indicates Filter
Options have been applied. This is a new feature of Operations Manager 2007 R2
that allows each report to pre-filter the object picker so that only instances of the
relevant types are available by default. This significantly increases the ease of use
for reports.
g. Click Search.
h. Select the MSSQLSERVER instance from the path RMS.contoso.com, click
Add, and click OK.
i. At the left end of the toolbar, click Run.
Note: You may need to change the scale of the report to view it properly.
j. Close the report.
Page 10 of 16
Exercise 3
Understanding and Tuning the Exchange 2007 Management
Pack
Scenario
In our environment, we have a an Exchange 2007 infrastructure that needs to be monitored. The Operations
Manager team has now released a major update to the Exchange 2007 management pack. In this scenario, you will
go through a set of steps that show key tasks that are required to install and configure this Management Pack. You
will also look at different aspects of how the management pack is designed.
This is a beta version of the native Exchange 2007 Management Pack.
The below scenario shows some key design features of the upcoming Exchange 2007 Management Pack, enabling
you to successfully implement the Management Pack in your environment. One of the first steps as an Exchange
Administrator is to understand the Management Packs that make up the Exchange 2007 MP.

Complete the following a. In the tree pane, click the Administration button to open the Administration
tasks on: view.
b. In the results pane, in the Look for box, type Exchange Server, and press
RMS Enter.
1. Search for the Note: The list of Exchange 2007 Management Packs is displayed.
Exchange 2007 Examine the Management Pack file descriptions for the Exchange 2007 MP by
Management Packs looking at the Description field. The Management Pack consists of the following
files:
File Description
Contains discovery scripts and monitoring
Microsoft.Exchange.Server.20
common to all Exchange servers.
07.Discovery
Contains class definitions.
07.Library
Contains monitors for the CAS server role.
07.Monitoring.CAS
Contains monitors for the Edge server role.
07.Monitoring.Edge
Contains monitors for the Hub server role.
07.Monitoring.Hub
Contains monitors for the Mailbox
server role.
07.Monitoring.Mailbox
Contains monitors for the UM server role.

07.Monitoring.UM
The Exchange Management Pack consists of a very large number of rules and
Page 11 of 16

monitors. By splitting the MP files up, we ensure that only the appropriate
monitoring is applied to each agent, reducing agent footprint and overall impact of
the Management Pack on the Operations Manager environment. Since each
Exchange 2007 implementation might not have all the Exchange 2007 server roles
implemented (such as Edge or UM Servers), this also allows the user to import only
the particular Exchange 2007 Management Packs files that are of interest.
Note: One of the first steps after importing the Exchange management pack is to
2. Ensure that Agent
enable an agent proxy on the Exchange server computers. An agent proxy relays or
Proxy is enabled forwards information from other computers or network devices to the management
server. The Exchange management pack requires an agent proxy to populate its
topology view.
a. In the tree pane, under Device Management, select Agent Managed.
b. In the results pane, right-click EXCH.contoso.com, and click Properties.
c. Click the Security tab, and ensure that Allow this agent to act as a proxy and
discover managed objects on other computers is selected.
d. Click OK.
Note: As the Exchange Administrator, one of the requirements you have is to run all
3. Examine the
applications on your servers with the minimum required credentials. With the
Exchange 2007 MP Exchange 2007 Management Pack you can now setup low-privilege installations
support for low- using an Action Account that has the minimum rights required by the Operations
privilege Manager agent. The purpose of this exercise is to configure Run As profiles in order
installations and to run workflows that require higher privileges than what the agent action account
create a Run As has, in a low-privilege scenario.
Account with Some out the box Run As profiles that are created:
Exchange View Only The “Exchange 2007 Administrator Account” profile is used for workflows that
Privileges require Exchange administrator privileges.
The “Exchange 2007 Local System Account” profile is used for workflows that
require local system privileges.
The “Exchange 2007 View Only Local User Account” is used for workflows that
require Exchange View Only administrator rights.
a. In the tree pane, under Run As Configuration, right-click Accounts, and click
Create Run As Account.
b. On the Introduction page, click Next.
c. On the General Properties page, from the Run As Account type drop-down,
select Windows.
d. In the Display Name box, type Exchange 2007 Read Only Account, and click
Next.
e. On the Credentials page, type the following:
User name: contosoadmin
Password: P@ssword
Confirm Password: P@ssword
f. Click Next.
g. On the Distribution Security page, ensure that the More secure distribution
security option is selected, and click Create.
h. On the Run As Account Creation Progress page, click Close.
4. Associate computers a. In the tree pane, under Run As Configuration, click Profiles.
b. In the results pane, in the Look for box, type Exchange 2007, and press Enter.
Page 12 of 16

to the Run As profile c. In the results pane, double-click the Exchange 2007 View Only Local User
Account.
d. On the Introduction page, click Next.
e. On the General Properties page, click Next.
f. On the Run As Accounts page, click Add.
g. From the Run As account drop-down, select Exchange 2007 Read Only
Account.
h. Click A selected class, group, or object.
i. Next to the A selected class, group, or object box, click the Select, and then
click Group.
j. In the Filter by box, type Exchange 2007, and click Search.
k. In the Available Groups box, select Exchange 2007 Server Roles Group, and
click OK.
l. Click OK.
m. On the Add Run As accounts page, click Save.
n. Read the Completion page and click Close.
5. Select the computer a. In the tree pane, under Run As Configuration, click Accounts.
the Run As account b. In the results pane, double-click the Exchange 2007 Read Only Account.
credentials get c. On the Distribution tab, click Add.
distributed d. Click Search.
e. In the Available items box, click EXCH.contoso.com, click Add, and click
OK.
f. Click OK.
Note: The Run As account has been created and configured.
Note: As the Exchange Administrator, one of the big concerns you have is how often
6. Examine the
monitoring scripts run in your environment. In Operations Manager 2007 R2 you
Exchange 2007 can configure how often discoveries are run by setting overrides.
Management Pack
In addition, the Exchange 2007 Discoveries are disabled by default, allowing the
Discoveries administrator to have full control of where and when the Management Pack gets
deployed.
a. In the tree pane, click the Authoring button to open the Authoring view.
b. Ensure that Object Discoveries is selected.
c. In the results pane, in the Look for box, type Exchange 2007 Discovery
Helper, and press Enter.
Note: This will show you all the Exchange 2007 discoveries that are part of the
Management Pack. Note: Turn off scoping by clicking Scope button on the
Operations Manager toolbar.
d. In the resulting Object Discoveries list, locate Exchange 2007 Discovery
Helper Discovery.
Note: This discovery has “Windows Server” as its target. This is a very light-weight
registry discovery whose only purpose is to discover Exchange 2007 servers. Other
more in-depth discoveries in the Management Pack are “chained” based on this
discovery. This ensures that the only discovery script that is run on all Windows
servers is the Exchange 2007 Discovery Helper script. Note that all other discoveries
target Exchange 2007 roles.
Page 13 of 16

Other discoveries such as the Exchange 2007 CAS Role Discovery is disabled by
default (scroll to the right to look at the Enabled by default column). This allows you
as the administrator full control over when the Exchange server roles are being
monitored.
e. In the results pane, right-click Exchange 2007 CAS Role Discovery, point to
Overrides | Override the Object Discovery, and click For all objects of class:
Exchange 2007 Discovery Helper.
f. Examine the Enabled item in the Parameter Name column.
Note: You can see that the discovery has been enabled via an override in this lab
environment. This is something an administrator would do in your environment. You
can decide if you want to enable the discovery for a single CAS server, a group of
servers or all servers at once. The benefit of this is that you are in control of when
Exchange 2007 monitoring is introduced into the Operations Manager environment.
g. Examine the Frequency item in the Parameter Name column.
Note: You can see that the default value is 86400 seconds, which corresponds to
once per day. This is true for all the discovery scripts in the Exchange 2007
Management Pack. If you want to change how often the new Exchange 2007 servers
are discovered or “undiscovered” in your Exchange environment, change this
discovery script.
h. Click Cancel.
Note: One of the big challenges for organizations is that when a new application
7. Examine the
owner joins or takes over administrating the Exchange environment, it usually takes
Exchange 2007 them some time to understand how the Exchange environment is modeled. With
Management Pack Operations Manager 2007 you can get a complete picture of your Exchange 2007
Topology View environment and how it is modeled by looking at the topology view provided out of
the box with the Exchange Management Pack.
b. In the tree pane, under Monitoring, click Distributed Applications.
c. In the results pane, right click the Exchange 2007 Service distributed
application, point to Open, and click Diagram View.
Note: The Exchange 2007 topology diagram for your lab environment opens.
Examine the diagram. The top level consists of the Exchange 2007 Service itself, i.e.
the health of all the Exchange 2007 components. The level below this is the
Exchange organization. The Management Pack supports monitoring of one or more
organizations.
d. Click the + button on the Exchange 2007 Organization to open the
Organization level.
Note: You can click and then hover over the Organization icon to see its properties;
you can also see it in the details pane.
e. Continue to expand the levels by clicking the + button on each.
Note: The next level is Sites. These correspond to Active Directory sites with
Exchange 2007 Servers in them. No other sites will be shown by the management
pack.
The next level is a service layer corresponding to the different Exchange 2007
services that are implemented within the site. Examples of these are ActiveSync,
MAPI, and OWA services. This level provides a health rollup of all servers that make
up the service level.
The next level consists of the Exchange 2007 servers themselves.
Page 14 of 16

f. Expand MAPI Service | Mailbox (EXCH).
Note: That the mailbox server has several components:
ExBPA: represents the state of running the Exchange Best Practice Analyzer. The
ExBPA is run weekly on all Exchange servers.
ESE: The Extensible storage (database) engine
Common: represents the state of the monitoring that applies to all Exchange server
roles (such as Active Directory access)
Mailflow Local: represents a mail flow synthetic transaction that is running on the
Exchange server to test the ability of Exchange to send a mail to itself
You will also see all the mailbox databases discovered.
Under ESE, you can see a number of disks that are discovered. These are disks that
have Exchange database, log or queue files on them. We will examine this
monitoring in more detail in a later exercise.
g. Right-click Mailbox (EXCH), and click Health Explorer.
Note: Look at the Health Explorer and the monitoring that is applied to the Mailbox
server.
h. Close the Health Explorer.
i. In the diagram view, click Mailbox (EXCH) and in the Actions pane, you can
see that there are a set of predefined tasks that you can use to start and stop
Exchange services using the Operations Manager Console.
j. Close the Exchange 2007 Diagram view.
Note: Storage utilization and growth is very important to Exchange administrators.
8. Examine the
In this exercise, you will look at how the Exchange 2007 Management Pack
Exchange 2007 implements disk monitoring and how you as the administrator can configure it to
Management Pack meet your needs.
Disk Monitoring
a. In the tree pane, expand Microsoft Server Exchange 2007, and click Server
State.
b. In the results pane, right click Mailbox (EXCH), point to Open, and click
Diagram View.
c. In the Diagram View, expand ESE (the Extensible Storage Engine, or DB
engine used by Exchange 2007).
Note: There are several disks discovered for the mailbox server and that there are
several monitors that apply to these disks. This is how the disk monitoring works:
The Management Pack discovers only disks that have Exchange Mailbox, Queue or
Log files on them. This means that disk monitoring is applied only to the Mailbox,
Hub and Edge roles.
The disks are implemented as classes, which makes it very easy to implement a
common standard, for example for Mailbox disks.
d. In the Diagram View, right-click MDB Disk C, and click Health Explorer.
e. Under Entity Health, expand Availability, right-click Exchange 2007 MDB
Disk Free Space Monitor, and click Monitor Properties.
f. Click the Overrides tab.
g. Click Override, and click For all objects of class: Exchange 2007 Mailbox
Database Disk.
Note: Examine the monitor parameters. This monitor works in the same way as the
base OS disk monitoring, with the difference that it only handles Exchange 2007
disks. You can set a Megabyte warning or error threshold, as well as a percentage
Page 15 of 16

free space threshold. By applying overrides to this monitor, you can do it once for all
Exchange 2007 disks with mailbox databases on them to enforce a common standard
for when Operations Manager should alert on disk free space.
h. Click Cancel.
i. Click the Product Knowledge tab.
j. Examine the Knowledge that explains how Exchange 2007 disk monitoring
works.
k. Click Close.
Page 16 of 16

Microsoft Virtual Labs: Monitoring Windows Server 2008, SQL Server 2008 and Exchange 2007

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Microsoft Virtual Labs: Monitoring Windows Server 2008, SQL Server 2008 and Exchange 2007

Загружено:

Авторское право:

Доступные форматы

Microsoft Virtual Labs

Monitoring Windows Server

Monitoring Windows Server 2008, SQL

Computers used in this

Tasks Detailed Steps

Tasks Detailed Steps

Tasks Detailed Steps

Tasks Detailed Steps

Tasks Detailed Steps

Tasks Detailed Steps

Contains definitions for object types and groups that

Provides all monitoring for SQL Server 2008.

Tasks Detailed Steps

Tasks Detailed Steps

Tasks Detailed Steps

Tasks Detailed Steps

Contains monitors for the UM server role.

Tasks Detailed Steps

Tasks Detailed Steps

Tasks Detailed Steps

Tasks Detailed Steps

Tasks Detailed Steps

Вам также может понравиться