System Center Operations Manager monitors computers and devices that it has discovered, and it also discovers applications and features that it discovers on monitored computers. There may be situations where you want to limit discovery. For example, you might want only some instances of SQL Server to be discovered and monitored, or you want to remove a computer that has already been discovered. The precise steps to limit or restrict discovery depend on the object, application, or feature that you want to exclude from discovery.
However, the general procedure is the same: identify the discovery that you want to limit and create an override to disable the discovery. All objects in the class that the discovery applies to. If you use this selection for your override, you disable the discovery completely.
A group. Group membership can be defined explicitly or dynamically. 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 more information, see Creating and Managing Groups. One or more specific objects in the class that the discovery applies to.
Using this method, you can select from discovered objects.MicroNuggets: Active Directory Discovery Explained
All objects of another class. Using this method, you specify a class of objects to apply the override to. Choosing how to apply the override to disable the discovery depends on your situation. The simplest situation is when you want to disable discovery for a specific object or for all objects in a class.
When you want to disable the discovery for any object that meets certain criteria, you must use a group that contains those objects or create a group that will identify those objects.
For example, you want to disable discovery of logical disks on management servers. You can configure an override to disable the discovery of Windows Server logical disks and apply it to the Operations Manager Management Servers group which is created automatically when you install Operations Manager.
If, instead, you want to disable discovery of logical disks on computers in a specific organizational unit, there is no built-in group that satisfies that definition and so you would need to create a group that identifies those computers.
After an object has been already discovered, if you want to delete the object and not let it be discovered again, disable the discovery for that object and then run the Remove-SCOMDisabledClassInstance cmdlet in Operations Manager Shell. To learn how to create a custom writeable management pack to store your overrides, see How to Create a Management Pack for Overrides. Before making changes to the monitoring settings defined in an Operations Manager management pack, review How to Override a Rule or Monitor to understand how to configure the change.
To understand the differences between classes and groups in Operations Manage and how workflows apply to each, review Using Classes and Groups for Overrides in Operations Manager. Skip to main content. Exit focus mode. The override to disable the discovery can apply to: All objects in the class that the discovery applies to.
Next steps To learn how to create a custom writeable management pack to store your overrides, see How to Create a Management Pack for Overrides. Related Articles Is this page helpful? Yes No. Any additional feedback?Here is another article ported from my old blog dating back to I recently revised a few key points.
Deploying SCOM Agents using the Discovery Wizard appears to have at least four distinct phases: setup, discovery, installation, and initialization. Each of these stages has unique requirements and troubleshooting.
Install Agent on Windows Using the Discovery Wizard
It is very useful to think of the discovery process in terms of separate stages to aid in troubleshooting. This is where you select a management server, setup AD integration or specify specific server names, specify execution credentials, and specify the install directory.
Note: The discovery process needs to return one result from the AD lookup for each listed server. Using FQDN names helps avoid returning multiple results. Issues sometimes arise when two servers have similar names. This is where SCOM checks to make sure all of the necessary components are available to execute a remote installation.
This appears to include AD lookup, DNS verification, and testing of several communication ports, services, and other necessary components to the setup process. The target device clearly needs to be online and accessible. Security permissions on the device also play a part in successful discovery. The important thing to understand is that the discovery stage does not appear to be logged and does not return a specific error.
Note: I have seen several posts stating that certain services need to be running though this has rarely proven to be relevant. The Windows Update service is commonly mentioned. Windows Update is not required. What you want to watch out for is chronic issues on the server that will be glaringly obvious in the event logs for WMI issues or other core service failure. Once you get past the discovery stage things start to become more clear.
The main issue with discovery troubleshooting is a lack of logging. Once the installation begins, a MSI installation log is created on the management server selected to deploy the agent.
You may also see an Operations Manager event log on the target Windows device if the install was partially successful. Note: You need access to the remote device to troubleshoot installation failures; relying on information in the console is almost useless at this point. You may encounter situations where remote agent deployment fails on a server where you do not have logon access or remote log access.
This is the final stage where the agent completes the post-installation initialization process. Failing the initialization process will leave the successfully installed agent in a disconnected state. You will see this as a successful install that remains in Pending Actions or that stays in a grey state indefinitely.
The key here is check the Operations Manager event log to track the initialization process starting with Event ID: You may find it helpful to refer to the logs on a successful install for comparison.
The basic initialization process includes identifying the RSM and Management Group, connecting to the MG, verifying that the MG action account, an authorization key exchange, confirmation, and finally MP download.
An alternative to TCP is to use a digital certificate. The initialization process checks for this digital certificate before the TCP authentication steps.To have a customized monitoring solution, one must understand the authoring capabilities in SCOM, so that the solution can be easily implemented, highly optimized and has less overhead on SCOM Management servers and agents. Basics — Classes, Objects, Targets and Discoveries:. An object is the basic unit of management in Operations Manager.
An object typically represents something in your computing environment, such as a computer, a logical disk, or a database. A class represents a kind of object, and every object in Operations Manager is considered an instance of a particular class. A target in the Operations console represents all instances of a particular class.
A discovery is a special kind of rule to populate the class with instances. We as SCOM Administrators are requested to configure monitoring for various TCP ports from different watcher nodes across various servers in datacenter. But the drawbacks of using this template are:. Each entry creates bunch of classes, groups, overrides and number of workflows increase which will impact SCOM performance.
If a watcher node is decommissioned, each port monitored by the watcher node need to be moved to other watcher node manually. In real environment, this includes Change requests, approvals etc which can consume considerable time. To overcome the issues, it would be better to have a configuration in a central location and pull the information to SCOM at regular intervals.
This way, once the initial configuration is setup. Thus with handful of monitors and rules s of objects can be monitored. The monitoring solution is self supported and cost effective in terms of support hours.
Below is step by step process with xml fragments included. Step 4: Now we need to create discovery data source. Before that we will discuss the CSV file format we will be using to store the configuration data.
NoOfRetries — Number of times the monitor should fail before the alert is generated. This will reduce the alerts generated due to network latency. Minimum value — 2.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 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 agentsyou 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 deploy the Operations Manager agent to the discovered computers from the Operations console.
For a list of the supported operating system versions, see Microsoft Monitoring Agent Operating System requirements. For information about port requirements for agents, see Agent and Agentless Monitoring in the Deployment Guide. Log on to the Operations console with an account that is a member of the Operations Manager Administrators role.
Select either Automatic computer discovery or Advanced discovery. If you select Automatic computer discoveryclick Nextand then go to step 7. If you select Advanced discoverycontinue with the following steps.
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. In the Management Server list, click the management server or gateway server to discover the computers. If you selected Servers and Clientsyou 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. 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. The wizard can return approximately computers if Verify discovered computers can be contacted is selected, and it can return 10, 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. 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 it is not already selected, select Scan Active Directory and then click Configure. In the Find Computers dialog box, type the criteria that you want to use for discovering computers, and then click OK. 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:.
SCOM Agent Deployment Troubleshooting
Select Browse for, or type-in computer namesclick Browsespecify 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.
Click Nextand on the Administrator Account page, do one of the following:. Select Other user accounttype the User name and Passwordand 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.System Center Operations Manager SCOMa component of Microsoft System Center is a software that helps you monitor services, devices, and operations for computers within your infrastructure.
This article provides an overview of object discoveries in SCOM and how to manually trigger them. SCOM uses a agent installed on a computer to collect data, compare sampled data to predefined values, create alerts, and run responses.
Manually Trigger Object Discoveries in SCOM
The agent then sends monitoring data to the management server in the SCOM management group. Management servers run various services, including the System Center Management configuration service which among other roles, distributes management packs to monitored objects. Management packs define the information that agents collect and return to the management server s for a specific technology or application.
Management packs are comprised of various configurations for discovering, and monitoring various technologies. The configurations include object discoveries, rules, monitors.
Object discoveries are a crucial part of the initial configuration that SCOM sends to agents. Object discoveries define the types of objects such as applications and features that SCOM will monitor on agent-managed computers, and once a given technology or application type is discovered on a computer, the relevant monitoring rules and monitors for that technology or workload then execute on the computer on a pre-defined interval.
In this post, we will make use of a discovery for SQL Instances. The discovery name in question is Discover Databases for a Database Engine. To review the properties for this object discovery you can make use of the Get-SCOMDiscovery cmdlet, or review the some limited configuration information for the discovery in the SCOM console.
To view the discovery properties in the SCOM console:. In the general tab of the properties for the object discovery, you can review the object discovery target.
You can get both of these IDs using the relevant PowerShell cmdlets. This returns all of the potential target instances for the class. You can then get Id information for the target instance of interest using the following:. To do so:. And all things being equal, you should see the desired output indicating that the task completed successfully.
I hope you find this instructive. And in the configuration tab, you can review configuration information for the object discovery. The following two tabs change content below. Bio Latest Posts. Chiyo Odika. Latest posts by Chiyo Odika see all.
Sorry, your blog cannot share posts by email.Welcome to System Center - Operations Manager. Operations Manager provides infrastructure monitoring that is flexible and cost-effective, helps ensure the predictable performance and availability of vital applications, and offers comprehensive monitoring for your datacenter and cloud, both private and public. Planning for System Center - Operations Manager. Deploying System Center - Operations Manager. Read these topics once you have Operations Manager up and running and are looking to start monitoring your environment, as well as procedures for day to day operations.
The Management Pack Authoring Guide for Operations Manager provides information on creating custom monitoring for your service or application. Skip to main content.
Exit focus mode. Planning for System Center - Operations Manager Review information to help you plan the deployment of Operations Manager into your organization Deploying System Center - Operations Manager Read these topics to learn how to deploy Operations Manager in your environment.
System Center - Operations Manager Operations Guide Read these topics once you have Operations Manager up and running and are looking to start monitoring your environment, as well as procedures for day to day operations. Related Articles Is this page helpful? Yes No. Any additional feedback? Skip Submit. Is this page helpful?Large Table query. I am putting this at the top, because I use it so much — to find out what is taking up so much space in the OpsDB or DW.
Database Size and used space. Operational Database Queries:. Number of console Alerts per Day:. Number of console Alerts per Day by Resolution State:. Computers generating the most events:. Performance insertions per day:. To view all performance data collected for a given computer:. To pull all perf data for a given computer, object, counter, and instance:. To find out how old your StateChange data is:. State changes per day:. Noisiest monitors changing state in the database in the last 7 days:.
Monitors with the most instances of critical state what workflows are causing the most unhealth-iness :. List of all monitors in a critical state:. Rules section:. Monitors Section:.
Groups Section:. Management Pack and Instance Space misc queries:. My Workspace Views:. Alerts Section Warehouse :. Events Section Warehouse :. Performance Section Warehouse :. Get members of a group. Get data about a specific object or a specific group. Grooming in the DataWarehouse:. Aggregations and Config churn queries for the Warehouse:. Analyzing Dataset data in the DW:.