Applies To: System Center 2016 - Operations Manager
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 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 Microsoft Monitoring Agent Operating System requirements.
For information about port requirements for agents, see Agent and Agentless Monitoring in the Deployment Guide.
To install an agent on a computer running Windows by using the Discovery Wizard
Log on to the Operations console with an account that is a member of the Operations Manager Administrators role.
At the bottom of the navigation pane, click Discovery Wizard.
In the Computer and Device Management Wizard, on the Discovery Type page, click Windows computers.
On the Auto or Advanced? page, do the following:
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.
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 Computer and Device Classes list, select Servers and Clients, Servers Only, or Clients Only.
In the Management Server list, click the management server or gateway server to discover the computers.
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.
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.
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.
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:
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:
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).
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.
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.
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.
Computers that are already managed by the management group will not be returned by the wizard.
On the Select Objects to Manage page, do the following:
Select the computers that you want to be agent-managed computers.
In the Management Mode list, click Agent and then click Next.
The discovery results show virtual nodes of clusters. Do not select any virtual nodes to be managed.
On the Summary page, do the following:
Leave the Agent installation directory set to the default of %ProgramFiles%\Microsoft Monitoring Agent or type an installation path.
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.
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.
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.
If the task fails for a computer, click the targeted computer. The reason for the failure is displayed in the Task Output text box.
If you would like to manually install the Windows agent from the command line or automate the deployment using a script or other automation solution, review Install Windows Agent Manually Using MOMAgent.msi.
After manually installing the Operations Manager agent on Windows or UNIX and Linux computers, you need to Process Manual Agent Installations.
To understand how to manage the configuration settings of a Windows agent and options available, review Configuring Windows Agents.
Review Uninstall Agent from Windows-based Computers to understand what options and steps need to be performed to properly uninstall the agent from your Windows computers.
If you would like to install the Nano Server agent from the command line or automate the deployment using a script or other automation solution, review Install Agent on Nano Server