SC2012 OpsMgr Operations
SC2012 OpsMgr Operations
Revision History
Release Date Changes
Feedback
Send suggestions and comments about this content to [email protected].
Revision History
Release Date Changes
9
operating tasks typically performed by an administrator or operator. It follows the Operations
Manager Deployment Guide in order of use during an Operations Manager implementation
project, but does not assume that the administrator or operator participated in the installation of
the Operations Manager infrastructure.
Before you read the Operations Guide:
If you are new to Operations Manager, you should read Key Concepts to understand what a
management group is and how Operations Manager works.
If you are familiar with Operations Manager 2007, you should read What’s New in System Center
2012 - Operations Manager to review the differences between Operations Manager 2007 and
Operations Manager for System Center 2012.
10
management server. It also includes recommendations for creating an inventory of your
Operations Manager infrastructure and for daily, weekly, and monthly tasks.
Related Resources
TechNet Library main page for System Center 2012 - Operations Manager
What’s New in System Center 2012 - Operations Manager
System Center 2012 - Operations Manager Release Notes
Deployment Guide for System Center 2012 - Operations Manager
System Center 2012 - Operations Manager Supported Configurations
Downloadable Documentation
You can download a copy of this technical documentation from the Microsoft Download Center.
Always use the TechNet library for the most up-to-date information.
Check for problems in a management group Check the Management Group Health
view in the Operations Manager folder in
the Monitoring workspace
See the State and Alerts summary on the
Monitoring Overview page
Check Active Alerts in the Monitoring
workspace
Check Task Status in the Monitoring
workspace
Customize the settings of a view for your own In the Monitoring workspace, right-click a view
use in the navigation pane, and then click
Personalize view. For more information, see
How to Personalize a View in Operations
Manager.
Change a setting for a rule, monitor, or alert. Make changes to rules, monitors, or alerts by
creating an override. Select a rule, monitor, or
alert, and then access the overrides options by
right-clicking, or clicking Overrides on the
toolbar, or clicking Overrides in the Tasks
pane. For more information, see Tuning
Monitoring by Using Targeting and Overrides
and Creating a Management Pack for
Overrides.
Change how frequently records are removed In the Administration workspace, click
from the operational database. Settings, right-click Database Grooming, and
then click Properties. For more information,
see How to Configure Grooming Settings for
the Operations Manager Database.
Give a user permissions to view Operations In the Administration workspace, click User
Manager information or perform tasks. Roles, and then right-click a specific role and
12
To perform this task Do this
Display a dashboard view on a SharePoint site. You must deploy the Operations Manager Web
Part to a SharePoint site, configure the Web
Part to connect to a web console, and add the
Web Part to a SharePoint page. For more
information, see Using SharePoint to View
Operations Manager Data.
See Also
Operations Guide for System Center 2012 - Operations Manager
13
servers, and databases are monitored. Monitoring of the infrastructure is provided by the
Monitoring Pack for Operations Manager, one of the management packs that is installed with
Operations Manager. You can view details for the Monitoring Pack for Operations Manager in its
guide at http://go.microsoft.com/fwlink/p/?LinkId=226940.
After Operations Manager is installed, you must decide which objects—computers and devices—
should be monitored, and which applications, features, and services should be monitored on
those objects.
Tip
As you install agents and import management packs, you should document your actions.
For more information, see Inventory of Operations Manager Infrastructure.
14
To begin monitoring, computers must be discovered. For a description of the discovery process,
see “How Objects Are Discovered and Monitored” in Key Concepts.
Comprehensive monitoring requires that an agent be installed on the discovered computer. This
section explains how to discover computers, install agents on discovered computers, and
configure agents. It also provides instructions for uninstalling agents. For information about
monitoring computers without installing an agent, see Agentless Monitoring in Operations
Manager and Client Monitoring Using Agentless Exception Monitoring in Operations Manager.
Note
For problems with discovery, see Troubleshooting Discovery in Operations Manager.
15
Operations Manager Agent Installation Methods
An Operations Manager agent is a service that is installed on a computer. The agent collects
data, compares sampled data to predefined values, creates alerts, and runs responses. A
management server receives and distributes configurations to agents on monitored computers.
There are several methods you can use to install an Operations Manager agent on a computer.
You can use the Discovery Wizard in the Operations console, sometimes called a push
installation. (All other methods are considered manual installations.) This method works for
computers running Windows, UNIX, and Linux operating systems.
You can run the Setup Wizard from the Operations Manager installation media and install the
agent directly on a computer running Windows.
You can install an agent directly on a computer running Windows, UNIX, and Linux operating
systems by using a command line.
To install the agent by using the Discovery Wizard, firewall ports must be open on the agent-
managed computers. Also, you must have an account that is a local administrator on the
computer on which you want to install the agent.
Note
For information about port requirements for agents, see Agent and Agentless Monitoring
in the Deployment Guide.
Agents that are installed by using the Discovery Wizard can be managed from the Operations
console, such as updating agent versions, applying patches, and configuring the management
server that the agent reports to.
When you install the agent using a manual method, updates to the agent must also be performed
manually. You will be able to use Active Directory integration to assign agents to management
groups. For more information, see Integrating Active Directory and Operations Manager.
See Also
Install Agent on Windows Using the Discovery Wizard
Install Agent on UNIX and Linux Using the Discovery Wizard
Install Agent Using the MOMAgent.msi Setup Wizard
Install Agent Using the Command Line
Install Agent and Certificate on UNIX and Linux Computers Using the Command Line
Managing Certificates for UNIX and Linux Computers
Process Manual Agent Installations
Applying Overrides to Object Discoveries
Configuring Agents
Examples of Using MOMAgent Command to Manage Agents
Upgrading and Uninstalling Agents on UNIX and Linux Computers
Manually Uninstalling Agents from UNIX and Linux Computers
Uninstall Agent from Windows-based Computers
16
Install Agent on Windows Using the Discovery Wizard
You can use the Operations console to search your environment for manageable objects and
then deploy an agent to any object that you want to monitor. The process of searching your
environment is called “discovery.” One of the advantages of using discovery is that it lists all
manageable objects, including any that you might not be aware of.
The Discovery Wizard does not show computers that the management group is already
monitoring. If you are doing a phased rollout of your management group, you can run the wizard
to add new computers to the group. Also, after your initial deployment, you can use the Discovery
Wizard to add newly installed computers to be managed.
When agents are pushed out to computers, System Center 2012 – Operations Manager sends
credentials that have local administrator rights for that computer; this is required to install the
agent.
If the Discovery Wizard is not right for your needs (for example, if you have a set list of computers
to which you want to deploy agents), you have the option of manually installing agents on
systems to be managed. Agents can also be embedded in the host image of the monitored
computer.
Use the following procedure to discover computers running Windows and to deploy the
Operations Manager agent to the discovered computers from the Operations console. For a list of
the supported operating system versions, see Supported Configurations.
Note
For information about port requirements for agents, see Agent and Agentless Monitoring
in the Deployment Guide.
Note
The Discovery Wizard links in the Operations console open the Computer and
Device Management Wizard.
4. On the Discovery Type page, click Windows computers.
5. On the Auto or Advanced? page, do the following:
a. Select either Automatic computer discovery or Advanced discovery. If you select
Automatic computer discovery, click Next, and then go to step 7. If you select
Advanced discovery, continue with the following steps.
Note
Automatic computer discovery scans for Windows-based computers in the
domain. Advanced discovery allows you to specify criteria for the computers
17
that the wizard will return, such as computer names starting with NY.
b. In the Computer and Device Classes list, select Servers and Clients, Servers
Only, or Clients Only.
c. In the Management Server list, click the management server or gateway server to
discover the computers.
d. If you selected Servers and Clients, you can select the Verify discovered
computers can be contacted check box. This is likely to increase the success rate
of agent deployment, but discovery can take longer.
Note
If the Active Directory catalog does not contain the NetBIOS names for
computers in a domain, select Verify discovered computers can be
contacted. Otherwise, the Browse, or Type In option fails to find computers.
This affects computers in the same domain as the management server, in
another domain with a full trust relationship, and in untrusted domains by
using a gateway server.
e. Click Next.
Note
The wizard can return approximately 4000 computers if Verify discovered
computers can be contacted is selected, and it can return 10,000 computers if
this option is not selected. Automatic computer discovery verifies that discovered
computers can be contacted. A computer that is already managed by the
management group is not returned.
6. On the Discovery Method page, you can locate the computers that you want to manage
by either scanning or browsing Active Directory Domain Services or typing the computer
names.
If you want to scan, do the following:
a. If it is not already selected, select Scan Active Directory and then click Configure.
b. In the Find Computers dialog box, type the criteria that you want to use for
discovering computers, and then click OK.
c. In the Domain list, click the domain of the computers that you want to discover.
If you want to browse Active Directory Domain Services or type the computer names, do
the following:
Select Browse for, or type-in computer names, click Browse, specify the names of
the computers that you want to manage, and then click OK.
In the Browse for, or type-in computer names box, type the computer names,
separated by a semi-colon, comma, or a new line. You can use NetBIOS computer
names or fully qualified domain names (FQDN).
7. Click Next, and on the Administrator Account page, do one of the following:
Select Use selected Management Server Action Account if it is not already
selected.
18
Select Other user account, type the User name and Password, and then select the
Domain from the list. If the user name is not a domain account, select This is a local
computer account, not a domain account.
Important
The account must have administrative privileges on the targeted computers.
If This is a local computer account, not a domain account is selected, the
management server action account will be used to perform discovery.
8. Click Discover to display the Discovery Progress page. The time it takes discovery to
finish depends on many factors, such as the criteria specified and the configuration of the
IT environment. If a large number (100 or more) of computers are being discovered or
agents are being installed, the Operations console will not be usable during discovery
and agent installation.
Note
Computers that are already managed by the management group will not be
returned by the wizard.
9. On the Select Objects to Manage page, do the following:
a. Select the computers that you want to be agent-managed computers.
b. In the Management Mode list, click Agent and then click Next.
Note
The discovery results show virtual nodes of clusters. Do not select any virtual
nodes to be managed.
10. On the Summary page, do the following:
a. Leave the Agent installation directory set to the default of %ProgramFiles%\
System Center Operations Manager or type an installation path.
Important
If a different Agent installation directory is specified, the root of the path
must exist on the targeted computer or the agent installation fails.
Subdirectories, such as \Agent, are created if they do not exist.
b. Leave Agent Action Account set to the default, Local System, or select Other and
type the User name, Password, and Domain. The Agent Action Account is the
default account that the agent will use to perform actions.
c. Click Finish.
11. In the Agent Management Task Status dialog box, the Status for each selected
computer changes from Queued to Success; the computers are ready to be managed.
Note
If the task fails for a computer, click the targeted computer. The reason for the
failure is displayed in the Task Output text box.
12. Click Close.
19
See Also
Operations Manager Agent Installation Methods
Install Agent on UNIX and Linux Using the Discovery Wizard
Install Agent Using the MOMAgent.msi Setup Wizard
Install Agent Using the Command Line
Install Agent and Certificate on UNIX and Linux Computers Using the Command Line
Managing Certificates for UNIX and Linux Computers
Process Manual Agent Installations
Applying Overrides to Object Discoveries
Configuring Agents
Examples of Using MOMAgent Command to Manage Agents
Upgrading and Uninstalling Agents on UNIX and Linux Computers
Manually Uninstalling Agents from UNIX and Linux Computers
Uninstall Agent from Windows-based Computers
20
discovered.
ii. For the Discovery type select Discover all computers or Discover only
computers with the UNIX/Linux agent installed.
If you choose to discover only computers with the agent installed, the only
credential that you will need to provide is for the agent verification. This can be a
low-privileged account on the UNIX or Linux computer.
Security
Discovering only computers with the agent installed requires that the
agent is currently installed and configured with a signed certificate.
iii. To specify the credentials for installing an agent, click Set credentials. For
detailed instructions, see “Credentials for Installing Agents” in Setting Credentials
for Accessing UNIX and Linux Computers.
iv. Click Save.
b. Select a management pool to monitor the UNIX or Linux computer.
Note
The option will be changed from management pool to resource pool in the
final release of Operations Manager.
6. Click Discover to display the Discovery Progress page. The time it takes to finish
discovery depends on many factors, such as the criteria specified and the configuration
of the environment. If a large number (100 or more) of computers are being discovered or
agents are being installed, the Operations console will not be usable during discovery
and agent installation.
7. On the Computer Selection page, on the Manageable computers tab, select the
computers that you want to be managed. The Additional results tab lists any errors and
computers that are already being managed.
8. Click Manage.
9. On the Computer Management page, after the deployment process is completed, click
Done.
You must have, at a minimum, a UNIX/Linux Action Account profile configured with a
Monitoring Run As Account to monitor the UNIX or Linux computer. For more information, see
How to Configure Run As Accounts and Profiles for UNIX and Linux Access.
See Also
Operations Manager Agent Installation Methods
Install Agent on Windows Using the Discovery Wizard
Install Agent Using the MOMAgent.msi Setup Wizard
Install Agent Using the Command Line
Install Agent and Certificate on UNIX and Linux Computers Using the Command Line
Managing Certificates for UNIX and Linux Computers
21
Process Manual Agent Installations
Applying Overrides to Object Discoveries
Configuring Agents
Examples of Using MOMAgent Command to Manage Agents
Upgrading and Uninstalling Agents on UNIX and Linux Computers
Manually Uninstalling Agents from UNIX and Linux Computers
Uninstall Agent from Windows-based Computers
Note
For information about port requirements for agents, see Agent and Agentless Monitoring
in the Deployment Guide.
To deploy the Operations Manager agent with the Agent Setup Wizard
1. Use local administrator privileges to log on to the computer where you want to install the
agent.
2. On the Operations Manager installation media, double-click Setup.exe.
3. In Optional Installations, click Local agent.
4. On the Welcome page, click Next.
5. On the Destination Folder page, leave the installation folder set to the default, or click
Change and type a path, and then click Next.
6. On the Management Group Configuration page, do one of the following:
Leave the Specify Management Group information check box selected, and then
22
click Next.
Clear the Specify Management Group information check box if management
group information has been published to Active Directory Domain Services, and then
click Next.
Note
Step 7 is bypassed by the Agent Setup Wizard if the Specify Management
Group information check box is cleared.
7. On the Management Group Configuration page, do the following:
a. Type the name of the management group in the Management Group Name field and
the (which server?) server name in the Management Server field.
Note
To use a gateway server, enter the gateway server name in the
Management Server text box.
b. Type a value for Management Server Port, or leave the default of 5273.
c. Click Next.
8. On the Agent Action Account page, leave it set to the default of Local System, or
select Domain or Local Computer Account; type the User Account, Password, and
Domain or local computer; and then click Next.
9. On the Microsoft Update page, select Use Microsoft Update when I check for
updates (recommended) or I don’t want to use Microsoft Update, and then click
Next.
10. On the Ready to Install page, review the settings and then click Install to display the
Installing System Center Operations Manager Agent page.
11. When the Completing the Operations Manager Agent Setup Wizard page appears,
click Finish.
See Also
Operations Manager Agent Installation Methods
Install Agent on Windows Using the Discovery Wizard
Install Agent on UNIX and Linux Using the Discovery Wizard
Install Agent Using the Command Line
Install Agent and Certificate on UNIX and Linux Computers Using the Command Line
Managing Certificates for UNIX and Linux Computers
Process Manual Agent Installations
Applying Overrides to Object Discoveries
Configuring Agents
Examples of Using MOMAgent Command to Manage Agents
Upgrading and Uninstalling Agents on UNIX and Linux Computers
Manually Uninstalling Agents from UNIX and Linux Computers
23
Uninstall Agent from Windows-based Computers
24
=MSname SECURE_PORT=PortNumber
ACTIONS_USE_COMPUTER_ACCOUNT={0|1} ACTIONSUSER=UserName
ACTIONSDOMAIN=DomainName ACTIONSPASSWORD=Password
nNote
Ensure you use the correct 32-bit or 64-bit version of MOMAgent.msi for the
computer you are installing the agent on.
where:
25
“0” to send reports immediately. If you
do not include this parameter, the agent
installation defaults to “0”.
See Also
Operations Manager Agent Installation Methods
Install Agent on Windows Using the Discovery Wizard
Install Agent on UNIX and Linux Using the Discovery Wizard
Install Agent Using the MOMAgent.msi Setup Wizard
Install Agent and Certificate on UNIX and Linux Computers Using the Command Line
26
Managing Certificates for UNIX and Linux Computers
Process Manual Agent Installations
Applying Overrides to Object Discoveries
Configuring Agents
Examples of Using MOMAgent Command to Manage Agents
Upgrading and Uninstalling Agents on UNIX and Linux Computers
Manually Uninstalling Agents from UNIX and Linux Computers
Uninstall Agent from Windows-based Computers
Install Agent and Certificate on UNIX and Linux Computers Using the
Command Line
Your environment may require that you manually install the agent. Use the following procedures
to manually install agents to UNIX and Linux computers for monitoring in System
Center 2012 – Operations Manager.
To install the agent on Red Hat Enterprise Linux and SUSE Linux Enterprise Server
1. Transfer the agent (scx-<version>-<os>-<arch>.rpm) to the Linux server, type:
scx-<version>-<os>-<arch>.rpm
27
To install the agent on HP-UX
1. Transfer the agent (scx-<version>-<os>-<arch>.gz) to the HP server:
cp scx-<version>-<os>-<arch>.gz
Installing Certificates
When you manually deploy an agent, you perform the first two steps that are typically handled by
the Discovery Wizard, deployment and certificate signing. Then, you use the Discovery Wizard to
add the computer to the Operations Manager database.
If there are existing certificates on the system, they are reused during agent installation. New
certificates are not created. Certificates are not automatically deleted when you uninstall an
agent. You must manually delete the certificates that are listed in the /etc/opt/microsoft/scx/ssl
folder. To regenerate the certificates at install, you must remove this folder before agent
installation.
28
You must have already manually installed an agent before you start this procedure. You will need
a root or elevated account to perform the procedure.
Note
Ensure that the location where Operations Manager is installed is in your path
statement, or use the fully qualified path of the scxcertconfig.exe file.
6. Securely copy or transfer the scx_new.pem file into the /etc/opt/microsoft/scx/ssl folder
on the computer that is hosting the UNIX or Linux operating system. This replaces the
original scx-host-<hostname>.pem file.
See Also
Operations Manager Agent Installation Methods
Install Agent on Windows Using the Discovery Wizard
Install Agent on UNIX and Linux Using the Discovery Wizard
Install Agent Using the MOMAgent.msi Setup Wizard
Install Agent Using the Command Line
Process Manual Agent Installations
Applying Overrides to Object Discoveries
Configuring Agents
Examples of Using MOMAgent Command to Manage Agents
Managing Certificates for UNIX and Linux Computers
29
Upgrading and Uninstalling Agents on UNIX and Linux Computers
Manually Uninstalling Agents from UNIX and Linux Computers
Uninstall Agent from Windows-based Computers
When you manually deploy an agent, you perform the first two steps that are typically handled by
the Discovery Wizard: deployment and certificate signing. Then, you use the Discovery Wizard to
add the computer to the Operations Manager database.
If there are existing certificates on the system, they are reused during agent installation. New
certificates are not created. Certificates are not automatically deleted when you uninstall an
agent. You must manually delete the certificates that are listed in the /etc/opt/microsoft/scx/ssl
30
folder. To regenerate the certificates during instalation, you must remove this folder before agent
installation.
For instructions on how to manually deploy an agent, see Install Agent and Certificate on UNIX
and Linux Computers Using the Command Line, and then use the following procedure to install
the certificates.
31
Agent File MD5 Hash
32
Agent File SHA1
33
Agent File SHA256
See Also
Operations Manager Agent Installation Methods
Install Agent on Windows Using the Discovery Wizard
Install Agent on UNIX and Linux Using the Discovery Wizard
Install Agent Using the MOMAgent.msi Setup Wizard
Install Agent Using the Command Line
Install Agent and Certificate on UNIX and Linux Computers Using the Command Line
34
Process Manual Agent Installations
Applying Overrides to Object Discoveries
Configuring Agents
Examples of Using MOMAgent Command to Manage Agents
Upgrading and Uninstalling Agents on UNIX and Linux Computers
Manually Uninstalling Agents from UNIX and Linux Computers
Uninstall Agent from Windows-based Computers
Option Action
Reject new manual agent installations Designates that all requests from a manually
installed agent will be denied by Operations
Manager. This is the most secure setting and is
selected by default.
Review new manual agent installations in Designates that all requests from a manually
pending management view installed agent will be directed to Pending
Management before being allowed to join the
management group. An administrator must
review the request and manually approve the
agents' request.
Auto-approve new manually installed agents This option is available only if Review new
manual agent installations in pending
management view has been selected. This
setting causes Operations Manager to
automatically allow any manually installed
agent to join the management group. This is the
least secure option.
Important
A management group or management server must be configured to accept agents that
are installed with MOMAgent.msi or they will be automatically rejected and therefore not
35
displayed in the Operations console. If a management group is configured to accept
manually installed agents, the agents will display in the console approximately one hour
after they are installed.
The following procedures show you how to configure settings for manual agent installations.
To override the manual agent installation setting for a single management server
1. Log on to the Operations console with an account that is a member of the Operations
Manager Administrators role.
2. Click Administration.
3. In the Administration workspace, expand Administration, expand Device
Management, and then click Management Servers.
4. In the results pane, right-click the management server that you want to view the
properties of, and then click Properties.
5. In the Management Server Properties dialog box, click the Security tab.
6. On the Security tab, do the following:
To maintain a higher level of security, select Reject new manual agent
installations, and then click OK.
To configure for manual agent installation, click Review new manual agent
installations in pending management view, and then click OK.
Optionally, select Auto-approve new manually installed agents.
7. Click OK.
36
3. In the Pending Management pane, select computers in Type: Manual Agent Install.
4. Right-click the computers, and then click Approve.
5. In the Manual Agent Install dialog box, click Approve. The computers now appear in the
Agent Managed node and are ready to be managed.
Note
Rejected agents remain in Pending Management until the agent is uninstalled
for the management group.
See Also
Operations Manager Agent Installation Methods
Install Agent on Windows Using the Discovery Wizard
Install Agent on UNIX and Linux Using the Discovery Wizard
Install Agent Using the MOMAgent.msi Setup Wizard
Install Agent and Certificate on UNIX and Linux Computers Using the Command Line
Managing Certificates for UNIX and Linux Computers
Install Agent Using the Command Line
Applying Overrides to Object Discoveries
Configuring Agents
Examples of Using MOMAgent Command to Manage Agents
Upgrading and Uninstalling Agents on UNIX and Linux Computers
Manually Uninstalling Agents from UNIX and Linux Computers
Uninstall Agent from Windows-based Computers
See Also
Operations Manager Agent Installation Methods
Install Agent on Windows Using the Discovery Wizard
Install Agent on UNIX and Linux Using the Discovery Wizard
Install Agent Using the MOMAgent.msi Setup Wizard
Install Agent and Certificate on UNIX and Linux Computers Using the Command Line
Managing Certificates for UNIX and Linux Computers
Process Manual Agent Installations
Install Agent Using the Command Line
Configuring Agents
Examples of Using MOMAgent Command to Manage Agents
Upgrading and Uninstalling Agents on UNIX and Linux Computers
Manually Uninstalling Agents from UNIX and Linux Computers
Uninstall Agent from Windows-based Computers
38
Configuring Agents
In System Center 2012 – Operations Manager, when you install an agent on a computer, an
Operations Manager Agent application is added to Control Panel. You can use the application to
change the account that the agent will use when performing actions requested by the
management server, to remove a management group from an agent configuration, and to
configure the Active Directory integration setting for the agent. To perform these tasks, you must
have local Administrator permissions on the computer.
Note
If you want to automate the process of adding or removing management groups from an
agent, you can use the Agent API that allows you to write scripts that can automate the
agent configuration process. For more information, see Using the Operations Manager
Agent Configuration Library.
Note
When you save changes in the Operations Manager Agent application, the Health service
will be stopped and restarted.
Configuring an Agent to Report to Multiple Management Groups
Changing the Account Configuration for an Agent
Removing a Management Group from an Agent
Changing the Active Directory Integration Setting for an Agent
Note
It might take one day or longer for the discovered instances of the agent to be made part
of the new management group. They will be added after the next discovery interval.
Note
You can remove all management groups while leaving the agent installed. This is
useful in situations such as when you want to prepare a computer for imaging
and want an image with the agent installed but without assignment to a specific
management group.
40
2. On the Management Group tab, clear or select Automatically update management
group assignments from AD DS. If you select this option, on agent startup, the agent
will query Active Directory for a list of management groups to which it has been assigned.
Those management groups, if any, will be added to the list. If you clear this option, all
management groups assigned to the agent in Active Directory will be removed from the
list.
3. Click OK.
See Also
Operations Manager Agent Installation Methods
Install Agent on Windows Using the Discovery Wizard
Install Agent on UNIX and Linux Using the Discovery Wizard
Install Agent Using the MOMAgent.msi Setup Wizard
Install Agent and Certificate on UNIX and Linux Computers Using the Command Line
Managing Certificates for UNIX and Linux Computers
Process Manual Agent Installations
Applying Overrides to Object Discoveries
Install Agent Using the Command Line
Examples of Using MOMAgent Command to Manage Agents
Upgrading and Uninstalling Agents on UNIX and Linux Computers
Manually Uninstalling Agents from UNIX and Linux Computers
Uninstall Agent from Windows-based Computers
41
The following example shows a fresh installation of an agent and uses the Local System for the
Action Account.
msiexec.exe /i path\Directory\MOMAgent.msi /qn /l*v %temp%\
MOMAgentinstall.log USE_SETTINGS_FROM_AD=0 MANAGEMENT_GROUP=<MG_Name>
MANAGEMENT_SERVER_DNS=<MSDNSName> MANAGEMENT_SERVER_AD_NAME=<MSDNSName>
ACTIONS_USE_COMPUTER_ACCOUNT=1 USE_MANUALLY_SPECIFIED_SETTINGS=1
Agent installation with Active Directory integration and using a specific Action Account
The following example installs an agent by using Active Directory and a specific Action Account.
msiexec /i path\Directory\MOMAgent.msi /qn /l*v %temp%mominst.NoGroupSpecified.log
USE_SETTINGS_FROM_AD=1 USE_MANUALLY_SPECIFIED_SETTINGS=0 ACTIONS_USE_COMPUTER_ACCOUNT=0
ACTIONSUSER=<AccountUser> ACTIONSDOMAIN=<AccountDomain> ACTIONSPASSWORD=<AccountPassword>
Agent installation with Active Directory integration and using the Local System account
The following example installs an agent by using Active Directory and the Local system account
for the Action Account.
msiexec /i path\Directory\MOMAgent.msi /qn /l*v %temp%\ mominst.NoGroupSpecified.log
USE_SETTINGS_FROM_AD=1 ACTIONS_USE_COMPUTER_ACCOUNT=1 USE_MANUALLY_SPECIFIED_SETTINGS=0
See Also
Operations Manager Agent Installation Methods
Install Agent on Windows Using the Discovery Wizard
Install Agent on UNIX and Linux Using the Discovery Wizard
Install Agent Using the MOMAgent.msi Setup Wizard
Install Agent and Certificate on UNIX and Linux Computers Using the Command Line
Managing Certificates for UNIX and Linux Computers
Process Manual Agent Installations
Applying Overrides to Object Discoveries
42
Configuring Agents
Install Agent Using the Command Line
Upgrading and Uninstalling Agents on UNIX and Linux Computers
Manually Uninstalling Agents from UNIX and Linux Computers
Uninstall Agent from Windows-based Computers
Upgrading Agents
You must run the UNIX/Linux Agent Upgrade Wizard to upgrade agents from earlier versions, or
when updates are issued by Microsoft, for of Operations Manager.
To Upgrade an Agent
1. In the Operations Console click Administration.
2. Click UNIX/Linux Computers in the Device Management node.
3. In the Actions pane, click Upgrade Agent to start the UNIX/Linux Agent Upgrade
Wizard.
4. In the Select Upgrade Targets page, all applicable computers that have the installed
agent will be selected by default for upgrade. Unselect any targets you do not want to
upgrade.
5. On the Credentials page, select one of the credentials options.
If you select the option to use existing credentials and are alerted that one or more of the
selected target computers does not have a Run As account assigned with the required
profiles, you must do one of the following:
Provide specified credentials with the Provide upgrade credentials option.
Click Show Computers (in the alert text) for a list of the computers that do not have
the required credentials specified in Run As Accounts. Then click Previous to
unselect them and try again.
For detailed instructions on how to set credentials, see How to Set Credentials for
Accessing UNIX and Linux Computers.
6. Click Upgrade.
43
Uninstalling Agents
You can uninstall an agent from the targeted computer by using the UNIX/Linux Agent Uninstall
Wizard. For information on manually uninstalling agents, see Manually Uninstalling Agents from
UNIX and Linux Computers.
To Uninstall an Agent
1. In the Operations Console click Administration.
2. Click UNIX/Linux Computers in the Device Management node.
3. In the Actions pane, click Uninstall Agent to start the UNIX/Linux Agent Uninstall
Wizard.
4. In the Select Uninstall Targets page, all applicable computers that have the installed
agent will be selected by default for uninstallation. Unselect any targets you do not want
to uninstall.
5. On the Credentials page, select one of the credentials options.
If you select the option to use existing credentials and are alerted that one or more of the
selected target computers does not have a Run As account assigned, you must do one of
the following:
Provide specified credentials with the Provide uninstall credentials option.
Click Show Computers (in the alert text) for a list of the computers does not have
the required credentials specified in Run As Accounts. Then click Previous to
unselect them and try again.
For detailed instructions on how to set credentials, see How to Set Credentials for
Accessing UNIX and Linux Computers.
6. Click Uninstall.
See Also
Operations Manager Agent Installation Methods
Install Agent on Windows Using the Discovery Wizard
Install Agent on UNIX and Linux Using the Discovery Wizard
Install Agent Using the MOMAgent.msi Setup Wizard
Install Agent and Certificate on UNIX and Linux Computers Using the Command Line
Managing Certificates for UNIX and Linux Computers
Process Manual Agent Installations
Applying Overrides to Object Discoveries
Configuring Agents
Examples of Using MOMAgent Command to Manage Agents
Install Agent Using the Command Line
Manually Uninstalling Agents from UNIX and Linux Computers
Uninstall Agent from Windows-based Computers
44
Manually Uninstalling Agents from UNIX and Linux Computers
There are three ways to uninstall the UNIX and Linux management packs and agents.
1. Delete selected UNIX or Linux system management packs from the Operations
Manager Operations Console.
2. Delete an agent from Operations Manager, and uninstall the agent from the monitored
computer. It will be uninstalled first from the UNIX or Linux computer.
3. Delete the agent from Operations Manager without uninstalling it on the UNIX or Linux host.
Use the following procedures to uninstall agents.
To uninstall the agent from Red Hat enterprise Linux and SUSE Linux enterprise
servers
1. Log on as the root user, and uninstall the agent by typing
rpm –e scx
2. To verify that the package is uninstalled, type
rpm –q scx
45
lslpp –L scx.rte
See Also
Operations Manager Agent Installation Methods
Install Agent on Windows Using the Discovery Wizard
Install Agent on UNIX and Linux Using the Discovery Wizard
Install Agent Using the MOMAgent.msi Setup Wizard
Install Agent and Certificate on UNIX and Linux Computers Using the Command Line
Managing Certificates for UNIX and Linux Computers
Process Manual Agent Installations
Applying Overrides to Object Discoveries
Configuring Agents
Examples of Using MOMAgent Command to Manage Agents
Upgrading and Uninstalling Agents on UNIX and Linux Computers
Install Agent Using the Command Line
Uninstall Agent from Windows-based Computers
Important
The account must have administrative rights on the computer or the uninstall
will fail.
c. Click Uninstall.
46
6. In the Agent Management Task Status dialog box, the Status for each selected
computer changes from Queued to Success.
Note
If the task fails for a computer, click the computer and read the reason for the
failure in the Task Output text box.
7. Click Close.
Note
The Agent Setup Wizard can also be run by double-clicking MOMAgent.msi,
1. Log on to the managed computer with an account that is a member of the administrators
To which isthe
uninstall available
agent on
by the Operations
using Managerfrom
MOMAgent.msi installation media. line
the command
security group for the computer.
2. Open the command window.
3. At the prompt, for example, type the following:
%WinDir%\System32\msiexec.exe /x <path>\MOMAgent.msi /qb
1. Using either the Operations console method or the command line method, uninstall the
To uninstall
agent the agent
from each node from
of theacluster.
cluster
2. In the Operations console, click Administration.
3. In the Administration workspace, click Agentless Managed.
4. In the Agentless Managed pane, locate all virtual instances for the cluster, right-click,
and then select Delete.
See Also
Operations Manager Agent Installation Methods
Install Agent on Windows Using the Discovery Wizard
Install Agent on UNIX and Linux Using the Discovery Wizard
Install Agent Using the MOMAgent.msi Setup Wizard
Install Agent and Certificate on UNIX and Linux Computers Using the Command Line
Managing Certificates for UNIX and Linux Computers
Process Manual Agent Installations
Applying Overrides to Object Discoveries
Configuring Agents
Examples of Using MOMAgent Command to Manage Agents
47
Upgrading and Uninstalling Agents on UNIX and Linux Computers
Manually Uninstalling Agents from UNIX and Linux Computers
Install Agent Using the Command Line
48
Operations Guide for System Center 2012 - Operations Manager
Managing Discovery and Agents
Tuning Monitoring by Using Targeting and Overrides
50
automatically when the monitor enters an error state, providing an automated way to solve
problems. They can also be run manually, because automated recovery isn’t always the preferred
approach.
Reports
Just as a management pack can contain views customized for the objects that management
pack targets, it can also contain custom reports. For example, a management pack might include
a customized definition of one of Operations Manager’s built-in reports, specifying the exact
objects that the report should target.
Object Discoveries
Object discoveries are used to find the specific objects on a network that need to be monitored.
Management packs define the type of objects that the management pack monitors. The object
discoveries can use the registry, WMI, scripts, OLE DB, LDAP, or even custom managed code to
find objects on a network. If an object discovery finds objects on your network that you do not
want to monitor, you can limit the scope of object discoveries by using overrides.
Run As Profiles
A management pack can include one or more Run As profiles. Run As profiles and Run As
accounts are used to select users with the privileges needed for running rules, tasks, and
monitors.
Management pack authors can create a Run As profile and associate the profile with one or more
rules, monitors, tasks, or discoveries. The named Run As profile is imported along with the
management pack into Operations Manager . The Operations Manager administrator then
creates a named Run As account and specifies users and groups. The administrator adds the
Run As account to the Run As profile and specifies the target computers that the account should
run on. The Run As account provides the credentials for running the rules, monitors, tasks, and
discoveries that are associated with the Run As profile to which the Run As account belongs.
51
Management Pack Libraries and Dependencies
Certain management packs are referred to as libraries, because they provide a foundation of
classes on which other management packs depend. A management pack that you download from
the Operations Manager Catalog might include a library management pack. Several library
management packs are imported as part of the Operations Manager installation process. For a
list of management packs imported during the installation of Operations Manager, see
Management Packs Installed with Operations Manager.
A dependency exists when a management pack references other management packs. You must
import all referenced management packs before you can import the management pack that
depends on those management packs. Management packs include a management pack guide
that should document the dependencies of the management pack. In addition, if you attempt to
import a management pack and the management packs that it is dependent on are not present,
the Import Management Packs dialog box will display a message that the management pack will
fail to import and a list of the missing management packs. After you import a management pack,
you can view its dependencies in the Operations console.
See Also
Creating a Management Pack for Overrides
Management Packs Installed with Operations Manager
Management Pack Life Cycle
How to Import an Operations Manager Management Pack
How to Remove an Operations Manager Management Pack
How to Export an Operations Manager Management Pack
How to Add Knowledge to a Management Pack
52
Purpose Associated management packs
53
Purpose Associated management packs
Template Library
Operations Manager APM Infrastructure
Operations Manager APM Infrastructure Monitoring
Operations Manager APM Library
Operations Manager APM Library Resources (enu)
Operations Manager APM Reports Library
Operations Manager APM Wcf Library
Operations Manager APM Web
Operations Manager Application Monitoring Library
Web Application Availability Monitoring Library
Web Application Availability Monitoring Solutions Base
Library
Web Application Availability Monitoring Solutions Library
Web Application Monitoring Library
System Application Log Library
Synthetic Transactions Library
Microsoft.SystemCenter.DataProviders.Library
54
Purpose Associated management packs
Microsoft.SystemCenter.Visualization.Configuration.Librar
y
Microsoft.SystemCenter.Visualization.Internal
Microsoft.SystemCenter.Visualization.Library
System Center Core Monitoring Views
See Also
Creating a Management Pack for Overrides
What Is in an Operations Manager Management Pack?
Management Pack Life Cycle
How to Import an Operations Manager Management Pack
How to Remove an Operations Manager Management Pack
How to Export an Operations Manager Management Pack
How to Add Knowledge to a Management Pack
55
Management Pack Life Cycle
System Center 2012 – Operations Manager uses management packs to extend monitoring
functionality. Ideally, a management pack tells you everything you want to know about the
application or technology that you are monitoring and nothing that you do not want to know.
Management packs are designed to provide a useful monitoring experience for most
environments, however you will want to test, tune, and tailor each management pack to provide
optimal results for your organization’s needs.
The management pack life cycle, described in the following table, is the recommended approach
to using management packs. The sections following the table provide details for each stage.
Stage Description
Review and evaluate management packs in a Before you deploy a management pack in your
pre-production environment production environment, you should familiarize
yourself with the contents of the management
pack and guide, and import the management
pack in a pre-production or test environment.
You can also view the management pack in a
virtual machine environment.
Tune the management pack settings and save Use overrides to tune the settings of a
in a customized management pack management pack—such as monitors, rules,
object discoveries, and attributes—to better
meet your organization’s needs. You should
save overrides to a management pack that you
create.
Deploy management packs into a production Export the management pack with overrides
environment that is associated with the management pack
that you are going to deploy, and import
management packs in your production
environment.
56
Stage Description
Note
Microsoft neither endorses nor provides support for this third-party product. Please
contact the specific provider for support issues.
When you have a new management pack, you should import it to a pre-production environment.
In Operations Manager, it is a best practice to have a production implementation that is used for
monitoring your production applications and a pre-production implementation that has minimal
interaction with the production environment. The pre-production management group is used for
testing and tuning management pack functionality before the management pack is deployed in
the production environment.
To accurately measure the data that a management pack gathers, you need to expose the agent
to the demands of your production environment. The hardware of the management server in the
pre-production environment should reflect the hardware that is in use in your production
environment. Your pre-production management group should have the same management packs
imported to the management server as the production management group. To test interoperability,
your pre-production environment should also include the same types of server roles that are in
your production environment, just on a smaller scale.
You can assign an Operations Manager agent to more than one management group, which is
called multihoming. If you multihome a representative subset of agents in your production
environment and your pre-production environment, the pre-production environment should give
you much of the information you need to correctly tune the management pack. For more
information on multihoming agents, see Configuring Agents.
57
Tune and Customize
You can use overrides to refine the settings of a monitoring object in Operations Manager,
including monitors, rules, object discoveries, and attributes. You should create a management
pack in which to save customizations that you make.
For more information about using overrides, see Tuning Monitoring by Using Targeting and
Overrides. For more information about creating management packs in which to save
customizations, see Best Practices for Change Control.
Deploy
When you are satisfied with the performance and results of the management pack in the pre-
production environment, you can deploy the management pack and its customizations in the
production environment. The management pack in which you saved the customizations must be
exported so that you can import it to other computers. For more information, see How to Export
an Operations Manager Management Pack. The management pack that contains the overrides
that you set is dependent on the original management pack and can be imported only to
management groups that have the original management pack installed.
Maintain
After a management pack has been deployed, you should periodically evaluate its performance
and results in the production environment to ensure that it continues to meet business needs. The
following list describes common events that might require changes to a management pack:
Environmental changes, such as new hardware or a new operating system
When you are testing new hardware or a new operating system that you plan to add to your
production environment, you should include existing management packs in your test plan to
identify any additional tuning that might be necessary. For a new operating system, you might
need to import new management packs specific to that operating system.
Adding a new application to the production environment
A new application might require a new management pack or adjustments to existing
management packs.
Upgrading a version of an application
When organizations upgrade application versions, they usually either upgrade in stages,
during which both versions of the application will exist in the network, or upgrade all
installations of the application at one time. After testing the management packs with the new
version and making any necessary adjustments, you should use the same approach for
deploying the management packs that you use for deploying the upgrades. If both versions of
the application will be in use at one time, you should install management packs appropriate
for each version. If all installations of the application will be upgraded at one time, remove the
management pack for the old version of the application and install the management pack for
the new version.
When a new or updated version of the management pack is available
You should use the pre-production environment to review and tune new or updated versions
of a management pack.
58
Policy changes
Ongoing changes in your business or organization might require adjustments to management
packs to accomplish more monitoring or less monitoring.
See Also
Creating a Management Pack for Overrides
Management Packs Installed with Operations Manager
What Is in an Operations Manager Management Pack?
How to Import an Operations Manager Management Pack
How to Remove an Operations Manager Management Pack
How to Export an Operations Manager Management Pack
How to Add Knowledge to a Management Pack
59
Import from disk (local storage or a network file share) by using the Operations console.
Use the Operations console to download a management pack from the catalog to import at a
later time.
Use an Internet browser to download a management pack from the catalog to import at a
later time.
Note
Using the management pack catalog service requires an Internet connection. If the
computer running Operations Manager cannot be connected to the Internet, use another
computer to download the management pack, and then copy the files to a shared folder
that is accessible to the Operations Manager management server.
The catalog on the Microsoft System Center Marketplace contains management packs from
Microsoft and some non-Microsoft companies. You can obtain management packs directly from
other companies and import them by using the procedure to import from disk. You can also
search for management packs created by the community, such as the packs available at the
System Center Central website.
Note
Microsoft neither endorses nor provides support for third-party products. Please contact
the specific provider for support issues.
You should always review the management pack guide before you import a management pack.
60
management packs, or you can expand SQL Server and select SQL Server 2005 for all
SQL Server 2005 management packs, or you can expand SQL Server 2005 and select
SQL Server Core Library Management Pack.
Note
When a management pack is labeled “(Online Catalog Only)”, you cannot import
the management pack directly from the catalog. You must download the .msi and
import from disk.
6. On the Select Management Packs page, the management packs that you selected for
import are listed. An icon next to each management pack in the list indicates the status of
the selection, as follows:
A green check mark indicates that the management pack can be imported. When all
management packs in the list display this icon, click Import.
A yellow information icon indicates that the management pack is dependent on one
or more management packs that are not in the Import list but are available in the
catalog. To add the management pack dependencies to the Import list, click Resolve
in the Status column. In the Dependency Warning dialog box that appears, click
Resolve.
A red error icon indicates that the management pack is dependent on one or more
management packs that are not in the Import list and are not available in the catalog.
To view the missing management packs, click Error in the Status column. To remove
the management pack with the error from the Import list, right-click the management
pack, and then click Remove.
Note
When you click Import, any management packs in the Import list that display the
Information or Error icon are not imported.
7. The Import Management Packs page appears and shows the progress for each
management pack. Each management pack is downloaded to a temporary directory,
imported to Operations Manager, and then deleted from the temporary directory. If there
is a problem at any stage of the import process, select the management pack in the list to
view the status details. Click Close.
Note
When you import a management pack that contains binary files (.mpb), you must
recycle the OperationsManager application pool in Internet Information Services (IIS)
Manager.
Note
When you click Import, any management packs in the Import list that display the
Error icon are not imported.
7. The Import Management Packs page appears and shows the progress for each
management pack. Each management pack is downloaded to a temporary directory,
imported to Operations Manager, and then deleted from the temporary directory. If there
is a problem at any stage of the import process, select the management pack in the list to
view the status details. Click Close.
Note
When you import a management pack that contains binary files (.mpb), you must
recycle the OperationsManager application pool in Internet Information Services (IIS)
Manager.
62
5. In the list of management packs, select the management pack that you want to import,
click Select, and then click Add.
In the list of management packs, you can select a product, or expand the product name
to select a specific version, or expand the product version to select a specific
management pack file. For example, you can select SQL Server for all SQL Server
management packs, or you can expand SQL Server and select SQL Server 2005 for all
SQL Server 2005 management packs, or you can expand SQL Server 2005 and select
SQL Server Core Library Management Pack.
6. The selected management packs are displayed in the Download list. In the Download
management packs to this folder field, enter the path where the management packs
should be saved, and then click Download.
7. The Download Management Packs page appears and shows the progress for each
management pack. If there is a problem with a download, select the management pack in
the list to view the status details. Click Close.
Note
Some management pack download pages contain a download link for the
management pack .msi file and a download link for the management pack guide.
Download both the .msi and the guide.
6. In the File Download dialog box, click Run to download and extract the management
pack files. Or, click Save to download the .msi file without extracting the files.
Note
Before you can import the management pack in Operations Manager, you must
run the .msi file to extract the files.
See Also
Creating a Management Pack for Overrides
Management Packs Installed with Operations Manager
What Is in an Operations Manager Management Pack?
Management Pack Life Cycle
How to Remove an Operations Manager Management Pack
How to Export an Operations Manager Management Pack
63
How to Add Knowledge to a Management Pack
Note
If any other imported management packs depend on the management pack you are
trying to remove, the Dependent Management Packs error message displays. You
must remove the dependent management packs before you can continue.
Operations Manager removes the selected management pack.
See Also
Creating a Management Pack for Overrides
Management Packs Installed with Operations Manager
What Is in an Operations Manager Management Pack?
Management Pack Life Cycle
How to Import an Operations Manager Management Pack
How to Export an Operations Manager Management Pack
How to Add Knowledge to a Management Pack
64
monitor, must be saved to an unsealed management pack. The unsealed management pack
references the sealed management pack that it modifies.
The following illustration shows the unsealed management packs that are installed with
Operations Manager.
Never use the management packs that are installed with Operations Manager to save any
settings that you change or elements that you create. When you have to select a destination
management pack, always select a management pack that you create.
You select a destination management pack when you create an override or disable a rule,
monitor, or object discovery. You also select a destination management pack when you create or
configure the following elements:
A folder in the Monitoring workspace
A unit, aggregate, or dependency monitor
An attribute
A group
A rule
A task
A Run As profile
Monitoring by using a management pack template
Monitoring of a distributed application
Tracking of service level objectives
Saving Overrides
As a best practice, save all overrides for each sealed management pack to an unsealed
management pack that is named ManagementPack_Override, where ManagementPack is the
name of the sealed management pack to which the overrides apply. For example, overrides to the
management pack Microsoft.InformationWorker.Office.XP.mp would be saved to
Microsoft.InformationWorker.Office.XP_Overrides.xml.
When you want to remove a sealed management pack, you must first remove any other
management packs that reference it. If the unsealed management packs that reference the
sealed management pack also contain overrides or elements that apply to a different sealed
management pack, you lose those overrides and elements when you remove the unsealed
management pack.
In the following image, overrides for management packs 1, 2, and 3 are all saved to a single
unsealed management pack. If you want to remove management pack 1, you first must remove
65
the unsealed management pack. As you can see, you would also remove all overrides for
management packs 2 and 3.
The recommended method is to create an unsealed management pack for each sealed
management pack that you want to override, as shown in the following image. Removing
management pack 1 and its unsealed management pack does not affect the other management
packs.
66
Create Management Pack.
-or-
In the Override Properties dialog box for a rule or monitor, in the Select destination
management pack section, click New.
See Also
How to Remove an Operations Manager Management Pack
Management Packs Installed with Operations Manager
What Is in an Operations Manager Management Pack?
Management Pack Life Cycle
How to Import an Operations Manager Management Pack
How to Export an Operations Manager Management Pack
How to Add Knowledge to a Management Pack
See Also
Creating a Management Pack for Overrides
Management Packs Installed with Operations Manager
What Is in an Operations Manager Management Pack?
67
Note
Management Pack Life Cycle
How to Import an Operations Manager Management Pack
How to Remove an Operations Manager Management Pack
How to Add Knowledge to a Management Pack
Tip
customizations to the Default Management Pack. As a best practice, you should instead create a
separate management pack for each sealed management pack you want to customize.
To avoid losing your company knowledge, be sure to back up management packs as part
of your general backup routine.
To add or edit company knowledge, the computer must meet the following software requirements:
The Operations console must be installed on a 32-bit computer. Adding and editing company
knowledge must be done on this computer.
Microsoft Office Word 2003 with the .NET Programmability feature, or Microsoft Office
Word 2007 or Office Word 2010 Professional edition (Standard edition is not supported)
Only the 32-bit version of Word 2010 is supported. The knowledge template will not
work with the 64-bit version of Word 2010.
Microsoft Visual Studio 2005 Tools for Office Second Edition Runtime at
http://go.microsoft.com/fwlink/?LinkId=74969. You must use this version of the Visual
Studio 2005 Tools for Office.
To add or edit company knowledge, you must have the Author or Administrator user role.
Important
Do not close Word.
10. Return to the company knowledge tab and click Save, and then click Close. This will
close both the properties dialog box and Word.
See Also
Creating a Management Pack for Overrides
Management Packs Installed with Operations Manager
What Is in an Operations Manager Management Pack?
Management Pack Life Cycle
How to Import an Operations Manager Management Pack
How to Remove an Operations Manager Management Pack
How to Export an Operations Manager Management Pack
69
Tuning Approach
For servers or applications, tune from the highest severity alerts and dependencies to the lowest.
Look at alerts first, then open the Health Explorer to gather more detailed information for the
problem. Validate results of the alerts generated, verify scope of monitoring against intended
targets (servers or services), and ensure the health model is accurate.
Each rule should be evaluated according to the following criteria:
Actionability: An alert is actionable if it tells you what went wrong and how to fix it. When
alerts are generated that do not require any action, consider disabling alerting for the rule.
Validity: An alert is valid if the issue that generated the alert can be confirmed and the issue
actually occurred at the moment the alert was generated.
Suppression: There should be only one alert stating the issue occurred.
What to Tune
Discovery frequency
Monitor thresholds
Targets
Intervals
Parameters
Tips
Import a single management pack at a time.
Review any new alerts reported for servers monitored with the new management pack. You
can use the Alerts and Most Common Alerts reports to help you discover your most common
alerts. When you first install a management pack, it tends to discover a multitude of
previously unknown issues. Monitor the alerts to determine potential areas of concern
Override the monitor or rule as applicable for a particular object type, a group, or a specific
object.
Disable the monitor or rule if the issue is not severe enough to warrant an alert and you do
not need to be made aware of the specific situation being monitored.
Change the threshold of the monitor that is generating the alert if you want the underlying
condition to be monitored, but the alert is being generated before the condition is actually a
problem for your particular environment.
When you set overrides for a management pack, save them to a management pack that is
named ManagementPack_Override, where ManagementPack is the name of the sealed
management pack to which the overrides apply. For example, overrides to the management
pack Microsoft.InformationWorker.Office.XP.mp would be saved to
Microsoft.InformationWorker.Office.XP_Overrides.xml..
70
Tuning Monitoring by Using Targeting and Overrides topics
Using Classes and Groups for Overrides in Operations Manager
How to Override a Rule or Monitor
How to Enable or Disable a Rule or Monitor
Using the Enforced Attribute in Overrides
How to Enable Recovery and Diagnostic Tasks
Classes
In Operations Manager, a class is a definition of an item that can be discovered and managed. A
class can represent a computer, a database, a service, a disk, an application, or any other kind of
object that requires monitoring. Monitors, rules, discoveries, overrides, and tasks can apply to a
class. For example, Windows Server 2003 Logical Disk is a class that defines logical disks on a
computer that is running the Windows Server 2003 operating system. A monitor that applies to
the Windows Server 2003 Logical Disk class will be applied only to objects that meet that class
definition.
Note
In the Operations console, the term target is used instead of class.
Classes are defined in the Operations Manager management pack libraries and in individual
product management packs that you import.
Groups
In Operations Manager, a group is a logical set of objects that can be used to define the scope of
overrides, views, user roles, and notifications. Some groups are provided in the Operations
Manager installation, such as All Windows Computers group and Agent Managed Computer
Group. You can create your own groups and add members to groups explicitly or dynamically.
71
Overrides
You have seen that classes are used to target workflows such as rules and monitors. A monitor or
rule is applied to a specific class. To change the value for a parameter of a rule or monitor, you
create an override. You have the following options for applying your override:
For all objects of class: Class
When you select this option for your override, the override settings apply to all objects in the
class at which the rule or monitor is targeted.
For a group
When you select this option for your override, the override settings apply only to members of
the group. The rule or monitor without the override settings continues to apply to all objects in
the targeted class except for those objects that are also members of the group used for the
override.
When you create a group, you save it to an unsealed management pack. However, an
element in an unsealed management pack, such as an override, cannot reference an element
in a different unsealed management pack, such as a group. If you are going to use a group to
limit the application of an override, you must either save the group to the same unsealed
management pack as the override, or you must seal the management pack that contains the
group.
For a specific object of class: Class
When you select this option for your override, the override settings apply only to the specified
object. The rule or monitor without the override settings continues to apply to all other objects
in the targeted class.
For all objects of another class
When you select this option for your override, the override settings apply only to objects of a
class other than the targeted class. The rule or monitor without the override settings
continues to apply to all objects in the targeted class.
Overrides that apply to a class are applied first, then overrides that apply to a group, and finally
overrides that apply to a specific object. For more information, see Using the Enforced Attribute in
Overrides.
72
You want to change the priority of an alert that applies to all operating systems for a
specific operating system
Select For all objects of another class and select the class that represents the operating
system for which you want to have a different alert priority.
You want the rule or monitor to apply only to specific computers
In this common scenario, you must perform the following two tasks:
1. Select to override For all objects of class: Class, and change Enabled to False. This will
disable the rule or monitor.
2. Select to override For a group, For a specific object of class: Class, or For all objects of
another class, and change Enabled to True. This enables the rule or monitor for members
of that group, the specified object, or the selected class only.
See Also
How to Override a Rule or Monitor
How to Enable or Disable a Rule or Monitor
Using the Enforced Attribute in Overrides
How to Enable Recovery and Diagnostic Tasks
To override a monitor
1. Log on to the computer with an account that is a member of the Operations Manager
Advanced Operator role.
2. In the Operations console, click Authoring.
3. In the Authoring workspace, expand Management Pack Objects and then click
73
Monitors.
4. In the Monitors pane, expand an object type completely and then click a monitor.
5. On the Operations console toolbar, click Overrides and then point to Override the
Monitor. You can choose to override this monitor for objects of a specific type or for all
objects within a group. After you choose which group of object type to override, the
Override Properties dialog box opens, enabling you to view the default settings
contained in this monitor. You can then choose whether to override each individual setting
contained in the monitor. For more information about applying an override, see Using
Classes and Groups for Overrides in Operations Manager.
Note
If the Overrides button is not available, make sure you have selected a monitor
and not a container object in the Monitors pane.
6. Click to place a check mark in the Override column next to each parameter that you want
to override. The Override Value can now be edited. Change the value in Override Value
to the value you want the parameter to use.
7. Either select a management pack from the Select destination management pack list or
create a new unsealed management pack by clicking New. For more information about
selecting a destination management pack, see Creating a Management Pack for
Overrides.
8. When you complete your changes, click OK.
See Also
Using Classes and Groups for Overrides in Operations Manager
How to Enable or Disable a Rule or Monitor
Using the Enforced Attribute in Overrides
How to Enable Recovery and Diagnostic Tasks
74
Advanced Operator role.
2. In the Operations console, click Authoring.
3. In the Authoring workspace, click Monitors (or Rules if you want to disable a rule).
4. In the Monitors or Rules section, click the monitor or rule that you want to disable.
5. On the Operations console toolbar, click Overrides and then point to Override the
Monitor (or Rule). You can choose to override this monitor or rule for objects of a specific
type or for all objects within a group. After you choose which group of object type to
override, the Override Properties dialog box opens, enabling you to view the default
settings contained in this monitor or rule. For more information about applying an
override, see Using Classes and Groups for Overrides in Operations Manager.
6. In the Override Properties dialog box, click to select the Override check box that
corresponds to the Enabled parameter.
Note
If you select Disable instead of Override, the Override Properties dialog box
opens with the Override check box selected and the Enabled value set to False.
7. In the Override Setting column, click True to enable the rule or monitor or False to
disable the rule or monitor.
8. In the Select destination management pack list, click the appropriate management
pack in which to store the override or create a new unsealed management pack by
clicking New. For more information about selecting a destination management pack, see
Creating a Management Pack for Overrides.
9. When you complete your changes, click OK.
See Also
Using Classes and Groups for Overrides in Operations Manager
How to Override a Rule or Monitor
Using the Enforced Attribute in Overrides
How to Enable Recovery and Diagnostic Tasks
When the Enforced attribute is selected for an override, this setting ensures that the override will
take precedence over all other overrides of the same type and context that do not have Enforced
set.
75
Overrides that apply to a class are applied first, then overrides that apply to a group, and finally
overrides that apply to a specific object. The Enforced attribute assures that the override will take
precedence when two overrides of the same type and context conflict.
For example, you have two Windows computers, COMPUTER1 and COMPUTER2.
COMPUTER1 is member of GROUP-A and is also member of GROUP-B. COMPUTER2 is not a
member of any group. The default threshold for a CPU monitor is 80%.
You apply an override to the Window Computer class that changes the CPU monitor threshold to
70%. You create another override to that monitor that applies to GROUP-A and sets the threshold
to 90%. At this point, the threshold for COMPUTER1 is 90% and the threshold for COMPUTER2
is 70%.
If you create an override that applies to GROUP-B and sets the threshold to 95%, the resulting
threshhold for COMPUTER1, which is member of both GROUP-A and GROUP-B, is
unpredictable. However, if you used the Enforced attribute on the override that appllies to
GROUP-B, you ensure that the 95% threshold applies to COMPUTER1.
If you create an override that applies to COMPUTER1 and sets the threshold to 60%, the
resulting threshhold for COMPUTER1 is 60% because the object override takes precedence over
the class and group overrides.
See Also
Using Classes and Groups for Overrides in Operations Manager
How to Override a Rule or Monitor
How to Enable or Disable a Rule or Monitor
How to Enable Recovery and Diagnostic Tasks
76
To enable a diagnostic or recovery task
1. In the Operations console, in the Authoring workspace, right-click a monitor and click
Properties.
2. Click the Diagnostic and Recovery tab.
3. On the Diagnostic and Recovery tab, in the Configure diagnostic tasks or Configure
recovery tasks section, ensure the desired task is selected and then click Edit.
4. On the Overrides tab, click Override. You can choose to override this monitor for objects
of a specific type or for all objects within a group. After you choose which group or object
type to override, the Override Properties dialog box opens. For more information about
applying an override, see Using Classes and Groups for Overrides in Operations
77
Manager.
5. In the Override-controlled parameters section, click Enabled and set the override
value to True.
6. Either select a management pack from the Select destination management pack list or
create a new unsealed management pack by clicking New. For more information about
selecting a destination management pack, see Creating a Management Pack for
Overrides.
7. Click OK. Close the open properties windows.
See Also
Diagnostic and Recovery Tasks
Using Classes and Groups for Overrides in Operations Manager
How to Override a Rule or Monitor
How to Enable or Disable a Rule or Monitor
Using the Enforced Attribute in Overrides
78
This section explains how to configure and manage access to computers running UNIX and
Linux operating systems.
Managing Run As Accounts and Profiles
Operations Manager workflows, such as rules, tasks, monitors, and discoveries, require
credentials to run on a targeted agent or computer. These credentials are configured by using
Run As profiles and Run As accounts. This section explains how to create, configure, and
manage Run As profiles and accounts.
Action Account
The action account is used to gather information about, and run responses on, the managed
computer (a managed computer being either a management server or a computer with an agent
installed). The MonitoringHost.exe processes run under the action account or a specific Run As
account. There might be more than one MonitoringHost.exe process running on the agent at any
given time.
Some of the actions that MonitoringHost.exe performs include:
Monitoring and collecting Windows event log data.
Monitoring and collecting Windows performance counter data.
Monitoring and collecting Windows Management Instrumentation (WMI) data.
79
Running actions such as scripts or batches.
The separation of the Health Service process from the single and multiple uses of the
MonitoringHost process means that if a script running on the managed computer stalls or fails,
the functionality of the Operations Manager service or other responses on the managed computer
will not be affected.
The action account can be managed through the Default action account located in Run As
Profiles in the Administration workspace.
Important
The minimum privileges described above are the lowest privileges that Operations
Manager supports for the Action account. Other Run As accounts can have lower
privileges. The actual privileges required for the Action account and the Run As accounts
will depend upon which management packs are running on the computer and how they
are configured. For more information about which specific privileges are required, see the
appropriate management pack guide.
Keep the following points in mind when choosing an credentials for the Management Server
Action Account:
A low-privileged account can be used only on computers running Windows Server 2003 and
Windows Vista. On computers running Windows 2000 and Windows XP, the action account
must be a member of the local Administrators security group or Local System.
Using a low-privileged domain account requires password updating consistent with your
password expiration policies.
You cannot enable Agentless Exception Monitoring (AEM) on a management server with a
low-privileged action account.
The Action account must be assigned the Manage Auditing and Security log privilege by
using Local or Global policy, if a management pack is to read the event in the Security Event
log.
80
the Operations Manager database from the action account and create a new separate Run As
Account for accessing the Operations Manager database.
See Also
Implementing User Roles
Managing Access in Operations Manager
How to Create a New Action Account in Operations Manager
How to Manage the Report Server Unattended Execution Account in Operations Manager
Control Access by Using the Health Service Lockdown Tool in Operations Manager
Accessing UNIX and Linux Computers in Operations Manager
Managing Run As Accounts and Profiles
81
monitoring data. All other users must have a user role assigned in order to view or act on
monitoring data.
User roles are created using the Create User Role Wizard. In this wizard, you configure which
Active Directory security groups are assigned this user role, which Operations Manager group or
groups of monitored objects this user can access, and which tasks and views this user role can
access.
A user role is the combination of a profile and scope as shown in as shown in the following
illustration. A user can be a part of multiple roles and the resultant scope is the union of all the
user roles.
82
Implementing User Roles topics
Choose a Profile
Define a Scope Using Operations Manager Groups
Assign Tasks and Views
How to Assign Members to User Roles
Operations Associated with User Role Profiles
See Also
Managing Access in Operations Manager
Operations Manager Accounts
How to Create a New Action Account in Operations Manager
How to Manage the Report Server Unattended Execution Account in Operations Manager
Control Access by Using the Health Service Lockdown Tool in Operations Manager
Accessing UNIX and Linux Computers in Operations Manager
Managing Run As Accounts and Profiles
Choose a Profile
Before you start the Create User Role Wizard, select one profile that applies to the user role you
are creating. A profile determines the actions that a user can perform. Profiles have a defined set
of rights and you cannot add or remove any of these assigned rights. When creating user roles
for operators and other users, select the profile that most closely matches the responsibilities of
the group of users in your System Center 2012 – Operations Manager deployment.
Operations Manager can monitor many types of applications in the enterprise. As the Operations
Manager administrator, you want to limit access to monitoring data. Role-based security allows
you to limit privileges that users have for various aspects of Operations Manager.
Important
Adding a machine account to a user role member allows all services on that computer to
have software development kit (SDK) access. It is recommended that you do not add a
machine account to any user role.
In Operations Manager, operations—such as resolving alerts, running tasks, overriding monitors,
creating user roles, viewing alerts, viewing events, and so on—have been grouped into profiles,
with each profile representing a particular job function as shown in the following table. For a list of
83
specific operations associated with each profile, see Operations Associated with User Role
Profiles.
Note
A scope defines the entity groups, object types, tasks, or views that a profile is restricted
to. Not all scopes apply to all profiles.
Note
Access to the Application Advisor
feature requires the Report Operator or
Administrator profile.
84
Profile Job Functions and Scope
Security
When a dashboard view uses data
from the data warehouse database,
operators might be able to view data
that they would not otherwise have
access to in views that use data from
the operational database.
Note
Members of the Read-only Operator
role are not assigned rights to the Task
Status view.
Security
When a dashboard view uses data
from the data warehouse database,
operators might be able to view data
that they would not otherwise have
access to in views that use data from
the operational database.
Caution
Users assigned to this role have
access to all report data in the
Reporting Data Warehouse and are not
limited by scope.
85
Profile Job Functions and Scope
See Also
Implementing User Roles
Define a Scope Using Operations Manager Groups
Assign Tasks and Views
How to Assign Members to User Roles
Operations Associated with User Role Profiles
See Also
Implementing User Roles
Choose a Profile
Assign Tasks and Views
How to Assign Members to User Roles
86
See Also
Implementing User Roles
Choose a Profile
Define a Scope Using Operations Manager Groups
How to Assign Members to User Roles
Important
When you add a group to the Operations Manager Administrators user role, you must
restart the management server for the change to take effect.
Note
You can only add Active Directory
security groups to the Administrator
role.
87
User role Description
Security
When a dashboard view uses data
from the data warehouse database,
operators might be able to view data
that they would not otherwise have
access to in views that use data from
the operational database.
Security
When a dashboard view uses data
from the data warehouse database,
operators might be able to view data
that they would not otherwise have
access to in views that use data from
the operational database.
88
See Also
Implementing User Roles
Choose a Profile
Define a Scope Using Operations Manager Groups
Assign Tasks and Views
Report Operator
The Report Operator profile includes a set of privileges designed for users who need access to
reports. A role based on the Report Operator profile grants members the ability to view reports
according to their configured scope.
Retrieve the instance of the data warehouse for the management group
Write to favorite reports
Delete favorite reports
Read favorite reports
Update favorite reports
Read reports
Run reports
Access Application Advisor
Read-Only Operator
The Read-Only Operator profile includes a set of privileges designed for users who need read-
only access to alerts and views. A role based on the Read-Only Operators profile grants members
the ability to view alerts and access views according to their configured scope.
Read alerts
Retrieve the instance of the data warehouse for the management group
Read state of a resolution
Read instance of a connector
Read console tasks
Enumerate diagnostic objects
Enumerate the results of diagnostics
Enumerate discovery objects as defined in a management pack
Read discovery rules
Read events
Write to favorite console tasks
Delete favorite console tasks
89
Enumerate favorite console tasks
Update favorite console tasks
Write favorite views
Delete favorite views
Enumerate favorite views
Update favorite views
Enumerate monitoring objects
Enumerate monitoring classes
Enumerate monitoring relationship classes
Enumerate management packs
Enumerate monitor types
Enumerate module types
Enumerate monitors
Enumerate overrides
Enumerate performance data
Enumerate discovery objects as defined in a management pack
Enumerate the status of past recoveries
Enumerate relationship between monitored objects
Enumerate rules
Enumerate saved searches
Update saved searches
Write to saved searches
Delete saved searches
Enumerate state
Allows access to connected management groups
Enumerate views
Enumerate view types
Review application monitoring alerts1
1
Permissions scope can be fine-tuned for the role.
Operator
The Operator profile includes a set of privileges designed for users who need access to alerts,
views, and tasks. A role based on the Operators profile grants members the ability to interact with
alerts, run tasks, and access views according to their configured scope. The Operator profile
contains all of the privileges found in the Read-Only Operator profile in addition to those listed
below.
Update alerts
Run diagnostics
Create favorite tasks
90
Note
Delete favorite tasks
Enumerate favorite tasks
Update favorite tasks
Run recovery routines
Update maintenance mode settings
Enumerate notification actions
Delete notification actions
Update notification actions
Enumerate notification endpoints
Enumerate notification recipients
Delete notification recipients
Update notification recipients
Enumerate notification subscriptions
Delete notification subscriptions
Update notification subscriptions
Enumerate tasks
Enumerate task status
Run tasks
Run monitoring compatibility check task1
Additional permissions are required for files/folders to create report files.
Review application monitoring alerts1
Close application monitoring alerts1
1
Permissions scope can be fine-tuned for the role.
Advanced Operator
The Advanced Operator profile includes a set of privileges designed for users who need access
to limited tweaking of monitoring configurations in addition to the Operators privileges. A role
based on the Advanced Operators profile grants members the ability to override the configuration
of rules and monitors for specific targets or groups of targets within the configured scope. The
Advanced Operator profile contains all of the privileges found in the Operator and Read-Only
Operator profiles in addition to those listed below.
Update management packs
Enumerate templates
Customize APM configuration with the overrides1
Run monitoring compatibility check task1
Additional permissions are required for files/folders to create report files.
Review application monitoring alerts1
Close application monitoring alerts1
91
Note
1
Permissions scope can be fine-tuned for the role.
Author
The Author profile includes a set of privileges designed for authoring monitoring configurations. A
role based on the Authors profile grants members the ability to create, edit, and delete monitoring
configuration (tasks, rules, monitors, and views) within the configured scope. For convenience,
Authors can also be configured to have Advanced Operator privileges scoped by group. The
Author profile contains all of the privileges found in the Advanced Operator, Operator, and Read-
Only Operator profiles in addition to those listed below.
Create management packs
Delete management packs
Enumerate Run As Profiles
Customize APM configuration with the overrides1
Author new APM workflows1
Run monitoring compatibility check task1
Additional permissions are required for files/folders to create report files.
Review application monitoring alerts1
Close application monitoring alerts1
1
Permissions scope can be fine-tuned for the role.
Administrator
The Administrator profile includes full privileges to Operations Manager. No scoping of the
Administrator profile is supported. The Administrator profile contains all of the privileges found in
the Author, Advanced Operator, Operator, and Read-Only Operator profiles in addition to those
listed below.
Create a resolution state
Delete a resolution state
Update a resolution state
Deploy an agent
Repair or update an installed agent
Uninstall an agent
Enumerate agent settings
92
Update agent settings
Enumerate agents
Start or stop managing computers or devices via a proxy health service
Enumerate computers or devices managed via a proxy health service
Insert a new instance of a computer or device
Delete an instance of a computer or device
Run discovery task
Create events
Enumerate global settings
Update global settings
Export management packs
Enumerate management servers
Delete notification endpoint
Update notification endpoint
Create performance data
Create Run As Accounts
Delete Run As Accounts
Enumerate Run As Accounts
Update Run As Accounts
Create mappings between Run As Accounts and Run As Profiles
Delete mappings between Run As Accounts and Run As Profiles
Enumerate mappings between Run As Accounts and Run As Profiles
Update mappings between Run As Accounts and Run As Profiles
Create connected management groups
Delete connected management groups
Enumerate user roles
Delete user roles
Update user roles
Write favorite reports
Delete favorite reports
Read favorite reports
Update favorite reports
Read reports
Run reports
Run APM Wizard or change APM settings
Access Application Diagnostics
Access Application Advisor
Author new APM workflows
93
Customize APM configuration with the overrides
Run monitoring compatibility check task
Review application monitoring alerts
Close application monitoring alerts
Control access rights to application monitoring
See Also
Implementing User Roles
Define a Scope Using Operations Manager Groups
Assign Tasks and Views
How to Assign Members to User Roles
Choose a Profile
94
Note
The display name you enter here becomes the Run As account you will add
to a new Run As profile in the following procedure.
c. You can also type a description in the Description text box.
d. Click Next.
6. On the Account page, type a user name, password, and then select the domain for the
account that you want to make a member of this Run As account, and then click Next.
7. On the Distribution Security page, the More secure option is selected and cannot be
changed. Click Create.
8. In the Administration workspace, click Run As Profiles.
9. In Run As Profiles, right-click Default Action Account, and then click Properties.
10. On the Introduction and General Properties pages, click Next.
11. On the Run As Accounts page, click Add, select the Run As account you created, and
then click OK twice.
12. Click Save.
See Also
Managing Access in Operations Manager
Operations Manager Accounts
Implementing User Roles
How to Manage the Report Server Unattended Execution Account in Operations Manager
Control Access by Using the Health Service Lockdown Tool in Operations Manager
Accessing UNIX and Linux Computers in Operations Manager
Managing Run As Accounts and Profiles
95
3. In the navigation pane, click Execution Account.
4. In the Execution Account pane, type a new user name or password as required.
5. Click Apply, and then click Exit.
See Also
Managing Access in Operations Manager
Operations Manager Accounts
Implementing User Roles
How to Create a New Action Account in Operations Manager
Control Access by Using the Health Service Lockdown Tool in Operations Manager
Accessing UNIX and Linux Computers in Operations Manager
Managing Run As Accounts and Profiles
Note
You will be unable to start the System Center Management service if you have used the
Health Service Lockdown tool to lock out the Action Account. To be able to restart the
System Center Management service, follow the second procedure in this topic to unlock
the Action Account.
The following command-line options are available:
HSLockdown [ManagementGroupName] /L - List Accounts/groups
HSLockdown [ManagementGroupName] /A - Add an allowed account|group
HSLockdown [ManagementGroupName] /D - Add a denied account|group
HSLockdown [ManagementGroupName] /R - Remove an allowed/denied account|group
Accounts must be specified in one of the following fully qualified domain name (FQDN) formats:
NetBios : DOMAIN\username
UPN : [email protected]
If you used the add or deny options when running the Health Service Lockdown tool, you will
need to restart the System Center Management service before the changes take effect.
When evaluating allowed and denied listings, know that denies takes priority over allows. If a user
is listed as allowed, and the same user is a member of a group that is listed as denied, the user
will be denied.
96
1. Log on to the computer with an account that is a member of the Administrators group.
2. On the Windows desktop, click Start, and then click Run.
3. In the Run dialog box, type cmd and then click OK.
4. At the command prompt, type <drive_letter>: (where <drive_letter> is the drive where the
Operations Manager installation media is located) and then press ENTER.
5. Type cd\Program Files\System Center Operations Manager 2012\Server and then
press ENTER.
6. Type HSLockdown [Management Group Name] /D [account or group] to deny the
group or account, and then press ENTER.
See Also
Managing Access in Operations Manager
Operations Manager Accounts
Implementing User Roles
How to Create a New Action Account in Operations Manager
How to Manage the Report Server Unattended Execution Account in Operations Manager
Accessing UNIX and Linux Computers in Operations Manager
Managing Run As Accounts and Profiles
97
Web Services for Management (WS-Management)
Used for all monitoring operations and include the discovery of agents that were already
installed.
The protocol that is used depends on the action or information that is requested on the
management server. All actions, such as agent maintenance, monitors, rules, tasks, and
recoveries, are configured to use predefined profiles according to their requirement for an
unprivileged or privileged account.
Note
All credentials referred to in this topic pertain to accounts that have been established on
the UNIX or Linux computer, not to the Operations Manager accounts that are configured
during the installation of Operations Manager. Contact your system administrator for
credentials and authentication information.
For detailed instructions for specifying credentials and configuring accounts, see How to Set
Credentials for Accessing UNIX and Linux Computers.
98
Other Resources for this Feature
Managing Access in Operations Manager
Credentials You Must Have to Access UNIX and Linux Computers
Implementing User Roles
How to Create a New Action Account in Operations Manager
How to Manage the Report Server Unattended Execution Account in Operations Manager
Control Access by Using the Health Service Lockdown Tool in Operations Manager
Managing Run As Accounts and Profiles
The installation is not completed until the agent is verified. Agent verification is performed by the
WS-Management protocol that uses credentials maintained on the management server, separate
from the privileged account that is used to install the agent. You are required to provide a user
name and password for agent verification if you have done one of the following:
Provided a privileged account by using a key.
Provided an unprivileged account to be elevated by using sudo with a key.
Ran the wizard with the Discovery Type set to Discover only computers with the
UNIX/Linux agent installed.
Alternatively, you can install the agent, including its certificate, manually on the UNIX or Linux
computer and then discover that computer. This method is the most secure way to install agents.
For more information, see Install Agent and Certificate on UNIX and Linux Computers Using the
Command Line.
99
Credentials for Monitoring Operations and Performing Agent Maintenance
Operations Manager contains three predefined profiles to use in monitoring UNIX and Linux
computers and performing agent maintenance:
UNIX/Linux action account
This profile is an unprivileged account profile that is required for basic health and
performance monitoring.
UNIX/Linux privileged account
This profile is a privileged account profile used for monitoring protected resources such as log
files.
UNIX/Linux maintenance account
This profile is used for privileged maintenance operations, such as updating and removing
agents.
In the UNIX and Linux management packs, all the rules, monitors, tasks, recoveries, and other
management pack elements are configured to use these profiles. Consequently, there is no
requirement to define additional profiles by using the Run As Profiles Wizard unless special
circumstances dictate it. The profiles are not cumulative in the scope. For example, the
UNIX/Linux maintenance account profile cannot be used in place of the other profiles simply
because it is configured by using a privileged account.
In Operations Manager, a profile cannot function until it is associated with at least one Run As
account. The credentials for accessing the UNIX or Linux computers are configured in the Run As
accounts. Because there are no predefined Run As accounts for UNIX and Linux monitoring, you
must create them.
To create a Run As account, you must run the UNIX/Linux Run As Account Wizard that is
available when you select UNIX/Linux Accounts in the Administration workspace. The wizard
creates a Run As account based on the choice of a Run As account type. There are two Run As
account types:
Monitoring account
Use this account for ongoing health and performance monitoring in operations that
communicate by using WS-Management.
Agent maintenance account
Use this account for agent maintenance such as updating and uninstalling in operations that
communicate by using SSH.
These Run As account types can be configured for different levels of access according to the
credentials that you supply. Credentials can be unprivileged or privileged accounts or unprivileged
accounts that will be elevated to privileged accounts. The following table shows the relationships
between profiles, Run As accounts, and levels of access.
100
Profiles Run As account type Allowable Access Levels
Privileged
Unprivileged, elevated to
privileged
Note that there are three profiles, but only two Run As Account types.
When you specify a Monitoring Run As Account Type, you must specify a user name and
password for use by the WS-Management protocol. When you specify an Agent Maintenance
Run As Account Type, you must specify how the credentials are supplied to the targeted
computer by using the SSH protocol:
Specify a user name and a password.
Specify a user name and a key. You can include an optional passphrase.
After you created the Run As accounts, you must edit the UNIX and Linux profiles to associate
them with the Run As accounts you created. For detailed instructions, see How to Configure Run
As Accounts and Profiles for UNIX and Linux Access.
101
elevation requires a password. If you use sudo elevation, you are prompted for a user name
and password for agent verification by using an unprivileged account.
For more information about upgrading and uninstalling, see Upgrading and Uninstalling Agents on
UNIX and Linux Computers.
See Also
How to Set Credentials for Accessing UNIX and Linux Computers
Accessing UNIX and Linux Computers in Operations Manager
How to Configure sudo Elevation and SSH Keys
Required Capabilities for UNIX and Linux Accounts
Configuring SSL Ciphers
To set a user (unprivileged) account for discovery of an installed agent with a signed
certificate.
1. On the Credential Settings page, click the Default Credentials tab, and then click the
Password option.
2. Type a user name, a password, and the password confirmation.
3. In the Does this account have privileged access list, click This account does not
have privileged access, and then click OK.
4. Click OK to return to the Discovery Criteria page and continue with the wizard.
102
To set a privileged credential by using an SSH key
1. On the Credential Settings page, click the Default Credentials tab, and then click the
SSH key option.
2. Type a user name, the path, and name of the key, or click Browse.
3. Enter a passphrase if the key requires it.
4. In the Does this account have privileged access list, click This account has
privileged access, and then click OK.
5. Click the Agent Verification tab, and on the Agent Verification page, type a user name
and password for an account on the targeted computer. This can be a user (unprivileged)
account.
6. Click OK to return to the Discovery Criteria page and continue with the wizard.
103
3. In the Does this account have privileged access list, click This account does not
privileged access, and then click OK.
4. Click the Elevation page, and select su or sudo elevation.
If you select su elevation, type the superuser password you established on the UNIX or
Linux computer.
5. Click OK to return to the Discovery Criteria page and continue with the wizard.
104
To set an unprivileged credential by using an SSH key with elevation for an agent
maintenance account
1. On the Account Credentials page, click the SSH key option.
2. Type a user name, the path, and name of the key, or click Browse.
3. Enter a passphrase if the key requires it.
4. In the Does this account have privileged access list, click This account does not
have privileged access, and then click Next.
5. Select the Elevation tab, and select su or sudo elevation.
If you select su elevation, type the superuser password as established on the UNIX or
Linux computer.
6. Click Next to continue with the wizard.
105
4. In the Does this account have privileged access list, click This account has
privileged access, and then click OK.
5. On the Agent Verification page, type a user name and password for an account on the
targeted computer. This can be a user (unprivileged) account.
6. Click OK to return to the Credentials page and continue with the wizard.
106
Credentials for Uninstalling an Agent
The following procedures begin in the UNIX/Linux Agent Uninstall Wizard, on the Credentials
page, when you select Provide Uninstall Credentials. For more information, see, Upgrading
and Uninstalling Agents on UNIX and Linux Computers.
107
This password is used for agent verification.
3. In the Does this account have privileged access list, click This account does not
privileged access, and then click OK.
4. On the Elevation page, select su or sudo elevation.
If you select su elevation, type the superuser password as established on the UNIX or
Linux computer.
5. Click OK to return to the Credentials page and continue with the wizard.
See Also
Credentials You Must Have to Access UNIX and Linux Computers
Accessing UNIX and Linux Computers in Operations Manager
How to Configure sudo Elevation and SSH Keys
Required Capabilities for UNIX and Linux Accounts
Configuring SSL Ciphers
Note
The sudo program exists at different locations on UNIX and Linux operating systems. To
provide uniform access to sudo, the UNIX and Linux agent installation script creates the
symbolic link /etc/opt/microsoft/scx/conf/sudodir to point to the directory expected to
contain the sudo program. The agent uses this symbolic link to invoke sudo. The
installation script automatically creates the symbolic link, so you do not need to take any
action on standard UNIX and Linux configurations; however, if you have sudo installed at
108
a non-standard location, you should change the symbolic link to point to the directory
where sudo is installed. If you change the symbolic link, its value is preserved across
uninstall, re-install, and upgrade operations with the agent.
You can now configure sudo elevation and create an SSH key for opsuser, as described in the
following procedures.
1. Log on to the UNIX or Linux computer as root.
2. Use the visudo program to edit the sudo configuration in a vi text editor. Run the following
command:
visudo
5. TTY allocation is not supported. Ensure the following line is commented out:
Important
This step is required for sudo to work.
6. Save the file and exit visudo:
Press ESC + : (colon) followed by wq!, and then press Enter.
7. Test the configuration by entering in the following two commands. The result should be a
listing of the directory without being prompted for a password:
su - opsuser
sudo ls /etc
You can use the opsuser account by using the password and sudo elevation for specifying
credentials in Operations Manager wizards and for configuring Run As accounts.
109
Create an SSH Key for Authentication
The following procedures create an SSH key for the opsuser account that was created in the
previous examples.
5. Give the user read and write permissions to the authorized keys file:
chmod 600 authorized_keys
You can now copy the private SSH key to the Windows-based computer, as described in the
next procedure.
To copy the private SSH key to the Windows-based computer and save in OpenSSH
format
1. Use a tool, such as WinSCP, to transfer the private key file (id_dsa – with no extension)
from the UNIX or Linux computer to a directory on your Windows-based computer.
2. Run PuTTYgen.
3. In the PuTTY Key Generator dialog box, click the Load button, and then select the
private key (id_dsa) that you transferred from the UNIX or Linux computer.
4. Click Save private key and name and save the file to the desired directory.
You can use the opsuser account by using the SSH key and sudo elevation for specifying
credentials in Operations Manager wizards and for configuring Run As accounts.
110
See Also
How to Set Credentials for Accessing UNIX and Linux Computers
Accessing UNIX and Linux Computers in Operations Manager
Credentials You Must Have to Access UNIX and Linux Computers
Required Capabilities for UNIX and Linux Accounts
Configuring SSL Ciphers
Note
The following table describes the required capabilities for accounts to communicate with
the Operations Manager agent on a managed UNIX or Linux computer, but the agent
itself must always run under the root account on the UNIX or Linux computer.
111
UNIX and Linux profile Required capabilities
112
UNIX and Linux profile Required capabilities
Agent maintenance profile, and for accounts To log the UNIX or Linux computer on to the
used to install agents for initial monitoring. network by using Secure Shell (SSH),
authenticated by the PAM. Must have the
ability to run a background shell (not
connected to a TTY). Interactive logons are
not required. In the case of an account that
is elevated by using sudo, this requirement
applies to the account before it is elevated.
To run the system package installation
program, such as rpm on Linux, to install
the Operations Manager agent.
To read and write the following directories,
and to create them and any subdirectories
under them if they do not exist:
/opt
/opt/microsoft
/opt/microsoft/scx
/etc/opt/microsoft/scx
/var/opt/microsoft/scx
To run the kill command against the
running Operations Manager agent
processes.
To start the Operations Manager agent.
To add and remove a system daemon,
including the Operations Manager agent, by
using platform tools to do so.
To run basic UNIX and Linux commands,
such as cat, ls, pwd, cp, mv, rm, gzip (or
equivalent).
113
See Also
How to Set Credentials for Accessing UNIX and Linux Computers
Accessing UNIX and Linux Computers in Operations Manager
How to Configure sudo Elevation and SSH Keys
Credentials You Must Have to Access UNIX and Linux Computers
Configuring SSL Ciphers
To set the sslCipherSuite configuration option, the following syntax shows a typical command.
scxcimconfig –s sslCipherSuite=’<cipher spec>’ –p
where <cipher spec> specifies the ciphers that are allowed, disallowed, and the order in which
allowed ciphers are chosen.
The format for <cipher spec> is the same as the format for the sslCipherSuite option in the
Apache HTTP Server version 2.0. For detailed information, see SSLCipherSuite Directive in the
Apache documentation. All information on this site is provided by the owner or the users of the
website. Microsoft makes no warranties, express, implied or statutory, as to the information at this
website.
After setting the sslCipherSuite configuration option, you must restart the UNIX and Linux agent
for the change to take effect. To restart the UNIX and Linux agent, run the following command,
also located in the /etc/opt/microsoft/scx/bin/tools directory.
scxadmin -restart
See Also
How to Set Credentials for Accessing UNIX and Linux Computers
Accessing UNIX and Linux Computers in Operations Manager
How to Configure sudo Elevation and SSH Keys
Required Capabilities for UNIX and Linux Accounts
Credentials You Must Have to Access UNIX and Linux Computers
115
In the image, three workflows use the same Run As profile. The Run As profile has three
associated Run As accounts. In this example, each workflow that uses the Run As profile will run
on Computer A using the credentials for Run As account 1, on Computer B and C using the
credentials for Run As account 2, and on Computer D using the credentials for Run As account 3.
Run As profiles are defined in management packs by the management pack author. A Run As
profile is used wherever its parent management pack is active. For example, the SQL
Server 2005 management pack contains the SQL Run As profile, so the SQL Run As profile
would be active on all servers running SQL Server 2005 that are monitored by the SQL
Server 2005 management pack. The Run As profile is an association of one or more Run As
accounts and the managed objects that the Run As accounts should be applied to.
In some cases, the Run As profile is imported into Operations Manager when the management
pack that contains it is imported. In other cases, you may need to create it manually. In all cases,
Run As profiles must be manually associated with a Run As account.
A Run As account contains a single set of credentials which are stored in the Operations
Manager operational database. Each Run As account has a security classification (more secure
or less secure) that controls how the credentials are distributed for use. If you elect more secure
credential distribution, you must configure the mapping of which computers the credentials are
distributed to.
116
This topic explains how to create a Run As account that can access the operational database.
How to Configure Run As Accounts and Profiles for UNIX and Linux Access
This topic explains the Run As accounts you must create to monitor UNIX and Linux
computers.
Distribution is an attribute of a Run As account in which you specify which computers will receive
the Run As account credentials. You can choose to distribute the Run As account credentials to
every agent-managed computer or only to selected computers.
Example of Run As account targeting and distribution:
117
Physical computer ABC hosts two instances of Microsoft SQL Server, instance X and instance Y.
Each instance uses a different set of credentials for the sa account. You create a Run As account
with the sa credentials for instance X, and a different Run As account with the sa credentials for
instance Y. When you configure the SQL Server Run As profile, you associate both Run As
account credentials for instance X and Y with the profile and specify that the Run As account
instance X credentials are to be used for SQL Server instance X and that the Run As account Y
credentials are to be used for SQL Server instance Y. Then, you configure both Run As accounts
to be distributed to physical computer ABC.
Note
The Run As account credentials must be distributed to…
118
Note
Operations Manager will perform tests to validate the Run As credentials, including
whether the credentials can be used to log on locally to the computer. If the account does
not have the right to log on locally, an alert will be generated.
See Also
Managing Run As Accounts and Profiles
How to Create a Run As Account
How to Associate a Run As Account to a Run As Profile
How to Create a New Run As Account for Accessing the Operations Manager Database
How to Configure Run As Accounts and Profiles for UNIX and Linux Access
119
7. Click Next.
8. On the Distribution Security page, select the Less secure or More secure option as
appropriate. For more information, see Distribution and Targeting for Run As Accounts
and Profiles.
9. Click Create.
10. On the Run As Account Creation Progress page, click Close.
See Also
Managing Run As Accounts and Profiles
Distribution and Targeting for Run As Accounts and Profiles
How to Associate a Run As Account to a Run As Profile
How to Create a New Run As Account for Accessing the Operations Manager Database
How to Configure Run As Accounts and Profiles for UNIX and Linux Access
120
How to Associate a Run As Account to a Run As Profile
In System Center 2012 – Operations Manager, Run As accounts are associated with Run As
profiles to provide the necessary credentials for workflows that use that Run As profile to run
successfully. Both distribution and targeting of Run As accounts must be correctly configured for
the Run As profile to work properly.
1. Identify the class, group, or objects the Run As account will be applied to. For more
information, see Distribution and Targeting for Run As Accounts and Profiles.
2. Create the Run As account. For more information, see How to Create a Run As Account.
3. Associate the Run As account with the Run As profile.
4. Configure the distribution of Run As account object credentials to specific computers.
This procedure can be used for creating and configuring a new Run As profile, or you can use the
configuring section to modify or configure Run As profiles that are pre-existing in your
management group. This procedure assumes that you have not previously created a Run As
account.
1. Log on to the Operations console with an account that is a member of the Operations
Manager Administrators role.
2. In the Operations console, click Administration.
3. In the Administration workspace, click Profiles.
4. In the results pane, double-click the Run As profile that you want to configure. The Run
As Profile Wizard opens.
5. In the left pane, click Run As Accounts.
6. On the Run As Accounts page, click Add.
7. In the Add a Run As Account window, in the Run As account field, select an existing
Run As account from the dropdown menu. You can also create an account by clicking
New and following the steps in the How to Create a Run As Account topic.
8. Select All targeted objects or A selected class, group, or object. If you select A
selected class, group, or object, click Select, and then locate and select the class,
group, or object that you want the Run As account to be used for. For more information,
see Distribution and Targeting for Run As Accounts and Profiles.
9. Click OK to close the Add a Run As Account window.
121
1. Open the properties for the Run As account using one of the following methods:
On the Run As Profile Wizard Completion page, click the account link.
In the Operations console, in the Administration workspace, under Run As
Configuration, click Accounts, and then in the results pane, double-click the
account you want to configure.
2. On the Distribution tab, click Add for the Selected computers box and do the following:
a. Select Search by computer name (Default) or Show suggested computers, or
Show management servers.
b. Optionally type in a value in the Filter by: (Optional) box.
c. Click Search. The result set is returned in the Available items box.
d. Select the computers you want from the result set, and click Add. This adds the
selected computers to the Selected objects box.
e. Click OK.
3. Click OK.
See Also
Managing Run As Accounts and Profiles
How to Create a Run As Account
Distribution and Targeting for Run As Accounts and Profiles
How to Create a New Run As Account for Accessing the Operations Manager Database
How to Configure Run As Accounts and Profiles for UNIX and Linux Access
To create a new Run As account for accessing the Operations Manager database
1. Log on to the computer with an account that is a member of the Operations Manager
Administrators role.
2. In the Operations console, click Administration.
3. In the Administration workspace, right-click Run As Accounts, and then click Create
Run As Account .
4. In the Create Run As Account Wizard, on the Introduction page, click Next.
5. On the General page, do the following:
a. Select Windows in the Run As Account type list.
b. Type a display name in the Display Name text box.
Note
The display name you enter here becomes the Run As account you will add
122
to a new Run As profile in the following procedure.
c. You can also type a description in the Description text box.
d. Click Next.
6. On the Account page, type a user name, password, and then select the domain for the
account that you want to make a member of this Run As account, and then click Create.
To assign the new Run As account to the Operational Database Account Run As
profile
1. In the Administration workspace, under Run As Configuration, click Profiles.
2. In the Profiles list, right-click Operational Database Account, and then click
Properties.
3. On the Introduction and General Properties pages, click Next.
4. Under Run As accounts, click Add.
5. In the Add a Run As Account dialog box, click the Run As Account dropdown menu,
click the Run As account you created in the previous procedure, and then click OK.
6. Click Save.
123
text box, and then click the ellipses (…) next to the Login name option.
5. In the Select Login dialog box, click Browse.
6. In the Browse for Objects dialog box, click the check box next to the new login, and
then click OK.
7. In the Database User - New dialog box, in the Database role membership list, select
dbmodule_users, and then click OK.
See Also
Managing Run As Accounts and Profiles
How to Create a Run As Account
Distribution and Targeting for Run As Accounts and Profiles
How to Associate a Run As Account to a Run As Profile
How to Configure Run As Accounts and Profiles for UNIX and Linux Access
How to Configure Run As Accounts and Profiles for UNIX and Linux Access
If you are the system administrator in charge of the monitoring of UNIX and Linux computers, you
must create Run As accounts for agent maintenance operations, and for health and performance
monitoring. These Run As accounts must then be associated with the Run As profiles defined in
the UNIX and Linux management packs, so they can access the agents on UNIX and Linux
computers. For an overview of the process, see Accessing UNIX and Linux Computers in
Operations Manager.
124
Username and password for privileged access to the UNIX or Linux computer. If you prefer
not to provide credentials for a privileged account, you can use unprivileged credentials and
have the credentials on the UNIX or Linux computer elevated.
You can choose between su or sudo elevation. If the account is to be elevated using ‘su’, you
will need the ‘su’ password.
Note
There is no need to run the Create Run As Profile Wizard unless you have authored a
new management pack that requires it.
125
profiles:
UNIX/Linux Action Account
UNIX/Linux Privileged Account
UNIX/Linux Agent Maintenance Account
4. In the Run As Profile wizard, click Next until you get to the Run As Accounts page.
5. On the Run As Accounts page, click Add to add a Run As account that you created.
Select the class, group, or object that will be accessed using the credentials in the Run
As account.
6. Click Save.
Repeat as needed until all three profiles have been configured with one or more Run As
accounts.
See Also
Managing Run As Accounts and Profiles
How to Create a Run As Account
Distribution and Targeting for Run As Accounts and Profiles
How to Create a New Run As Account for Accessing the Operations Manager Database
How to Associate a Run As Account to a Run As Profile
Important
Agentless management of a computer will not work if the agentless-managed computer
and its proxy communicate through a firewall. A management server will not collect
descriptions for events or publishers that are present on an agentless managed computer
but are not present on the proxy agent.
For information about configuring an agent-managed computer as a proxy for agentless-managed
computers, see How to Configure a Proxy for Agentless Monitoring.
Important
An agentless-managed computer places greater resource requirements on a
management server than an agent-managed computer.
To change an agentless-managed computer to an agent-managed computer, do the following:
1. Delete the agentless-managed computer from the management group by right-clicking the
computer in Agentless Managed in the Administration workspace and then clicking Delete.
2. Deploy the agent to the computer. For more information, see Managing Discovery and
Agents.
127
Windows Error Reporting service. For information on AEM, see Client Monitoring Using Agentless
Exception Monitoring in Operations Manager.
You can monitor a computer without an agent by using either agentless monitoring, AEM, or both.
See Also
How to Configure a Computer for Agentless Management
How to Configure a Proxy for Agentless Monitoring
128
3. At the bottom of the navigation pane, click Discovery Wizard.
4. On the Discovery Type page, click Windows computers.
5. On the Auto or Advanced? page, do the following:
a. Select either Automatic computer discovery or Advanced discovery. Automatic
computer discovery scans for Windows-based computers in the domain. Advanced
discovery allows you to specify criteria for the computers that the wizard will return,
such as computer names starting with NY. If you select Automatic computer
discovery, click Next, and then go to step 7. If you select Advanced discovery,
continue with the following steps.
b. In the Computer and Device Classes list, select Servers and Clients, Servers
Only, or Clients Only.
c. In the Management Server list, click the management server or gateway server to
discover the computers.
d. If you selected Servers and Clients, you can select the Verify discovered
computers can be contacted check box. This is likely to increase the success rate
of agent deployment, but discovery can take longer.
Note
If the Active Directory catalog does not contain the NetBIOS names for
computers in a domain, select Verify discovered computers can be
contacted. Otherwise, the Browse, or Type In option fails to find computers.
This affects computers in the same domain as the management server, in
another domain with a full trust relationship, and in untrusted domains by
using a gateway server.
e. Click Next.
Note
The wizard can return approximately 4000 computers if Verify discovered
computers can be contacted is selected, and it can return 10,000 computers if
this option is not selected. Automatic computer discovery verifies that discovered
computers can be contacted. A computer that is already managed by the
management group is not returned.
6. On the Discovery Method page, you can locate the computers that you want to manage
by either scanning or browsing Active Directory Domain Services or typing the computer
names.
If you want to scan, do the following:
a. If it is not already selected, select Scan Active Directory and then click Configure.
b. In the Find Computers dialog box, type the criteria that you want to use for
discovering computers, and then click OK.
c. In the Domain list, click the domain of the computers that you want to discover.
129
If you want to browse Active Directory Domain Services or type the computer names, do
the following:
Select Browse for, or type-in computer names, click Browse, specify the names of
the computers that you want to manage, and then click OK.
In the Browse for, or type-in computer names box, type the computer names,
separated by a semi-colon, comma, or a new line. You can use NetBIOS computer
names or fully qualified domain names (FQDN).
7. Click Next, and on the Administrator Account page, do one of the following:
Select Use selected Management Server Action Account if it is not already
selected.
Select Other user account, type the User name and Password, and then select the
Domain from the list. If the user name is not a domain account, select This is a local
computer account, not a domain account.
Important
The account must have administrative privileges on the targeted computers.
If This is a local computer account, not a domain account is selected, the
management server action account will be used to perform discovery.
8. Click Discover to display the Discovery Progress page. The time it takes discovery to
finish depends on many factors, such as the criteria specified and the configuration of the
environment.
Note
Computers that are already managed by the management group will not be
returned by the wizard.
9. On the Select Objects to Manage page, do the following:
a. Select the computers that you want to be agent-managed computers.
b. In the Management Mode list, click Agentless and then click Next.
c. Click Change, select the proxy agent that you want to use, click OK, and then click
Next.
10. On the Summary page, do the following:
a. Leave the Agent installation directory set to the default of %ProgramFiles%\
System Center Operations Manager or type an installation path.
Important
If a different Agent installation directory is specified, the root of the path
must exist on the targeted computer or the agent installation fails.
Subdirectories, such as \Agent, are created if they do not exist.
b. Leave Agent Action Account set to the default, Local System, or select Other and
type the User name, Password, and Domain. The Agent Action Account is the
default account that the agent will use to perform actions.
c. Click Finish.
11. In the Agent Management Task Status dialog box, the Status for each selected
130
computer changes from Queued to Success; the computers are ready to be managed.
Note
If the task fails for a computer, click the targeted computer. The reason for the
failure is displayed in the Task Output text box.
12. Click Close. The computers will be listed in the Administration workspace in Agentless
Managed.
See Also
Agentless Monitoring in Operations Manager
How to Configure a Proxy for Agentless Monitoring
Note
Not all management packs support agentless management, so make sure agentless
management will serve your needs before using it. For example, the Active Directory and
Microsoft Exchange Server 2003 management packs do not support agentless
management.
When you set up agentless monitoring of a computer, you select a proxy for each agentless-
managed computer. Being configured as a proxy agent allows an agent to submit data on behalf
of another source. A management group can serve as a proxy, but this takes up system
resources. A best practice is using an agent-managed computer as a proxy agent.
You might also configure a computer to act as a proxy to support specific features of a
management pack. For example, the Active Directory Management Pack requires enabling
domain controllers to act as proxy agents.
Note
If a proxy agent is removed from management, its agentless systems are no longer
managed.
Both the agentless-managed system and its proxy need to have access to the managing server
through any firewalls. For more information about interacting with firewalls, see (link to
appropriate content in deployment).
131
3. On the Security tab, select Allow this agent to act as a proxy and discover managed
objects on other computers, and then click OK.
See Also
Agentless Monitoring in Operations Manager
How to Configure a Computer for Agentless Management
132
Managing Access in Operations Manager
Getting Information from Operations Manager
General Tasks in Operations Manager
Maintenance of Operations Manager
Operations Manager Report Authoring Guide
Managing Discovery and Agents
For information about installing a gateway server, see Deploying a Gateway Server in the
Deployment Guide.
See Also
Monitoring Across Untrusted Boundaries in Operations Manager
Determining the Health of Gateway Servers
Using Multiple Gateway Servers
133
How to Configure Agent Failover to Multiple Gateway Servers
How to Configure a Gateway Server to Failover Between Multiple Management Servers
Certificate Renewal for Gateway Servers and Management Servers
Direct Method
Gateway servers are a type of management server, and therefore they are included in
Management Servers under Device Management in the Administration workspace of the
Operations console. In the details pane of this view, you can immediately see the Health State of
any of management servers in the management group. By selecting any gateway server (or any
server for that matter) and opening the context menu, you can view the properties of the server or
any of the views that are available. Typically, you can directly access the Event View, Alert View,
Performance View, Diagram View, and State View for the selected object.
For a more comprehensive understanding of the health of a gateway server, open the Monitoring
view and navigate to the Operations Manager, Management Server folder and select the
Management Server State view object in the navigation pane. This displays the state of all
management servers in the management group, with gateway servers displayed next to the
bottom by default. In the Gateway Management Server State pane, select the health status icon
for the server you are interested in under the Gateway column to bring up the health state of the
gateway servers component monitors in the details pane. Typically, you will get details on the
Health Service Availability, Audit Collection Availability, Configuration, Performance, and
Security.
Indirect Method
Gateway servers relay monitoring data from agents to collection management servers in the
management group across trust boundaries. They also relay configuration information from the
collection management server to the agents that they serve. Therefore, if agents that have a
gateway server as their primary management server are reporting their data and are showing a
heartbeat, you can be sure that their gateway server is performing satisfactorily.
134
2. In the Administration workspace, click Agent Managed.
3. Displayed in the results pane are all the agent-managed devices grouped by their
Primary Management Server.
4. Look for the gateway server of interest. Grouped under it are all the agents that are
currently using the gateway server.
See Also
Monitoring Across Untrusted Boundaries in Operations Manager
About Gateway Servers in Operations Manager
How to Configure Agent Failover to Multiple Gateway Servers
How to Configure a Gateway Server to Failover Between Multiple Management Servers
Certificate Renewal for Gateway Servers and Management Servers
See Also
Monitoring Across Untrusted Boundaries in Operations Manager
About Gateway Servers in Operations Manager
Determining the Health of Gateway Servers
How to Configure Agent Failover to Multiple Gateway Servers
How to Configure a Gateway Server to Failover Between Multiple Management Servers
Certificate Renewal for Gateway Servers and Management Servers
Important
135
When changing the primary management server of an agent, allow the agent to connect
to its new primary management server before making changes to its failover server.
Allowing the agent to get current topology information from the new primary management
server prevents the agent from losing communication with all management servers.
See Also
Monitoring Across Untrusted Boundaries in Operations Manager
About Gateway Servers in Operations Manager
Determining the Health of Gateway Servers
Using Multiple Gateway Servers
How to Configure a Gateway Server to Failover Between Multiple Management Servers
Certificate Renewal for Gateway Servers and Management Servers
136
multiple management servers. The commands can be run from any command shell in the
management group.
See Also
Monitoring Across Untrusted Boundaries in Operations Manager
About Gateway Servers in Operations Manager
Using Multiple Gateway Servers
Determining the Health of Gateway Servers
How to Configure Agent Failover to Multiple Gateway Servers
Certificate Renewal for Gateway Servers and Management Servers
137
To do this, follow the procedures that were used to obtain and import the certificates in the first
place. For more information, see Deploying a Gateway Server in the Deployment Guide. It is not
necessary to rerun the Gateway Approval Tool.
See Also
Monitoring Across Untrusted Boundaries in Operations Manager
About Gateway Servers in Operations Manager
Determining the Health of Gateway Servers
Using Multiple Gateway Servers
How to Configure Agent Failover to Multiple Gateway Servers
How to Configure a Gateway Server to Failover Between Multiple Management Servers
AEM Views
By default, the following views display AEM data in the Monitoring area of the Operations
console:
Application View
A state view that lists applications that have failures.
Error Events
An event view that lists the application error reports generated by severe application or
138
operating system failures.
Important
If you plan to configure the management server to forward error reports to Microsoft and
receive links to available solutions for those errors or participate in the Customer
Experience Improvement Program (CEIP), you must first configure the management
server's proxy settings if it uses a proxy server to access the Internet.
139
The Operations Manager Client Monitoring Configuration Wizard is used to configure the server
component of Client Monitoring on an Operations Manager management server. To configure the
server component of Client Monitoring on multiple management servers, run the wizard once for
each management server. An example of when you might configure multiple management
servers for Client Monitoring is if the connection between specific clients and management
servers is less expensive.
Important
The management server and error reporting clients must be in the same or fully trusted
domains.
Note
The Configure Client Monitoring option will be unavailable if the selected
computer is a gateway server.
140
management server that will be used to collect error reports. The file share will be
created at the local path on the management server and shared with the necessary
permissions.
Important
The file share path must be on an NTFS partition and have at least 2 GB of
free disk space. It is recommended that the path is no longer than 120
characters. The file share path must not be a UNC path or mapped drive
letter.
b. Select Collect application errors from Windows Vista or later computers if you
are managing Windows Vista or later operating systems with Operations Manager.
Type a Port number, or leave the default 51906. Leave Use Secure Socket Layer
protocol selected if you have installed a certificate on your management server,
leave Use Windows Authentication selected if you want the client computers to
authenticate with the management server; otherwise, clear the options.
c. Type the Organization Name, using no more than 22 characters, and then click
Next. The Organization Name can display on computers experiencing errors that are
running Windows Server 2003 and earlier operating systems.
4. On the Error Forwarding page, do one of the following:
Leave the Automatically forward all collected errors to Microsoft check box
cleared, and then click Next.
Or
a. Select Automatically forward all collected errors to Microsoft if the management
server is connected to the Internet and you want to forward error reports to Microsoft
and receive links to available solutions for those errors.
b. Select Detailed to help ensure Microsoft can provide a solution to the issue, or leave
the default setting of Basic.
c. Click Next.
5. On the Create File Share page, do one of the following:
Select an Existing User Account from the list, and then click Next.
Select Other user account, type the User name and Password, select the Domain
from the list, and then click Next.
Important
The account must have the permissions necessary to create a file share on
the path provided in step 3a.
6. On the Create file Share: Task Status page, after the file share is successfully created,
click Next.
Note
To modify the Client Monitoring settings on the management server, such as the
file share, you must disable and then re-enable Client Monitoring on the
management server. You must also then modify the Client Monitoring Group
141
Policy settings on the clients.
7. On the Client Configuration Settings page, type or Browse to the location you want to
save the settings from the Client Monitoring Configuration Wizard. These settings are
saved in a Group Policy template file named ServerName.ADM. Click Finish.
Important
You must use the ServerName.ADM file to configure clients to redirect their
Client Monitoring data to the management server. For more information, see How
to Configure Clients for Client Monitoring.
See Also
Client Monitoring Using Agentless Exception Monitoring in Operations Manager
How to Configure Clients for Client Monitoring
How to Customize Client Monitoring Data Collection and Solution Response URLs for Error
Groups
How to Configure Error Transmission Settings for Client Monitoring in Operations Manager
Forwarding Client Error Reports (Client Monitoring)
Important
You must first configure a management server for the server component of Client
Monitoring by running the Client Monitoring Configuration Wizard. For more information,
see How to Configure a Management Server for Client Monitoring.
Note
For information about Group Policy, see http://go.microsoft.com/fwlink/?
LinkId=156845.
2. If needed, disable the Turn off Windows Error Reporting policy. This policy can be
found in Computer Configuration/Administrative Templates/System/Internet
Communication Management/Internet Communication settings.
3. Add the Agentless Exception Monitoring (AEM) Group Policy administrative template
(ServerName.ADM) to the domain or local computer policy. The ADM file is created when
the Client Monitoring Configuration Wizard is run.
Note
Use the same procedure to Disable the Group Policy settings, thereby disabling
142
Client Monitoring on the clients.
See Also
Client Monitoring Using Agentless Exception Monitoring in Operations Manager
How to Configure a Management Server for Client Monitoring
How to Customize Client Monitoring Data Collection and Solution Response URLs for Error
Groups
How to Configure Error Transmission Settings for Client Monitoring in Operations Manager
Forwarding Client Error Reports (Client Monitoring)
Note
To customize client monitoring data collection and the solution response URL for an
error group
You can use variables, such as %ProgramFiles%, for file paths. For information
about WMI, see http://go.microsoft.com/fwlink/?LinkId=71799.
8. In the Error Group Responses dialog box, select Custom error information, type the
URL for the custom error information, such as http://server/errors/100.htm, click Test
Link, and then click OK.
143
See Also
Client Monitoring Using Agentless Exception Monitoring in Operations Manager
How to Configure Clients for Client Monitoring
How to Configure a Management Server for Client Monitoring
How to Configure Error Transmission Settings for Client Monitoring in Operations Manager
Forwarding Client Error Reports (Client Monitoring)
Note
For information about enabling the Client Monitoring feature of System
Center 2012 – Operations Manager, see How to Configure a Management Server for
Client Monitoring.
To find the Error Transmission tab of the Global Management Server Settings -
Privacy dialog box
1. Log on to the computer with an account that is a member of the Operations Manager
Administrators role.
2. In the Operations console, click Administration.
3. In the Administration workspace, click Settings.
4. In the Settings pane, expand Type: General, right-click Privacy, and then click
Properties.
5. In the Global Management Server Group Settings - Privacy dialog box, click the Error
Transmission tab.
Note
Click Read the privacy statement to view the privacy statement.
144
To filter errors that are sent to Microsoft
1. On the Error Transmission tab of the Global Management Server Group Settings -
Privacy dialog box, click Filter.
2. In the Error Forwarding Filters dialog box, select one or more of the options for sources
of errors that you do not want forwarded to Microsoft, such as that come from specific
computers.
3. In the Criteria description text box, click specific, and provide the values for the criteria
of errors that you do not want forwarded to Microsoft, such as contoso.com.
4. Click OK twice.
See Also
Client Monitoring Using Agentless Exception Monitoring in Operations Manager
How to Configure Clients for Client Monitoring
How to Customize Client Monitoring Data Collection and Solution Response URLs for Error
Groups
How to Configure a Management Server for Client Monitoring
Forwarding Client Error Reports (Client Monitoring)
145
When you choose to participate in the CEIP, you configure clients with Group Policy to redirect
CEIP reports to a System Center 2012 – Operations Manager management server, instead of
reporting directly to Microsoft. The management servers are configured to forward these reports
to Microsoft.
Important
The CEIP reports do not contain contact information about you or your organization, such
as names or an address.
The CEIP reports forwarded from your organization to Microsoft are combined with CEIP reports
from other organizations and individual customers to help Microsoft solve issues and improve the
Microsoft products and features that customers use most often. For more information about the
CEIP, see the CEIP page.
Use the following procedure to configure CEIP settings. The management server must have
access to the Internet to participate in the program.
Important
CEIP is a component of the Client Monitoring feature of Operations Manager. Client
Monitoring must be enabled on at least one management server and managed
computers to participate in the CEIP. For information about enabling the Client Monitoring
feature of Operations Manager, see Client Monitoring Using Agentless Exception
Monitoring. After a management server has been configured for client monitoring, all
agents that are participating in CEIP should be configured via Group Policy to send their
CEIP data to that management server.
Note
You can click Tell me more about the program to view information about the
CEIP program, including the privacy statement.
See Also
Client Monitoring Using Agentless Exception Monitoring in Operations Manager
How to Configure Clients for Client Monitoring
146
How to Customize Client Monitoring Data Collection and Solution Response URLs for Error
Groups
How to Configure Error Transmission Settings for Client Monitoring in Operations Manager
How to Configure a Management Server for Client Monitoring
Note
You might see alerts from Cluster discovery connect functionality monitor and
Cluster state connect functionality monitor when the Action Account uses low
privilege credentials. To resolve this problem, assign higher privilege credentials to the
Windows Cluster Action Account. For instructions, see the procedure “To modify Run As
account properties” in How to Create a Run As Account.
See Also
Operations Manager Monitoring Scenarios
Integrating Active Directory and Operations Manager
Connecting Operations Manager With Other Management Systems
Collecting Security Events Using Audit Collection Services in Operations Manager
Monitoring UNIX and Linux Computers by Using Operations Manager
147
Monitoring .NET Applications
Monitoring Service Level Objectives by Using Operations Manager
Monitoring Networks by Using Operations Manager
Monitoring Operations Manager from a Second Management Group
Client Monitoring Using Agentless Exception Monitoring in Operations Manager
Monitoring Across Untrusted Boundaries in Operations Manager
Agentless Monitoring in Operations Manager
148
Note
Ports that are connected to a computer are not monitored; only ports that connect to
other network devices are monitored. You can monitor a port that is connected to a
computer that is not agent-managed in the same management group by adding the
port to the Critical Network Adapters Group.
Processor - % Utilization (for some certified devices)
Memory - including high utilization, high buffer utilization, excessive fragmentation, and buffer
allocation failures (for some certified devices)
In-depth memory counters (Cisco devices only)
Free memory
Note
Some of the monitoring capabilities are disabled by default. For more information, see
Tuning Network Monitoring.
Operations Manager supports monitoring of the following number of network devices:
2000 network devices (approximately 25,000 monitored ports) managed by two resource
pools
1000 network devices (approximately 12,500 monitored ports) managed by a resource pool
that has three or more management servers
500 network devices (approximately 6,250 monitored ports) managed by a resource pool that
has two or more gateway servers
149
Note
How Network Device Discovery Works
Network device discovery is performed by discovery rules that you create. For instructions on
creating a discovery rule, see How to Discover Network Devices in Operations Manager and
Network Device Discovery Settings.
When you create a discovery rule, you designate a management server or gateway server to run
the rule. Each management server or gateway server can run only one discovery rule. You may
need to strategically place management servers on different network segments so that they can
access the network devices that they are discovering.
Discovery rules run on a schedule that you can specify, and you can also run a rule on demand.
Each time the discovery rule runs, it attempts to find new devices within its definition or changes
to devices that were previously discovered. A discovery rule can perform explicit discovery or
recursive discovery.
Explicit discovery – An explicit discovery rule will only attempt to discover those devices that
you explicitly specify in the wizard by IP address or FQDN. It will only monitor those devices
that it can successfully access. The rule will attempt to access the device by using ICMP,
SNMP, or both depending on the configuration of the rule.
Recursive discovery – A recursive discovery rule will attempt to discover those devices that
you explicitly specify in the wizard by IP address, as well as other network devices that are
connected to the specified SNMP v1 or v2 device and that the specified SNMP v1 or v2
device knows about through the device’s Address Routing Protocol (ARP) table, its IP
address table, or the topology Management Information Block (MIB).
If you use recursive discovery, you can elect to discover all the other network devices that the
specified SNMP v1 or v2 device knows about or only network devices that are connected to
the specified SNMP v1 or v2 device that are in a specified IP address range. You can also
filter recursive discovery by using such properties as the device type, name, and object
identifier (OID).
Operations Manager can identify connected devices in a recursive discovery that use
an IPv6 address; however, the initial device that is discovered must use an IPv4
address.
A discovery rule can perform only explicit or recursive discovery, but cannot perform a
combination of discovery types. You can change the discovery type of a rule after the rule is
created. If you know all of the network devices that you want discovered, you should use explicit
discovery. Recursive discovery can discover devices that you have no business need to monitor
and as a result, can increase the administrative workload of monitoring your network.
A discovery rule can discover any combination of SNMP v1, v2, and v3 devices. SNMP v3
devices can only be discovered by explicit discovery or by being specified in a recursive
discovery rule. If you specify an SNMP v3 device in a recursive discovery rule, the SNMP v3
device will be discovered but devices connected to it will not be discovered. If you specify an
SNMP v1 or v2 device in a recursive discovery rule, only SNMP v1 and v2 devices connected to it
will be included in the recursive discovery.
150
Note
Windows computers running SNMP are filtered out of discovery results if:
The device type is “Host” and the vendor is “Microsoft”
The sysDescription field contains “Microsoft”
The sysOid starts with .1.3.6.1.4.1.311.1.1.3.1
The sysOid contains 1.3.6.1.4.1.199.1.1.3.11
In the discovery rule configuration, you specify whether Operations Manager will use ICMP,
SNMP, or both to communicate with the network device. The network device must support the
protocol that you specify. When the discovery rule runs, Operations Manager attempts to contact
the network devices that you specify, using the protocol or protocols that you specified. If you
specify that a device uses both ICMP and SNMP, Operations Manager must be able to contact
the device by using both methods or discovery will fail. If you specify ICMP as the only protocol to
use, discovery is limited to the specified device and monitoring is limited to whether the device is
online or offline.
Credentials are also needed to communicate with the device. You associate each discovery rule
with Run As accounts that supply the community string (for SNMP v1 and v2 devices) or access
credentials (SNMP v3) to Operations Manager. For more information, see Run As Accounts for
Network Monitoring in Operations Manager.
After Operations Manager successfully accesses a specified network device, if you selected
recursive discovery, it attempts to discover other network devices that the specified device knows
about through the device’s ARP table, its IP address table, or the topology MIB files.
Network device discovery consists of the following phases, which are displayed in the status of
the discovery task:
1. Probing
During the probing phase, Operations Manager attempts to contact device using the specified
protocol, as follows:
ICMP only: ping the device
ICMP and SNMP: contact the device using both protocols
SNMP only: uses the SNMP GET message
2. Processing
After probing is complete, Operations Manager processes all of the components of the
device, such as ports and interfaces, memory, processors, VLAN membership, and HSRP
groups.
3. Post Processing
Operations Manager correlates network device ports to the servers that the ports are
connected to, inserts items into the operational database, and associates Run As accounts.
After discovery is complete, the management server resource pool that you specify in the
discovery rule begins monitoring the discovered network devices. For more information on
monitoring network devices, see Viewing Network Devices and Data in Operations Manager and
Reports for Network Monitoring in Operations Manager.
151
Note
See Also
How to Discover Network Devices in Operations Manager
Network Device Discovery Settings
Run As Accounts for Network Monitoring in Operations Manager
How to Delete or Restore a Network Device in Operations Manager
Viewing Network Devices and Data in Operations Manager
Security for Servers Performing Network Discovery
Network Devices Supported for Discovery by Operations Manager
Reports for Network Monitoring in Operations Manager
Tuning Network Monitoring
Note
rules that you create. Each time the rule runs, it will attempt to find new devices within its
definition or changes to devices that were previously discovered.
Discovery of a large number of devices can take several hours to complete.
Each management server or gateway server can run only one discovery rule. You specify a single
management server or gateway server to run the discovery rule and a management server
resource pool to perform the actual monitoring of the network devices. If you plan to monitor more
Note
than 1000 network devices, you should use two resource pools and split the number of devices
evenly between the pools.
If you create discovery rules on multiple management servers, you should create a
management pool for each and make sure that each discovery defines a different set of
devices. If a single device is managed in different pools, it will not be able to be deleted.
For more information on how network device discovery works, see How Network Device
Discovery Works.
Prerequisites
To create a network devices discovery rule, you need the following information:
The IP address or FQDN of each device that you want to discover and monitor.
Operations Manager can identify connected devices in a recursive discovery that use
an IPv6 address; however, the initial device that is discovered must use an IPv4
address.
The version of SNMP that each devices uses. This can be SNMP v1, v2, or v3.
152
The SNMP community string of each SNMP v1 or v2 device that you want to discover and
monitor.
The user name, context, authentication protocol, authentication key, privacy protocol, and
privacy key for each SNMP v3 device that you want to discover and monitor.
If you are using recursive discovery and you only want to discover network devices that have
interfaces whose addresses fall within a specified IP address range, you must have the IP
address range.
The name of the management server resource pool that will monitor the discovered devices.
Note
When Network Load Balancing (NLB) is used, the destination MAC address for the
network adapter (cluster adapter) uses the format of 02-BF-1-2-3-4 and the cluster hosts
use a format of 02-h-1-2-3-4, where h is the host's priority within the cluster (set in the
Network Load Balancing Properties dialog box). Operations Manager will create a
network connection between the devices using 02-h-1-2-3-4 to the destination MAC
address of 02-BF-1-2-3-4.
You must ensure the following firewall configuration before creating the network devices
discovery rule:
All firewalls between the management server and the network devices need to allow SNMP
(UDP) and ICMP bi-directionally, and ports 161 and 162 need to be open bi-directionally. This
includes Windows Firewall on the management server itself.
If your network devices are using a port other than 161 and 162, you need to open bi-
directional UDP traffic on these ports.
Note
153
If you know all of the network devices that you want discovered, you should use
explicit discovery. Recursive discovery can discover devices that you have no
business need to monitor and as a result, can increase the administrative
workload of monitoring your network
6. On the Default Accounts page, if you are discovering only SNMP v3 devices, click Next.
If you are discovering any SNMP v1 or v2 devices, do the following:
a. If you previously created Run As accounts for SNMP v1 or v2 devices, the Run As
accounts will be listed and you can select a listed account for this discovery rule. If no
accounts are listed or the listed accounts are not appropriate for this discovery rule,
continue to the next step.
Note
If you are creating a recursive discovery rule, you must create a default
account, which will be used to connect to and discover devices connected to
the device that you specify on the Devices page. If you do not create and
select an account on the Default Accounts page, the recursive discovery
will discover the device that you specify but will not discover devices
connected to it.
b. Click Create Account.
c. In the Create Run As Account Wizard, on the Introduction page, click Next.
d. In the Display Name text box, type a name such as Router Credentials.
e. Optionally, type a description in the Description box. Click Next.
f. On the Credentials page, type the SNMP community string for your network devices,
and then click Create.
Note
If the rule will discover devices that use more than one SNMP community
string, you must create one Run As account for each SNMP community
string.
g. On the Default Accounts page, you will see that the Run As account that you just
created is listed in the SNMPv1/v2 Run As accounts box and is selected. Click Next
7. If you are adding an SNMP v1 or v2 device, on the Devices page, do the following:
Note
This procedure describes how to add devices one at a time. You can also add
multiple devices by clicking the Import button to import a text file with a list of
IPv4 addresses. This file should have a single IP address on each line. After
import, the IP addresses are part of the discovery rule and the text file is no
longer needed.
a. Click Add to open the Add Device page.
b. On the Add Device page, type the IPv4 address or FQDN of the device that you
want to discover and monitor. If you are creating a recursive discovery, the discovery
will access this device to locate other devices on your network.
154
c. In Access Mode, select ICMP, SNMP, or ICMP and SNMP. This specifies how the
device will be discovered and how it will be monitored after discovery.
Note
If you select ICMP and SNMP, the device must be accessible by both
protocols or it will not be discovered. If you select ICMP, discovery will be
limited to the specified device, and monitoring will be limited to whether the
device is online or offline.
d. In Port number, retain the default port (161) or select another port number for the
device.
e. Select v1 or v2 from the SNMP version drop-down box.
f. In SNMP V1 or V2 Run As account, select Use selected default account. If you
specify an account in this window, then only the specified account will be used for
discovery.
Note
If you are discovering devices that use more than one SNMP community
string and therefore have multiple Run As accounts, you can retain the
default value of Use selected default accounts in the SNMP V1 or V2 Run
As account field. When you do this, the Network Devices Discovery Wizard
will attempt to use the community string for every Run As account that you
selected on the Default Accounts page against every device that you add to
the discovery list until a community string succeeds.
g. Click OK. This returns you to the Devices page and you should see the device that
you just added listed.
Note
The Advanced Discovery Settings button on the Devices page opens a
dialog box that contains a number of settings that you can use to configure
discovery of network devices, such as number of retry attempts. If you know
you are going to discover more than 1500 devices, you must change the
Maximum number of devices to discover in Advanced Discovery
Settings. For more information on the available settings, see Network
Device Discovery Settings.
h. Add other SNMP v1 or v2 devices and Run As accounts as necessary, and then click
Next.
Note
If you add multiple devices to the rule, you can set a common Run As
Account for all of them by selecting all of the devices and then clicking Edit.
8. If you are adding an SNMP v3 device, on the Devices page, do the following:
Note
This procedure describes how to add devices one at a time. You can also add
155
multiple devices by clicking the Import button to import a text file with a list of
IPv4 addresses. This file should have a single IP address on each line. After
import, the IP addresses are part of the discovery rule and the text file is no
longer needed. Each device requires an SNMP v3 credential. After you import the
addresses, you can edit each device to add the credential or you can select
multiple devices and provide the same credential for all selected devices.
a. Click Add. This opens the Add Device page.
b. On the Add a Device page, type the IPv4 address or FQDN of the SNMP v3 device
that you want to discovery and monitor.
c. In Access Mode, select ICMP, SNMP, or ICMP and SNMP. This specifies how the
device will be discovered and how it will be monitored after discovery.
Note
If you select ICMP and SNMP, the device must be accessible by both
protocols or it will not be discovered. If you select ICMP, discovery will be
limited to the specified device, and monitoring will be limited to whether the
device is online or offline.
d. In Port number, retain the default port (161) or select another port number for the
device.
e. Select v3 from the SNMP version drop-down box.
f. Click Add SNMP V3 Run As Account.
Note
Each SNMP v3 device requires its own Run As account.
g. In the Create Run As Account Wizard, on the Introduction page, click Next.
h. Type a value in the Display name box, optionally type a description, and then click
Next.
i. On the Credentials page, enter the values for User name, Context, Authentication
protocol, Authentication key, Privacy protocol and Privacy key for the SNMP v3
device. Click Create.
j. Click OK. This returns you to the Devices page.
Note
The Advanced Discovery Settings button on the Devices page opens a
dialog box that contains a number of settings that you can use to configure
discovery of network devices, such as number of retry attempts. If you know
you are going to discover more than 1500 devices, you must change the
Maximum number of devices to discover in Advanced Discovery
Settings. For more information on the available settings, see “Network
Device Discovery Settings” in the Operations Manager 2012 Operations
Guide.
k. Add other SNMP v3 devices and Run As accounts as necessary, and then click Next.
9. If you are creating an explicit discovery rule, go to the next step. If you are creating a
156
recursive discovery rule, do the following:
a. On the Include Filters page, leave the default setting to discover all devices. If you
want to filter for only a particular set of devices, select Discover only network
devices within the specific IP address ranges, and then click Add to configure a
filter. Click Next when complete.
In the IP address range field, you can enter addresses such as the following:
10.193.220.25 (a single IP address to include one specific device)
172.23.136<1-100> (include any IP address from 1 to 100 in
172.23.136/255.255.255.0)
172.23.135.* (include any IP address in 172.23.135/255.255.255.0)
Note
For more information on formatting an IP address range, see “Network
Device Discovery Settings” in the Operations Manager 2012 Operations
Guide.
b. On the Exclude Filters page, leave the default setting to not exclude any of the
discovered devices. If you want to filter an IP address from being discovered, click
Add and specify an IP address. Click Next when complete.
Note
Although the dialog box states that an IP address or host name can be entered
for an exclude filter, only an IP address is valid. A host name cannot be specified
here.
10. On the Schedule Discovery page, either accept the default value of Saturday at 2 AM or
specify an alternate schedule, and then click Next.
Note
We recommend that you do not run network discovery more frequently than twice
per week because network discovery can take hours to complete and may place
an excessive load on the management server or gateway server during
discovery.
11. Review your settings on the Summary page, and then click Finish when you are ready
to proceed.
12. You will see a Warning popup that reads "The following accounts need to be distributed
to the health service management server name in order for the discovery to work:
DiscoveryName\Run As Account. Would you like Operations Manager to distribute the
accounts? Yes: Distribute the accounts and create the discovery. No: Do not distribute the
accounts and do not create the discovery.” Click Yes.
13. The wizard completes and you see the message The network discovery rule was
successfully created. Ensure Run the network discovery rule after the wizard is
closed is selected if you want the rule to run immediately, and then click Close. The
network devices discovery rule is created. If you did not select Run the network
discovery rule after the wizard is closed, the discovery rule will run on the scheduled
day and time.
157
To change the discovery type of a network devices discovery rule
Note
It can take several minutes for the network discovery rule to appear in the
Operations console and begin discovery if you select Run the network
discovery rule after the wizard is closed.
14. To monitor the progress of network device discovery, watch the status column of the
discovery rule. It will provide the following statuses while it is running, along with the
number of devices that it has located:
a. Probing
During the probing phase, Operations Manager attempts to contact device using the
specified protocol, as follows:
ICMP only: ping the device
ICMP and SNMP: contact the device using both protocols
SNMP only: uses the SNMP GET message
b. Processing
After probing is complete, Operations Manager processes all of the components of
the device, such as ports and interfaces, memory, processors, VLAN membership,
and HSRP groups.
c. Post Processing
Operations Manager correlates network device ports to the servers that the ports are
connected to, inserts items into the operational database, and associates Run As
accounts.
15. To confirm the successful discovery and management of the devices, select Device
Management, and then select Network Devices. You should see your discovered
devices listed in the results pane.
If a network device discovery rule fails, the device or devices will be listed in Network
Devices Pending Management. This can be a subset of the devices specified in the
discovery rule. Use one of the following methods to retry the discovery:
To attempt to discover that specific device only, right-click the device in Network Devices
Pending Management and then click Submit rediscovery.
To retry a recursive discovery that begins with that device, click Discovery Rules, right-
click the respective rule, and then click Run.
1. In the Operations console, in the Administration workspace, click Discovery Rules.
2. In the results pane, right-click the discovery rule that you want to change and click
Properties.
3. On the General Properties page, click Next.
4. On the Discovery Method page, click the type of discovery you want the rule to use.
5. Follow the instructions for creating a discovery rule to complete the remaining wizard
pages, and then click Save.
158
See Also
Monitoring Networks by Using Operations Manager
Tuning Network Monitoring
Network Device Discovery Settings
Run As Accounts for Network Monitoring in Operations Manager
How to Delete or Restore a Network Device in Operations Manager
Viewing Network Devices and Data in Operations Manager
Security for Servers Performing Network Discovery
Network Devices Supported for Discovery by Operations Manager
Reports for Network Monitoring in Operations Manager
Name or IP address Devices page, Add button Enter either a fully qualified
domain name (FQDN) or an
IPv4 address. Operations
Manager can identify
connected devices in a
recursive discovery that use an
IPv6 address; however, the
initial device that is discovered
must use an IPv4 address.
Access mode Devices page, Add button Select either ICMP and SNMP,
ICMP, or SNMP. This specifies
the protocol that will be used for
both discovery and monitoring.
If you select ICMP and SNMP,
the device must be accessible
by both protocols, or discovery
will fail.
159
Setting Location Notes
account.
Port number Devices page, Add button The default port is 161. You can
change this value if you are
discovering a network device
that uses another port.
Run As account Devices page, Add button The available accounts in the
menu are populated based on
your selection in the SNMP
version box. You can create
the appropriate Run As account
by clicking Add SNMP version
Run As Account.
Number of retry attempts Devices page, Advanced This setting specifies how many
Discovery Settings button times the management server
should attempt to contact the
network device before reporting
that discovery failed.
ICMP time-out (in Devices page, Advanced If you specify ICMP and SNMP
milliseconds) Discovery Settings button or ICMP for Access mode, the
management server attempts to
contact the network device by
using ping. The default setting
is 1500 milliseconds (1.5
seconds).
SNMP time-out (in Devices page, Advanced If you specify ICMP and SNMP
milliseconds) Discovery Settings button or SNMP for Access mode, the
management server attempts to
contact the network device by
using SNMP. The default
setting is 1500 milliseconds
(1.5 seconds).
Maximum number of devices Devices page, Advanced This setting applies during
to discover Discovery Settings button recursive discovery and sets a
limit on the number of devices
to discover. The default is 1500.
If you know you are going to
discovery more than 1500
devices, you must change this
160
Setting Location Notes
setting.
IP address range Include Filters page, Add Use this field to limit the
button, when configuring a recursive discovery to IP
recursive discovery rule addresses that meet the
specified criteria. This field uses
a wildcard format.
For example, if you enter
192.168.1.*, the discovery rule
discovers devices that use any
IP address between
192.168.1.1 and
192.168.1.255.
If you enter 192.168.1.<1-140>,
the discovery rule discovers
devices that use any IP address
between 192.168.1 and
192.168.140.
For more options, see IP
Address Range for Network
Device Filtering.
Included device types Include Filters page, Add Any devices that you select are
button, when configuring a included in the recursive
recursive discovery rule discovery. Clear the selection
for any type of device that you
do not want discovered.
Include only network devices Include Filters page, Add If you enter a value here, only
with the following system button, when configuring a devices with a matching name
attributes (OIDs) - Name recursive discovery rule are discovered. This field allows
a wildcard format. For more
options, see IP Address
Range for Network Device
Filtering.
Include only network devices Include Filters page, Add If you enter a value here, only
with the following system button, when configuring a devices with a matching OID
attributes (OIDs) – Object ID recursive discovery rule are discovered. This field allows
(OID) a wildcard format. For more
options, see IP Address
Range for Network Device
Filtering.
161
Setting Location Notes
Include only network devices Include Filters page, Add If you enter a value here, only
with the following system button, when configuring a devices with a matching
attributes (OIDs) – recursive discovery rule description are discovered. This
Description field allows a wildcard format.
For more options, see IP
Address Range for Network
Device Filtering.
IP Address or Host Name Exclude Filters page, Add Enter either a fully qualified
button, when configuring a domain name (FQDN), an IPv4
recursive discovery rule address, or an IPv6 address to
exclude from discovery. You
can add multiple IP address
individually.
162
Character Description Example
\ Escape character
163
Character Description Example
*Router*~*Cisco*&*10.20.30.<5-10>
matches routers except Cisco routers
with the addresses between 10.20.30.5
and 10.20.30.10.
See Also
Monitoring Networks by Using Operations Manager
How to Discover Network Devices in Operations Manager
Tuning Network Monitoring
Run As Accounts for Network Monitoring in Operations Manager
How to Delete or Restore a Network Device in Operations Manager
Viewing Network Devices and Data in Operations Manager
Security for Servers Performing Network Discovery
164
Note
Network Devices Supported for Discovery by Operations Manager
Reports for Network Monitoring in Operations Manager
See Also
Monitoring Networks by Using Operations Manager
How to Discover Network Devices in Operations Manager
Network Device Discovery Settings
Tuning Network Monitoring
How to Delete or Restore a Network Device in Operations Manager
Viewing Network Devices and Data in Operations Manager
165
Security for Servers Performing Network Discovery
Network Devices Supported for Discovery by Operations Manager
Reports for Network Monitoring in Operations Manager
Note
You can identify the discovery rule associated with a discovered network device by right-
clicking the device in Network Devices or Network Devices Pending Management and
then clicking Discovery Rule Properties.
If you delete a device that was discovered by a recursive discovery rule, it will be added to the
exclude list of the rule. If you want to have that device discovered and monitored again, you must
remove the device from the Exclude Filters page of the rule’s properties and run the discovery
again.
Note
You can select multiple devices to delete.
See Also
Monitoring Networks by Using Operations Manager
How to Discover Network Devices in Operations Manager
Network Device Discovery Settings
Run As Accounts for Network Monitoring in Operations Manager
Tuning Network Monitoring
Viewing Network Devices and Data in Operations Manager
Security for Servers Performing Network Discovery
Network Devices Supported for Discovery by Operations Manager
Reports for Network Monitoring in Operations Manager
167
Tuning Network Monitoring
System Center 2012 – Operations Manager includes the following management packs specific to
network device discovery and monitoring:
Network Management - Core Monitoring
This management pack contains monitoring logic for network devices.
Windows Client Network Discovery
This management pack contains discovery rules to set the properties of discovered network
adapters connected to computers running client operating systems.
Windows Server Network Discovery
This management pack contains discovery rules to set the properties of discovered network
adapters connected to computers running server operating systems.
Network Discovery Internal
This management pack contains definitions and rules for discovering network devices.
Network Management Library
This management pack contains definitions for core network device management.
Network Management Reports
This management pack contains reports for network management.
Network Management Templates
This management pack contains templates for authoring network management workflows.
168
Rule Description Types
Probe
Relay Device
Route Switch
Feature Card
Route Switch
Module
Router
Switch
Terminal Server
Output Packet Error Collects the percentage of output packet Interface (if-mib
Percentage errors dot3)
Interface (if-mib
ethernet)
Interface (if-mib
netcor)
Interface (if-mib
router)
Interface (netcor
cisco ethernet)
Interface (netcor if-
mib cisco ethernet)
Interface (netcor if-
mib cisco)
Interface (netcor if-
mib MIB2)
Interface (netcor
MIB2)
Interface (netcor
router)
Network adapter
(dot3)
Network adapter (if-
mib cisco)
Network adapter (if-
mib performance)
Network adapter (if-
mib)
Network adapter
(MIB2)
169
Rule Description Types
Network adapter
(netcor cisco)
Network adapter
(netcor ethernet)
Network adapter
(netcor if-mib)
Network adapter
(netcor
performance)
Network adapter
(netcor)
Port (MIB2 Dot3
ethernet)
Port (netcor if-mib
dot3)
170
Rule Description Types
mib)
Network adapter
(netcor if-mib)
Network adapter
(netcor
performance)
Port (MIB2 Dot3
ethernet)
Port (netcor if-mib
dot3)
Input Packet Error Collects the percentage of input packet Interface (if-mib
Percentage errors dot3)
Interface (if-mib
ethernet)
Interface (if-mib
netcor)
Interface (if-mib
router)
Interface (netcor
cisco ethernet)
Interface (netcor if-
mib cisco ethernet)
Interface (netcor if-
mib cisco)
Interface (netcor if-
mib MIB2)
Interface (netcor
MIB2)
Interface (netcor
router)
Network adapter
(dot3)
Network adapter (if-
mib cisco)
Network adapter (if-
mib performance)
Network adapter (if-
mib)
Network adapter
(MIB2)
171
Rule Description Types
Network adapter
(netcor cisco)
Network adapter
(netcor ethernet)
Network adapter
(netcor if-mib)
Network adapter
(netcor
performance)
Network adapter
(netcor)
Port (MIB2 Dot3
ethernet)
Port (netcor if-mib
dot3)
172
Rule Description Types
router)
Network adapter (if-
mib base)
Network adapter (if-
mib cisco)
Network adapter (if-
mib performance)
Network adapter (if-
mib)
173
Rule Description Types
(MIB2)
Network adapter
(netcor base)
Network adapter
(netcor cisco)
Network adapter
(netcor ethernet)
Network adapter
(netcor if-mib)
Network adapter
(netcor
performance)
Network adapter
(netcor)
Port (MIB2 Dot3
ethernet)
Port (netcor if-mib
dot3)
174
Rule Description Types
netcor)
Interface (if-mib
router)
Interface (netcor
cisco ethernet)
Interface (netcor if-
mib cisco ethernet)
Interface (netcor if-
mib cisco)
Interface (netcor if-
mib MIB2)
Interface (netcor
MIB2)
Interface (netcor
router)
Network adapter
(dot3)
Network adapter (if-
mib base)
Network adapter (if-
mib cisco)
Network adapter (if-
mib performance)
Network adapter (if-
mib)
Network adapter
(MIB2)
Network adapter
(netcor base)
Network adapter
(netcor cisco)
Network adapter
(netcor ethernet)
Network adapter
(netcor if-mib)
Network adapter
(netcor
performance)
Network adapter
(netcor)
175
Rule Description Types
Input Packet Discard Collects the percentage of discarded input Interface (if-mib
Rate packets dot3)
Interface (if-mib
ethernet)
Interface (if-mib
netcor)
Interface (if-mib
router)
Interface (netcor
cisco ethernet)
Interface (netcor if-
mib cisco ethernet)
Interface (netcor if-
mib cisco)
Interface (netcor if-
mib MIB2)
Interface (netcor
MIB2)
Interface (netcor
router)
Network adapter
(dot3)
Network adapter (if-
mib base)
Network adapter (if-
mib cisco)
Network adapter (if-
mib performance)
Network adapter (if-
mib)
Network adapter
(MIB2)
Network adapter
(netcor base)
Network adapter
(netcor cisco)
176
Rule Description Types
Network adapter
(netcor ethernet)
Network adapter
(netcor if-mib)
Network adapter
(netcor
performance)
Network adapter
(netcor)
Port (MIB2 Dot3
ethernet)
Port (netcor if-mib
dot3)
Outbound Bits per Collects outbound bits per second Interface (if-mib
Second dot3)
Interface (if-mib
ethernet)
Interface (if-mib
netcor)
Interface (if-mib
router)
Interface (netcor
cisco ethernet)
Interface (netcor if-
mib cisco ethernet)
Interface (netcor if-
mib cisco)
Interface (netcor if-
mib MIB2)
Interface (netcor
MIB2)
Interface (netcor
router)
Network adapter
(dot3)
Network adapter (if-
mib base)
Network adapter (if-
mib cisco)
Network adapter (if-
177
Rule Description Types
mib performance)
Network adapter (if-
mib)
Network adapter
(MIB2)
Network adapter
(netcor base)
Network adapter
(netcor cisco)
Network adapter
(netcor ethernet)
Network adapter
(netcor if-mib)
Network adapter
(netcor
performance)
Network adapter
(netcor)
Port (MIB2 Dot3
ethernet)
Port (netcor if-mib
dot3)
Inbound Bits per Collects inbound bits per second Interface (if-mib
Second
178
Rule Description Types
dot3)
Interface (if-mib
ethernet)
Interface (netcor
cisco ethernet)
Interface (netcor if-
mib cisco ethernet)
Interface (if-mib
netcor)
Interface (if-mib
router)
Interface (netcor if-
mib cisco)
Interface (netcor if-
mib MIB2)
Interface (netcor
MIB2)
Interface (netcor
router)
Network adapter
(dot3)
Network adapter (if-
mib base)
Network adapter (if-
mib cisco)
Network adapter (if-
mib performance)
Network adapter (if-
mib)
Network adapter
(MIB2)
Network adapter
(netcor base)
Network adapter
(netcor cisco)
Network adapter
(netcor ethernet)
Network adapter
(netcor if-mib)
Network adapter
179
Rule Description Types
(netcor
performance)
Network adapter
(netcor)
Port (MIB2 Dot3
ethernet)
Port (netcor if-mib
dot3)
180
Rule Description Types
mib MIB2)
Interface (netcor
MIB2)
Interface (netcor
router)
Network adapter
(dot3)
Network adapter (if-
mib base)
Network adapter (if-
mib cisco)
Network adapter (if-
mib performance)
Network adapter (if-
mib)
Network adapter
(MIB2)
Network adapter
(netcor base)
Network adapter
(netcor cisco)
Network adapter
(netcor ethernet)
Network adapter
(netcor if-mib)
Network adapter
(netcor
performance)
Network adapter
(netcor)
Port (MIB2 Dot3
ethernet)
Port (netcor if-mib
dot3)
181
Rule Description Types
Interface (if-mib
router)
Interface (netcor
cisco ethernet)
Interface (netcor if-
mib cisco ethernet)
Interface (netcor if-
mib cisco)
Interface (netcor if-
mib MIB2)
Interface (netcor
MIB2)
Interface (netcor
router)
Network adapter
(dot3)
Network adapter (if-
mib base)
Network adapter (if-
mib cisco)
Network adapter (if-
mib performance)
Network adapter (if-
mib)
Network adapter
(MIB2)
Network adapter
(netcor base)
Network adapter
(netcor cisco)
Network adapter
(netcor ethernet)
Network adapter
(netcor if-mib)
Network adapter
(netcor
performance)
Network adapter
(netcor)
Port (MIB2 Dot3
182
Rule Description Types
ethernet)
Port (netcor if-mib
dot3)
Inbound Queue Collects the number of packets dropped Interface (Cisco Router)
Packets Dropped Per per second due to the input queue being
Second full.
Inbound Giant Packets Collects giant inbound packets per second. Interface (Cisco Router)
per Second
Inbound Packets with Collects the number of inbound packets Interface (Cisco Router)
CRC Error per Second per second with CRC errors.
Inbound Packets Collects the number of inbound packets Interface (Cisco Router)
Aborted per Second aborted per second.
Inbound Misaligned Collects the number of inbound misaligned Interface (Cisco Router)
Packets per Second packets per second.
Output Queue Packets Collects the number of packets dropped Interface (Cisco Router)
Dropped per Second per second due to the output queue being
full.
Inbound Runts per Collects the number of inbound packets Interface (Cisco Router)
Second smaller than permitted by the physical
media.
Inbound Packets Collects inbound packets ignored per Interface (Cisco Router)
Ignored per Second second.
Output Packet Queue Collects the number of output packets Interface (if-mib
Drop Percentage discarded because of output queue ethernet)
overflow. Interface (if-mib
router)
Interface (netcor
cisco ethernet)
Interface (netcor if-
mib cisco ethernet)
Interface (netcor if-
mib cisco)
Interface (netcor
router)
Network adapter (if-
mib cisco)
Network adapter
183
Rule Description Types
(netcor cisco)
Network adapter
(netcor ethernet)
Input Packet Queue Collects the number of input packets Interface (if-mib
Drop Percentage discarded because of input queue ethernet)
overflow. Interface (if-mib
router)
Interface (netcor
cisco ethernet)
Interface (netcor if-
mib cisco ethernet)
Interface (netcor if-
mib cisco)
Interface (netcor
router)
Network adapter (if-
mib cisco)
Network adapter
(netcor cisco)
Network adapter
(netcor ethernet)
184
Rule Description Types
Network adapter
(netcor cisco)
Network adapter
(netcor ethernet)
Network adapter
(netcor if-mib)
Network adapter
(netcor
performance)
Network adapter
(netcor)
Port (MIB2 Dot3
ethernet)
Port (netcor if-mib
dot3)
185
Rule Description Types
(netcor
performance)
Network adapter
(netcor)
Port (MIB2 Dot3
ethernet)
Port (netcor if-mib
dot3)
Port Alignment Errors Determines the change in the SNMP Port (Dot3 ethernet)
Rate dot3StatsAlignmentErrorsRate value for
the dot3_Ethernet_Performance_Port
since the last polling.
Port Carrier Sense Determines the change in the SNMP Port (Dot3 ethernet)
Errors Rate dot3StatsCarrierSenseErrorsRate value for
the dot3_Ethernet_Performance_Port
since the last polling.
Port FCS Errors Rate Determines the change in the SNMP Port (Dot3 ethernet)
dot3StatsFCSErrorsRate value for the
dot3_Ethernet_Performance_Port since
the last polling.
Port Frame Too Longs Determines the change in the SNMP Port (Dot3 ethernet)
Rate dot3StatsFrameTooLongsRate value for
the dot3_Ethernet_Performance_Port
since the last polling.
Port Internal Mac Determines the change in the SNMP Port (Dot3 ethernet)
Receive Errors Rate dot3StatsInternalMacReceiveErrorsRate
value for the
dot3_Ethernet_Performance_Port since
the last polling.
Port Internal Mac Determines the change in the SNMP Port (Dot3 ethernet)
Transmit Errors Rate dot3StatsInternalMacTransmitErrorsRate
value for the
dot3_Ethernet_Performance_Port since
the last polling.
High Discard Percentage Aggregate monitor that rolls up BPX Port (Cisco)
discard percentage health Interface
monitors. Network Adapter
Port
Token Ring Port
VR Interface
High Error Percentage Aggregate monitor that rolls up BPX Port (Cisco)
error percentage health Interface
monitors. Network Adapter
Port
Token Ring Port
VR Interface
High Queue Drop Aggregate monitor that rolls up BPX Port (Cisco)
Percentage queue drop percentage health Interface
monitors Network Adapter
Port
Token Ring Port
VR Interface
187
Monitor Description Targets
ping.
See Also
Monitoring Networks by Using Operations Manager
How to Discover Network Devices in Operations Manager
Network Device Discovery Settings
Run As Accounts for Network Monitoring in Operations Manager
How to Delete or Restore a Network Device in Operations Manager
Viewing Network Devices and Data in Operations Manager
Security for Servers Performing Network Discovery
Network Devices Supported for Discovery by Operations Manager
Reports for Network Monitoring in Operations Manager
Important
You must open the Operations console as an Operations Manager administrator to view
the dashboard views.
This topic describes the following views:
Network Summary Dashboard View
Network Node Dashboard View
Network Interface Dashboard View
Network Vicinity Dashboard
189
Network Interface Dashboard View
An interface is a physical entity with which network connections are made, such as a port. By
default, Operations Manager will only monitor ports that are connected to another device that is
being monitored. Ports that are not connected will not be monitored. Use the Network Interface
Dashboard view to view the following information:
Bytes sent and received over the past 24 hours
Packets sent and received over the past 24 hours
Interface properties
Send and receive errors and discards over the past 24 hours
Network interface usage percentage
Alerts generated by this interface
Alert details
Note
Because devices that use OSI layer 1, such as hubs, do not have MAC addresses, layer
1 devices will not be connected to computers in the Network Vicinity Dashboard. The
vicinity view will only show connections between layer 1 devices and layer 2 or 3 devices.
Note
190
Network adapters using NIC teaming will not be identified as “teamed” in the Network
Vicinity Dashboard.
Note
Virtual machines are associated with the same network device as their host. This version
of Operations Manager does not show a relationship between the two computers.
Note
Operations Manager does not display UNIX- and Linux-based devices in the Network
Vicinity Dashboard.
See Also
Monitoring Networks by Using Operations Manager
How to Discover Network Devices in Operations Manager
Network Device Discovery Settings
Run As Accounts for Network Monitoring in Operations Manager
How to Delete or Restore a Network Device in Operations Manager
Tuning Network Monitoring
Security for Servers Performing Network Discovery
Network Devices Supported for Discovery by Operations Manager
Reports for Network Monitoring in Operations Manager
191
All firewalls between the management servers in the resource pool and the network devices
need to allow SNMP (UDP) and ICMP bi-directionally, and ports 161 and 162 need to be
open bi-directionally. This includes Windows Firewall on the management server itself.
If your network devices are using a port other than 161 and 162, you need to open bi-
directional UDP traffic on these ports as well.
Important
Note for customers who used EMC Solutions for Microsoft System Center Operations
Manager: EMC Smarts included tools to create an isolation layer to prevent denial of
service attacks. In System Center 2012 – Operations Manager, you need to protect your
network against packet storms by using external tools.
See Also
Monitoring Networks by Using Operations Manager
How to Discover Network Devices in Operations Manager
Network Device Discovery Settings
Run As Accounts for Network Monitoring in Operations Manager
How to Delete or Restore a Network Device in Operations Manager
Viewing Network Devices and Data in Operations Manager
Tuning Network Monitoring
Network Devices Supported for Discovery by Operations Manager
Reports for Network Monitoring in Operations Manager
See Also
Monitoring Networks by Using Operations Manager
How to Discover Network Devices in Operations Manager
Network Device Discovery Settings
192
Run As Accounts for Network Monitoring in Operations Manager
How to Delete or Restore a Network Device in Operations Manager
Tuning Network Monitoring
Viewing Network Devices and Data in Operations Manager
Security for Servers Performing Network Discovery
Reports for Network Monitoring in Operations Manager
193
Memory Utilization
This report displays the percentage of free memory on a particular network device over a period
of time.
See Also
Monitoring Networks by Using Operations Manager
How to Discover Network Devices in Operations Manager
Network Device Discovery Settings
Run As Accounts for Network Monitoring in Operations Manager
How to Delete or Restore a Network Device in Operations Manager
Viewing Network Devices and Data in Operations Manager
Security for Servers Performing Network Discovery
Network Devices Supported for Discovery by Operations Manager
Tuning Network Monitoring
194
Other resources for this component
TechNet Library main page for Operations Manager
Operations Guide for System Center 2012 - Operations Manager
Initial Monitoring After Operations Manager Is Installed
Managing Access in Operations Manager
Getting Information from Operations Manager
General Tasks in Operations Manager
Maintenance of Operations Manager
Operations Manager Report Authoring Guide
Managing Discovery and Agents
195
a. In the Service level objective name text box, type a name for the service level
objective. For this scenario, type Availability.
b. From the Monitor drop-down list, choose the specific monitor that you want to use to
measure the objective. For this scenario, choose Availability.
c. Using the Service level objective goal (%) spin box, provide the numerical measure
for your objective. For example, select 99.990 to indicate that your goal is 99.99%
availability.
d. You can refine what the monitor tracks to determine availability by selecting or
clearing any of the following state criteria:
Unplanned maintenance
Unmonitored
Monitoring unavailable
Monitor disabled
Planned maintenance
Warning
13. Click OK.
14. On the Service Level Objectives page, click Add, and then click Collection rule SLO to
create a new collection rule. This rule will track the performance of the application
15. Define the performance collection rule as follows:
a. In the Service level objective name: text box, type a name for the service level
objective. For this scenario, type Performance.
b. Under Targeted class, click Select to open the Select a Target Class dialog box.
Specify the target class for the rule from the list of targets in the text box. Note that
this class must be contained in the distributed application. For this scenario, select
the specific class the rule is targeted to, such as Windows Server 2008 Operating
System.
c. Under Performance collection rule, click Select to open the Select a Rule dialog
box. Specify the performance collection rule to use. For this scenario, choose Collect
Processor\ % Processor Time performance counter, and then click OK.
d. Using one of the Aggregation method options, choose one of the following:
Average
Min
Max
e. Use the Service level objective goal drop-down list to specify either Less than or
More than, and enter a value in the adjacent text box. For this scenario, choose
Less Than and 80. This indicates that the performance goal is to never exceed 80%
processor time.
f. Click OK.
16. On the Service Level Objectives page, click Next.
17. On the Summary page, review the settings, and then click Finish.
18. When the Completion page appears, click Close.
196
After you create a service level objective, you can monitor it by using a Service Level
Tracking dashboard view and the Service Level Tracking Report.
See Also
Running a Service Level Tracking Report
Defining a Service Level Objective Against a Group
Creating a Service Level Dashboard
Monitoring Service Level Objectives by Using Operations Manager
See Also
Running a Service Level Tracking Report
Defining a Service Level Objective Against an Application
Creating a Service Level Dashboard
Monitoring Service Level Objectives by Using Operations Manager
198
4. Click Add SLA.
5. In SLA Name, type the name of the defined service level and then click Search.
6. Select the service level, and then click Add.
7. Click OK to close the Add SLA window.
8. Define the data period for the report. You can select the following options:
Data aggregation
Day range
Time range
9. Under Report Fields, select the fields that you want to include in the report. The fields
that are available depend on the day and time range selection. For example, if you have
specified a day range of Thursday to Wednesday, you do not have the option to include
the Last 30 Days field.
10. Click Run to generate the report.
See Also
Defining a Service Level Objective Against a Group
Defining a Service Level Objective Against an Application
Monitoring Service Level Objectives by Using Operations Manager
199
The gauge will show the average actual value, along with the target value and a indication as to
whether the value and goal relationship corresponds to success (green) or failure (red). The chart
will show a time history of the actual values, which will be a function of the aggregation of the
values in the data warehouse, which will depend on the timeframe of the configured dashboard,
as to whether the values come from the Hourly or Daily aggregation table.
200
9. Click Close.
See Also
Monitoring Service Level Objectives by Using Operations Manager
Defining a Service Level Objective Against an Application
Defining a Service Level Objective Against a Group
Additional views:
To see why a monitoring aspect is unhealthy, use the application group state view
and click the state view cell related to it. The Details View will show you the instance
and the state of the Availability, Configuration, Performance, and Security monitors.
You can also start the Health Explorer in context of the application instance to see
which monitors have gone into a critical or warning state.
Application group state view
202
To see application performance, in the application component folder, click All
Performance Data. This gives you the base information about each component,
shown by instance.
All performance data
To see the overall health dashboard view of the components you selected for the
application you are monitoring, in the application component folder, click Overall
Component Health. You will see the application state, active alerts, and a detail
203
view.
Overall component health
To work with data collected by client-side monitoring, in the Operations Manager console,
in the navigation pane, click the Monitoring button, expand Application Monitoring,
expand .NET Monitoring, and then application name (client) folder. The client-side
monitoring process is very similar to server-side monitoring, except that you click All
Performance Data and Overall Component Health in the application name (client)
folder to view alerts pertaining to the client-side monitoring for the application group.
To make sure client-side application monitoring is working, go to the application group
state view and the CSM Application Component will have application monitoring status
filled in.
Note
Client-side monitoring is an extension of server-side monitoring that is not
enabled by default. You set it up through the same template as server-side
monitoring. It might take a few minutes to discover the objects after you set up
client-side monitoring.
204
2. To see general details about an alert, click an alert. The Alert Details pane describes the
alert, including information about its source, rule, creation date, and the monitoring
setting that caused the alert to be raised.
3. To begin investigating an alert and view the alert description, double-click an alert. The
Alert Properties page will open.
Begin investigating alerts on the Alert Properties page
Note
205
To see details about an alert in any of these views, click the alert you want to
investigate and look in the Alert Details pane for the Knowledge section. You
can also open the Alert Properties page, which shows the details of an alert and
you can enter alert status. To open the Alert Properties page, double-click an
alert or in the Tasks pane, in the Tasks section, click Alert Properties.
4. On the Alert Properties page, click the link in the Alert Description pane. This opens
Application Diagnostics, a new monitoring feature in Operations Manager in a web
browser. Here on the Event properties tab you can see information, such as the
performance metrics, the call stack, and collection notes. For more information on the
Event properties tab, see Performance Event Details. Click Yes to close the main window
once the event information has loaded.
Note
This link to Application Diagnostics is also on the Alert Context tab.
5. Application Diagnostics Event properties
6. On the Event Properties tab, expand the Stack section. The stack is the order in which
events happened. The Resource Group View and Execution Tree View allow you to
expand nodes to investigate the various calls. This view helps answer which tier the
problem is in, or where is it occurring.
Application Diagnostics tree views lets you see exactly what went wrong where
and when.
206
7. To see how this event relates to other events in the chain of events, on the Application
Diagnostics page, click the Distributed chains tab. This view shows all of the
components that are involved in the request.
Application Diagnostics Distributed chains show how events relate to each other.
207
8. To pinpoint the root cause of the problem or incident, click the last event in the chain. This
is the latest event that broke the performance threshold. The Event Properties tab for
that event will open.
9. On the Application Diagnostics page, click the Performance counters tab.
Performance counters show the system 15 minutes before the event happened. This
gives a baseline measure before the event, which allows you to see your system state
before the event so that you know if the system was impacting the performance of the
application.
Application Diagnostics Performance counters allow you to compare system
performance before, during, and after an event.
208
10. On the Application Diagnostics page, click the Similar events tab. Similar events are
the other events that are in the same problem group. On this page you can filter similar
events by Problem and Heaviest Resource to help you identify trends.
Application Diagnostics Similar events allow you to compare similar events to
identify trends.
209
11. On the Application Diagnostics page, click the Related events tab. Related events are
events that occurred around the same time as the event you are investigating. Related
events tell you what else is going on about the same time as the event you are
investigating. You can increase or decrease the range of time in which other related
events occurred relative to the event you are investigating. In general, specifying a
greater time range shows you more related events.
Application Diagnostics Related events allows you to see what other events are
occurring about the same time as the event you are investigating.
210
Working with the Application Diagnostics Console
The Application Diagnostics console is an event management system for .NET Application
Performance Monitoring in System Center 2012 – Operations Manager. You can use Application
Diagnostics console to monitor deployed .NET applications for slowdowns, faults, and failures,
and immediately pinpoint the source of the problem.
211
To open the Application Diagnostics console
1. Application Diagnostics and Application Advisor are installed along with the Operations
Manager web console. To find the web address of the Operations Manager web console,
open the Operations console. In the navigation pane, click the Administration button,
click Settings, and then double-click Web Addresses. The Operations Manager web
console URL will be specified as: http(s)://<web host>/OperationsManager. Using this
URL format and the same web host, here are the links to Application Advisor and
Application Diagnostics:
The Application Diagnostics console address is: http(s)://<web host>/AppDiagnostics
The Application Advisor console address is: http(s)://<web host>/AppAdvisor
To make access to the consoles easy, add all three console URLs to your web browser’s
favorites list.
To open Application Diagnostics, paste the Application Diagnostics URL into your
browser. Application Diagnostics opens in the web browser window.
Note
If you are running Operations Manager on a server rather than a client computer,
you can access Application Diagnostics and Application Advisor from the Start
menu in All Programs.
Access to Application Diagnostics is controlled through the Application Monitoring
Operator and Administrator roles. You must be a member of one of these roles to have
rights to the console. For more information, see User Roles for Application Performance
Monitoring
212
Grouping Events within Areas of Interest
Grouping application events by similarity provides the best method for determining if the same
issue has occurred before and ensuring that resources responsible for the issue resolution are
allocated in the most efficient way.
213
To group application errors by exception class
1. Open Application Diagnostics and select Events from the Navigation pane.
2. In the Navigation pane, in the Search for menu, select Application Errors.
3. In the Group By menu, select Exception Class.
4. To sort by count, at the top of the Count column, click Count. The exception classes that
have occurred most often are ranked from highest to lowest.
5. To begin investigating the issue and open Event properties, click an Exception Class
entry. For information about working with events, see Working with Events by Using
Application Diagnostics
214
To group application errors by failed function
1. In the navigation pane, in the Search for menu, select Application Errors.
2. In the Group By menu, select Failed Function.
3. To sort by count, at the top of the Count column, click Count. The functions that have
failed most often are ranked from highest to lowest.
4. To begin investigating the issue and open Event properties, click a Failed Function entry.
For information about working with events, see Working with Events by Using Application
Diagnostics
215
See Also
Prioritizing Alerts by Using Application Advisor
Viewing and Investigating Alerts for .NET Applications (Server-side Perspective)
216
properties tab, see Performance Event Details. Click Yes to close the main window once
the event information has loaded.
Note
This link to Application Diagnostics is also on the on the Alert Context tab.
Use the following procedures to investigate your alert. IT Pros will most likely want to use
information on the Event properties, Performance counters, and Distributed chains tabs to find
out what happened, understand if a system issue caused the problem, and investigate where the
root cause occurred. Developers will most likely need to use the information on the Distributed
chains, Similar events, and Related events tabs to understand the specific context around a code
problem.
Tip
Use the same troubleshooting steps for Performance events, Similar events,
Related events, Distributed chains, and Performance counters as you did for
Exception events.
217
click the Event properties tab to view key details about the alert. This is the first place to
check to see if the alert problem is apparent. Some of the key categories of information
you will see on the Performance properties page are as follows:
Source To display the application load and response times, click the Source link in
the upper-left corner. This information shows the load the system was under in the
context of the exception event failure. To view performance counters and further
assess system state, on the Source page, click the Trend reports tab. To see which
computers this application is working on and see if there might be a load balancing
problem across computers, click the Computers tab. To see a breakdown of related
calls, or where the events are happening based on chains, click the Topology tab.
Slowest Nodes This is a list of the slowest nodes in the Execution Tree View and the
most likely cause of the performance issues in the application.
Stack This is the call stack, or order in which things happened. The Execution Tree
View allows you to expand nodes to investigate the calls. Click the Resource Group
View radio button to display an overview of where time was spent. This answers
which tier the problem is in—where is it occurring?
Collection Notes This displays any notes about the event.
1. To view a table or diagram of key performance counters, click the Performance
counters tab.
Note
Fifteen minutes of performance data is collected and cached on the monitored
system. When a performance or exception is raised, the performance data is
sent back to Operations Manager along with the event.
2. Select the performance counter checkboxes for the performance counters you want to
include in your information, and then click Apply.
3. Use the information in this display to assess the system performance state around the
event you are investigating. For example, if the performance is uniformly slow at the time
of the event, then your alert is likely due to a system performance problem.
218
Note
Get the time stamp from the call you select as you will pair this with an event on
the next page.
3. The Select Possible Chain Event page, select the event that you want to examine.
Ideally it will be the event with the time stamp that is closest to call you selected in the
Distributed Chains view.
4. What you see next depends on the kind of problem you are investigating. For example, if
you select a transaction where a server is not found, you might go to the event properties
page for that event. This will let you pair the server error with the event you were initially
investigating. Since it is a server error, you know that the problem is not on the client
side, but server side. You might see a graph of the event you selected and be able to
breakdown a performance event in terms of the page load time.
5. From event properties, click the server-side call, and click the Performance Counters
tab for more details.
219
give you a better idea of exactly how they are related. So, using the Similar Events filters,
you might find that most of your total events have the same problem as the event you are
viewing, that it is a performance problem, that they belong to an exception class you
configured, and that half of the similar events had the same failed function. Action: The
function goes to the developer who needs to update the function code.
220
Access to Application Advisor is controlled through the Application Monitoring Operator,
Report Operator and Administrator roles. You must be a member of Application
Monitoring Operator and Report Operator roles or the Administrator role. For more
information, see User Roles for Application Performance Monitoring
Access to Application Diagnostics is controlled through the Application Monitoring
Operator and Administrator roles. You must be a member of one of these roles to have
rights to the console.
Note
Application Advisor requires SQL Server Report Services (SSRS). You must have
Operations Manager reporting installed before using Application Advisor.
2. In the Navigation pane, in the All application groups dropdown menu, select whether
you want reports to include information for all application groups or a subset of
application groups.
Note
Application groups are created in the Application Diagnostics console. Use them
to create a group of applications to which you would like to scope your reports.
Using many application groups can have a performance impact.
3. In the Select report menu, select how you want to scope the reports, and then click the
report you want to run. You can scope reports by Client-Side Monitoring, Problem
Analysis Reports, Resource Utilization analysis, or choose just one of the individual
reports to view.
You can also select a report by clicking on one of the report graphics.
4. Use the Start Date and End Date fields to select the time or date range for the alerts you
want included in the reports.
5. Click the Status text box to filter alerts by those that are New, Reviewed, Deleted, or By
Design.
Tip
Viewing alerts categorized as By Design can show you if the way an application
is designed is actually causing issues.
6. Click Source dropdown menu to select the application component you want to include in
the report.
Note
Only applications that are part of the application group you initially selected are
available to be used as a source.
7. Click the Computer dropdown menu to select which computer or computers you want
reported on.
8. In the Problem dropdown menu, you can filter by all problems detected or only critical
problems.
9. Click Apply to save this report configuration and run the report.
221
To add an Application Advisor report to Favorites
1. If you want to save a report with certain scoped information that you can easily view later,
add it to your Favorites list. In the Select report menu or by clicking the report graphic,
select the report you want to run.
Note
You can scope the information you want included in the report before making it a
favorite or create the scoping information in the Favorite Management Wizard.
2. In the Results pane, to open the Favorite Management Wizard, click the Favorites icon.
3. In the Favorite Management Wizard, you can either keep the settings you used to scope
the information to be included in your report, reset them, or set them for the first time.
4. As you make or confirm your scoping settings, click Next to proceed through the wizard
settings pages, and then click Finish.
5. In the Favorites namespace, click Favorites and you will be able to view the report you
just configured.
6. To view a report in your Favorites, just click the report you want to view.
222
Overall Source Statistics section. This section shows you what percentage of
performance and exception events are being raised by the application resources,
such as function calls or database queries.
3. Click the first link in whichever view you want to investigate. This first link shows the
highest cause of alerts and launches a list of all problems related to that application or
source.
Important
This is the stage where you shift from a prioritized list to investigating individual
alerts related to the most important issue. None of the events in this list is more
important than another, but each can help highlight the route cause.
4. Click a link in Event Description and the Application Diagnostics Event Properties page
opens. Here you are viewing data about the event itself. And this is the place to start
troubleshooting. See Working with Events by Using Application Diagnostics for more
information.
Beginning with Event properties tab, use this and other tabs to discover more about what
happened, whether it was likely a system issue as shown by performance data, and what
application tier the problem occurred in, using distributed chains. Following this
information should reveal if it was a system problem or an application code problem, and
thus who should resolve the issue.
See Also
Working with the Application Diagnostics Console
Working with Events by Using Application Diagnostics
223
Administrat Autho Advance Applicatio Operat Read- Report Report
or r d n or Only Operat Security
Operator Monitorin Operat or Administrat
g or or
Operator
change
APM
settings
Note
* The Application Monitoring Operator role and Report Operator role are both required to
access Application Advisor.
224
Rule, and then select For all objects of class: .NET Application Monitoring Agent.
4. On the Override Properties page, in the Override-controlled parameters section,
select Sensitive data rules.
5. In the Sensitive data rules row, in the Override Value column, enter the formula for the
mask you want to apply, using the syntax <Hidden><Expression>((pwd|password)=?)
[^;]*</Expression><CompareExpression>((pwd|password)=?)[^;]*</
CompareExpression><Replacement>$1*****</Replacement><Type>all</Type></Hidden>,
where the <Expression> and <CompareExpression> use regular expression syntax and
<Replacement> defines the characters to use when masking out the actual value of the
parameter.
6. In the Management Pack section, select an existing management pack or create a new
one where the override will be stored.
7. Click OK.
Note
Methods can also be defined at the application group level and be applied to all
application components. To do this, follow the same steps after clicking the
Advanced Settings button on the Server-Side Defaults tab.
3. On the Modifying Settings page, click Set Methods. Specify the method name for the
function where you want to disable parameter collection, and then clear the Collect
function parameters checkbox.
Additionally, if you do not want to continue monitoring this method, clear the Enable
monitoring checkbox.
4. Click OK.
225
Pack Templates, click .NET Application Performance Monitoring, right-click the
application group you want to modify, and then click Properties.
2. On the Server-Side Defaults tab, click Advanced Settings.
3. On the Advanced settings page, click Exception Tracking.
4. On the Exception tracking list page, click Add, enter the namespace or class where
you want to stop collecting exceptions, and then clear the Enable monitoring checkbox.
5. Click OK.
See Also
Operations Manager Privacy Statement
Continuing to Use AVIcode 5.7 with System Center 2012 – Operations Manager
Features of AVIcode 5.7 and .NET Application Performance Monitoring can generally co-exist, but
some cannot. For example, the AVIcode 5.7 SEViewer and the new Application Diagnostics
cannot be installed on the same system. You can use both consoles in the same environment, but
they must be installed on separate IIS hosts.
226
Important
When monitoring applications using both AVIcode 5.7 and .NET Application Performance
Monitoring in Operations Manager, data is shown in the respective monitoring views. For
AVIcode 5.7, data continues to flow through SELog and SEViewer. For .NET Application
Performance Monitoring in Operations Manager, monitoring data is viewed in Application
Diagnostics.
Supported AVIcode Versions
Only AVIcode 5.7 when integrated with Operations Manager 2007 R2 with the latest cumulative
updates is supported. Previous AVIcode versions are not supported. AVIcode 5.7 functionality has
not been enhanced. The AVIcode 5.7 configurations you have been using to monitor applications
have not been converted to .NET Application Performance Monitoring configurations. When
upgrading from Operations Manager 2007 R2 to System Center 2012 – Operations Manager, you
need to manually import new AVIcode 5.7 management packs. For more information, see Steps
to import AVIcode 5.7 templates after upgrading.
How Upgrade Works with AVIcode 5.7 Agents and .NET Application Performance
Monitoring Agents
Upgrading to Operations Manager behaves this way:
Upgrading to Operations Manager is not blocked because AVIcode 5.7 agents are present.
When an Operations Manager 2007 R2 agent and an AVIcode 5.7 agent are found, the
upgrade to Operations Manager proceeds, but the .NET Application Performance Monitoring
service is not installed. The AVIcode 5.7 service is left instead.
You cannot have the AVIcode 5.7 service installed on the management servers. In
this case, you will need to remove the AVIcode 5.7 service before upgrading.
When Operations Manager 2007 R2 agents are found without AVIcode 5.7 on the system, the
upgrade to Operations Manager proceeds and the .NET Application Performance Monitoring
agent is installed.
If .NET Application Performance Monitoring has already been deployed and you try to install
AVIcode 5.7 on it, this is blocked through the push install. If you manually force it, you could
succeed, but the agents will conflict with one another and neither will work correctly. There it
is a monitor that targets activated Application Performance Monitoring agents that will put the
agent into a warning state if both the AVIcode 5.7 and the Operations Manager Application
Performance Monitoring agents are on the same server.
If you are using AVIcode 5.7 and do not want to install .NET Application Performance
Monitoring on your agent-managed computers, use the /NOAPM=1 agent manual install
command line switch to prevent .NET Application Performance Monitoring from being
installed. This leaves the AVIcode agent in place. For more information, see Install Agent
Using the Command Line.
Note
There is a monitor named AVIcode Intercept Service found that targets the Agent class in
System Center 2012 – Operations Manager that is disabled by default, but can be
227
enabled to monitor for the AVIcode agents on systems where the Operations Manager
agent is present alongside the AVIcode 5.7 service.
Manually Importing AVIcode 5.7 Management Packs
When the AVIcode.NET Enterprise Management Pack for Operations Manager 2007 is present in
the management group, Setup will continue, but some management packs will need to be
manually upgraded after setup has finished fixing incompatibilities with Operations Manager. The
management pack files are in the /SupportTools directory on the Operations Manager media.
They are not imported automatically.
The management packs that need to be imported are:
AVIcode.DotNet.SystemCenter.Enterprise.Monitoring.mpb
AVIcode.DotNet.SystemCenter.Client.Monitoring.mp
228
Operations Manager Report Authoring Guide
Accessing UNIX and Linux Computers in Operations Manager
Managing Discovery and Agents
229
Required Package Description Minimum Version
Protocol
HP-UX 11i v2 IA 64
230
Required Package Description Minimum Version
231
Required Package Description Minimum Version
Protocol
Solaris 9 SPARC
232
Required Package Description Minimum Version
Solaris 10 SPARC
233
Solaris 10 x86
234
Required Package Description Minimum Version
Modules
See Also
Using Templates for Additional Monitoring of UNIX and Linux
Troubleshooting UNIX and Linux Monitoring
Accessing UNIX and Linux Computers in Operations Manager
Required Capabilities for UNIX and Linux Accounts
Managing Certificates for UNIX and Linux Computers
Managing Resource Pools for UNIX and Linux Computers
Install Agent on UNIX and Linux Using the Discovery Wizard
See Also
Supported UNIX and Linux Operating System Versions
235
Troubleshooting UNIX and Linux Monitoring
Accessing UNIX and Linux Computers in Operations Manager
Required Capabilities for UNIX and Linux Accounts
Managing Certificates for UNIX and Linux Computers
Managing Resource Pools for UNIX and Linux Computers
Install Agent on UNIX and Linux Using the Discovery Wizard
See Also
Supported UNIX and Linux Operating System Versions
Using Templates for Additional Monitoring of UNIX and Linux
Accessing UNIX and Linux Computers in Operations Manager
Required Capabilities for UNIX and Linux Accounts
Managing Certificates for UNIX and Linux Computers
Managing Resource Pools for UNIX and Linux Computers
Install Agent on UNIX and Linux Using the Discovery Wizard
Certificate Issues
This topic describes resolutions to certificate issues for monitoring UNIX or Linux computers.
Certificate Signing Error Message
During the installation of UNIX/Linux agents, you might see the following error.
Event Type: Error
Date: 4/1/2009
Time: 4:02:27 PM
User: N/A
Computer: COMPUTER1
Description:
236
Unexpected ScxCertLibException: Can't decode from base64
This error occurs when the certificate signing module is called but the certificate itself is empty.
This error can be caused by an SSH connection failure to the remote system.
If you see this error, do the following:
1. Make sure that the SSH daemon on the remote host is running.
2. Make sure that you can open an SSH session with the remote host by using the credentials
specified in the Discovery Wizard.
3. Make sure that the credentials specified in the Discovery Wizard have the required privileges
for discovery. For more information see Required Capabilities for UNIX and Linux Accounts.
Certificate Name and Host Name do not Match
The common name (CN) that is used in the certificate must match the fully qualified domain name
(FQDN) that is resolved by Operations Manager. If the CN does not match, you will see the
following error when you run the Discovery Wizard:
The SSL certificate contains a common name (CN) that does not match the hostname
You can view the basic details of the certificate on the UNIX or Linux computer by entering the
following command:
openssl x509 -noout -in /etc/opt/microsoft/scx/ssl/scx.pem -subject -issuer -dates
When you do this, you will see output that is similar to the following:
subject= /DC=name/DC=newdomain/CN=newhostname/CN=newhostname.newdomain.name
issuer= /DC=name/DC=newdomain/CN=newhostname/CN=newhostname.newdomain.name
Validate the hostnames and dates and ensure that they match the name being resolved by the
Operations Manager management server.
If the hostnames do not match, use one of the following actions to resolve the issue:
If the UNIX or Linux hostname is correct but the Operations Manager management server is
resolving it incorrectly, either modify the DNS entry to match the correct FQDN or add an
entry to the hosts file on the Operations Manager server.
If the UNIX or Linux hostname is incorrect, do one of the following:
Change the hostname on the UNIX or Linux host to the correct one and create a new
certificate.
Create a new certificate with the desired hostname.
To Change the Name on the Certificate:
237
If the certificate was created with an incorrect name, you can change the host name and re-
create the certificate and private key. To do this, run the following command on the UNIX or Linux
computer:
/opt/microsoft/scx/bin/tools/scxsslconfig -f -v
/opt/microsoft/scx/bin/tools/scxadmin -restart
See Also
Using Templates for Additional Monitoring of UNIX and Linux
Troubleshooting UNIX and Linux Monitoring
Accessing UNIX and Linux Computers in Operations Manager
Required Capabilities for UNIX and Linux Accounts
Management Pack Issues
Operating System Issues
Logging and Debugging
Managing Certificates for UNIX and Linux Computers
Managing Resource Pools for UNIX and Linux Computers
Install Agent on UNIX and Linux Using the Discovery Wizard
Note
The ExecuteShellCommand parameter uses the default shell of the user who is running
the command. If you require a specific shell, use the ExecuteCommand parameter, and
prefix the command arguments with the required shell.
The following examples show how to use the ExecuteCommand and ExecuteShellCommand
parameters:
To pass the command-line arguments to the console without starting a shell process:
<p:ExecuteCommand_INPUT xmlns:p="http://schemas.microsoft.com/wbem/wscim/1/cim-
schema/2/SCX_OperatingSystem"> <p:Command> service syslog status </p:Command>
<p:timeout>10</p:timeout> </p:ExecuteCommand_INPUT>
To pass the command-line arguments to a shell process that references an explicit shell:
<p:ExecuteCommand_INPUT xmlns:p="http://schemas.microsoft.com/wbem/wscim/1/cim-
schema/2/SCX_OperatingSystem"> <p:Command> /bin/sh ps -ef syslog | grep -v grep
</p:Command> <p:timeout>10</p:timeout> </p:ExecuteCommand_INPUT>
To pass the command arguments to a shell process that uses the user's default shell:
<p:ExecuteShellCommand_INPUT xmlns:p="http://schemas.microsoft.com/wbem/wscim/1/cim-
schema/2/SCX_OperatingSystem"> <p:Command> uptime | awk '{print $10}' |awk -F","
'{print $1}' </p:Command> <p:timeout>10</p:timeout> </p:ExecuteShellCommand_INPUT>
See Also
Using Templates for Additional Monitoring of UNIX and Linux
Troubleshooting UNIX and Linux Monitoring
Accessing UNIX and Linux Computers in Operations Manager
Required Capabilities for UNIX and Linux Accounts
239
Certificate Issues
Operating System Issues
Logging and Debugging
Managing Certificates for UNIX and Linux Computers
Managing Resource Pools for UNIX and Linux Computers
Install Agent on UNIX and Linux Using the Discovery Wizard
240
attached to each zone that is configured on the Solaris-based server, Operations Manager
collects data for each network adapter.
See Also
Using Templates for Additional Monitoring of UNIX and Linux
Troubleshooting UNIX and Linux Monitoring
Accessing UNIX and Linux Computers in Operations Manager
Required Capabilities for UNIX and Linux Accounts
Management Pack Issues
Certificate Issues
Logging and Debugging
Managing Certificates for UNIX and Linux Computers
Managing Resource Pools for UNIX and Linux Computers
Install Agent on UNIX and Linux Using the Discovery Wizard
Note
Generally, it is the SYSTEM account making the calls, and C:\Windows\Temp is
the default SYSTEM temp folder.
After creation of the blank file, Operations Manager will immediately begin logging SSH and
Certificate activity to the \Temp directory.Scripts that call into SSH modules will log to
<Scriptname.vbs>.log. Other modules have their own logs.
In some cases, it may be required to restart the HealthService to get the
EnableOpsmgrModuleLogging logging to take effect.
241
These logs will report the UNIX agent actions. If there is a problem with the data returned to
Operations Manager, look in this log. These logs are used infrequently.
Note
WinRM is also known as WS-Management (WS-Man).
Note
The FormatTracing command opens a Windows Explorer window displaying the c:\
Windows\temp\OpsMgrTrace directory. The TracingGuidsNative.log file is in that
directory.
Use DebugView to Troubleshoot Discovery Issues
DebugView is an alternative method to EnableOpsmgrModuleLogging for troubleshooting
discovery issues.
To use DebugView
1. Download DebugView from: http://go.microsoft.com/fwlink/?Linkid=129486.
2. Launch DebugView on the Management Server performing the discovery.
3. Start discovering the UNIX Agents. You should start seeing output in your DebugView
242
windows.
4. DebugView will present a step-by-step readout of the discovery wizard process. This is
often the fastest method of troubleshooting discovery issues.
See Also
Using Templates for Additional Monitoring of UNIX and Linux
Troubleshooting UNIX and Linux Monitoring
Accessing UNIX and Linux Computers in Operations Manager
Required Capabilities for UNIX and Linux Accounts
Management Pack Issues
Operating System Issues
Certificate Issues
Managing Certificates for UNIX and Linux Computers
Managing Resource Pools for UNIX and Linux Computers
Install Agent on UNIX and Linux Using the Discovery Wizard
ACS Forwarders
The service that runs on ACS forwarders is included in the Operations Manager agent. By default,
this service is installed but not enabled when the Operations Manager agent is installed. You can
243
enable this service for multiple agent computers at the same time using the Enable Audit
Collection task. After you enable this service, all security events are sent to the ACS collector in
addition to the local Security log.
ACS Collector
The ACS collector receives and processes events from ACS forwarders and then sends this data
to the ACS database. This processing includes disassembling the data so that it can be spread
across several tables within the ACS database, minimizing data redundancy, and applying filters
so that unnecessary events are not added to the ACS database.
The number of ACS forwarders that can be supported by a single ACS collector and ACS
database can vary, depending on the following factors:
The number of events that your audit policy generates.
The role of the computers that the ACS forwarders monitor (such as domain controller versus
member server).
The level of activities on the computer.
The hardware on which the ACS collector and ACS database run.
If your environment contains too many ACS forwarders for a single ACS collector, you can install
more than one ACS collector. Each ACS collector must have its own ACS database.
The requirements for an ACS collector are as follows:
An Operations Manager management server
A member of an Active Directory domain
A minimum of 1 gigabyte (GB) of RAM, with 2 GB recommended
At least a 1.8 gigahertz (GHz) processor, with a 2.8 GHz processor recommended
10 GB of hard disk space available, at a minimum, with 50 GB recommended
On each computer on which you plan to install the ACS collector, you must download and install
the latest version of the Microsoft Data Access Components (MDAC) from the Microsoft Web site.
To learn more about MDAC, see at Learning Microsoft Data Access Components (MDAC).
ACS Database
The ACS database is the central repository for events that are generated by an audit policy within
an ACS deployment. The ACS database can be located on the same computer as the ACS
collector, but for best performance, each should be installed on a dedicated server.
The requirements for an ACS database are as follows:
Microsoft SQL Server 2005 or SQL Server 2008. You can choose an existing or new
installation of SQL Server. The Enterprise edition of SQL Server is recommended because of
the stress of daily ACS database maintenance.
A minimum of 1 GB of RAM, with 2 GB recommended
244
Note
If your SQL Server has more than 2 GB of memory some additional configuration
steps are needed. For more information and the steps needed, see at How to
configure SQL Server to use more than 2 GB of physical memory.
At least a 1.8 GHz processor, with a 2.8 GHz processor recommended
20 GB of hard disk space available, at a minimum, with 100 GB recommended
If you use SQL Server standard edition, the database must pause during daily maintenance
operations. This may cause the ACS collector queue to fill with requests from ACS forwarders. A
full ACS collector queue then causes ACS forwarders to be disconnected from the ACS collector.
Disconnected ACS forwarders reconnect after the database maintenance is complete and the
queue backlog is then processed. To ensure no audit events are lost, allocate a sufficient amount
of hard disk space for the local security log on all ACS forwarder.
SQL Server enterprise edition can continue to service ACS forwarder requests, although at a
lower performance level, during daily maintenance operations. For more information on the ACS
collector queue and ACS forwarder disconnection see Audit Collection Services Capacity
Planning and Monitoring Audit Collection Services Performance.
See Also
Collecting Security Events Using Audit Collection Services in Operations Manager
How to Configure Certficates for ACS Collector and Forwarder
Audit Collection Services Capacity Planning
Audit Collection Services Performance Counters
How to Enable Audit Collection Services (ACS) Forwarders
How to Enable Event Logging and ACS Rules on Solaris and AIX Computers
How to Filter ACS Events for UNIX and Linux Computers
Monitoring Audit Collection Services Performance
How to Remove Audit Collection Services (ACS)
Audit Collection Services Administration (AdtAdmin.exe)
247
this queue along with maintaining the correct amount of RAM on the ACS collector can improve
the performance of ACS.
You might want to adjust the value of one or more of the preceding registry entries, depending on
your environment. For best results, you should consider how a value change of one entry will
affect the rest. For example, the value of BackOffThreshold should always be less than
DisconnectThreshold, allowing the ACS collector to gracefully degrade performance when the
ACS database cannot keep up with demand.
248
ACS Collector Memory
Memory on the ACS collector is used for caching ACS events that need to be written to the ACS
database. The amount of memory needed by an ACS collector can vary depending on the
number of ACS forwarders connected and the number of events generated by your audit policy.
You can use the following formula, based on expected traffic, to calculate whether more memory
is needed for better ACS performance:
Recommended Memory = (M x .5)+(50 x N)+(S x .5)+(P x .1)
The formula variables are defined in the following table.
249
Var Definition Registry Key Entry Name
i-
abl
e
paramet
ers, to
avoid
unneces
sary
queries
to the
dtString
tables in
the ACS
database
.
Size of
the string
cache on
the ACS
collector,
expresse
d by the
maximu
m
number
of entries
the
cache
can hold.
On
average,
each
queue
entry
consume
s 512
bytes of
memory.
This
cache is
used for
250
Var Definition Registry Key Entry Name
i-
abl
e
event
record
data.
251
To reduce the number of events written to the ACS database, you can change your audit policy to
reduce the number of generated events or use filters, applied at the ACS collector, to discard
unnecessary events and keep them out of the ACS database. You can also reduce the number of
ACS forwarders that send events to the ACS database by deploying an additional ACS collector
and database so that fewer ACS forwarders are serviced by each ACS collector.
For more information on filters, see the AdtAdmin.exe /SetQuery. For more information on the
number of ACS forwarders that an ACS collector can support, see Collecting Security Events
Using Audit Collection Services in Operations Manager.
See Also
Collecting Security Events Using Audit Collection Services in Operations Manager
How to Configure Certficates for ACS Collector and Forwarder
Audit Collection Services Security
Audit Collection Services Performance Counters
How to Enable Audit Collection Services (ACS) Forwarders
How to Enable Event Logging and ACS Rules on Solaris and AIX Computers
How to Filter ACS Events for UNIX and Linux Computers
Monitoring Audit Collection Services Performance
How to Remove Audit Collection Services (ACS)
Audit Collection Services Administration (AdtAdmin.exe)
Collector Object
The following table describes each counter in the Collector performance object. If the counter
describes information that is added to a specific table in the ACS database, that table is defined in
the counter description.
252
Connected Clients
The number of ACS forwarders currently connected to the ACS collector.
253
Event time in collector in milliseconds
The amount of time, in milliseconds, between event arrival at the ACS collector and
insertion into the ACS database queues.
Incoming Events/sec
The total number of events arriving, per second, at the collector from all connected ACS
forwarders.
Registered Queries
The total number of subscription requests that WMI has received for ACS events since
the ACS Collector service was last started.
Note
Asset values are assigned automatically by the ACS collector. You can change the
assigned asset values using AdtAdmin.exe and the \UpdForwarder parameter. For more
information about the AdtAdmin.exe tool, see Audit Collection Services Administration
(AdtAdmin.exe).
The Collector Client performance object has two counters. The following table describes each of
these counters.
254
Average time between event generation
The average amount of time, in milliseconds, from the creation of an event to the time
the event arrives at the ACS collector.
Incoming Audits/sec
The total number of events sent to the ACS collector from the ACS forwarder.
See Also
Collecting Security Events Using Audit Collection Services in Operations Manager
How to Configure Certficates for ACS Collector and Forwarder
Audit Collection Services Capacity Planning
Audit Collection Services Security
How to Enable Audit Collection Services (ACS) Forwarders
How to Enable Event Logging and ACS Rules on Solaris and AIX Computers
How to Filter ACS Events for UNIX and Linux Computers
Monitoring Audit Collection Services Performance
How to Remove Audit Collection Services (ACS)
Audit Collection Services Administration (AdtAdmin.exe)
255
performed in the right pane.
4. In the details pane, click all agents that you want to enable as ACS forwarders. You can
make multiple selections by pressing CTRL or SHIFT.
5. In the Actions pane, under Health Service Tasks, click Enable Audit Collection to
open the Run Task - Enable Audit Collection dialog box.
6. In the Task Parameters section, click Override to open the Override Task Parameters
dialog box.
7. In the Override the task parameters with the new values section, click the
CollectorServer parameter; in the New Value column, type the FQDN of the ACS
collector; and then click Override.
Note
If you are enabling ACS on a gateway or management server and you do not
specify the CollectorServer parameter, the task will fail with a “Type Mismatch
Error.” To avoid this, provide a value for the override.
8. In the Task credentials section, click Other. In the User Name box, type the name of a
user account that belongs to the local Administrators group on the agent computers. In
the Password box, type the password for this user account. Click to expand the Domain
list to view the available domains, and then click the domain of the user account.
9. Click Run Task. The Task Status dialog box displays tracking the progress of the task.
10. When the task completes successfully, click Close.
See Also
Collecting Security Events Using Audit Collection Services in Operations Manager
How to Configure Certficates for ACS Collector and Forwarder
Audit Collection Services Capacity Planning
Audit Collection Services Performance Counters
Audit Collection Services Security
How to Enable Event Logging and ACS Rules on Solaris and AIX Computers
How to Filter ACS Events for UNIX and Linux Computers
Monitoring Audit Collection Services Performance
How to Remove Audit Collection Services (ACS)
Audit Collection Services Administration (AdtAdmin.exe)
How to Enable Event Logging and ACS Rules on Solaris and AIX
Computers
This topic does not apply to Windows computers.
By default, Solaris and AIX computers do not log audit events. The logging configuration is
controlled by the file located at /etc/syslog.conf. You must make edits to this file and then enable
ACS rules.
256
To Configure the Solaris Syslog
1. Add the following code to the syslog.conf file:
auth.info;local2.info /var/log/authlog
Note
Use the TAB key to separate log components from the log file names. Spaces do
not work.
2. Restart the Syslog daemon.
3. On Solaris 5.8 and 5.9, enter the following commands:
/etc/init.d/syslog stop
/etc/init.d/syslog start
The Syslog file is rotated when it becomes larger than 1 megabyte (MB) and the number
of rotated files is limited to 10.
Note
Use the TAB key to separate log components from the log file names. Spaces do
not work.
2. Enter the following command to refresh the computer’s configuration:
# refresh –s syslogd
257
click Override the Rule, and then click For all object of class for a class of objects to
be monitored by the rule.
5. Set the Enabled parameter to True, modify the Override Value to True, and then click
OK.
See Also
Collecting Security Events Using Audit Collection Services in Operations Manager
How to Configure Certficates for ACS Collector and Forwarder
Audit Collection Services Capacity Planning
Audit Collection Services Performance Counters
How to Enable Audit Collection Services (ACS) Forwarders
Audit Collection Services Security
How to Filter ACS Events for UNIX and Linux Computers
Monitoring Audit Collection Services Performance
How to Remove Audit Collection Services (ACS)
Audit Collection Services Administration (AdtAdmin.exe)
258
EventID=4658 OR EventID=5159)”.
For additional information about how to use AdtAdmin.exe, see Audit Collection Services
Administration (AdtAdmin.exe).
See Also
Collecting Security Events Using Audit Collection Services in Operations Manager
How to Configure Certficates for ACS Collector and Forwarder
Audit Collection Services Capacity Planning
Audit Collection Services Performance Counters
How to Enable Audit Collection Services (ACS) Forwarders
Audit Collection Services Security
Audit Collection Services Security
Monitoring Audit Collection Services Performance
How to Remove Audit Collection Services (ACS)
Audit Collection Services Administration (AdtAdmin.exe)
259
Important
Certificates used on various components in Operations Manager (for example, ACS
Collector, ACS Forwarder, agent, gateway server, or management server) must be issued
by the same CA.
On the computer hosting the ACS Collector:
Run ADTServer -c.
Map the ACS Forwarder Certificate in Active Directory.
In the Operations console, enable ACS.
On the computer hosting the ACS Forwarder:
Export the certificate to a disk, USB flash drive, or network share.
Run ADTAgent -c.
Note
You will need to copy this certificate to the computer hosting the ACS Collector,
so choose a location that the ACS Collector can read from, or consider saving
the certificate to a disk, USB flash drive, or network share. In addition, it is
recommended that you include the computer name in the file name if you are
exporting certificates from more than one computer.
261
17. On the File to Export page, ensure that the path and file name are correct, click Next,
and then click Finish.
See Also
Collecting Security Events Using Audit Collection Services in Operations Manager
Audit Collection Services Security
Audit Collection Services Capacity Planning
Audit Collection Services Performance Counters
How to Enable Audit Collection Services (ACS) Forwarders
How to Enable Event Logging and ACS Rules on Solaris and AIX Computers
How to Filter ACS Events for UNIX and Linux Computers
Monitoring Audit Collection Services Performance
How to Remove Audit Collection Services (ACS)
Audit Collection Services Administration (AdtAdmin.exe)
262
Collector Object
The following table describes each counter in the Collector performance object. If the counter
describes information that is added to a specific table in the ACS database, that table is defined in
the counter description.
Counter Description
DB Request Queue Length The number of requests from the ACS collector
currently waiting to be serviced by the ACS
database. These requests are used during
forwarder handshake and during database
maintenance. They are not part of normal event
handling.
263
Counter Description
ACS database.
Interface Audit Insertions/sec The number of event records, per second, sent
by the collector to Windows Management
Instrumentation (WMI) for forwarding to an
application outside of ACS.
Note
Asset values are assigned automatically by the ACS collector. You can change the
assigned asset values using AdtAdmin.exe and the \UpdForwarder parameter. For more
information about the AdtAdmin.exe tool, see Audit Collection Services Administration
(AdtAdmin.exe).
The Collector Client performance object has two counters. The following table describes each of
these counters.
Counter Description
Average time between event generation The average amount of time, in milliseconds,
264
Counter Description
See Also
Collecting Security Events Using Audit Collection Services in Operations Manager
How to Configure Certficates for ACS Collector and Forwarder
Audit Collection Services Capacity Planning
Audit Collection Services Performance Counters
How to Enable Audit Collection Services (ACS) Forwarders
Audit Collection Services Security
How to Filter ACS Events for UNIX and Linux Computers
Audit Collection Services Security
How to Remove Audit Collection Services (ACS)
Audit Collection Services Administration (AdtAdmin.exe)
265
collection services. The Audit Collection Services Collector Setup wizard starts.
3. On the Welcome page click Next.
4. On the ACS Collector Maintenance page, click Remove the ACS collector and then
click Next.
5. On the Summary page, the wizard lists the actions it performs to remove the ACS
collector. Review the list and click Next.
6. When the removal of the ACS collector is complete, click Finish.
4. In Name, type a descriptive name, such as ACS Forwarders, and a short description in
Description.
5. If necessary, click the Criteria tab. In Show data related to, click Agent and then click
OK.
6. In the Actions pane, under Health Service Tasks, click Disable Audit Collection. The
Run Task - Enable Audit Collection dialog box displays.
7. In the Specify the credentials you want to run the task with section, click Other. In
the User Name box, type the name of a user account that belongs to the local
Administrators group on the agent computers. In the Password box, type the password
for this user account. Click to expand the Domain drop-down list to view the available
domains, and then click the domain of the user account.
8. Click Run Task. The Task Status dialog box displays tracking the progress of the task.
9. When the task completes successfully, click Close.
266
Audit Collection Services Security
How to Filter ACS Events for UNIX and Linux Computers
Monitoring Audit Collection Services Performance
Audit Collection Services Security
Audit Collection Services Administration (AdtAdmin.exe)
AdtAdmin Syntax
AdtAdmin has 12 parameters, each of which has a few to several subparameters. The general
syntax of AdtAdmin is as follows:
AdtAdmin.exe /<Parameter> [/<Subparameter>:<Value>]
The following table lists each parameter of AdtAdmin along with a description. For more
information about the syntax of a specific parameter, click the name of the parameter in the table
to link to the topic that describes it.
Parameter Description
267
Parameter Description
AdtAdmin.exe /UpdForwarder Allows you to change the name and the value
of an ACS forwarder and also to change the
group to which an ACS forwarder belongs
Common Subparameters
Each AdtAdmin parameter has from a few to several subparameters. The subparameters allow
you to apply a command to a specific ACS collector, a specific ACS forwarder, or group of
forwarders and are the same for most AdtAdmin parameters. The subparameters, defined in the
following table, can be used with an AdtAdmin parameter unless otherwise noted.
Subparameter Description
268
Subparameter Description
See Also
Collecting Security Events Using Audit Collection Services in Operations Manager
How to Configure Certficates for ACS Collector and Forwarder
Audit Collection Services Capacity Planning
Audit Collection Services Performance Counters
How to Enable Audit Collection Services (ACS) Forwarders
Audit Collection Services Security
How to Filter ACS Events for UNIX and Linux Computers
Monitoring Audit Collection Services Performance
How to Remove Audit Collection Services (ACS)
Audit Collection Services Security
269
AdtAdmin.exe /AddGroup
The /AddGroup parameter creates a group that is used to organize ACS forwarders. The group
does not contain any ACS forwarders when it is created. Use the /UpdForwarder parameter to
add ACS forwarders to a group. This command does not generate output. You can use the
/ListGroups parameter to verify that the group was created.
Syntax
AdtAdmin.exe /AddGroup [/Collector:<CollectorName>] [/Group:<GroupName>]
Subparameter Description
Example
Use the following example to create a group called "Accounting Computers":
adtadmin /addgroup /group:"Accounting Computers"
See Also
Audit Collection Services Administration (AdtAdmin.exe)
AdtAdmin.exe /DelGroup
AdtAdmin.exe /Disconnect
AdtAdmin.exe /GetDBAuth
AdtAdmin.exe /GetQuery
AdtAdmin.exe /ListForwarders
AdtAdmin.exe /ListGroups
AdtAdmin.exe /SetDBAuth
AdtAdmin.exe /SetQuery
AdtAdmin.exe /Stats
AdtAdmin.exe /UpdForwarder
AdtAdmin.exe /UpdGroup
AdtAdmin.exe /DelGroup
The /DelGroup parameter deletes a group from an ACS collector by using its name or group
identification number. When a group is deleted, the forwarders that belong to the group are not
deleted. Any forwarders assigned to a group when it is deleted are added to or still belong to the
default top-level groups.
270
No output is generated from this command. You can use the /ListGroups parameter to verify that
the group was created and also to determine a group’s assigned identification number.
Syntax
AdtAdmin.exe /DelGroup [/Collector:<CollectorName>] {[/Group:<GroupName>] |
[/GroupID:<IdentificationNumber>]}
Subparameter Description
Example
Use the following example to delete an ACS group that has the name "Accounting Computers":
adtadmin /delgroup /group:"Accounting Computers"
See Also
Audit Collection Services Administration (AdtAdmin.exe)
AdtAdmin.exe /AddGroup
AdtAdmin.exe /Disconnect
AdtAdmin.exe /GetDBAuth
AdtAdmin.exe /GetQuery
AdtAdmin.exe /ListForwarders
AdtAdmin.exe /ListGroups
AdtAdmin.exe /SetDBAuth
AdtAdmin.exe /SetQuery
AdtAdmin.exe /Stats
AdtAdmin.exe /UpdForwarder
AdtAdmin.exe /UpdGroup
AdtAdmin.exe /Disconnect
The /Disconnect parameter disconnects a specified ACS forwarder or group of forwarders from
the ACS collector. No output is generated from the /Disconnect parameter. To check an ACS
271
forwarder’s status after using the /Disconnect parameter, use the/Connected subparameter of the
/Stats parameter.
Syntax
AdtAdmin.exe /Disconnect [/Collector:<CollectorName>] {/Forwarder:<Name> |
/ForwarderSid:<SID> | /Group:<GroupName> | /GroupID:<IdentificationNumber> |
/Value:<ValueNumber>}
Subparameter Definition
272
Example
This example disconnects an ACS forwarder named Server1:
adtadmin /disconnect /forwarder:"Server1"
See Also
Audit Collection Services Administration (AdtAdmin.exe)
AdtAdmin.exe /AddGroup
AdtAdmin.exe /DelGroup
AdtAdmin.exe /GetDBAuth
AdtAdmin.exe /GetQuery
AdtAdmin.exe /ListForwarders
AdtAdmin.exe /ListGroups
AdtAdmin.exe /SetDBAuth
AdtAdmin.exe /SetQuery
AdtAdmin.exe /Stats
AdtAdmin.exe /UpdForwarder
AdtAdmin.exe /UpdGroup
AdtAdmin.exe /GetDBAuth
The /GetDBAuth parameter displays the current authentication method used by the ACS collector
to access the ACS database. The two available authentication methods are Windows
Authentication and SQL authentication. If SQL authentication is used, the /GetDBAuth parameter
displays the name of the user account currently in use by the ACS collector to connect to the ACS
database.
Syntax
AdtAdmin.exe /GetDBAuth [/Collector:<CollectorName>]
Subparameter Definition
Example
This example retrieves the authentication method used by the ACS collector to connect to the
ACS Database. In the following example, the local ACS collector is assumed:
AdtAdmin /GetDBAuth
See Also
273
Audit Collection Services Administration (AdtAdmin.exe)
AdtAdmin.exe /AddGroup
AdtAdmin.exe /DelGroup
AdtAdmin.exe /Disconnect
AdtAdmin.exe /GetQuery
AdtAdmin.exe /ListForwarders
AdtAdmin.exe /ListGroups
AdtAdmin.exe /SetDBAuth
AdtAdmin.exe /SetQuery
AdtAdmin.exe /Stats
AdtAdmin.exe /UpdForwarder
AdtAdmin.exe /UpdGroup
AdtAdmin.exe /GetQuery
The /GetQuery parameter lists the Windows Management Instrumentation (WMI) Query
Language (WQL) queries that are currently in use as filters on the ACS collector(s). Only the
/Collector subparameter applies to the /GetQuery parameter.
Note
The /SetQuery parameter applies a WQL filter. For more information about the /SetQuery
parameter, see AdtAdmin.exe /SetQuery.
Syntax
AdtAdmin.exe /GetQuery [/Collector:CollectorName]
Subparameter Definition
See Also
Audit Collection Services Administration (AdtAdmin.exe)
AdtAdmin.exe /AddGroup
AdtAdmin.exe /DelGroup
AdtAdmin.exe /Disconnect
AdtAdmin.exe /GetDBAuth
AdtAdmin.exe /ListForwarders
AdtAdmin.exe /ListGroups
AdtAdmin.exe /SetDBAuth
274
AdtAdmin.exe /SetQuery
AdtAdmin.exe /Stats
AdtAdmin.exe /UpdForwarder
AdtAdmin.exe /UpdGroup
AdtAdmin.exe /ListForwarders
The /ListForwarders parameter lists the ACS forwarders, along with some statistics on each, that
have ever connected to the ACS collector. The data that displays is a subset of the data that
displays using the /Stats parameter. If no subparameters are used, all ACS forwarders that have
ever connected to the ACS collector are included. If you specify an ACS group, all ACS
forwarders that belong to the group are listed.
Syntax
AdtAdmin.exe /ListForwarders [/Collector:<CollectorName>] {/[Forwarder:<Name>] |
[/ForwarderSid:<SID>] | } {[/Group:<GroupName>] | [/GroupID:<IdentificationNumber>] |
[/Value:<ValueNumber>]}
Subparameter Definition
Examples
Use the following example to list all ACS forwarders, along with some statistics on each, that
have connected to this ACS collector:
adtadmin /listforwarders
Use the following example to list the ACS forwarders, along with some statistics on each, that
belong to the ACS group that has a group identification number of 4:
adtadmin /listforwarders /groupid:4
Note
Use quotation marks if the name contains spaces.
Use the following example to list statistics on an ACS forwarder that has the name PC 101:
adtadmin /listforwarders /forwarder:"PC 101"
See Also
Audit Collection Services Administration (AdtAdmin.exe)
AdtAdmin.exe /AddGroup
AdtAdmin.exe /DelGroup
AdtAdmin.exe /Disconnect
AdtAdmin.exe /GetDBAuth
AdtAdmin.exe /GetQuery
AdtAdmin.exe /ListGroups
AdtAdmin.exe /SetDBAuth
AdtAdmin.exe /SetQuery
AdtAdmin.exe /Stats
AdtAdmin.exe /UpdForwarder
AdtAdmin.exe /UpdGroup
276
AdtAdmin.exe /ListGroups
The output of the /ListGroups parameter is a comma-separated list of groups that is maintained
by an ACS collector. If no subparameters are used, all groups from this ACS collector are listed.
None of the subparameters that specify individual ACS forwarders apply to the /ListGroups
parameter.
Syntax
AdtAdmin.exe /ListGroups [/Collector:<CollectorName>] {[/Group:<GroupName>] |
[/GroupID:<IdentificationNumber>] | [/Value:<ValueNumber>]}
Subparameter Definition
Example
Use the following example to list all ACS groups defined on this ACS collector:
adtadmin /listgroups
See Also
Audit Collection Services Administration (AdtAdmin.exe)
277
AdtAdmin.exe /AddGroup
AdtAdmin.exe /DelGroup
AdtAdmin.exe /Disconnect
AdtAdmin.exe /GetDBAuth
AdtAdmin.exe /GetQuery
AdtAdmin.exe /ListForwarders
AdtAdmin.exe /SetDBAuth
AdtAdmin.exe /SetQuery
AdtAdmin.exe /Stats
AdtAdmin.exe /UpdForwarder
AdtAdmin.exe /UpdGroup
AdtAdmin.exe /SetDBAuth
The /SetDBAuth parameter specifies the authentication method that the ACS collector uses to
access the ACS database. The two available authentication methods are Windows Authentication
and SQL authentication. Windows Authentication is the most secure method but can be used only
if the computer that runs the ACS collector and the computer that hosts the ACS database belong
to the same Active Directory domain or to domains that trust each other.
Using the /Name and the /Pwd subparameters automatically configures the ACS collector to use
SQL authentication. To check which authentication method the ACS collector is using, run the
/GetDBAuth parameter.
Syntax
To specify that the ACS collector use Windows Authentication, use the following syntax:
AdtAdmin.exe /SetDBAuth [/Collector:<CollectorName>]
To specify that the ACS collector use SQL authentication and identify the user name and
password of the user account that can access the ACS database, use the following syntax:
AdtAdmin.exe /SetDBAuth [/Collector:<CollectorName>] /Name:<UserAccount> /Pwd:<Password>
Subparameter Description
278
Subparameter Description
Example
Use the following example to change the user account used by the ACS collector to connect to
the ACS Database to an account that has a user name of "SQLDatabase" and a password of
"SQLPass#1":
AdtAdmin /SetDBAuth /Name:SQLDatabase /Password:SQLPass#1
See Also
Audit Collection Services Administration (AdtAdmin.exe)
AdtAdmin.exe /AddGroup
AdtAdmin.exe /DelGroup
AdtAdmin.exe /Disconnect
AdtAdmin.exe /GetDBAuth
AdtAdmin.exe /GetQuery
AdtAdmin.exe /ListForwarders
AdtAdmin.exe /ListGroups
AdtAdmin.exe /SetQuery
AdtAdmin.exe /Stats
AdtAdmin.exe /UpdForwarder
AdtAdmin.exe /UpdGroup
AdtAdmin.exe /SetQuery
An ACS collector can use Windows Management Instrumentation (WMI) Query Language (WQL)
queries as filters to limit the events that are stored in the ACS database. The /SetQuery
parameter implements the filter before events are saved to the ACS database. For more
information on WQL and WQL queries, see Querying with WQL.
Note
Because ACS supports only event queries, it does not support WQL aggregation
operators.
Syntax
AdtAdmin.exe /SetQuery [/Collector:CollectorName] /Query:QuerySyntax
Subparameter Definition
Example
This example uses the /SetQuery parameter to define a WQL query that filters out specified
events. When applied, this query filters out events generated by System, Local Service, and
Network Service services, and it also filters events that have specified event ID numbers.
adtadmin /setquery /collector:"Collector Name" /query:"SELECT * FROM AdtsEvent WHERE NOT
((HeaderUser='SYSTEM' OR HeaderUser='LOCAL SERVICE' OR HeaderUser='NETWORK SERVICE') OR
(EventId=538 OR EventId=566 OR EventId=672 OR EventId=680 OR (EventId>=541 AND
EventId<=547))"
See Also
Audit Collection Services Administration (AdtAdmin.exe)
AdtAdmin.exe /AddGroup
AdtAdmin.exe /DelGroup
AdtAdmin.exe /Disconnect
AdtAdmin.exe /GetDBAuth
AdtAdmin.exe /GetQuery
AdtAdmin.exe /ListForwarders
AdtAdmin.exe /ListGroups
AdtAdmin.exe /SetDBAuth
AdtAdmin.exe /Stats
AdtAdmin.exe /UpdForwarder
AdtAdmin.exe /UpdGroup
AdtAdmin.exe /Stats
The /Stats parameter lists statistical information about ACS forwarders that are connected to the
ACS collector. These statistics include identification numbers, SIDs, names, and assigned value
numbers. The /Stats parameter is used to verify recently completed configuration changes and to
retrieve information that is needed when using other AdtAdmin parameters, such as /Disconnect
or /Setquery. All ACS collectors, ACS groups, and ACS forwarders are included in the list unless
you specify otherwise. Also, every statistic is listed, by default. If you want only a single statistic,
you can specify which statistic that you want to display as part of the command syntax.
Syntax
280
After you chose a parameter, you can then choose to list all statistics or you can choose to list a
particular statistic. This topic includes a table of the parameters that specify the ACS forwarder or
group of ACS forwarders that you want to list and a second table that includes the individual
statistic subparameters that you can specify.
The syntax of the AdtAdmin.exe /Stats parameter is as follows:
AdtAdmin.exe /Stats [/Collector:<CollectorName>] {/[Forwarder:<Name>] |
[/ForwarderSid:<SID>] | [/Value:<ValueNumber>} | {[/Group:<GroupName>] |
[/GroupID:<IdentificationNumber>]} [<StatisticParameter>]
Subparameter Definition
281
Subparameter Definition
The following table lists the available statistic parameters. If you do not list a statistic parameter,
all statistics display.
282
Statistic Parameter Definition
See Also
Audit Collection Services Administration (AdtAdmin.exe)
AdtAdmin.exe /AddGroup
AdtAdmin.exe /DelGroup
AdtAdmin.exe /Disconnect
AdtAdmin.exe /GetDBAuth
AdtAdmin.exe /GetQuery
AdtAdmin.exe /ListForwarders
AdtAdmin.exe /ListGroups
AdtAdmin.exe /SetDBAuth
AdtAdmin.exe /SetQuery
AdtAdmin.exe /UpdForwarder
AdtAdmin.exe /UpdGroup
AdtAdmin.exe /UpdForwarder
Using the /UpdForwarder parameter, you can change the name and the value of an ACS
forwarder and also change the group membership of an ACS forwarder.
Syntax
AdtAdmin.exe /UpdForwarder [/Collector:<CollectorName>] {/Forwarder:<Name> |
/ForwarderID:<ForwarderIDNumber> | /ForwarderSid:<SID> | /Group:<GroupName> |
/GroupID:<IdentificationNumber> | /GroupValue:<ValueNumber> | /Value:<ValueNumber>}
{/Name:<NewName> | /Value:<NewValueNumber> /GroupValue:<NewValue>}
Subparameter Definition
283
Subparameter Definition
Example
In this example, an ACS forwarder identified as Server1 has a current connection value of 5. This
connection value is changed to 3:
adtadmin /updforwarder /forwarder:Server1 /value:5 /value:3
In this example, a group that contains the ACS forwarder named "Accounting Computer" is
assigned a new configuration value of 2:
284
adtadmin /updforwarder /forwarder:"Accounting Computer" /groupvalue:2
In this example, the connection value of a group, specified by its identification number, is changed
to 50:
adtadmin /updforwarder /forwarderid:1 /value:50
Note
An ACS forwarder can be a member of only one group at a time. If the ACS forwarder is
already a member of an ACS group, running this command removes the forwarder from
that group. All names with spaces must be contained within parentheses.
See Also
Audit Collection Services Administration (AdtAdmin.exe)
AdtAdmin.exe /AddGroup
AdtAdmin.exe /DelGroup
AdtAdmin.exe /Disconnect
AdtAdmin.exe /GetDBAuth
AdtAdmin.exe /GetQuery
AdtAdmin.exe /ListForwarders
AdtAdmin.exe /ListGroups
AdtAdmin.exe /SetDBAuth
AdtAdmin.exe /SetQuery
AdtAdmin.exe /Stats
AdtAdmin.exe /UpdGroup
AdtAdmin.exe /UpdGroup
The /UpdGroup parameter renames an existing group. Groups are used in ACS to organize ACS
forwarders.
Syntax
AdtAdmin.exe /UpdGroup {/Group:<ExistingName> | /GroupID:<IdentificationNumber>}
/Name:<NewName>
Subparameter Description
285
Subparameter Description
Note
A group’s identification number can be obtained using the AdtAdmin /ListGroups
command.
Example
Use the following example to rename the Accounting Computers ACS group to "Desktop
Computers":
AdtAdmin /UpdGroup /Group:"Accounting Computers" /Name:"Desktop Computers"
See Also
Audit Collection Services Administration (AdtAdmin.exe)
AdtAdmin.exe /AddGroup
AdtAdmin.exe /DelGroup
AdtAdmin.exe /Disconnect
AdtAdmin.exe /GetDBAuth
AdtAdmin.exe /GetQuery
AdtAdmin.exe /ListForwarders
AdtAdmin.exe /ListGroups
AdtAdmin.exe /SetDBAuth
AdtAdmin.exe /SetQuery
AdtAdmin.exe /Stats
AdtAdmin.exe /UpdForwarder
286
Connections to Other Management Systems
Product connectors allow communication between Operations Manager and other management
systems, regardless of whether Operations Manager is the highest level management system or
not. If Operations Manager is not the top-tier management system, a product connector can
forward all Windows-generated alerts for consolidation at another management system. If the
connector is bidirectional, Operations Manager can update the state of the monitored component
in the Operations Console when it receives notification from the top-level management system. If
Operations Manager is the top-tier management system, a product connector allows it to receive
and consolidate alert information from another management system.
Note
You must have a product connector installed prior to beginning this procedure. Install the
product connector according to the product connector vendor's installation instructions.
Note
Operations Manager internal product connectors are listed in the Operations
console. These connectors are used for discovery workflows. Do not create
subscriptions for these internal product connectors.
4. On the General page, type a name and a short description for the subscription you are
creating, and then click Next.
5. On the Groups page, you can filter which alerts this connector forwards to an external
management system based on groups. By default, all check boxes are selected, so alerts
from all groups are forwarded. To enable the child check boxes, clear the top-level check
box. After you make your selections, click Next.
6. On the Targets page, you can filter which alerts this connector forwards based on object
type. By default, alerts are accepted from all object types in all management packs. You
can specify particular management packs or certain monitored objects from which you
want to forward alerts. To accept alerts from only specified types of objects, click
Forward alerts from targets explicitly added to the 'Approved targets' grid are
approved and then click the Add button to select individual targets.
7. On the Criteria page, you can filter which alerts this connector forwards based on the
severity, priority, resolution state, and category of the alert. By default, all criteria are
selected, so all alerts are forwarded. However, you can individually select which alerts
you want forwarded. After you make your selections, click Create to create the product
connector subscription. You can view the newly created subscription in the details pane.
See Also
Connecting Operations Manager With Other Management Systems
288
Monitoring Operations Manager from a Second Management
Group
Businesses using System Center 2012 – Operations Manager in multiple management groups
sometimes want to monitor one management group from another management group. This topic
provides some tips for monitoring one management group (management group A) from a second
management group (management group B).
You can install an agent on management servers in management group A from management
group B. If you install the agent manually, configure the agent to report to a management
server in management group B.
Disable Active Directory integration for the agent you install on the management server in
management group A.
To upgrade the management server in management group A, you must remove the
management group B agent first.
After the agent is installed, ensure that you do not configure the agent to also report to
management group A (“multihome” the agent).
Ensure that the Run As accounts for the Default Action Account and Privileged Monitoring
Account profiles for the management server in management group B are using credentials
that can remotely authenticate and that have sufficient permissions on the management
servers in management group A.
See Also
Operations Manager Monitoring Scenarios
Integrating Active Directory and Operations Manager
Connecting Operations Manager With Other Management Systems
Collecting Security Events Using Audit Collection Services in Operations Manager
Monitoring UNIX and Linux Computers by Using Operations Manager
Monitoring .NET Applications
Monitoring Service Level Objectives by Using Operations Manager
Monitoring Networks by Using Operations Manager
Monitoring Clusters by Using Operations Manager
Client Monitoring Using Agentless Exception Monitoring in Operations Manager
Monitoring Across Untrusted Boundaries in Operations Manager
Agentless Monitoring in Operations Manager
289
Note
How to Create an Active Directory Domain Services Container for a Management Group
How to Use Active Directory Domain Services to Assign Computers to Management Servers
Changing the Active Directory Integration Setting for an Agent
290
Note
2. An Operations Manager administrator uses the Agent Assignment and Failover Wizard to
assign computers to a primary management server and secondary management server.
Domain controllers cannot be assigned to a management group using Active
Directory Domain Services.
3. The Operations Manager agent is deployed using MOMAgent.msi to the desired computers
and configured to get its management group information from Active Directory.
Active Directory Integration is disabled for agents that were installed from the
Operations console. By default, Active Directory Integration is enabled for agents
installed manually using MOMAgent.msi. To disable Active Directory Integration for
manual installs, use the command line parameter USE_SETTINGS_FROM_AD=0 as
explained in Install Agent Using the Command Line.
Configuring agents to get their management group information from AD DS is also helpful if your
organization uses images to deploy computers. For example, add the Operations Manager agent
to the SQL Server 2005 image and configure the agent to get its management group information
from Active Directory. When you bring up a new SQL Server 2005 server from an image, the
server is automatically configured to be managed by the appropriate Operations
Manager management group and download the applicable management packs.
See Also
Integrating Active Directory and Operations Manager
How to Create an Active Directory Domain Services Container for a Management Group
How to Use Active Directory Domain Services to Assign Computers to Management Servers
Changing the Active Directory Integration Setting for an Agent
Important
You must put a value inside quotation marks if the value contains a space.
ManagementGroupName is the name of the management group for which an AD container is
being created.
291
Note
MOMAdminSecurityGroup is a domain security group, domain\security_group format, which
is a member of the Operations Managers Administrators security role for the management group.
For Active Directory integration to work, the security group must be either a global security
group (if Active Directory integration needs to function in multiple domains with 2 way trusts)
or a local domain group (if Active Directory integration is only used in one domain)
To make a security group to be the Management Group Operations Manager Group
Administrator, use the following procedure.
a. In Operations console, select Administration.
b. In the Administration workspace, select User Roles under Security.
c. In User Roles, select Operations Manager Administrators and click the Properties
action or right click Operations Manager Administrators and select Properties.
d. Click Add to open the Select Group dialog box.
e. Select the desired security group, and then click OK to close the dialog box.
f. Click OK to close User Role Properties.
We recommend one security group, which might contain several groups, be used for
the Operations Manager Administrators role. That way, groups and members of
groups can be added and removed from groups without a domain administrator
needing to perform manual steps to assign them Read and Delete Child permissions
to the Management Group container.
RunAsAccount: This is the domain account which will be used by the management server to
read, write, and delete objects in AD. Use the format domain\username.
Domain is the name of the domain in which the management group container will be created.
MOMADAdmin.exe can be run across domains only if a two-way trust exists between them.
292
See Also
Integrating Active Directory and Operations Manager
Using Active Directory Domain Services to Assign Computers to Operations Manager
Management Groups
How to Use Active Directory Domain Services to Assign Computers to Management Servers
Changing the Active Directory Integration Setting for an Agent
Important
The Active Directory Domain Services container for the management group must be
created prior to running the Agent Assignment and Failover Wizard.
The Agent Assignment and Failover Wizard does not deploy the agent. You must deploy the
agent to the computers using MOMAgent.msi.
Changing the agent assignment rule can result in computers no longer being assigned to, and
therefore monitored by, the management group. The state of these computers will change to
critical, because the computers no longer send heartbeats to the management group. These
computers can be deleted from the management group and, if the computer is not assigned to
other management groups, the Operations Manager agent can be uninstalled.
Note
Gateway servers work like management servers in this context.
5. In the Management Server Properties dialog box, click the Auto Agent Assignment
tab, and then click Add to start the Agent Assignment and Failover Wizard.
To use the Operations Manager Agent Assignment and Failover Wizard to assign
computers to a management group
293
1. In the Agent Assignment and Failover Wizard, on the Introduction page, click Next.
Note
The Introduction page does not appear if the wizard has been run and Do not
show this page again was selected.
2. On the Domain page, do the following:
Note
To assign computers from multiple domains to a management group, run the
Agent Assignment and Failover Wizard for each domain.
Select the domain of the computers from the Domain name drop-down list. The
management server and all computers in the AD Agent Assignment resource pool
must be able to resolve the domain name.
Important
The management server and the computers that you want to manage must
be in two-way trusted domains.
Set Select Run As Profile to the Run As profile associated with the Run As account
provided when MOMADAdmin.exe was run for the domain. The default account used
to perform agent assignment is the default action account specified during Setup,
also referred to as the Active Directory Based Agent Assignment Account. This
account represents credentials used when connecting to the specified domain’s
Active Directory and modifying Active Directory objects, and should match the
account specified when running MOMAdmin.exe. If this was not the account used to
run MOMADAdmin.exe, select Use a different account to perform agent
assignment in the specified domain, and then select or create the account from
the Select Run As Profile drop-down list. The Active Directory Based Agent
Assignment Account profile must be configured to use an Operations Manager
administrator account which is distributed to all servers in the AD Agent Assignment
resource pool.
Note
For more information about Run As profiles and Run As accounts, see
Managing Run As Accounts and Profiles.
3. On the Inclusion Criteria page, either type the LDAP query for assigning computers to
this management server in the text box and then click Next, or click Configure. If you
click Configure, do the following:
a. In the Find Computers dialog box, type the desired criteria for assigning computers
to this management server.
b. Click OK, and then click Next.
Note
The following LDAP query will return computers with a name starting with
MsgOps, (&(sAMAccountType=805306369)(objectCategory=computer)
(cn=MsgOps*)). For more information about LDAP queries, see Creating a
294
Query Filter.
4. On the Exclusion Criteria page, type the FQDN of computers that you explicitly want to
prevent from being managed by this management server, and then click Next.
Important
You must separate the computer FQDNs that you type with a semicolon, colon,
or a new line (CTRL+ENTER).
5. On the Agent Failover page, either select Automatically manage failover and click
Create or select Manually configure failover. If you select Manually configure
failover, do the following:
a. Clear the check boxes of the management servers to which you do not want the
agents to failover.
b. Click Create.
Note
With the Manually configure failover option, you must run the wizard again
if you subsequently add a management server to the management group and
want the agents to failover to the new management server.
6. In the Management Server Properties dialog box, click OK.
Note
It can take up to one hour for the agent assignment setting to propagate in AD
DS.
See Also
Integrating Active Directory and Operations Manager
Using Active Directory Domain Services to Assign Computers to Operations Manager
Management Groups
How to Create an Active Directory Domain Services Container for a Management Group
Changing the Active Directory Integration Setting for an Agent
295
Those management groups, if any, will be added to the list. If you clear this option, all
management groups assigned to the agent in Active Directory will be removed from the
list.
3. Click OK.
See Also
Integrating Active Directory and Operations Manager
How to Create an Active Directory Domain Services Container for a Management Group
How to Use Active Directory Domain Services to Assign Computers to Management Servers
296
Using Reports in Operations Manager
Reports are a valuable tool for communicating status and trends. This section explains how to
use the standard reports that are provided in Operations Manager
Not Monitored and Gray Agents
This topic explains what is going on when you see agents in a “gray” state or labeled as “not
monitored”.
How to View All Rules and Monitors Running on an Agent-Managed Computer
This topic explains how to view all rules and monitors running on an agent-managed
computer.
See Also
Getting Information from Operations Manager
297
Comparing the Operations Console and Web Console in Operations
Manager
System Center 2012 – Operations Manager operators use a console to view monitoring data. The
consoles available are the Operations console and the web console. The Operations console
allows you to perform all actions that your user role allows, while the web console displays only
My Workspace and the Monitoring workspace.
Both consoles share a similar layout:
Each navigation button opens a specific workspace, such as Monitoring or Administration. In the
Operations console, the following navigation buttons may be available, depending on the user
role you are assigned:
298
Tip
In the Operations console, you can change the navigation buttons into small icons and
increase the space available in the navigation pane by clicking on the top border of the
navigation buttons and dragging downward. You can also hide and reveal the navigation
and task panes.
There are a few differences between the Operations console and web console that you should be
aware of:
There are minor differences in sort. For example, in the web console, when you sort alerts,
only the alerts visible on the page are sorted rather than all alerts.
Fewer alerts display per page in the web console.
You cannot run tasks that require elevated access in the web console.
You do not have the options to show, hide, personalize, or create views in the web console,
although you can create a dashboard view in My Workspace in the web console.
There are no subscription options in the web console.
299
To connect an Operations console to a management server
1. Click Start, click All Programs, click System Center Operations Manager 2012, and
click Operations Console to open the Operations console.
2. In the Connect To Server dialog box, type in the server name or select a server from the
list. (In the image above, the console has not yet connected to any management group. If
the console has previously connected to any management servers, the servers will be
listed in Recent Connections.)
The Operations console opens with the focus on the most recently viewed workspace. For
example, if the Authoring workspace is selected when the console is closed, the next time
that the console is started, it will open to the Authoring workspace. To switch to a different
workspace, click the appropriate navigation button.
In the Operations console, click Tools and then click Connect as shown in the following
image, which will open the Connect To Server window.
See Also
Comparing the Operations Console and Web Console in Operations Manager
Connecting Management Groups in Operations Manager
Using the Reporting
To change Workspace
the in Operations
management Manager
server that the Operations console is connected to
Using the Administration Workspace in Operations Manager
300
Using My Workspace in Operations Manager
Using Health Explorer in Operations Manager
Using the Monitoring Workspace in Operations Manager
How to Connect to the Web Console
Using the Authoring Workspace in Operations Manager
Using the Operations Manager Consoles
Note
You must use Internet Explorer 7, Internet Explorer 8, or Internet Explorer 9 to connect to
the Operations Manager web console. In addition, the Operations Manager web console
requires that JavaScript be enabled. To enable JavaScript in Internet Explorer, open
Internet Options, and click the Security tab. Select the zone for the web console
(Internet, Local intranet, or Trusted sites), and then click Custom level. Enable Active
scripting, click OK, click OK, and then connect to the web console.
The Operations Manager environment must have the web console installed on a management
server for users to connect to the web console by using a web browser.
By default, the web console session is limited to 30 minutes. You can change this limit by editing
the web.config file (Program Files\System Center Operations Manager 2012\WebConsole\
WebHost) and changing the autoSignOutInterval value from “30” to a shorter or longer interval, or
disable the session limit by changing the value to “0”, as shown in the following example.
<connection autoSignIn=”true” autoSignOutInterval=”0”>
Note
After you change the web.config file, you must open a new web console session for the
changes to take effect.
See Also
Comparing the Operations Console and Web Console in Operations Manager
Using the Monitoring Workspace in Operations Manager
301
Using My Workspace in Operations Manager
Managing Alerts
In the State and Alerts overview, click any of the numbers to see a detailed view. For example, if
you click the number shown for Maintenance Mode, a state view of all computers in
maintenance mode opens.
The health states that are summarized in the overview only tell you part of what is going on in
your environment. You will also want to review the alerts that have been generated. In the
navigation pane, click Active Alerts to see all alerts. For more information about dealing with
alerts, see Managing Alerts.
There are number of views in the Monitoring workspace that allow you to view the status of your
environment. For information on each view, see Standard Views in Operations Manager. You can
change the display options of a view and save it as a personalized view. For more information,
see How to Personalize a View in Operations Manager.
302
As you work with Operations Manager, you may discover that there are specific views that you
frequently access. You can create a customized workspace that displays your favorite views and
searches. For more information, see Using My Workspace in Operations Manager.
See Also
Using My Workspace in Operations Manager
Comparing the Operations Console and Web Console in Operations Manager
Standard Views in Operations Manager
How to Personalize a View in Operations Manager
Finding Data and Objects in the Operations Manager Consoles
Using the Reporting Workspace in Operations Manager
Using the Administration Workspace in Operations Manager
Using My Workspace in Operations Manager
Using Health Explorer in Operations Manager
Using the Authoring Workspace in Operations Manager
How to Connect to the Web Console
How to Connect to the Operations Console
Using the Operations Manager Consoles
303
The icons used to indicate state are as follows:
Icon Meaning
Warning (yellow)
Critical (red)
By default, when the Health Explorer windows first opens, all monitors that are in a failed, or red,
state are expanded. If a monitor contains other monitors, as in the case of a roll-up monitor, all
monitors are shown in a hierarchical layout so that monitoring data for all dependent services and
applications is displayed. If you want to view more detail on any dependent monitor, right-click
that monitor and then click Monitor Properties to open another Health Explorer window.
When the Health Explorer window is open, you can review a history of diagnostic tests that have
run automatically and the output from those tasks. You can also run additional diagnostic tasks.
Any task that is formatted as a hyperlink can run directly from the Knowledge tab.
The Health Explorer window refreshes automatically every 30 seconds. Press the F5 function key
for an immediate refresh.
For more information on using Health Explorer, see Using Health Explorer to Investigate
Problems.
304
See Also
Using the Reporting Workspace in Operations Manager
Using the Administration Workspace in Operations Manager
Using My Workspace in Operations Manager
Using the Authoring Workspace in Operations Manager
Using the Monitoring Workspace in Operations Manager
How to Connect to the Web Console
How to Connect to the Operations Console
Using the Operations Manager Consoles
Note
To create a nested folder, right-click the folder in which you want to create a child
folder, and then continue to step 2.
2. Point to New and click Folder.
3. Type a folder name, and then click OK.
305
2. Specify the folder in My Workspace where you want the view to appear.
3. Click OK.
When you go to My Workspace, you will see the view that you added listed in the navigation
pane.
Save Searches
You can save useful searches in My Workspace to run at any time.
Create Views
Views that you create in My Workspace are unique views, not shortcuts to existing views. As an
operator, you can create views in the My Workspace pane. You must have the rights of the Author
role to create a view in the Monitoring workspace.
306
Note
The general instructions in the following procedure do not apply to Diagram, Web Page,
or Dashboard views. For more information on creating a view, see the specific view type
in Creating Views in Operations Manager.
See Also
Standard Views in Operations Manager
How to Personalize a View in Operations Manager
Using Advanced Search
Guidance for Scoping and Targeting Views
Using the Reporting Workspace in Operations Manager
Using the Administration Workspace in Operations Manager
Using the Authoring Workspace in Operations Manager
Using Health Explorer in Operations Manager
Using the Monitoring Workspace in Operations Manager
How to Connect to the Web Console
How to Connect to the Operations Console
Using the Operations Manager Consoles
307
Using the Administration Workspace in Operations Manager
In the System Center 2012 – Operations Manager Operations console, the Administration
workspace is the primary workspace for administrators. You use the Administration workspace to
configure a management group and its managed objects.
When you first open the Administration workspace or when you click Administration in the
navigation pane, the Administration Overview opens, which displays task links for any required or
optional configuration steps that have not been completed yet.
The sections below describe the different options in the Administration workspace and link to
more detailed information about the task or option.
Device Management
You can use Device Management in the Administration workspace to perform configuration of
specific management servers, agent-managed computers, agentless-managed computers, UNIX
servers, and Linux servers. The following table summarizes the uses of the items in Device
Management and provides links to more detailed information.
309
Item Use For more information
Management Packs
When you select Management Packs in the Administration workspace, you see a list of all
management packs imported into your management group. When you right-click an individual
management pack in the results pane, you can view its properties, delete it, or export any
customizations to another management group. You can use links in the tasks pane to create,
import, and download management packs.
For more information, see Using Management Packs.
Network Management
You can use Network Management in the Administration workspace to discover network devices
and managed discovered network devices. The following table summarizes the uses of the items
in Network Management and provides links to more detailed information.
310
Notifications
Notifications generate messages or run commands automatically when an alert is raised on a
monitored system. By default, notifications for alerts are not configured. For Operations Manager
users to be notified immediately when an alert is generated, you need to configure a channel for
notifications, add subscribers, and then create a notification.
In Notifications in the Administration workspace, you can create channels, subscribers,
subscriptions, and modify the channels, subscribers, and subscriptions that you create. For more
information, see Subscribing to Alert Notifications.
Product Connectors
Product connectors are used to synchronize Operations Manager data with other management
systems such as those that monitor non-Windows computers or create trouble-tickets. Product
connectors can integrate a deployment of Operations Manager into another management
platform or connect other management systems into a full Operations Manager management
solution. Any product connectors that you integrate with Operations Manager will be displayed in
this section of the Administration workspace.
When you install Operations Manager, two internal product connectors are installed. These are
used by Operations Manager.
For more information, see Connecting Operations Manager With Other Management Systems.
Run As Configuration
You can use Run As Configuration in the Administration workspace to manage Run As accounts
and profiles. The following table summarizes the uses of the items in Run As Configuration and
provides links to more detailed information.
Security
In Operations Manager, operations such as resolving alerts, running tasks, overriding monitors,
viewing alerts, viewing events, and so on have been grouped into user roles, with each user role
representing a particular job function. Role-based security allows you to limit privileges that users
have for various aspects of Operations Manager. In Security in the Administration workspace,
you can add and remove users to specific user roles. You can also modify the properties of user
roles that you create.
For more information, see Implementing User Roles.
311
Settings
The following table summarizes the settings you can manage in Settings in the Administration
workspace.
Web Addresses Designate web addresses for How to Connect to the Web
the Web console and online Console
company knowledge.
312
See Also
Using the Reporting Workspace in Operations Manager
Using the Authoring Workspace in Operations Manager
Using My Workspace in Operations Manager
Using Health Explorer in Operations Manager
Using the Monitoring Workspace in Operations Manager
How to Connect to the Web Console
How to Connect to the Operations Console
Using the Operations Manager Consoles
Important
Users must be a member of the Report Operator Users role to run reports.
Reporting
Reporting in the Reporting workspace contains all reports installed with Operations Manager, as
well as those reports included in management packs that you have imported.
The report library contains generic reports (for example, Availability and Configuration Changes
reports). Generic reports have no specified context. The context for the report is defined in the
parameter header, located at the top of the Report window.
For more information on using the reports library, see Using Reports in Operations Manager.
Authored Reports
Authored reports are based on existing reports from the report library. You configure a report with
prepopulated parameters and then make it available to other users.
After you run a report, click File, and then click Publish to publish the report with the configured
parameters to Authored Reports.
Favorite Reports
You can save configured reports to Favorite Reports to make them continually available to you
and to save you the time of reconfiguring a report you run frequently.
After you run a report, click File, and then click Save to favorites to save the report.
Scheduled Reports
You can schedule configured reports to run on a one-time or recurring basis.
313
After you run a report, click File, and then click Schedule to configure the report subscription. For
more information, see Scheduling Reports.
See Also
Using the Authoring Workspace in Operations Manager
Using the Administration Workspace in Operations Manager
Using My Workspace in Operations Manager
Using Health Explorer in Operations Manager
Using the Monitoring Workspace in Operations Manager
How to Connect to the Web Console
How to Connect to the Operations Console
Using the Operations Manager Consoles
Unix/Linux LogFile Monitor a Unix or Linux log file for a specific log
entry one a specific computer or group of
computers.
314
Unix/Linux Service Monitor the availability of a service on a Unix or
Linux computer or group of computers.
Distributed Applications
Distributed Applications allow you to group together multiple components that are part of a single
application. The health of each included object are used to calculate an overall health for the
application itself. This health can be used to support alerts, views, and reports.
Groups
Groups contain a particular set of managed objects. They are used to scope views, reports, and
certain monitoring scenarios. Criteria can be provided to automatically populate a group based on
properties of the objects, or you can add specific objects to a group.You can create new groups
and edit existing groups. You can also view the current members of a group. Once it has been
created, a group can be used in the Monitoring workspace for scoping views, the Reporting
workspace for scoping reports, or in the Authoring workspace for overrides, management pack
templates, or service level objects.
315
the Authoring console.
316
tasks in the Operations console for specific
monitoring scenarios which will address the
requirements of most users. More complex
tasks must be created and modified using the
Authoring console.
See Also
Using the Reporting Workspace in Operations Manager
Using the Administration Workspace in Operations Manager
Using My Workspace in Operations Manager
Using Health Explorer in Operations Manager
Using the Monitoring Workspace in Operations Manager
How to Connect to the Web Console
How to Connect to the Operations Console
Using the Operations Manager Consoles
Note
Any time that you do not see the information you expect in the results pane, check the
scope and time filters to ensure that the correct objects and time period are set for the
results you need.
The Scope, Search, Find, and Time tools apply a temporary filter to the data you are viewing in
the console. While you can locate a specific object using Search or Find, you can also use Scope
or Time to display a set of objects that meet a set of criteria. The following table shows the
differences between the different filtering options.
317
Filter When to use For more information, see
Find Use to display a known single How to Use Find and Search
object.
Time Use to limit the data displayed How to Change the Time
to only that data (such as Criteria
alerts) that has been
generated within a defined
time frame.
318
3. If the list is too long, you can find a specific group or distributed application by entering a
word or phrase in the Look for field. After you make a selection, click OK. Now only the
objects that meet the scope criteria are shown in the Results pane.
319
in the Results pane.
3. Check to see whether a Look for box is at the top of the Results pane. If there is no
Look for box, click the Find button on the toolbar. In Look for, type a word, such as the
name of an object, that you want to find in the list, and then click Find.
The object that you are looking for is displayed.
4. Click Clear to go back to the original list of objects.
320
sure that you have an object, not a folder, selected in the navigation pane.
3. Select the time criteria you are interested in.
Now only the objects that meet the time criteria are shown in the Results pane.
321
Object type Criteria associated with the object type
time period
For a specific site
With specific text in the available custom
fields
322
Object type Criteria associated with the object type
1
A remotable rule or discovery can run against a computer that does not have an agent installed.
323
For variables with limited values, such as alert priorities, the dialog box provides checkboxes that
you can select.
Note
When you run a saved search, change the parameters, click Search, and then close the
results window, you will be asked if you want to save the changes to the search.
See Also
Finding Data and Objects in the Operations Manager Consoles
Examples of Using Advanced Search in Operations Manager
324
To find Use this object, condition, and value
See Also
Finding Data and Objects in the Operations Manager Consoles
Using Advanced Search
325
For more information on specific view types, see:
Alert View Type
Event View Type
State View Type
Performance View Type
Diagram View Type
Task Status View Type
Web Page View Type
Overrides Summary View Type
Dashboard View Type
326
Event View Type
The event view queries the event logs and displays events that are based on criteria specified in
the event view properties. For information on creating an event view, see How to Create an Event
View.
327
Performance View Type
The performance view allows you to customize how you want to view performance data collected
from performance objects and counters. This includes the ability to view historical and current
operational data together. You must select Show in the Details pane to display data from a rule in
the graph in the Results pane. For information on creating a performance view, see How to
Create a Performance View.
328
Diagram View Type
The Diagram view displays a graphical view of a set of managed objects and how they relate to
one another. For information on creating a diagram view, see How to Create a Diagram View.
329
Task Status View Type
The task status view displays tasks that meet criteria specified in the properties, such as only
those tasks that apply to certain object types. For information on creating a task status view, see
How to Create a Task Status View.
330
Note
Users that are members of the Read-only Operator role cannot view or run any tasks. For
this reason, no tasks appear in a task status view that is opened by a Read-only
Operator.
331
Overrides Summary View Type
You can only create an overrides summary view in My Workspace.
You can view all rule and monitor overrides in the overrides summary view. The overrides
summary view can be used for both sealed and unsealed management packs. You can customize
this view by grouping items by multiple column headers. For information on creating an overrides
summary view, see How to Create an Overrides Summary View.
Security
When a dashboard view uses data from the data warehouse database, operators might
be able to view data that they would not otherwise have access to in views that use data
from the operational database.
332
For information on creating a dashboard view, see How to Create a Dashboard View.
See Also
Using Views in Operations Manager
Creating Views in Operations Manager
How to Personalize a View in Operations Manager
Guidance for Scoping and Targeting Views
Active Alerts This view shows all alerts that are active (not
333
View or View Folder Description
Discovered Inventory This view shows all objects that have been
discovered and their states.
Click Change Target Type in the Tasks pane
to filter the discovered inventory list to a single
type of object. The target type determines the
type of information that will be displayed in the
details pane for a selected object. For example,
if you change the target type to Health Service,
Detail View displays information about the
health service for the selected object, such as
port and action account identity. If you change
the target type to Computer, Detail View
displays computer information such as name
and asset status.
Select an object and click Health Explorer in the
Tasks pane to open Health Explorer in the
context of this object.
When the state of an object in Discovered
Inventory is Not monitored, that means…
For more information, see Using Health
334
View or View Folder Description
Task Status This view shows the output from tasks that you
have executed in the console. The Task Status
view shows when a task is completed, finished,
and the user who executed this specific task.
335
Explorer to Investigate Problems.
Data Warehouse (folder) The data warehouse is the database that stores
operations data which is used by Reporting
Server to build reports.The Data Warehouse
336
folder contains views to help you monitor the
state and performance of the data warehouse.
Active Alerts
All Event View
Collection Performance
Collection Servers
Synchronizaton Performance
Microsoft Audit Collection Services (folder) Audit Collection Services (ACS) collects
records generated by an audit policy. The ACS
collector receives and processes events from
ACS forwarders and then sends this data to the
ACS database. The service that runs on ACS
forwarders is included in the Operations
Manager agent. The Microsoft Audit Collection
Services folder contains views specific to ACS
operations.
The ACS Collector folder contains an
event view, a state vew, and multiple
performance views.
The ACS Fowarder folder contains an
event view and a state vew.
337
Management Data Access
Management Group Details
Management Packs and Workflows
Management Server
Notification
Web Application Transaction Monitoring (folder) The Web Application Transaction Monitoring
folder contains a state view of monitored Web
applications.
Windows Service and Process Monitoring The Windows Service and Process Monitoring
(folder) folder contains state views for Windows
services and processes.
See Also
Using Views in Operations Manager
Creating Views in Operations Manager
How to Personalize a View in Operations Manager
Guidance for Scoping and Targeting Views
338
How to Create a Diagram View
How to Create a Task Status View
How to Create a Web Page View
How to Create a Dashboard View
How to Create an Overrides Summary View
Note
You can add multiple criteria to refine the view to fit your needs.
5. Customize the appearance of the alert view on the Display tab. You can specify the
columns to display, the sort order for the columns, and the manner in which items are
grouped.
6. Click OK to create the view.
Note
When you select generated by specific rules, only event collection rules
can be selected. If you do not see the rule that you want to select when you
click specific, ensure that the category of the rule you want is Event
Collection.
c. Refine the criteria description by clicking the underlined text in the Criteria
description box.
For the UNIX-based computers event view, click specific. In the Event Type window,
select Audit Failure, and then click OK.
Note
You can add multiple criteria to refine the view to fit your needs.
5. Customize the appearance of the event view on the Display tab. You can specify the
columns to display, the sort order for the columns, and the manner in which items are
grouped.
6. Click OK to create the view.
Note
When a state view is displayed, you might find that multiple objects are listed by the
same name. For example, a Windows-based computer object and management server
object might have the same computer name. The Windows-based computer object and
the management server object will be listed on their own row in the state view and thus,
the same computer name will be listed twice. This is expected behavior.
340
To create a state view
1. Right-click the folder where you want to store the view, point to New, and then click State
View.
2. In the Properties dialog box of the event view, type a name and a description for the
view. (The description is optional.)
3. On the Criteria tab, click the ellipses (…) next to the Show data related to box. The
Select a Target Type dialog box displays a list of the object types available in your
management group. Click to select the object type of the objects that you want to view,
and then click OK. For more information, see Guidance for Scoping and Targeting Views.
The object type you select is listed in the Show data related to box. If you want to
narrow the focus of the view, you can also click the ellipses (…) next to Show data
contained in a specific group. Click a group to filter the objects shown in your view, and
then click OK.
Note
If you do not see the object type that you want, click View all targets and then
type a word or phrase in Find to filter the displayed list.
4. Use the checkboxes provided to select individual criteria to apply additional filters to the
objects that you want to display in your view. You might need to further define the criteria
in the Criteria description box.
5. Click the Display tab. By default, all columns in your state view display. Click to deselect
one or more columns that you do not want to display. Choose how you want to sort the
objects in your view in Sort columns by.
6. Click OK to create the view.
Note
You can add multiple criteria to refine the view to fit your needs.
5. Customize the appearance of the alert view on the Display tab. You can specify the chart
type to display, the period of time that the chart should cover, and the display options for
the X axis and Y axis.
6. Click OK to create the view.
Note
If you do not see the object type that you want, click View all targets and then
type a word or phrase in Find to filter the displayed list.
343
1. In the Operations console, click My Workspace.
2. Right-click the folder where you want to store the view, point to New, and then click Web
Page View.
3. Enter a name and description for the view. (The description is optional.)
4. In the Target website field, enter the URI for the web page to be displayed in the view.
You can specify an Internet or intranet address.
Note
The web view will only display the specified web page on computers that have
access to that web page. For example, if you create a web page view that links to
the System Center page on Microsoft.com, an Operations console on a computer
that does not have Internet access will not display the correct web page in that
web page view.
5. Click OK.
Security
When a dashboard view uses data from the data warehouse database, operators might
be able to view data that they would not otherwise have access to in views that use data
from the operational database.
You can use dashboard views to present multiple types of data in a single view. You select either
a flow layout, which consists of multiple columns, or a grid layout, which consists of multiple cells.
In the grid layout, you also specify the layout of the cells.
If you create a dashboard view that uses a flow layout, you can change the number of columns
afterward. If you create a dashboard view that uses a grid layout, you can change the layout
afterward but you cannot change the number of cells.
For both layouts, after you create the dashboard view, you add widgets which will display specific
types of data.
Note
A column or cell in a dashboard view can contain a widget or another dashboard view.
Operations Manager contains the following widgets:
State
Performance
Alert
Additional widgets may be provided by management packs.
Widgets in a dashboard view can display data for a particular target class or group of objects. To
support the dashboard view that you are going to create, you should first create a group
344
containing a set of computers or objects to include in the displayed data. For information on
creating groups, see How to Create Groups.
Note
When you create a dashboard view that includes a widget that displays data for a target
class that contains instances (a non-singleton class), that dashboard view cannot be
imported into other management groups.
You can also create a service level dashboard view to track data for service level objectives that
you create. For more information, see Creating a Service Level Dashboard.
345
d. On the Display page, select the columns you want displayed. You can also configure
the sort order and how to group the data. Click Next.
e. Review the settings on the Summary page, and then click Create.
f. Click Close.
Performance Widget:
a. On the General Properties page, enter a name for the widget. The description is
optional. Click Next.
b. On the Specify the Scope and Counters page, select a group or object. For more
information, see Guidance for Scoping and Targeting Views.
c. On the Specify the Scope and Counters page, click Add.
d. In the Select performance counters dialog box, use the Object, Counter, and
Instance dropdown menus to filter the performance counters listed in Available
Items. Select performance counters from the Available Items list, click Add, and
then click OK.
Note
The performance counters available are scoped to the group or object you
selected in Select a group or object.
e. Click Next.
f. On the Time Range page, select the time range for the data, and click Next.
g. On the Specify the Chart Preferences page, select the items you want displayed in
the performance chart. You can configure order of the items by using the up and
down arrows. For the vertical axis, you can select Automatic or configure the
minimum and maximum values manually. Cilck Next.
h. Review the settings on the Summary page, and then click Create.
i. Click Close.
State Widget:
a. On the General Properties page, enter a name for the widget. The description is
optional. Click Next.
b. On the Specify the Scope page, click Add.
c. In the Add Groups or Objects window, click the groups or objects in Available
items and click Add, and then click OK.
d. In Select a class to scope the members of the specific groups, you can change
the selected class. (Object is selected by default.) Click Next.
e. On the Specify the Criteria page, use the health state checkboxes to select the
criteria for data to be displayed, and then click Next.
Note
You can also select to display only objects in maintenance mode.
f. On the Display page, select the columns you want displayed. You can also configure
the sort order and how to group the data. Click Next.
g. Review the settings on the Summary page, and then click Create.
346
How to Create an Overrides Summary View
You can only create an overrides summary view in My Workspace.
You can view all rule and monitor overrides in an overrides summary view. The overrides
summary view can be used for both sealed and unsealed management packs.
Note
You can add multiple criteria to refine the view to fit your needs.
5. Customize the appearance of the alert view on the Display tab.
6. Click OK to create the view.
See Also
Using Views in Operations Manager
Standard Views in Operations Manager
How to Personalize a View in Operations Manager
Guidance for Scoping and Targeting Views
Note
Personalized views are only visible to the user who personalized the view.
To personalize a view
1. In the Operations console, click Monitoring.
2. In the Monitoring workspace, right-click the view that you want to personalize and then
347
click Personalize view. The Personalize view dialog box displays with the default
settings of the view.
3. In Columns to display, click to place a check next to the property that you want to
display in your view. You can also click to remove any checkmarks set by the original
view. In the Sort columns by box, click the drop-down arrow to choose a property by
which you want to sort the monitored objects in your view, and then click OK.
Note
In a state view, the option to sort by groups is not available. This option is
available in other view types, such as the alert view and event view.
See Also
Using Views in Operations Manager
Standard Views in Operations Manager
Creating Views in Operations Manager
Guidance for Scoping and Targeting Views
348
See Also
Using Views in Operations Manager
Standard Views in Operations Manager
Creating Views in Operations Manager
How to Personalize a View in Operations Manager
349
Note
Note
You can get more information on the scripts included with Operations Manager by using
the command shell and the get-help cmdlet. For example: get-help install-
OperationsManager-DashboardViewer.ps1.
Using the install-OperationsManager-DashboardViewer.ps1 script, you can deploy the web part to
all sites and web applications in the farm or to a specific site or web application.
350
Example that deploys the web part to a specific portal address:
.\install-OperationsManager-DashboardViewer.ps1 “C:\Program Files\System
Center Operations Manager 2012\” http://localhost:4096
If an error occurs when you run the script, you must disable the RemoteSigned default
code-signing execution policy for the SharePoint 2010 Management Shell. To allow the
install-OperationsManager-DashboardViewer.ps1 script to run, type the following
command, and then press enter:
Set-ExecutionPolicy Unrestricted
You will see some confirmation messages, select Y to confirm, and then run the script.
4. Verify that the web part is deployed and activated by performing the following steps:
a. Open the site http://localhost.
b. In the Site Actions dropdown menu, click Site Settings.
c. In the Site Collection Administration section, click Site collection features.
d. Locate Operations Manager Dashboard Web Part.
If the button to the right says Activate, then the feature was not automatically
activated during deployment. To activate the web part, click the Activate button.
If the button to the right says Deactivate, no steps are required. The Operations
Manager Dashboard web part can now be inserted into site pages.
5. If you disabled the RemoteSigned default code-signing execution policy to run the install-
OperationsManager-DashboardViewer.ps1 script, you should re-enable it after the script
runs. Type the following command and then press enter:
Set-ExecutionPolicy Restricted
You will see some confirmation messages, select Y to confirm.
To configure the environment for a web part by using the user interface
1. On the SharePoint central administration site, in the Site Actions dropdown menu, click
View All Site Content.
2. In Lists, click Operations Manager Web Console Environments.
3. Click Add new item.
4. In the Name field, enter a unique name.
5. In the HostURI field, enter the URI to a server hosting the Operations Manager web
console. For example: http://ServerName/OperationsManager/
6. Click Save.
351
How to Add the Operations Manager Web Part to a SharePoint Page
After you deploy the Operations Manager web part to a SharePoint site, you can add the web part
to pages. When you add the web part, you configure it to display a specific dashboard view. For
the configuration, you will need the URI for the dashboard view that you want displayed.
To obtain the URI, open the web console and navigate to the desired dashboard view. The
address bar will display an address such as the following:
http://localhost/OperationsManager/#/dashboard
%7Btype=Microsoft.SystemCenter.Visualization.Library!
Visualization.SlaDashboardViewInstanceDaily%7D
The following procedure creates a SharePoint page with the Operations Manager Dashboard
Viewer web part that can only be accessed by users who have an Operations Manager user role,
such as Operator or Administrator. To configure the Operations Manager Dashboard Viewer web
part so that those who are not Operations Manager users can view it, perform the following steps
and then see the procedure How to Configure the Web Part to Use Shared Credentials.
Note
After you correctly set up a dashboard web part in SharePoint, you might receive an error
message saying “ticket has expired”. This is because there is a very narrow time-out for
an override ticket (by default, 5 seconds). If the time on the server running SharePoint
and the Web console server differ by more than this value, the connection fails. This is a
likely situation if the computers are in different domains and are using a different time
source. You can increase the time-out on the SharePoint Server in the web console list,
but this would make the server more vulnerable to attack. The best solution is to
synchronize the time between the server running SharePoint and the web console server.
352
How to Configure the Web Part to Use Shared Credentials
To configure the Operations Manager Dashboard Viewer web part so that those who are not
Operations Manager users can view it, perform the following procedures. In the first procedure,
you configure credentials by creating a Target Application ID in SharePoint. Next, you configure
the web part environment.
Note
Operations Manager provides two scripts in the setup\SharePoint directory to allow users
to add and update the SharePoint web environment keys from the web config file: add-
OperationsManager-WebConsole-Environment.ps1 and update-OperationsManager-
WebConsole-Environment.ps1. These scripts strip the encryptionAlgorithm and
encryptionValidationAlgorithm for the override ticket from the web config file and add or
update it in the sharepoint environment. This allows you to automate the creation and
rotation of keys. Procedures for using these scripts are in this section.
Note
You cannot configure shared credentials in SharePoint Foundation 2010.
1. In SharePoint Central Administration, in the Application Management section, click
Manage service applications.
2. Double-click Secure Store Service.
3. Click New.
4. On the Application settings page, enter a Target Application ID, a display name, and an
email contact address. The Target Application ID is a unique text string that is used by the
Secure Store Service application to identify this target application. The display name is
displayed in the user interface. The contact can be any legitimate email address and
does not have to be the identity of an administrator of the Secure Store Service
application. In Target Application Type, select Group. Click Next.
5. On the Add Field page, accept the default of Windows User Name and Windows
Password, and click Next.
6. In Target Application Administrators, enter a domain account, and click OK.
7. Click the dropdown arrow to the right of the name of the Target Application ID that you
created, and click Set Credentials.
8. In the Windows User Name field, enter the user name of the account you want the web
part to use. Enter the password for the account and confirm the password, and then click
353
2. Open Web.config in a text editor.
3. Locate the <encryption> section.
4. Locate the OverrideTicketEncryptionKey entry. In the following example, the first bold
value is the encryption algorithm key and the second bold value is the encryption
validation algorithm key:
Example: <key name="OverrideTicketEncryptionKey" algorithm="3DES"
value="92799B26F0BF54EE76A40CFECDB29868927D2DA4D7E57EBD"> <validation
algorithm="HMACSHA1" value="7526BAC9FC9562835A3872A3DC12CB8B"/>
5. Copy both keys and close Web.config.
6. On the SharePoint site, in the Site Actions dropdown menu, click View All Site Content.
7. In Lists, click Operations Manager Web Console Environments .
8. Click the web part that you want to configure, and then click Edit Item.
9. In the TargetApplicationID field, enter the Target Application ID that you created in the
previous procedure.
10. In the Encryption Algorithm Key field, enter the encryption algorithm key that you
copied from Web.config.
11. In the Encryption Validation Algorithm Key field, enter the encryption validation
algorithm key that you copied from Web.config.
12. Click Save.
Repeat this procedure for each Operations Manager environment.
Note
The web.config file is found under Program Files\System Center 2012\
Operations Manager\WebConsole\WebHost on the computer running the web
console.
-targetApplicationID the Target Application ID
354
To add environments to the Web Part
1. On the SharePoint site, in the Site Actions dropdown menu, click View All Site Content.
2. In Lists, click Operations Manager Web Consoles.
3. Click Add new item.
4. In the Name field, enter a unique name.
5. In the HostURI field, enter the URI to a server hosting the Operations Manager web
console. For example: http://localhost/OperationsManager/
6. Click Save.
1. Copy the update-OperationsManager-WebConsole-Environment.ps1 file, which is in the
Operations Manager installation folder under Setup\amd64\SharePoint, to the SharePoint
server.
2. Open Operations Manager Shell.
3. Run update-OperationsManager-WebConsole-Environment.ps1 using the following
parameters:
-title the name of the dashboard view
-webconsoleUNC “path to the web.config file, not including filename”
Note
The web.config file is found under Program Files\System Center 2012\
Operations Manager\WebConsole\WebHost on the computer running the web
console.
-targetApplicationID the Target Application ID
355
.\uninstall-OperationsManager-DashboardViewer.ps1 –solutionPath <directory for
Microsoft.EnterpriseManagement.SharePointIntegration.wsp> -url <optional, for
uninstalling from a specific portal address or website>
Example that uninstalls the Web Part from a specific portal address:
.\uninstall-OperationsManager-DashboardViewer.ps1 “C:\Program Files\System
Center Operations Manager 2012\” http://localhost:4096
If an error occurs when you run the script, you must disable the RemoteSigned default
code-signing execution policy for the SharePoint 2010 Management Shell. To allow the
install-OperationsManager-DashboardViewer.ps1 script to run, type this command, and
then press enter:
Set-ExecutionPolicy Unrestricted
You will see some confirmation messages, select Y to confirm, and then run the script.
4. If you disabled the RemoteSigned default code-signing execution policy to run the install-
OperationsManager-DashboardViewer.ps1 script, you should re-enable it after the script
runs. Type this command, and then press enter:
Set-ExecutionPolicy Restricted
You will see some confirmation messages, select Y to confirm.
1. Open the SharePoint 2010 Central Administration site.
2. Click System Settings.
3. Click Manage Farm Solutions.
4. Right-click the Microsoft.EnterpriseManagement.SharePointIntegration.wsp file, and then
click Retract.
See Also
Using the Operations Manager Consoles
Finding Data and Objects in the Operations Manager Consoles
Using Views in Operations Manager
Not Monitored and Gray Agents
Subscribing to Alert Notifications
Using Reports in Operations Manager
356
A Run As account that provides credentials to the Notification Account Run As profile.
A notification channel which defines the format for the notification and the method by which
the notification is sent.
A notification subscriber which defines the recipients and the schedule for sending
notifications to the subscriber.
A notification subscription which defines the criteria for sending a notification, the channel to
be used, and the subscribers to receive the notification.
An Operations Manager administrator must configure the Run As account for notifications and
define the notification channels. An Operations Manager administrator, advanced operator, or
operator can create a subscriber and a subscription.
357
correctly, you must create a Run As account that provides the credentials for sending notifications
and associate the Run As account to the Notification Account profile.
See Also
How to Enable an Email Notification Channel
How to Enable an Instant Message Notification Channel
How to Enable a Text Message (SMS) Notification Channel
358
How to Enable a Command Notification Channel
How to Create Notification Subscribers
How to Create Notification Subscriptions
How to Customize Message Content for Notifications
How to Subscribe to Notifications from an Alert
How to Create Subscriptions Using Classes and Groups
How to Specify Which Alerts Generate Notifications (Conditions)
Sending Notifications for Specific Computers and Specific Alerts to Specific Teams
Note
You can add one or more additional servers to act as backup servers. If the
primary SMTP server is unavailable, notifications are sent through the secondary
359
server.
7. Type the Return Address that should appear on email notifications, and then in the
Retry interval list, select the number of minutes to wait before trying to resend a
notification to the primary SMTP server. Click Next.
8. In the Default e-mail notification format area, specify the E-mail subject and E-mail
message text or leave the default selections, select the Importance level that you want
the emails sent with, and then specify the Encoding type. You can click the right arrow
next to the E-mail subject and E-mail message boxes for a full list of available
variables. For more information, see How to Customize Message Content for
Notifications.
9. Click Finish, and then click Close.
Next task: How to Create and Configure the Notification Action Account
See Also
How to Enable an Instant Message Notification Channel
How to Enable a Text Message (SMS) Notification Channel
How to Enable a Command Notification Channel
How to Create Notification Subscribers
How to Create Notification Subscriptions
Subscribing to Alert Notifications
How to Create and Configure the Notification Action Account
How to Customize Message Content for Notifications
How to Subscribe to Notifications from an Alert
How to Create Subscriptions Using Classes and Groups
How to Specify Which Alerts Generate Notifications (Conditions)
Sending Notifications for Specific Computers and Specific Alerts to Specific Teams
360
Return address to be used for the instant messages.
Note
The return address should be a dedicated address that is used only for
Operations Manager notifications.
7. Click Next.
8. In the Default instant messaging notification format area, in the IM message box,
specify the text that is sent to notification subscribers. The IM message box contains a
default message that includes text and variables. You can edit the default message or
delete it and replace it with another message. You can click the right arrow next to the IM
message box for a full list of available variables. For more information, see How to
Customize Message Content for Notifications.
9. In the Encoding box, select the text format that your IM server and notification
subscribers use for transmission. By default, Unicode (UTF-8) is used.
10. Click Finish and then click Close.
Next task: How to Create and Configure the Notification Action Account
See Also
How to Enable an Email Notification Channel
How to Enable a Text Message (SMS) Notification Channel
How to Enable a Command Notification Channel
How to Create Notification Subscribers
How to Create Notification Subscriptions
Subscribing to Alert Notifications
How to Create and Configure the Notification Action Account
361
How to Customize Message Content for Notifications
How to Subscribe to Notifications from an Alert
How to Create Subscriptions Using Classes and Groups
How to Specify Which Alerts Generate Notifications (Conditions)
Sending Notifications for Specific Computers and Specific Alerts to Specific Teams
Note
The modem used for SMS must support SMS Protocol Data Unit (PDU) mode.
See Also
How to Enable an Instant Message Notification Channel
How to Enable an Email Notification Channel
How to Enable a Command Notification Channel
How to Create Notification Subscribers
How to Create Notification Subscriptions
Subscribing to Alert Notifications
How to Create and Configure the Notification Action Account
How to Customize Message Content for Notifications
362
How to Subscribe to Notifications from an Alert
How to Create Subscriptions Using Classes and Groups
How to Specify Which Alerts Generate Notifications (Conditions)
Sending Notifications for Specific Computers and Specific Alerts to Specific Teams
Important
Unlike the other notification channels, the command notification channel will run its
command by using Local System, rather than the Notification Action Account.
See Also
How to Enable an Instant Message Notification Channel
363
How to Enable a Text Message (SMS) Notification Channel
How to Enable an Email Notification Channel
How to Create Notification Subscribers
How to Create Notification Subscriptions
Subscribing to Alert Notifications
How to Create and Configure the Notification Action Account
How to Customize Message Content for Notifications
How to Subscribe to Notifications from an Alert
How to Create Subscriptions Using Classes and Groups
How to Specify Which Alerts Generate Notifications (Conditions)
Sending Notifications for Specific Computers and Specific Alerts to Specific Teams
Note
364
The settings on the Schedule Notifications page apply globally to the
subscriber. You can also specify unique schedule settings for each address that
you add to the subscriber, in the following steps. For example, you can add one
email address that receives the notifications during business hours and add a
second email address that receives the notifications outside of business hours.
6. On the Subscriber Addresses page, click Add to add subscriber addresses to the
notification.
7. On the Describe the Subscriber Address page, enter a name to identify the subscriber
address, and then click Next.
8. On the Provide the Channel and Delivery Address page, perform the following steps:
a. In Channel Type, select between email, instant message, text message, or
command for the method of notification.
b. If you select command for channel type, in Command Channel, select the name of a
command channel. The command channel must be created before you create the
subscriber. Skip the next step, because no delivery address is specified for a
command channel.
c. In Delivery address for the selected channel, enter the address to which the
notification should be sent.
d. Click Next.
9. On the Schedule Notifications page, click Always send notifications, or Notify only
during the specified times and click Add to create a date range, and then click Next.
10. Click Add to define another subscriber address. Otherwise, click Finish, and then click
Close.
11. The new subscriber displays in the Subscribers pane.
Next task: How to Create Notification Subscriptions
365
command for the method of notification.
b. If you select command for channel type, in Command Channel, select the name of a
command channel. The command channel must be created before you create the
subscriber. Skip the next step, because no delivery address is specified for a
command channel.
c. In Delivery address for the selected channel, enter the address to which the
notification should be sent.
d. Click Next.
8. On the Schedule Notifications page, click Always send notifications, or Notify only
during the specified times and click Add to create a date range, and then click Next.
9. Click Add to define another subscriber address. Otherwise, click Finish, and then click
Close.
Next task: How to Create Notification Subscriptions
See Also
How to Enable an Instant Message Notification Channel
How to Enable a Text Message (SMS) Notification Channel
How to Enable a Command Notification Channel
How to Enable an Email Notification Channel
How to Create Notification Subscriptions
Subscribing to Alert Notifications
How to Create and Configure the Notification Action Account
How to Customize Message Content for Notifications
How to Subscribe to Notifications from an Alert
How to Create Subscriptions Using Classes and Groups
How to Specify Which Alerts Generate Notifications (Conditions)
Sending Notifications for Specific Computers and Specific Alerts to Specific Teams
366
1. Log on to the computer with an account that is a member of the Operations Manager
Administrators role.
2. In the Operations console, click Administration.
3. In the Administration workspace, expand Notifications, right-click Subscriptions, and
then click New subscription. The Notification Subscription Wizard starts.
4. On the Description page, in Subscription name, type a descriptive name for the
subscription, type a short description, and then click Next.
5. On the Subscription Criteria page, you can set conditions that will determine when
notifications will be sent to specified subscribers. If you do not set conditions, notifications
will be sent for all alerts. Click Next.
Note
You will also receive notifications when an alert is updated.
6. On the Subscribers page, click Add to add subscribers who are already defined, or click
New to add new subscribers. For more information on defining subscribers, see How to
Create Notification Subscriptions.
7. Click Next.
8. On the Channels page, click Add to add a channel that is already defined, or click New
to add a new channel. For more information on defining channels, see How to Enable an
Email Notification Channel, How to Enable an Instant Message Notification Channel, How
to Enable a Text Message (SMS) Notification Channel, and How to Enable a Command
Notification Channel.
9. In the Alert aging section on the Channels page, select to send notifications without
delay or set a value in minutes that notification should be delayed unless conditions
remain unchanged, and then click Next.
10. Review the settings on the Summary page, click Finish, and then click Close.
Note
You will also receive notifications when an alert is updated.
6. On the Subscribers page, click Add to add subscribers who are already defined, or
select a subscriber in the Selected subscribers box and click Edit to change the
367
settings for this subscription. For more information on defining subscribers, see How to
Create Notification Subscriptions.
7. Click Next.
8. On the Channels page, click Add to add a channel that is already defined, or click New
to create a customized copy of an existing channel. For more information on defining
channels, see How to Enable an Email Notification Channel, How to Enable an Instant
Message Notification Channel, How to Enable a Text Message (SMS) Notification
Channel, and How to Enable a Command Notification Channel.
9. In the Alert aging section on the Channels page, select to send notifications without
delay or set a value in minutes that notification should be delayed unless conditions
remain unchanged, and then click Next.
10. Review the settings on the Summary page, click Finish, and then click Close.
See Also
How to Enable an Instant Message Notification Channel
How to Enable a Text Message (SMS) Notification Channel
How to Enable a Command Notification Channel
How to Create Notification Subscribers
How to Enable an Email Notification Channel
Subscribing to Alert Notifications
How to Create and Configure the Notification Action Account
How to Customize Message Content for Notifications
How to Subscribe to Notifications from an Alert
How to Create Subscriptions Using Classes and Groups
How to Specify Which Alerts Generate Notifications (Conditions)
Sending Notifications for Specific Computers and Specific Alerts to Specific Teams
Note
The command channel type is not mentioned because it generates a command rather
than a notification message.
368
Channel type Default notification format
new or closed
Alert:
Source:
Path:
Last modified by:
Last modified time:
Alert description:
Alert view link:
Notification subscription ID generating this
message:
Instant message (IM) Alert: alert name Path: path to managed entity
Resolution state: new or closed Last modified
by:
You can change the format on the Format page of the channel type wizard when you create the
channel or after the channel is created. The procedure is the same for all three channel types.
369
5. Click any item in that list to add the corresponding variable to the notification message.
For example, if you click Alert Severity, the following variable will be added to the box:
$Data[Default='Not Present']/Context/DataItem/Severity$
Note
When a default value for a parameter is included, such as [Default=’Not Present’]
in the preceding example, it indicates the text to provide when the alert does not
contain data for that parameter.
6. When you are done, click Finish. All notification messages that use the same channel
will be formatted the same way.
370
channel. Click Finish when you are done making changes.
See Also
How to Enable an Instant Message Notification Channel
How to Enable a Text Message (SMS) Notification Channel
How to Enable a Command Notification Channel
How to Create Notification Subscribers
How to Create Notification Subscriptions
Subscribing to Alert Notifications
How to Create and Configure the Notification Action Account
How to Enable an Email Notification Channel
How to Subscribe to Notifications from an Alert
How to Create Subscriptions Using Classes and Groups
How to Specify Which Alerts Generate Notifications (Conditions)
Sending Notifications for Specific Computers and Specific Alerts to Specific Teams
Note
You must have configured a notification channel and notification subscriber to perform
this procedure.
371
6. Double-click the subscriber you want to use, and then click OK.
7. Click Next.
8. Click Add or Remove to select the notification channel to use.
9. Click Search to display all available channels.
10. Double-click the channel you want to use, and then click OK.
11. Click Next, and then click Finish.
12. Click Close.
See Also
How to Enable an Instant Message Notification Channel
How to Enable a Text Message (SMS) Notification Channel
How to Enable a Command Notification Channel
How to Create Notification Subscribers
How to Create Notification Subscriptions
Subscribing to Alert Notifications
How to Create and Configure the Notification Action Account
How to Customize Message Content for Notifications
How to Enable an Email Notification Channel
How to Create Subscriptions Using Classes and Groups
How to Specify Which Alerts Generate Notifications (Conditions)
Sending Notifications for Specific Computers and Specific Alerts to Specific Teams
372
Note
Operations Manager does not support using “not equal to” or “not a member of” for
notification subscriptions.
Groups
Groups are logical collections of objects, such as Windows-based computers, hard disks, or
instances of Microsoft SQL Server. Some groups are created by Operations Manager, such as
the Operations Manager Agent Managed Computer Group and the All Windows Computers
group. You can create groups to meet your specific monitoring needs, such as all Windows
computers in a specific organizational unit (OU). For more information on creating groups, see
How to Create Groups in Operations Manager.
Groups can have explicit or dynamic membership. Suppose you wanted to create a subscription
that would send notifications for alerts generated by five specific servers to one person and
notifications for alerts generated by a different five servers to a second person. You could create
two groups and explicitly assign each server to one of the groups, and then create a subscription
that would send notifications for each group to the appropriate person.
When you select a specific group as a condition for an alert notification, notifications are sent for
alerts raised by any member of the specified group.
Classes
A class represents a kind of object, and every object in Operations Manager is considered an
instance of a particular class. All instances of a class share a common set of properties. Each
object has its own values for these properties which are determined when the object is
discovered. Most management packs define a set of classes that describe the different
components that make up the application that is being monitored and to the relationships
between those classes.
Every class in Operations Manager has a base class. A class has all the properties of its base
class and potentially adds more. All of the classes from the different management packs installed
in your management group can be arranged in a tree with each class positioned under its base
class. If you start at any class, and then walk up the tree following its base class, and then the
base class of that class, and so on, you eventually reach the Object class which is the root of the
System Center class library.
When you select a specific class as a condition for an alert notification, notifications are sent for
alerts raised by any instance of the specified class.
Examples
Example 1: To send notifications of alerts for UNIX computers to your UNIX administrator, you
create a subscription using the condition Raised by any instance in a specific group, select the
UNIX/Linux Computer Group as the value for the condition, and select the UNIX administrator
as the subscriber.
Example 2: To send notifications of alerts for the UNIX operating system to your UNIX
administrator, you create a subscription using the condition Raised by any instance in a
373
specific class, select the UNIX/Linux Operating System as the value for the condition, and
select the UNIX administrator as the subscriber.
In the first example, the UNIX administrator would be notified of alerts raised by the operating
system on a UNIX computer, as well as any other alerts that are raised by a UNIX computer. In
the second example, the notifications would only be sent when the alert was raised by the UNIX
operating system.
See Also
How to Enable an Instant Message Notification Channel
How to Enable a Text Message (SMS) Notification Channel
How to Enable a Command Notification Channel
How to Create Notification Subscribers
How to Create Notification Subscriptions
Subscribing to Alert Notifications
How to Create and Configure the Notification Action Account
How to Customize Message Content for Notifications
How to Subscribe to Notifications from an Alert
How to Enable an Email Notification Channel
How to Specify Which Alerts Generate Notifications (Conditions)
Sending Notifications for Specific Computers and Specific Alerts to Specific Teams
374
When you select a condition, it is added to the Criteria description. In the Criteria description
box, the word specific is blue and underlined, and is a placeholder for the value for the condition.
Click specific to set the value for that condition.
For example, for the condition of a specific severity, click specific, and then select from the
available values: Information, Warning, and Critical.
When you create a notification subscription from an alert that has been generated, the conditions
for the subscription are configured automatically with values from the specific alert.
See Also
How to Enable an Instant Message Notification Channel
How to Enable a Text Message (SMS) Notification Channel
How to Enable a Command Notification Channel
How to Create Notification Subscribers
375
How to Create Notification Subscriptions
Subscribing to Alert Notifications
How to Create and Configure the Notification Action Account
How to Customize Message Content for Notifications
How to Subscribe to Notifications from an Alert
How to Create Subscriptions Using Classes and Groups
How to Enable an Email Notification Channel
Sending Notifications for Specific Computers and Specific Alerts to Specific Teams
See Also
How to Enable an Instant Message Notification Channel
How to Enable a Text Message (SMS) Notification Channel
How to Enable a Command Notification Channel
How to Create Notification Subscribers
How to Create Notification Subscriptions
Subscribing to Alert Notifications
How to Create and Configure the Notification Action Account
How to Customize Message Content for Notifications
How to Subscribe to Notifications from an Alert
376
How to Create Subscriptions Using Classes and Groups
How to Specify Which Alerts Generate Notifications (Conditions)
How to Enable an Email Notification Channel
Note
When you first install Operations Manager, it may take several minutes for all report
libraries to appear in Reporting.
Report Description
377
Report Description
Most Common Alerts This report shows the most common alerts
raised during the selected report duration and
for given filter parameters for selected objects.
Most Common Events This report shows the most common events
raised during the selected report duration and
for given filter parameters for selected objects.
Performance Top Instances This report shows the top or bottom “N”
instances for selected objects and a specific
performance counter rule.
Performance Top Objects This report shows the top or bottom “N” objects
for selected objects and a specific performance
counter rule.
378
Client Monitoring Views Library
Report Description
Top N Applications Growth and Resolution This report shows the top “N” applications
based on their growth percentile computed
against two specified time intervals.
Top N Error Groups This report shows the top “N” error groups
based on their crash count.
Top N Error Groups Growth and Resolution This report shows the top “N” error groups
based on their growth percentile computed
against two specified time intervals.
Report Description
Data Warehouse Availability This report shows the availability of the data
warehouse components based on the monitor
"Data Warehouse Connectivity and Processes
State".
Report Description
379
Report Description
Most Common Alerts This report shows the most common alerts
generated within the report period (by default
one week). It also shows this data by
management pack.
Report Description
Agent Counts by Date, Management Group and This report shows detail information for agent
Version acounts during specified time interval.
Data Volume by Management Pack This report shows the volume of data generated
by management packs. The purpose of this
report is to provide insight into which
management packs are driving the data
volumes in your environment so that you can
establish baselines and identify opportunities
for tuning. From this report, you can obtain
more specific details per management pack by
clicking one of the counts cells in the table at
the top of the report to open the Data Volume
by Workflow and Instance report for the
management packs.
Data Volume by Workflow and Instance This report shows the volume of data
generated, organized by workflows
(discoveries, rules, monitors, etc.), as well as
by instances.
380
Microsoft Service Level Report Library
Report Description
Service Level Tracking Summary Report This reports shows whether the configured
Service Level Objectives (SLOs) met their
respective goals, for selected service levels.
Report Description
Web Application Availability This report shows how available the web
application was. The web application
availability is the rollup of all tests defined in
your web application.
Report Description
Application Failure Analysis This report provides detailed failure analysis for
a selected application.
381
Report Description
Summary User Analysis This report highlights the application users who
experience most of the problems.
(Client Side Monitoring) Application AJAX Calls This report provides detailed failure analysis for
Analysis a selected application.
(Client Side Monitoring) Application Analysis This report provides an overview of activity,
performance and exception statistics for a
selected application.
(Client Side Monitoring) Application Status This report provides daily, weekly and monthly
application status summaries.
(Client Side Monitoring) Client Latency This report provides an analysis of client side
Distribution performance in relation to network latency.
(Client Side Monitoring) Load Time Analysis This report provides an analysis of client side
Based on Subnet performance based on client subnets.
(Client Side Monitoring) Summary Performance This report provides an analysis of performance
Analysis violations by application.
(Client Side Monitoring) Summary Size This report provides an analysis of content size
Analysis across multiple applications and shows the
correlation between content size and load time.
(Client Side Monitoring) Summary User This report highlights the application users who
Analysis experience most of the problems.
(Problem Analysis Reports) Application Activity This report shows application activity trends for
Breakdown a selected period in relation to an application's
activity during a previous period and average
application activity.
(Problem Analysis Reports) Application Daily This report shows application activity trends for
Activity a selected day in relation to an application's
activity during a previous period and average
application activity.
(Problem Analysis Reports) Application Failure This report shows the list of application
Breakdown by Functionality requests that experience most of the problems.
(Problem Analysis Reports) Application Failure This report provides failure analysis for
Breakdown by Resources distributed applications based on the
application components and external resource
dependencies.
(Problem Analysis Reports) Application Heavy This report provides performance analysis for
382
Report Description
(Problem Analysis Reports) Application Slow This report shows the breakdown of application
Request Analysis performance violations based on application
requests.
(Problem Analysis Reports) Day of Week This report shows application activity trends
Utilization and application resource utilization trends for a
selected period.
(Problem Analysis Reports) Hour of Day This report shows application activity trends
Utilization and application resource utilization trends for a
selected period.
(Problem Analysis Reports) Utilization Trend This report shows application activity trends
and application resource utilization trends for a
selected period.
(Resource Utilization Analysis) Application CPU This reports highlights applications that have
Utilization Analysis the heaviest CPU utilization and provides a
breakdown of CPU utilization based on the
servers which host the application.
(Resource Utilization Analysis) Application IO This reports highlights applications that have
Utilization Analysis the heaviest IO utilization and provides a
breakdown of IO utilization based on the
servers which host each application.
(Resource Utilization Analysis) Application This reports highlights applications that have
Memory Utilization Analysis the heaviest memory utilization and provides a
breakdown of memory utilization based on the
servers which host each application.
(Resource Utilization Analysis) Computer CPU This reports highlights servers that have the
Utilization Analysis heaviest CPU utilization and provides a
breakdown of CPU utilization based on the
monitored applications running on each server.
(Resource Utilization Analysis) Computer IO This reports highlights servers that have the
383
Report Description
(Resource Utilization Analysis) Computer This reports highlights servers that have the
Memory Utilization Analysis heaviest memory utilization and provides a
breakdown of memory utilization based on the
monitored applications running on each server.
See Also
Using Reports in Operations Manager
How to Create Reports in Operations Manager
How to Save a Report
How to Run a Report
Scheduling Reports
How to Export a Report
How to Troubleshoot Reports that Return No Data
Note
Operations Manager Reporting must be installed before you can run an alert logging
latency report.
384
To create an alert logging latency report
1. Log on to the computer with an account that is a member of the Operations Manager
Administrators role.
2. In the Operations console, click Monitoring.
3. In the Monitoring workspace, expand Monitoring and then click Windows Computers.
4. In the Windows Computers pane, click a row with a Health Service instance.
5. In the Tasks pane, under Report Tasks, click Alert Logging Latency.
6. In the Parameter Area, click the down arrow in the From box and then click Yesterday.
Note
You can further specify the timeframe for the report in the additional options in
the Parameter Area.
7. Click the down arrow on the Threshold list, and select the latency threshold you want to
measure.
8. Click the down arrow on the Aggregation Type list, and click the value you want for this
report.
9. Click Run to display the Alert Logging Latency Report.
10. Click Close to close the report.
Note
Operations Manager Reporting must be installed before you can run an alerts report.
To create an alerts report
1. Log on to the computer with an account that is a member of the Operations Manager
Administrators role.
2. In the Operations console, click Monitoring.
3. In the Monitoring workspace, expand Monitoring, and then click Wndows Computers.
4. In the Windows Computers pane, click a row with a Health Service instance.
5. In the Tasks pane, under Report Tasks, click Alerts.
6. In the Reporting Parameter area, click the down arrow in the From box and then click
Yesterday.
Note
You can further specify the timeframe for the report in the additional options in
the Reporting Parameter area.
385
7. Click Run to display the Alert Report.
8. Click Close to close the report.
Note
Operations Manager Reporting must be installed before you can run an Availability
report.
The availability report provides the following information about the selected computers:
Down – computer state is critical (red)
Up – computer state is healthy (green)
Yellow – computer state is warning (yellow)
Unmonitored – computer or monitor did not exist during reporting period
Monitor disabled – monitor has been disabled, such as by using an override
Monitoring unavailable – the System Center Management Health service monitoring the
computer is unavailable
Planned/unplanned maintenance – computer is in maintenance mode; overrides all other
states
Note
You can further specify the timeframe for the report in the additional options in
the Parameter area.
9. When you have specified the timeframe for the report, click Run to display the Availability
Report.
386
10. For a more detailed report, such as a report showing a graph for every day, click the
horizontal bar graph under Availability Tracker.
11. In the tool bar, click View, point to Go To, and then click Back to Parent Report to return
to the original report.
12. Click Close to close the report.
Note
You can further specify the timeframe for the report in the additional options in
the Reporting Parameter area.
11. In the Reporting Parameter area, under Monitoring Object, click Add.
12. In the Add Object dialog box, in the Object Name list, click the down arrow and then
click Begins with.
13. In the Object name text box, type the computer name for the computer you selected in
step 5, and then click Search.
14. In the Available items list, click the computer with the Type of Health Service, click
Add, and then click OK.
15. In the Reporting Parameter area, in the Monitoring Object list, click the entry that is not
387
of the type Health Service, and then click Remove.
16. Click Run to display the Configuration Changes Report.
17. Click Close to close the report.
Note
You can further specify the timeframe for the report in the additional options in
the Reporting Parameter area.
7. In the Reporting Parameter area, under Monitoring Object, click Add.
8. In the Add Object dialog box, in the Object Name list, click the down arrow, and then
click Begins with.
9. In the Object name text box, type the computer name for the computer you selected in
388
During setup of Operations Manager Reporting, on the Operational Data Reports page, you had
the option to join CEIP. If you elected to join CEIP, Operations Manager Reporting collects
information about your installation and sends reports to Microsoft on a weekly basis. You can
view the contents of these Operational Data Reports by creating a Microsoft ODR Report.
Note
Be aware of the following when saving reports:
Reports can be saved to a management pack from Favorite Reports.
Reports cannot be saved to a management pack from authored reports.
389
Management packs can be exported and imported into other management groups and
the reports will work only when these management groups share the same data
warehouse.
Only users with administrator authorization can save reports to management packs.
See Also
Using Reports in Operations Manager
How to Create Reports in Operations Manager
Operations Manager Reports Library
How to Run a Report
Scheduling Reports
Operations Manager Reports Library
How to Troubleshoot Reports that Return No Data
Note
You can further specify the timeframe for the report in the additional options in
the Parameter area.
8. Click Add Object.
9. In the Add Object dialog box, in the Object Name text box, type the computer name for
a computer that you want to report availability, and then click Search.
10. In the Available items list, click the computer you want to run a report for, click Add, and
then click OK.
11. Click Run to display the Availability Report.
390
12. For a more detailed report, such as a report showing a graph for every day, click the
horizontal bar graph under Availability Tracker.
13. In the toolbar, click View, point to Go To, and then click Back to Parent Report to return
to the original report.
14. Click Close to close the report.
See Also
Using Reports in Operations Manager
How to Create Reports in Operations Manager
How to Save a Report
Operations Manager Reports Library
Scheduling Reports
Operations Manager Reports Library
How to Troubleshoot Reports that Return No Data
Scheduling Reports
System Center 2012 – Operations Manager enables you to schedule report delivery for reports
that you have created and saved. Scheduled reports can be sent by email to specified individuals
and groups. Scheduled reports can also be delivered to the cache in the SQL Server Report
Server and thereby shorten the time required to retrieve a report.
391
How to Create a Report Schedule
Use the following procedure to create a schedule to save a report. Make sure that you have
created an Availability report and saved it as a favorite before using this procedure. For more
information about creating an Availability report, see How to Create an Availability Report and for
more information about saving a report as a favorite, see How to Save a Report.
Note
If you want to manage and distribute reports securely, you could deliver
reports to Microsoft Windows SharePoint Services, which offers digital rights
management. Consult your network security administrator.
c. Type a file name for the report in the File name text box.
d. Type a file path for the report in the Path text box.
Note
Report scheduling supports Universal Naming Convention (UNC) file names
and must not end in a backslash.
e. Click the down arrow in the Render Format list, and then click the file format you
want for the report.
f. Type a user name in the User name text box, and then type a password in the
Password text box.
Note
The credentials must have Write user rights on the file share.
g. Click the down arrow in the Write mode list, select the Write mode you want for
subsequent files, and then click Next.
6. In the Subscribe to a Report Wizard, on the Subscription Schedule page, do the
following:
a. Select one of the Generate the report options.
b. Type a start date and start time for the reports to be generated in The Subscription
is effective beginning list. You can also enter the date when this subscription will
392
end in The subscription expires on list, and then click Next.
7. In the Subscribe to a Report Wizard, on the Parameters page, specify a span of time
for the report in the From and To lists.
8. Make any other changes you need for this report, and then click Finish.
See Also
Scheduling Reports
How to Edit a Scheduled Report
How to Email Scheduled Reports
How to Schedule the Delivery of a Report to the SQL Report Server Cache
How to Cancel a Scheduled Report
393
Type a description in the Description text box.
Click the down arrow in the Delivery method list, and then click Report Server E-
Mail.
Type an email address of the destination inbox to receive reports in the To text box.
You can also type email addresses in the Cc, Bcc, and the Reply To text boxes.
Click the down arrow in the Render Format list, and then click the file format you
want for the report.
Click the down arrow in the Priority list, and then select the appropriate priority.
Type a subject for the email in the Subject text box.
Click Next.
6. On the Subscription Schedule page, do the following:
Select one of the Generate the report options.
Type a start date and start time for the reports to be generated in The Subscription
is effective beginning list. You can also enter the date when this subscription will
end in The subscription expires on list, and then click Next.
7. On the Parameters page, specify a span of time for the report in the From and To lists,
make any other changes you need for this report, and then click Finish.
See Also
Scheduling Reports
How to Create a Report Schedule
How to Edit a Scheduled Report
How to Schedule the Delivery of a Report to the SQL Report Server Cache
How to Cancel a Scheduled Report
How to Schedule the Delivery of a Report to the SQL Report Server Cache
You can create a schedule for sending reports to the cache in the SQL Server Report Server and
thereby shorten the time required to retrieve a report if the report is large or accessed frequently.
For more information about report caching, see Caching Reports (SSRS).
The example in this procedure uses an availability report that you have already created and
saved as a favorite. For more information about creating an availability report, see How to Create
an Availability Report. For more information about saving a report as a favorite, see How to Save
a Report.
394
5. In the Subscribe to a Report Wizard, on the Delivery Settings page, do the following:
a. Type a description in the Description text box.
b. Click the down arrow in the Delivery method list, and then click Null Delivery
Provider.
c. Click Next.
6. On the Subscription Schedule page, do the following:
a. Select one of the Generate the report options.
b. Type a start date and start time for the reports to be generated in The Subscription
is effective beginning list. You can also enter the date when this subscription will
end in The subscription will end list, and then click Next.
7. On the Parameters page, specify a span of time for the report in the From and To lists,
make any other changes you need for this report, and then click Finish.
See Also
Scheduling Reports
How to Create a Report Schedule
How to Email Scheduled Reports
How to Edit a Scheduled Report
How to Cancel a Scheduled Report
See Also
Scheduling Reports
How to Create a Report Schedule
How to Email Scheduled Reports
How to Schedule the Delivery of a Report to the SQL Report Server Cache
To cancel a scheduled report
How to Edit a Scheduled Report
395
To edit a scheduled report
1. Log on to the computer with an account that is a member of the Operations Manager
Report Operators role.
2. In the Operations console, click Reporting.
3. In the Reporting workspace, click Scheduled Reports.
4. In the Scheduled Reports pane, right-click the scheduled report you want to edit, and
then click Edit Schedule.
5. In the Subscribe to a Report Wizard, on the Delivery Settings page, if you select the
Windows File Share as a Delivery method, you must type the password in the
Password text box before you can make any other changes.
6. Type any other changes you need on the Delivery Settings page, and then click Next.
7. Type any changes you need to make on the Subscription Schedule page, and then
click Next.
8. Type any changes you need to make on the Report Parameters page, and then click
Finish.
See Also
Scheduling Reports
How to Create a Report Schedule
How to Email Scheduled Reports
How to Schedule the Delivery of a Report to the SQL Report Server Cache
How to Cancel a Scheduled Report
Note
Operations Manager Reporting must be installed before you can run a report.
If you want to manage and distribute reports securely, you can export reports to Microsoft
Windows SharePoint Services, which offers digital rights management. Consult your network
security administrator.
To export a report
1. After a report has been run, in the toolbar, click the File menu, point to Export, and then
click the format you want to export the file to.
2. In the Save As dialog box, select the folder where you want to save the report, and then
click Save.
See Also
Using Reports in Operations Manager
396
How to Create Reports in Operations Manager
How to Save a Report
How to Run a Report
Scheduling Reports
Operations Manager Reports Library
How to Troubleshoot Reports that Return No Data
397
5. In the Report Details pane, a list of the performance counters available in this report is
displayed. Keep in mind one of the counters, for example, LogicalDisk\Disk Bytes/sec\
_Total.
6. In the Operations console, click My Workspace.
7. In My Workspace, right-click My Workspace, point to New, and then click Performance
View.
8. In the Properties dialog box, in the Name field, type a name for this view (for this
example use Test).
9. In the Criteria tab, click with a specific counter name.
10. In Criteria description field, click specific.
11. In the Counter Name dialog box, type the name of the counter you noted in step 5, for
example Disk Bytes/sec, and then click OK.
12. In the Properties dialog box, click OK.
13. In the Test results pane, in Legend area, click one or more of the Show check boxes.
If data appears in the Test pane, that data is available in the Operations Manager
database and should be available for the report.
If no data appears, click the Authoring button. In Authoring, expand Authoring,
expand Management Pack Objects, and then click Rules. Look in the Enabled by
default column for any rules that are not enabled. If they are not enabled, use
overrides to enable the rule that you need for your report.
Note
Some performance data collection rules in the Exchange Management Packs
store data in only the Reporting data warehouse and cannot be verified with this
procedure.
14. In the Legend area, examine the Target column and verify that the text in the Target
column matches what is listed in the Object column in the Parameter Area of the report.
If the value listed in the Target column is different, use the value listed in Target column
in the report and run the report again.
Note
When searching for the name of an object in a report, you might find that the
name of the hosting computer is listed only in the Object path column in the
Parameter Area. If you want to locate multiple specific objects, you can create a
dynamic group containing the correct types of objects and run the report with this
new group. For more information about creating groups, see How to Create
Groups in Operations Manager.
398
3. In My Workspace, right-click My Workspace, point to New, and then click State View.
4. In the Properties dialog box, in the Name field, type a name for this view (for this
example use Test1).
5. On the Criteria tab, click the ellipses (…) next to the Show data related to box.
6. In the Select a Target Type dialog box, click View all Targets.
7. In the Find box, type Windows Operating System.
8. In the Target column, click Windows Operating System, and then click OK.
9. In the Properties dialog box, examine the contents in the list with the check boxes
contain the data that you wanted to run a report against (for example, Build Number), and
then click OK.
10. In the Test1 results pane, examine the content in the Name column. The values listed in
the Name column are the correct object names you need to search for when searching
for objects for the report.
Note
When searching for the name of an object in a report, you might find that the
name of the hosting computer is listed only in the Object path in the Parameter
Area. In this instance, you need to create a dynamic group containing the correct
types of objects and run the report with this new group. For more information
about creating groups, see How to Create Groups in Operations Manager.
See Also
Using Reports in Operations Manager
How to Create Reports in Operations Manager
How to Save a Report
How to Run a Report
Scheduling Reports
How to Export a Report
Operations Manager Reports Library
The state view in the previous illustration contrasts two “unknown” states.
The agent is shown as healthy, but the indicator is gray.
The operating system is shown as not monitored.
399
The gray icon indicates that the health service watcher on the management server that is
watching the health service on the monitored computer is not receiving heartbeats from the agent
anymore. The health service watcher had received heartbeats previously and the state was
reported as healthy. This also means that the management servers are no longer receiving any
information from the agent.
The not monitored icon indicates that there are no monitors for the object. In the previous
illustration, the view tells you that there are no monitors for the operating system on this
computer. In this case, this is because the management packs for the Windows Server operating
systems have not been imported in this management group.
400
For information on troubleshooting, see the Knowledge Base article Troubleshooting gray agent
state. Although the article was written for Operations Manager 2007, the troubleshooting steps
will also be helpful for System Center 2012 – Operations Manager.
An agent can also show as not monitored because the new agent has the same NetBIOS name
as a previously installed agent. When the agent is deleted from Operations Manager, the
grooming of the deleted agent is occurs after two days. Therefore, the agent is not immediately
groomed out of the database completely. To work around this limitation, wait three days after
deleting the agent to install the new agent.
For more ideas for troubleshooting, see the blog post Getting headaches trying to figure out why
you are seeing the 'Not Monitored' state for Management Servers or Agents?.
See Also
Using the Operations Manager Consoles
Finding Data and Objects in the Operations Manager Consoles
Using Views in Operations Manager
Using SharePoint to View Operations Manager Data
Subscribing to Alert Notifications
Using Reports in Operations Manager
401
Management Server\Management Servers State view.
3. Click the agent you want to see rules and monitors for.
4. In the Tasks pane, select the task Show Running Rules and Monitors for this Health
Service.
5. The Run Task – Show Running Rules and Monitors for this Health Service dialog
box appears. Click Run.
6. The Task Status dialog box appears. When the task is completed, you can click Copy
Text or Copy HTML and paste the task output in the appropriate tool for further review.
See Also
How Heartbeats Work in Operations Manager
Resolving Heartbeat Alerts
Viewing Active Alerts
Viewing Alert Details
Examining Properties of Alerts, Rules, and Monitors
Impact of Closing an Alert
How to Close an Alert Generated by a Monitor
How to Reset Health
Identifying the Computer Experiencing a Problem
Using Health Explorer to Investigate Problems
Using Event View to Investigate Problems
Investigating Alert Storms
How an Alert is Produced
How to Set Alert Resolution States
How to Configure Automatic Alert Resolution
Diagnostic and Recovery Tasks
Viewing and Investigating Alerts for .NET Applications (Server-side Perspective)
Using the Visio 2010 Add-in and SharePoint 2010 Visio Services
Data Provider
The Visio 2010 Add-in for System Center 2012 – Operations Manager combines the strengths of
two applications widely used in enterprise IT to simplify the creation of customized dashboards
that show the health of an environment. The Visio Add-in lets you create diagrams that show
objects by geography on a map, by location in a data center or building, by role in a logical view
of an application, or by topology for complex distributed applications such as Microsoft Exchange
Server or technologies such as Active Directory Domain Services.
The SharePoint 2010 Visio Services Data Provider for System Center 2012 – Operations
Manager enables you to take the customized dashboards you create with the Visio 2010 Add-in
402
and include them in SharePoint 2010 Web sites. These Web-based dashboards are updated and
provide access to instant status information through the familiar SharePoint browser-based
experience.
The Visio 2010 Add-in and SharePoint 2010 Visio Services Data Provider have the following
features:
Distributed applications exported from Operations Manager as Visio documents automatically
show live health state information on the exported objects when opened in Microsoft Office
Visio.
You can easily create new Visio documents and link shapes to any managed object (such as
a computer, database, Web site, or perspective) to show the current health state.
You can automatically link entire existing Visio documents to the computer and to network
devices managed by Operations Manager by matching computer names or IP addresses.
Health states can be automatically refreshed in Visio documents. You can use this option
along with Visio’s full-screen view to create dashboard views suitable for use as a summary
display in a data center control room.
Predefined data graphics enable you to switch from Operations Manager health icons to the
shape color for health state.
Health states can be automatically refreshed in published Visio documents that are hosted in
SharePoint 2010 document libraries, when the Visio Services data provider for System
Center 2012 – Operations Manager is installed and configured on the SharePoint 2010
server farm.
The following topics provide information about how to install, configure, and use the Visio Add-in
and the SharePoint 2010 Visio Services Data Provider.
Install the Visio 2010 Add-in
Install the Visio Services Data Provider
Grant Visio Services with Read-Only Operator Permissions
Configure the Operations Manager Data Source in Visio 2010
View an Operations Manager Distributed Application Diagram in Visio 2010
Add Links to Operations Manager to a New or Existing Visio 2010 Document
Build a simple monitoring dashboard using the Visio Web Part
Publish a Visio diagram to SharePoint 2010
Change the Way Health State is Represented in Visio 2010
Troubleshooting the Visio 2010 Add-in
403
Microsoft Office Visio 2010 Professional or Premium.
The Microsoft .NET Framework 3.5 SP1 (http://go.microsoft.com/fwlink/?LinkID=131605).
When you run the Setup program for the Visio Add-in, your system is checked against these
requirements. If your system does not meet the requirements, a link is provided so that you can
download the missing software.
Note
If you have previously installed the Vision 2007 version of the Add-in on this computer,
uninstall it before installing the Visio 2010 Add-in.
Note
If you previously installed the Visio Add-in with System Center Operations Manager 2007
R2, and upgraded to System Center 2012 – Operations Manager, you must uninstall it
prior to installing the System Center 2012 – Operations Manager version.
Note
You must install SharePoint Server 2010 in a farm environment versus standalone (on a
single server with a built-in database by using the default settings) so that Visio Services
404
can be configured to run as a domain account with Operations Manager access. For
more information about installing SharePoint Server 2010 on a single server farm, see
Deploy a single server with SQL Server (SharePoint Server 2010). For more information
about installing SharePoint Server 2010 on a multiple server farm, see Multiple servers
for a three-tier farm (SharePoint Server 2010).
Note
The .msi program does not install or deploy the data provider to the SharePoint
servers in the server farm. This program simply extracts the SharePoint
deployment package to a location specified by the SharePoint administrator.
4. Open the SharePoint 2010 Management Shell as an administrator.
5. Run the following command:
.\InstallOpsMgrDataModule.ps1
Note
The SharePoint 2010 Administration service must be running prior to running .\
InstallOpsMgrDataModule.ps1
405
The easiest way to configure this is to make the account that Visio Services is running as a Read-
Only Operator on the management server.
If you need to determine the account that is configured for Visio Services, use SharePoint’s
Central Administration:
1. Open the Central Administration site.
2. In the Security section, click Configure Service Accounts.
3. In the list of Service Accounts, select Service Application Pool – SharePoint Web Services
Default.
The account is listed in the Select an account for this component field.
To grant the Visio Services account Read-Only Operator access to the management
server
1. In the Operations console, open the Administration view.
2. In the Administration pane, expand Administration, expand Security, and then click
User Roles.
3. In the User Roles pane, right-click Read-Only Operator, and then click Properties.
4. In the Operations Manager Read-Only Operators – User Role Properties dialog box,
on the General Properties page, click Add.
5. On the Select User or Groups page, enter the account that is configured for Service
Application Pool, and then click OK.
6. Click Apply, and then click OK to close the Operations Manager Read-Only Operators
-User Role Properties dialog box.
Note
This latest version of the Visio 2010 Add-in also functions with Operations Manager 2007
R2. If installing this version with Operations Manager 2007 R2, ensure that credentials
and access are configured to communicate with the root management server (RMS).
To configure the Operations Manager data source and Web console address in Visio
1. Open a new drawing in Visio.
2. Click Operations Manager in the ribbon, and then click Configure.
3. In the Name field, type the name of the management server.
4. In the Address field, type the address for the Web console. This is the console that is
406
used to launch the Health Explorer and Alert view from Visio.
If you do not know the address, and you have Operations Manager administrator
privileges, click Look up web console address. If you do not know the address, and you
are not an Operations Manager administrator, contact the administrator for the address,
and then type it in the Address field.
5. If you want to receive regular updates of state information from the management server,
select Automatically refresh data, and then specify a refresh interval in seconds.
6. Click OK.
407
the object, and then click a data graphic on the right side of Visio.
Note
This latest version of the Visio 2010 Add-in also functions with Operations Manager 2007
R2. If installing this version with Operations Manager 2007 R2, ensure that credentials
and access are configured to the RMS instead of the management server.
1. Click Operations Manager in the ribbon, and then click Link Shape.
2. Select the Operations Manager class of the object, such as Windows Computer, to
display a filtered list of available Operations Manager objects.
3. Select the object that you want to link to this shape, and then click Link.
The shape in the diagram now includes a state indicator in the upper-right corner of the
image.
408
This adds the selected managed objects to the dataset in the Visio diagram, which can
be viewed in the External Data window.
4. In the External Data window, select the object that you want to connect to a shape in the
diagram or image.
For example, if you want to add the management server for a geographic location to a
map, select the management server.
5. Drag the object to the diagram or image and drop it onto the shape. This establishes the
link between the shape and that managed object’s record.
409
3. Select the specific object, and then click Insert.
The new shape is added to the diagram. The shape icon matches those of other Operations
Manager objects of the same class, and the shape data is populated with information from
the management server.
410
available in the Web part toolbar.
411
the three health states and to represent a managed object in maintenance mode.
412
Known issues with the Visio 2010 Add-in
You might see the following issues when you use the Visio Add-in for System
Center 2012 – Operations Manager.
The font size of inserted shapes might appear too small
When you insert a new graphic by using the Insert Shape option, the font size for the shape text
might appear too small. The size is determined by the default font size set for a template.
You can change the font size by selecting the shape and then choosing a different font size in the
Visio toolbar.
Hyperlinks on sub-shapes are not available
Health Explorer and Alert View hyperlinks might not be available in Edit mode or Full Screen
mode if you have grouped your shapes or added links to any shapes that were already contained
within groups.
You receive a ConfigurationErrorsException error message
You might see the following error message:
System.Configuration.ConfigurationErrorsException: Configuration system failed to
initialize --->
\OpsMgrAddin.vsto_vstoloca_Path_logwdvddmizljsrbc2bvt5gtm5juzdix\12.0.6325.5000\
user.config
line 3)
To work around this problem, delete the configuration file identified at the top of the error
message. For example, delete the following file:
\OpsMgrAddin.vsto_vstoloca_Path_logwdvddmizljsrbc2bvt5gtm5juzdix\12.0.6325.5000\
user.config
You receive a MissingMethodException error message
You might see the following error message:
System.MissingMethodException: Method not found: 'System.Security.SecureString
System.Windows.Controls.PasswordBox.get_SecurePassword()'.
at Microsoft.EnterpriseManagement.VisioAddin.EnterCredentials.get_Password()
413
at
Microsoft.EnterpriseManagement.VisioAddin.SCOMHelpers.EnterCredentials(ManagementGroupConn
ectionSettings& connectSettings)
at Microsoft.EnterpriseManagement.VisioAddin.Document.ConnectToManagementGroup()
at Microsoft.EnterpriseManagement.VisioAddin.Document.AddDataLinkToShape()
To resolve this problem, install Microsoft .NET Framework 3.5 SP1, available from
http://go.microsoft.com/fwlink/?LinkID=131605.
The state graphic is not displayed
The state graphic does not appear on a stencil even though you have linked the shape with the
Link Shape to Data option.
Some stencils in Visio are not defined with a wrapping group. To resolve this problem, create a
group for the shape, and then use the Link Shape to Data option again. To create a group, right-
click the shape, and then click Shape and Group.
You see security warnings when you open a diagram
When you open a document that you previously linked to Operations Manager, you receive
multiple security warnings.
This problem occurs because the status of the document components is set to refresh
automatically. To suppress the warnings, select Don’t show this message again.
You cannot re-install the Visio Add-in
If you delete the Operations Manager Add-in by using the Visio Trust Center, you cannot add it
again later.
This behavior occurs by design in Visio. Before you can add the Operations Manager Add-in
again, uninstall it by using Add/Remove Programs (or Programs and Features) in the Control
Panel, and then reinstall it.
414
Other resources for this component
TechNet Library main page for Operations Manager
Operations Guide for System Center 2012 - Operations Manager
Initial Monitoring After Operations Manager Is Installed
Managing Access in Operations Manager
Operations Manager Monitoring Scenarios
Getting Information from Operations Manager
Maintenance of Operations Manager
Operations Manager Report Authoring Guide
Managing Alerts
An alert is an indication of a significant event requiring attention. Rules and monitors can
generate alerts. You can view alerts in the Monitoring workspace of the Operations console or
web console.
415
How to Suspend Monitoring Temporarily by Using Maintenance Mode
Creating and Managing Groups
Running Tasks in Operations Manager
How to Create a Resource Pool
Connecting Management Groups in Operations Manager
Operations Manager Report Authoring Guide
When you see both alerts, you know the computer cannot be contacted by the management
server. When you see only the heartbeat failure alert, you know the computer can be contacted
but there is a problem with the agent. Both alerts are closed automatically when heartbeats
resume.
Note
By default, alerts for missed heartbeats and response to ping are disabled for client
operating systems. To receive alerts for client operating systems, override the Health
416
Service Heartbeat Failure and Computer Not Reachable monitors for the class
Windows Client Operating System to set the Generates Alert parameter to True.
The health state for the agent-managed computer will change to critical (red) when the Health
Service Heartbeat Failure alert is generated. To view details for the health state, right-click the
computer in Active Alerts, point to Open, and click Health Explorer. The Availability node will be
expanded to display the critical item. Click Health Service Heartbeat Failure, and then click the
State Change Events tab. You will see a list of state changes with the date and time of
occurrence. Select any occurrence to display information in the Details pane. The health state
will change to healthy (green) when heartbeats resume.
You can change the heartbeat interval for all agents and number of missed heartbeats for all
management servers in Settings in the Administration workspace, as shown in the following
illustration.
You can also override the global heartbeat interval for individual agents and the number of missed
heartbeats for individual management servers by opening the properties for the computer in
Agent Managed or Management Servers in the Administration workspace. For example, you
might increase the heartbeat interval for a computer that has a slow connection to the network.
See Also
Resolving Heartbeat Alerts
How an Alert is Produced
Viewing Active Alerts
Viewing Alert Details
Examining Properties of Alerts, Rules, and Monitors
Impact of Closing an Alert
How to Close an Alert Generated by a Monitor
How to Reset Health
Identifying the Computer Experiencing a Problem
Using Health Explorer to Investigate Problems
417
Using Event View to Investigate Problems
Investigating Alert Storms
How to View All Rules and Monitors Running on an Agent-Managed Computer
How to Set Alert Resolution States
How to Configure Automatic Alert Resolution
Viewing and Investigating Alerts for .NET Applications (Server-side Perspective)
Diagnostic and Recovery Tasks
Note
Use this same procedure and select Start in step 4 when you are done testing.
Note
Depending on the heartbeat interval and the number of missing heartbeats, a few
minutes might be required to see the alert.
4. Click the alert to highlight it and read the information in the Alert Details area. The Alert
Details area provides information about the alert, including a description and knowledge
about the cause and resolution.
418
How to Troubleshoot Agent Heartbeat Issues
Use the tasks in the Tasks pane to diagnose the cause of the alert. Different alerts have different
tasks. For a Health Service Heartbeat Failure alert, the tasks deal with pinging the system and
verifying or restarting the service.
Note
If the ping fails, use standard networking troubleshooting to figure out the issue
with connectivity. Verify that the system is turned on.
2. Click Close to close the dialog box.
3. Under Health Service Watcher Tasks, click Computer Management. A Computer
Management dialog box for the target system opens.
4. Click Services and Applications to expand it.
5. Click Services to display services.
6. Right-click the System Center Management service, and then click Start.
Note
After the connection with the agent is restored, the alert will be automatically
resolved and the computer status will return to healthy.
These steps will fix the test failure created in this topic, as well as address a number of
possible causes of a Health Service Heartbeat Failure. If an actual failure is not resolved by
these steps, use standard troubleshooting techniques to figure out the cause of the issue. For
instance, the alert displayed in Active Alerts shows how old the alert is. Check for events
that happened at this time to see what might have caused an issue.
A sudden increase in the number of alerts is called an alert storm. An alert storm can be a
symptom of massive changes of some kind within your management group, such as
catastrophic failure of networks. An alert storm can also be a symptom of configuration issues
within Operations Manager. A newly imported management pack starts monitoring
immediately. If you have a large number of managed computers, an unforeseen configuration
issue could cause a large increase in alerts.
See Also
How Heartbeats Work in Operations Manager
How an Alert is Produced
Viewing Active Alerts
Viewing Alert Details
Examining Properties of Alerts, Rules, and Monitors
Impact of Closing an Alert
419
How to Close an Alert Generated by a Monitor
How to Reset Health
Identifying the Computer Experiencing a Problem
Using Health Explorer to Investigate Problems
Using Event View to Investigate Problems
Investigating Alert Storms
How to View All Rules and Monitors Running on an Agent-Managed Computer
How to Set Alert Resolution States
How to Configure Automatic Alert Resolution
Diagnostic and Recovery Tasks
Viewing and Investigating Alerts for .NET Applications (Server-side Perspective)
420
Most alerts generated by monitors will be automatically resolved when the health state returns to
healthy. If a monitor is not configured to automatically resolve its alert, you can configure an
override on the parameter Auto-Resolve Alert for the monitor.
Note
Rules cannot automatically resolve alerts.
Unlike monitors, rules can continue to send alerts as long as the condition that caused the alert
persists or repeats. Depending on what the rule is checking for, a single issue could possibly
generate a huge number of alerts. To prevent the noise of too many alerts, alert suppression can
be enabled for a rule.
Note
Alert suppression can only be enabled when the rule is created. You cannot enable alert
suppression by using an override.
When alert suppression is enabled for a rule, only the first alert is sent and further alerts are
suppressed. A suppressed alert is not displayed in the Operations console. Operations Manager
suppresses only duplicate alerts as defined by the alert suppression criteria. Fields stated in the
suppression criteria must be identical for the alert to be considered a duplicate and suppressed.
An alert must be created by the same rule and be unresolved to be considered a duplicate.
You can personalize the Active Alerts view to add the Repeat Count column. The repeat count
for an alert with suppression enabled will be incremented for each suppressed alert. You can also
view the repeat count in the properties for an alert.
Important
By default, all alerts that are generated by monitors and that use the same instance ID
are suppressed, however nothing in the alert properties as viewed in a console will
indicate that suppression is enabled. Alerts that are generated by rules will also be
421
suppressed by default if the rule definition in the management pack contains an empty
Suppression Value tag, however nothing in the alert properties as viewed in a console will
indicate that suppression is enabled. You will only be aware of the suppression if you
view the Repeat Count column for the alert.
See Also
How Heartbeats Work in Operations Manager
Resolving Heartbeat Alerts
Viewing Active Alerts
Viewing Alert Details
Examining Properties of Alerts, Rules, and Monitors
Impact of Closing an Alert
How to Close an Alert Generated by a Monitor
How to Reset Health
Identifying the Computer Experiencing a Problem
Using Health Explorer to Investigate Problems
Using Event View to Investigate Problems
Investigating Alert Storms
How to View All Rules and Monitors Running on an Agent-Managed Computer
How to Set Alert Resolution States
How to Configure Automatic Alert Resolution
Diagnostic and Recovery Tasks
Viewing and Investigating Alerts for .NET Applications (Server-side Perspective)
422
To view the actual alerts, click Active Alerts in the navigation pane.
Tip: If you are using the Web console, you can filter the view of alerts by severity:
The list of alerts in the Results pane includes the severity, source, maintenance mode status,
name, resolution state, and when the alert was created:
The following folders in the Monitoring workspace include a standard Active Alerts view scoped to
the objects for that folder.
Data Warehouse
Network Monitoring
Operations Manager
Operations Manager\Agent Details
Operations Manager\APM Agent Details
Management Server
Notification
UNIX/Linux Servers
423
Web Application Availability Monitoring
See Also
How Heartbeats Work in Operations Manager
Resolving Heartbeat Alerts
How an Alert is Produced
Viewing Alert Details
Examining Properties of Alerts, Rules, and Monitors
Impact of Closing an Alert
How to Close an Alert Generated by a Monitor
How to Reset Health
Identifying the Computer Experiencing a Problem
Using Health Explorer to Investigate Problems
Using Event View to Investigate Problems
Investigating Alert Storms
How to View All Rules and Monitors Running on an Agent-Managed Computer
How to Set Alert Resolution States
How to Configure Automatic Alert Resolution
Diagnostic and Recovery Tasks
Viewing and Investigating Alerts for .NET Applications (Server-side Perspective)
Standard Views in Operations Manager
424
Tips
Locate and investigate monitors in the Warning and Error states in the Health Explorer of the
computer that was the source of the alert. (To open Health Explorer, right-click the alert, point
to Open, and click Health Explorer.) If there are unhealthy monitors, they may correlate with
the alert you are researching. Check out the Context pane of the State Change Events tab
for possible additional clues to the root cause.
Read all text in the alert properties. (Right-click the alert, and select Properties.) In particular,
carefully review the Alert Description field on the General tab and the Description field on
the Alert Context tab.
Right-click the alert, and open the Event view. Sort the events by the Level column, and then
locate the events with the Error and Warning event levels. Events may correlate with the
alert you are investigating and provide insight to its resolution.
See Also
How Heartbeats Work in Operations Manager
Resolving Heartbeat Alerts
How an Alert is Produced
Viewing Active Alerts
Examining Properties of Alerts, Rules, and Monitors
Impact of Closing an Alert
How to Close an Alert Generated by a Monitor
How to Reset Health
Identifying the Computer Experiencing a Problem
Using Health Explorer to Investigate Problems
Using Event View to Investigate Problems
Investigating Alert Storms
How to View All Rules and Monitors Running on an Agent-Managed Computer
How to Set Alert Resolution States
How to Configure Automatic Alert Resolution
Diagnostic and Recovery Tasks
Viewing and Investigating Alerts for .NET Applications (Server-side Perspective)
425
Tab Description
Tab Description
Tab Description
427
Tab Description
Diagnostic and Recovery This tab lists any diagnostic or recovery tasks
associated with this monitor. Administrators can
add either type of task to the monitor on this
tab.
See Also
How Heartbeats Work in Operations Manager
Resolving Heartbeat Alerts
How an Alert is Produced
Viewing Active Alerts
Viewing Alert Details
Impact of Closing an Alert
428
How to Close an Alert Generated by a Monitor
How to Reset Health
Identifying the Computer Experiencing a Problem
Using Health Explorer to Investigate Problems
Using Event View to Investigate Problems
Investigating Alert Storms
How to View All Rules and Monitors Running on an Agent-Managed Computer
How to Set Alert Resolution States
How to Configure Automatic Alert Resolution
Diagnostic and Recovery Tasks
Viewing and Investigating Alerts for .NET Applications (Server-side Perspective)
See Also
How Heartbeats Work in Operations Manager
429
Resolving Heartbeat Alerts
Viewing Active Alerts
Viewing Alert Details
Examining Properties of Alerts, Rules, and Monitors
How an Alert is Produced
How to Close an Alert Generated by a Monitor
How to Reset Health
Identifying the Computer Experiencing a Problem
Using Health Explorer to Investigate Problems
Using Event View to Investigate Problems
Investigating Alert Storms
How to View All Rules and Monitors Running on an Agent-Managed Computer
How to Set Alert Resolution States
How to Configure Automatic Alert Resolution
Diagnostic and Recovery Tasks
Viewing and Investigating Alerts for .NET Applications (Server-side Perspective)
See Also
How Heartbeats Work in Operations Manager
Resolving Heartbeat Alerts
Viewing Active Alerts
Viewing Alert Details
Examining Properties of Alerts, Rules, and Monitors
Impact of Closing an Alert
How an Alert is Produced
How to Reset Health
Identifying the Computer Experiencing a Problem
Using Health Explorer to Investigate Problems
Using Event View to Investigate Problems
Investigating Alert Storms
How to View All Rules and Monitors Running on an Agent-Managed Computer
How to Set Alert Resolution States
How to Configure Automatic Alert Resolution
Diagnostic and Recovery Tasks
Viewing and Investigating Alerts for .NET Applications (Server-side Perspective)
Note
431
Only reset health for a monitor when you are sure that all issues have been resolved.
Note
You may also notice Recalculate Health on the toolbar. This function
reexamines the health state of a monitor or monitors; however, it only works with
monitors that implement On Demand Detection. Most monitors do not
implement On Demand Detection.
The following message displays: Resetting the health of a monitor may take several
minutes and will not be reflected in the Health Explorer immediately. The health
state of some monitors cannot be reset and will not be updated as a result of this
request. Do you wish to continue?
3. If you are sure that you want to reset the monitor, click Yes.
4. Return to the Monitoring workspace, right-click the alert, point to Set Resolution State,
and click Closed.
See Also
How Heartbeats Work in Operations Manager
Resolving Heartbeat Alerts
Viewing Active Alerts
Viewing Alert Details
Examining Properties of Alerts, Rules, and Monitors
Impact of Closing an Alert
How to Close an Alert Generated by a Monitor
How an Alert is Produced
Identifying the Computer Experiencing a Problem
Using Health Explorer to Investigate Problems
Using Event View to Investigate Problems
Investigating Alert Storms
How to View All Rules and Monitors Running on an Agent-Managed Computer
How to Set Alert Resolution States
How to Configure Automatic Alert Resolution
Diagnostic and Recovery Tasks
Viewing and Investigating Alerts for .NET Applications (Server-side Perspective)
432
Identifying the Computer Experiencing a Problem
This topic helps you answer questions such as “I see an alert that says logical disk
defragmentation is high. Where is it high?”
Notice that this alert also includes the affected computer in the Description.
3. Click Windows Computers to view the state of the computer.
433
In this illustration, you see that the logical disk fragmentation levels for C: and D: on this computer
are in a warning state. Notice that the state rolls up to the Performance state for each disk, then
to Hardware Performance for the computer, then to Performance for the computer, and finally
to Entity Health for the computer.
See Also
How Heartbeats Work in Operations Manager
Resolving Heartbeat Alerts
Viewing Active Alerts
Viewing Alert Details
Examining Properties of Alerts, Rules, and Monitors
Impact of Closing an Alert
How to Close an Alert Generated by a Monitor
How to Reset Health
How an Alert is Produced
Using Health Explorer to Investigate Problems
Using Event View to Investigate Problems
Investigating Alert Storms
How to View All Rules and Monitors Running on an Agent-Managed Computer
434
How to Set Alert Resolution States
How to Configure Automatic Alert Resolution
Diagnostic and Recovery Tasks
Viewing and Investigating Alerts for .NET Applications (Server-side Perspective)
435
Click a monitor to view more information about the monitor in the Details pane. The State
Change Events tab in the Details pane shows you when the state for the monitor changed, and
the details give you information for the context of the state change:
436
See Also
How Heartbeats Work in Operations Manager
Resolving Heartbeat Alerts
Viewing Active Alerts
Viewing Alert Details
Examining Properties of Alerts, Rules, and Monitors
Impact of Closing an Alert
How to Close an Alert Generated by a Monitor
How to Reset Health
Identifying the Computer Experiencing a Problem
How an Alert is Produced
Using Event View to Investigate Problems
Investigating Alert Storms
How to View All Rules and Monitors Running on an Agent-Managed Computer
How to Set Alert Resolution States
How to Configure Automatic Alert Resolution
Diagnostic and Recovery Tasks
Viewing and Investigating Alerts for .NET Applications (Server-side Perspective)
437
Using Health Explorer in Operations Manager
In the Details pane, click Generating Rule to view information about the rule that generated the
alert. The General tab shows you the name, description, and the source management pack of the
rule.
438
See Also
How Heartbeats Work in Operations Manager
Resolving Heartbeat Alerts
Viewing Active Alerts
Viewing Alert Details
Examining Properties of Alerts, Rules, and Monitors
Impact of Closing an Alert
How to Close an Alert Generated by a Monitor
How to Reset Health
Identifying the Computer Experiencing a Problem
Using Health Explorer to Investigate Problems
How an Alert is Produced
Investigating Alert Storms
How to View All Rules and Monitors Running on an Agent-Managed Computer
How to Set Alert Resolution States
How to Configure Automatic Alert Resolution
Diagnostic and Recovery Tasks
439
Viewing and Investigating Alerts for .NET Applications (Server-side Perspective)
See Also
How Heartbeats Work in Operations Manager
440
Resolving Heartbeat Alerts
Viewing Active Alerts
Viewing Alert Details
Examining Properties of Alerts, Rules, and Monitors
Impact of Closing an Alert
How to Close an Alert Generated by a Monitor
How to Reset Health
Identifying the Computer Experiencing a Problem
Using Health Explorer to Investigate Problems
Using Event View to Investigate Problems
How an Alert is Produced
How to View All Rules and Monitors Running on an Agent-Managed Computer
How to Set Alert Resolution States
How to Configure Automatic Alert Resolution
Diagnostic and Recovery Tasks
Viewing and Investigating Alerts for .NET Applications (Server-side Perspective)
441
3. Double-click Alerts.
4. On the Alert Resolution States tab, click New.
5. In Add Alert Resolution State, type a name for the resolution state and select a value in
the Unique ID box, and then click OK.
6. In Global Management Group Settings – Alerts, click OK.
See Also
How Heartbeats Work in Operations Manager
Resolving Heartbeat Alerts
Viewing Active Alerts
Viewing Alert Details
Examining Properties of Alerts, Rules, and Monitors
Impact of Closing an Alert
How to Close an Alert Generated by a Monitor
How to Reset Health
Identifying the Computer Experiencing a Problem
Using Health Explorer to Investigate Problems
Using Event View to Investigate Problems
Investigating Alert Storms
How to View All Rules and Monitors Running on an Agent-Managed Computer
How an Alert is Produced
How to Configure Automatic Alert Resolution
Diagnostic and Recovery Tasks
Viewing and Investigating Alerts for .NET Applications (Server-side Perspective)
442
5. Change the days for either or both of the following settings:
6. Click OK.
See Also
How Heartbeats Work in Operations Manager
Resolving Heartbeat Alerts
Viewing Active Alerts
Viewing Alert Details
Examining Properties of Alerts, Rules, and Monitors
Impact of Closing an Alert
How to Close an Alert Generated by a Monitor
How to Reset Health
Identifying the Computer Experiencing a Problem
Using Health Explorer to Investigate Problems
Using Event View to Investigate Problems
Investigating Alert Storms
How to View All Rules and Monitors Running on an Agent-Managed Computer
How to Set Alert Resolution States
How an Alert is Produced
Viewing and Investigating Alerts for .NET Applications (Server-side Perspective)
Running Tasks in Operations Manager
Diagnostic and Recovery Tasks
443
Monitors can have two kinds of tasks associated with them: diagnostic tasks that try to discover
the cause of a problem or provide you with additional information to assist with that diagnosis,
and recovery tasks that try to fix the problem.
Diagnostic and recovery tasks can run a script or command line executable. These tasks can be
run automatically when the monitor enters an error state, providing an automated way to solve
problems.
Diagnostic and recovery tasks can only be created for a specific monitor. A diagnostic or recovery
task that you create for one monitor cannot be shared with or associated with a different monitor;
you must recreate the task for each monitor. In addition, tasks that you create in the Authoring
workspace using the Create Task Wizard cannot be used as a diagnostic or recovery for a
monitor.
For example, the Health Service Heartbeat Failure monitor has several diagnostic and recovery
tasks associated with it. The following list provides a sample of the tasks associated with the
monitor.
Ping Computer on Heartbeat Failure and Check If Health Service Is Running
These are diagnostic tasks that run automatically when the state for this monitor changes to
critical (red).
Set the "Computer Not Reachable" monitor to success because the "Ping Computer
on Heartbeat Failure" diagnostic succeeded
This is a recovery task that runs automatically when the Ping Computer on Heartbeat
Failure task succeeds.
Restart Health Service
This is a recovery task that you can run manually or you can enable it to run automatically by
using an override.
You can see the tasks available for a monitor on the Diagnostic and Recovery tab in the
properties of the monitor, as shown in the following illustration.
444
On this tab, you can also add tasks or edit tasks that you have added previously. For more
information on how to add diagnostic and recovery tasks, see Diagnostics and Recoveries in the
Author’s Guide. Tasks that are configured by a sealed management pack can only be modified by
using overrides. For more information, see How to Enable Recovery and Diagnostic Tasks.
See Also
How Heartbeats Work in Operations Manager
Resolving Heartbeat Alerts
Viewing Active Alerts
Viewing Alert Details
Examining Properties of Alerts, Rules, and Monitors
445
Impact of Closing an Alert
How to Close an Alert Generated by a Monitor
How to Reset Health
Identifying the Computer Experiencing a Problem
Using Health Explorer to Investigate Problems
Using Event View to Investigate Problems
Investigating Alert Storms
How to View All Rules and Monitors Running on an Agent-Managed Computer
How to Set Alert Resolution States
How to Configure Automatic Alert Resolution
How an Alert is Produced
Viewing and Investigating Alerts for .NET Applications (Server-side Perspective)
Running Tasks in Operations Manager
446
Selected objects and all their contained objects.
6. Select Planned if this is a planned event; otherwise, leave it cleared.
7. In the Category list, click the appropriate maintenance category.
8. Under Duration, select and enter the Number of minutes or select and enter the
Specific end time, and then click OK. A maintenance mode icon appears in the
Computers pane, in the Maintenance Mode column for the computer you selected.
Note
The minimum value for Number of minutes is 5. The maximum value is
1,051,200 (2 years).
Note
Because Operations Manager polls maintenance mode settings only once
every 5 minutes, there can be a delay in an object's scheduled removal from
maintenance mode.
447
See Also
General Tasks in Operations Manager
Managing Alerts
Connecting Management Groups in Operations Manager
Creating and Managing Groups
Running Tasks in Operations Manager
How to Create a Resource Pool
Managing Resource Pools for UNIX and Linux Computers
Using Operations Manager Shell
448
The icons differentiate between computer groups and instance groups, as shown in the following
image.
Computer groups only contain computers. Instance groups can contain all object types, such as
an instance of a health service or an instance of a SQL database. Both computer groups and
instance groups can contain other computer and instance groups. Another way to view the
difference between the group types is:
An instance group is populated with objects that match your criteria.
A computer group is populated by computers that host objects that match your criteria.
Using the Operations console, you can only create instance groups. To create a computer group,
you must use the Authoring console or work directly in the XML of a management pack.
449
Connecting Management Groups in Operations Manager
Operations Manager Report Authoring Guide
See Also
General Tasks in Operations Manager
Managing Alerts
How to Suspend Monitoring Temporarily by Using Maintenance Mode
Using Operations Manager Shell
Running Tasks in Operations Manager
How to Create a Resource Pool
Managing Resource Pools for UNIX and Linux Computers
Connecting Management Groups in Operations Manager
450
You can assign both explicit and dynamic members in the same group definition, and you can
exclude explicit members. For examples of dynamic group queries and formulas, see Operations
Manager Dynamic Group Examples.
451
steps:
a. In the Search for list, select an object type, such as Windows Computer.
b. Optionally, in the Filter by part of the name box, type all or part of the object name,
and then click Search.
c. In the Available items box, select the desired objects, click Add, and then click
Next.
6. On the Dynamic Members - Create a Membership Formula page, you can add a
dynamic membership formula to the group or click Next to continue to the Subgroups
page. To add a dynamic membership formula, click Create/Edit rules and then perform
the following steps:
Warning
This procedure tells you how to create a query for Windows computers based on
NetBIOS computer name.
a. In the Query Builder dialog box, leave the default Windows Computer and click
Add.
b. In the Property list, select NetBIOS computer name.
c. In the Operator list, select Contains.
d. Set Value to part of the name of the computers you want in the group, such as NY or
MKTG.
Note
Click Insert to add an Expression or group expressions with OR or AND
operators. Repeat the preceding steps to add additional object types to the
rule.
e. Click OK, review the Query formula, and then click Next.
7. On the Choose Optional Subgroups page, either click Next to not add groups to the
group, or click Add/Remove Subgroups to add groups, for example.
a. In the Group Selection dialog box, in Filter by part of name, you can optionally
type part or the all of the group's names, and then click Search.
b. In the Available items text box, select the desired groups, click Add, click OK, and
then click Next.
8. On the Excluded Members - Specify Exclude List page, click Finish to not exclude
objects from the group, or click Exclude Objects, and then perform the following steps:
a. In the Object Exclusion dialog box, from the Search for list, select an object type,
such as Windows Computer.
b. Optionally, in the Filter by part of the name box, type all or part of the object name,
and then click Search.
c. In the Available items text box, select the objects you want to exclude, click Add,
click OK, and then click Finish.
Note
It can take approximately one minute to populate the membership of a group.
452
See Also
Creating and Managing Groups
Define a Scope Using Operations Manager Groups
Using Classes and Groups for Overrides in Operations Manager
How to View Group Members, State, and Diagram
How to Create Subscriptions Using Classes and Groups
Guidance for Scoping and Targeting Views
See Also
Creating and Managing Groups
Define a Scope Using Operations Manager Groups
Using Classes and Groups for Overrides in Operations Manager
How to Create Groups in Operations Manager
How to Create Subscriptions Using Classes and Groups
Guidance for Scoping and Targeting Views
Note
If the Tasks pane is not displayed, click Tasks on the toolbar to display it.
453
Click an alert or object to see tasks for that alert or object. Click a task to run the task.
In the example above, if you click the first task (Check Health Service Startup Configuration
Diagnostic Task), you see a Run Task dialog box:
454
Tasks use the default action account, unless you specify other credentials in this dialog box.
Tasks can also be configured by a management pack author to use a specific Run As profile.
Generally, you should accept the defaults and click Run. You will then see a Task Status window:
In this instance, the task could not be completed successfully. Task Output provides you with
instructions on troubleshooting the issue.
See Also
General Tasks in Operations Manager
Managing Alerts
How to Suspend Monitoring Temporarily by Using Maintenance Mode
Creating and Managing Groups
Connecting Management Groups in Operations Manager
How to Create a Resource Pool
Managing Resource Pools for UNIX and Linux Computers
Using Operations Manager Shell
Note
The membership of the All Management Servers Resource Pool is read-only.
455
For information about configuring resource pools with managed UNIX and Linux computers and
for configuring certificates, see Managing Resource Pools for UNIX and Linux Computers.
By default, all management servers are members of the resource pools created when Operations
Manager is installed, and any management servers added to the management group are
automatically added to the resource pools that have an automatic membership type. You can
remove individual management servers from those resource pools, however that will change the
membership type to manual. If you add a management server to a management group after the
membership type of the resource pools created when Operations Manager was installed is
changed to manual, you must add the management server to the resource pool manually.
456
Manager Administrators role.
2. Click Administration.
3. In the navigation pane, click Resource Pools.
4. In the results pane, click the resource pool that you want to modify.
5. In the Tasks pane, click Manual Membership, and then click Yes in the Manual
Membership message.
Important
When you click Yes, the membership type of the selected resource pool changes
to manual. Even if you make no changes to the resource pool membership and
cancel the properties dialog box, the membership type will remain manual after
this step.
6. On the General Properties page for the resource pool, click Next.
7. On the Pool Membership page, click the management servers that you want to remove
from the resource pool, click Remove, and then click Next.
8. On the Summary page, click Save.
See Also
General Tasks in Operations Manager
Managing Alerts
How to Suspend Monitoring Temporarily by Using Maintenance Mode
Creating and Managing Groups
Running Tasks in Operations Manager
Connecting Management Groups in Operations Manager
Managing Resource Pools for UNIX and Linux Computers
Using Operations Manager Shell
457
Resource Pool. The following procedure does not modify the members of a resource pool, only
what the resource pool manages.
4. Copy the exported file to a shared directory that is accessible by all the management
servers in the resource pool.
5. Repeat the previous four steps until the shared directory contains all the exported
certificate files from each management server in the resource pool.
6. Log on to a management server to start the process of importing certificates.
7. At the command prompt, change the directory to %ProgramFiles%\System Center
Operations Manager 2012\Server.
8. Run the following command for each exported certificate file (except for the file that was
exported by the current management server):
458
scxcertconfig.exe –import <filename>
Note
If you attempt to import the certificate file that was exported by that same
management server, the process will fail with an error message that the object or
property already exists.
9. Repeat the previous three steps until all the certificate files have been imported to the
applicable management servers in the resource pool.
10. Delete the certificate files from the shared directory. Although the file contains only the
public key of the certificate, you should still treat it as a security-sensitive file.
Perform this procedure whenever you add a new management server to the resource pool so that
high availability is maintained.
See Also
General Tasks in Operations Manager
Managing Alerts
How to Suspend Monitoring Temporarily by Using Maintenance Mode
Creating and Managing Groups
Running Tasks in Operations Manager
How to Create a Resource Pool
Using Operations Manager Shell
Note
Operations Manager does not support communication of data between peer
management groups. Only the local to connected hierarchy configuration is supported.
Multiple tiers, where a management group would be both a local group and a connected
group, are not supported.
When you connect management groups, you are not deploying any new servers; rather, you are
allowing the local management group to have access to the alerts and discovery information that
is in a connected management group. In this way, you can view and interact with all the alerts and
459
other monitoring data from multiple management groups in a single Operations console. In
addition, you can run tasks on the monitored computers of the connected management groups.
Connecting management groups offers these additional services:
Consolidated monitoring and alerting for greater than 6,000 agents
Consolidated monitoring across trust boundaries
Important
Both management groups must be running the same build of Operations Manager. For
example, both management groups must be running System Center 2012 – Operations
Manager.
In addition to all of the communications channels used in the multiple server, single management
group configuration, connected management groups require communication between the
management servers of the local group and the management servers of the connected group
over TCP 5723 and 5724. For a complete list of ports used by Operations Manager, see
Operations Manager Supported Configurations.
Connected management groups support all Operations Manager user roles and makes use of the
Operations Manager Connector Framework to enable bidirectional communication between the
connected groups and local groups.
In this procedure, you create a connection between two management groups. These
management groups can be in the same domain, or they can be in trusted domains. You can
connect to management groups that are in domains that are not trusted, but you cannot view data
from those domains until you add an account from the domain of the local management groups to
an Operations Manager role for the connected management group. To do this, a trust must be
established between the domains.
Note
If local and connected management groups are not in the same domain and
there is no trust relationship between the two domains, you will have to create
accounts in the connected management group domain for the users in the local
management group domain to use.
3. In the Operations console for the local management group, in the Administration view,
expand Security, and then click User Roles.
4. In the right pane, right-click the user role to which you want to grant connected
management group access, and then click Properties.
5. On the Group Scope tab, select the connected management groups to which you want
to grant access to this user role, and then click OK. A user with both permission and
access to at least one connected management group will see the Show Connected
461
Alerts button in the toolbar of any Alert view in the Monitoring space.
6. A Log On dialog box appears and prompts the user for credentials (to log on to the
connected management groups). Enter the credentials, and then click OK. Alerts appear
from all connected management groups for which you have access and permission. You
can run tasks in the managed computers of connected management groups.
See Also
General Tasks in Operations Manager
Managing Alerts
How to Suspend Monitoring Temporarily by Using Maintenance Mode
Creating and Managing Groups
Running Tasks in Operations Manager
How to Create a Resource Pool
Managing Resource Pools for UNIX and Linux Computers
Using Operations Manager Shell
You can access cmdlet help in the Operations Manager Shell by typing Get-Help cmdlet name or
view the help online at Cmdlets in System Center 2012 – Operations Manager.
To learn more about Windows PowerShell, see Windows PowerShell Getting Started Guide.
See Also
General Tasks in Operations Manager
462
Managing Alerts
How to Suspend Monitoring Temporarily by Using Maintenance Mode
Creating and Managing Groups
Running Tasks in Operations Manager
How to Create a Resource Pool
Managing Resource Pools for UNIX and Linux Computers
Connecting Management Groups in Operations Manager
463
such as management servers. It also shows you recent agent health state including gray agents,
agent configuration for agents pending management, and agent versions.
You can display Management Group Health on a SharePoint site by using the Operations
Manager Web Part, giving all authorized users a useful summary of management group status.
For more information, see Using SharePoint to View Operations Manager Data.
Management Group Health automatically refreshes every 15 minutes by default. To manually
refresh the view, right-click the view and click Refresh. It may take some time before the
dashboard starts to show data. The agent data is recalculated every 15 minutes, and not when
you refresh the dashboard.
This topic describes the specific information you will see in each cell of the Management Group
Health dashboard view.
Management Group Functions shows you the health state of any of the following functions that
are installed in your management group:
Agentless exception monitoring
Audit collection services
System Center Data Access service group
System Center Management service group
Network discovery
Resource pools
Web user interfaces (web console and reporting web site)
You can open Health Explorer, alert view, diagram view, event view, performance view, and state
view for any of the functions listed. To open a different view, right-click the display name for the
function, and click Health Explorer or Navigation.
464
Management Group Infrastructure
Management Group Infrastructure shows you the health state of any of the following
infrastructure features that are installed in your management group:
Operational database
Data warehouse database
Management group
Management servers
Gateway servers
Agents
You can open Health Explorer, alert view, diagram view, event view, performance view, and state
view for any of the features listed. To open a different view, right-click the display name for the
feature, and click Health Explorer or Navigation.
Agent Health State displays a graph of health states for all agents over the past 7 days.
Note
465
The screenshot for Agent Health State displays 9 hour’s worth of data. As additional
data is collected, the scale will compress to show a maximum of 7 day’s worth of data.
The graph captures all possible agent states, including “unavailable”, or “gray”, agents. It is
possible to unselect health states, if you only want to focus on certain health states.
Agent Configuration
In Agent Configuration, you can see how the status of agents in the Pending Management
folder in the Administration workspace. Agents can be pending management for the following
reasons:
Manual agent install
Installation in progress
Agent update in progress
Repair in progress
Agent license limit exceeded
Failed agent installation
Agent requires update
Repair failed
Agent Versions
Agent Versions lists the number of agents running each agent version number, including
cumulative updates.
See Also
Maintenance of Operations Manager
How to Configure Grooming Settings for the Reporting Data Warehouse Database
466
Inventory of Operations Manager Infrastructure
Scheduling Maintenance in Operations Manager
How and When to Clear the Cache
How to Restart a Management Server
How to Configure Grooming Settings for the Operations Manager Database
Recommendations for Daily, Weekly, and Monthly Operations Manager Tasks
467
Whether it has ever been migrated to other hardware, or from physical to virtual or
vice versa
Any major issues such outages and other major downtimes
Installed language
Reporting feature:
What is the SSRS url
What SQL server is hosting is the Data Warehouse
Web console:
What is the url
Is SSL used
Is it published to the internet
Placement:
Fully qualified domain name (FQDN) of forest
LAN segment
Environment, such as production, testing, or anything else
Version of Operations Manager, including any cumulative updates
Management servers:
FQDN
IP address
LAN segment
Physical location (even when it is virtualized)
Physical or virtual computer
Amount of CPU, RAM, disks
Operating system and patch level
Disk configuration, RAID settings, and sizes
Whether it is clustered or not
Any SMS-enabled devices attached to it
Accounts and passwords (encrypted)
Operations Manager SDK Account
Operations Manager Action Account
Operations Manager Data Warehouse Read Account
Operations Manager Data Warehouse Write Account
Operations Manager Health Account
Any third party software account
Run-As-Profile accounts (such as accounts used for the SQL Server and Active
Directory management packs)
Backup of encryption key and its location
The total amount of gateway servers and per gateway server:
468
FQDN
IP address
LAN segment
Physical location (even when it is virtualized)
Physical or virtual computer
Amount of CPU, RAM, disks
Operating system and patch level
Disk configuration, RAID settings, and sizes
Functions of gateway server: what is being monitored and how many
Whether the gateway server is configured in a fail-over configuration
FQDN of PKI which is used
Operations Manager Action Account for the forest (and its password) where the gateway
server resides
SQL Server and Operations Manager databases
FQDN
IP address
LAN segment
Physical location (even when it is virtualized)
Physical or virtual computer
Amount of CPU, RAM, disks
Operating system and patch level
SQL Server:
Version
Edition
Architecture
Patch level (service packs, cumulative updates, and so forth)
Installed features
Disk configuration, RAID settings, and sizes
Whether it is clustered or not
If the SQL server also hosts other databases or SQL instances
Operations Manager database sizes and locations
Management packs:
Which Microsoft management packs are imported and configured, including version
information
Which management packs are custom-made, including version information
Which non-Microsoft management packs are imported and configured, including version
information
Backups:
Are the Operations Manager databases backed up on a regular basis
469
What tooling is used
Where are the backups stored
What retention policy is used
Are the Operations Manager servers backed up on a regular basis
What tooling is used
Where are the backups stored
What retention policy is used
Are the unsealed management packs backed up on a regular basis
Are the backups tested on their validity on a regular basis
See Also
Maintenance of Operations Manager
Monitoring the Health of the Management Group
How to Configure Grooming Settings for the Reporting Data Warehouse Database
Scheduling Maintenance in Operations Manager
How and When to Clear the Cache
How to Restart a Management Server
How to Configure Grooming Settings for the Operations Manager Database
Recommendations for Daily, Weekly, and Monthly Operations Manager Tasks
470
Task Description Schedule
database.
Detect and Fix Object Space A rule that repairs data block Every 30 minutes
Inconsistencies corruption in database schema
objects.
Alert Auto Resolve Execute All A rule that automatically Every day at 4 AM
resolves active alerts after a
period of time.
Note
The scheduled times of the grooming jobs cannot be reconfigured by using an
override. If you need to change the schedules of these maintenance tasks, you
must first disable them with an override and then create new system rules that
match the configuration of the original rules with new schedules.
See Also
Maintenance of Operations Manager
Monitoring the Health of the Management Group
Inventory of Operations Manager Infrastructure
How to Configure Grooming Settings for the Reporting Data Warehouse Database
How and When to Clear the Cache
How to Restart a Management Server
How to Configure Grooming Settings for the Operations Manager Database
Recommendations for Daily, Weekly, and Monthly Operations Manager Tasks
471
How and When to Clear the Cache
In System Center 2012 – Operations Manager, when troubleshooting an issue with the
Operations console or with an agent, you may see recommendations to “clear the cache”. (For
example, see the Knowledge Base article Troubleshooting gray agent state.) The following table
explains how and when to clear the console cache or agent cache.
Ope Open the Operations Use this Opening the Operations console with
ratio console with the method to /clearcache deletes the following file:
ns /clearcache parameter. open the %systemdrive%\Users\username\AppData\
cons "C:\Program Files\System Operation Local\Microsoft\
ole Center Operations Manager s console Microsoft.EnterpriseManagement.Monitoring.Co
2012\Console\ if you nsole\momcache.mdb
Microsoft.EnterpriseManag experienc
ement.Monitoring.Console. e errors
exe" /clearcache trying to
retrieve
data in
views,
such as
ObjectNot
FoundExc
eptions, or
when the
cache file
grows too
large and
you want
to reduce
its size on
disk.
Heal 1. In the Monitoring This Clearing the agent cache can cause data loss of
th workspace, expand should be monitoring data from that system.
servi Operations Manager the final 1. Stops the System Center Management
ce and then expand step when service.
on Agent Details. troublesho 2. Deletes the health service store files.
age 2. Click Agent Health oting
3. Resets the state of the agent, including all
nt- State. issues rules, monitors, outgoing data, and cached
man 3. In Agent State, click with the management packs.
age an agent. agent,
4. Starts the System Center Management
d 4. In the Tasks pane, before
472
Cac How to clear When Results
he
Heal 1. In the Monitoring Run this Clearing the agent cache can cause data loss of
th workspace, expand task on a monitoring data from agents to the management
servi Operations Manager managem server.
ce and then expand ent server 1. Stops the System Center Management
on Management Server. when the service.
man 2. Click Management managem 2. Deletes the health service store files.
age Servers State. ent server
3. Resets the state of the agent, including all
men 3. In Management is not rules, monitors, outgoing data, and cached
t Server State, click a functional, management packs.
serv management server. a restart
4. Starts the System Center Management
er 4. In the Tasks pane, has not service.
click Flush Health fixed the
Service State and problem, Note
Cache. and you Because this task deletes the cached
have data in the health service store files,
exhausted including the record of this task itself, no
other task status will be reported on
troublesho completion of the task.
oting
options.
See Also
Maintenance of Operations Manager
Monitoring the Health of the Management Group
Inventory of Operations Manager Infrastructure
Scheduling Maintenance in Operations Manager
How to Configure Grooming Settings for the Reporting Data Warehouse Database
How to Restart a Management Server
473
How to Configure Grooming Settings for the Operations Manager Database
Recommendations for Daily, Weekly, and Monthly Operations Manager Tasks
See Also
Maintenance of Operations Manager
Monitoring the Health of the Management Group
Inventory of Operations Manager Infrastructure
Scheduling Maintenance in Operations Manager
How and When to Clear the Cache
How to Configure Grooming Settings for the Reporting Data Warehouse Database
How to Configure Grooming Settings for the Operations Manager Database
Recommendations for Daily, Weekly, and Monthly Operations Manager Tasks
474
Data Set Aggregation Type Days To Be Kept
Settings for grooming the data warehouse can be changed through Microsoft SQL Server
Management Studio.
475
Note
After you have located the dataset and its aggregation type, scroll to the MaxDataAgeDays
column, and then edit the value there to set the grooming interval.
See Also
Maintenance of Operations Manager
Monitoring the Health of the Management Group
Inventory of Operations Manager Infrastructure
Scheduling Maintenance in Operations Manager
How and When to Clear the Cache
How to Restart a Management Server
How to Configure Grooming Settings for the Operations Manager Database
Recommendations for Daily, Weekly, and Monthly Operations Manager Tasks
476
3. In the Settings pane, right-click Database Grooming, and then click Properties.
4. In the Global Management Group Settings - Database Grooming dialog box, select a
record type, and then click Edit.
5. In the dialog box for the record type, specify Older than days, and then click OK.
6. In the Global Management Group Settings - Database Grooming dialog box, select
another record type to Edit or click OK.
See Also
Maintenance of Operations Manager
Monitoring the Health of the Management Group
Inventory of Operations Manager Infrastructure
Scheduling Maintenance in Operations Manager
How and When to Clear the Cache
How to Restart a Management Server
How to Configure Grooming Settings for the Reporting Data Warehouse Database
Recommendations for Daily, Weekly, and Monthly Operations Manager Tasks
Daily Tasks
Task References
Weekly Tasks
Task References
477
Task References
Manager
Monthly Tasks
Task References
See Also
Maintenance of Operations Manager
Monitoring the Health of the Management Group
478
Inventory of Operations Manager Infrastructure
Scheduling Maintenance in Operations Manager
How and When to Clear the Cache
How to Restart a Management Server
How to Configure Grooming Settings for the Operations Manager Database
How to Configure Grooming Settings for the Reporting Data Warehouse Database
479