Managed Computer Scan
|Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.|
The Agent Manager scans Active Directory based on the MCRs. If Active Directory is not available, MOM scans the Windows NT 4.0 domain controllers. By default, this scan runs daily at 2:05 A.M. You can also configure the scan to run at a different time or to be initiated manually.
Listing computers in the ManualMC.txt file overrides any exceptions that are configured in the MCR. For more information, see Chapter 8, "MOM Agent Management."
The computers whose attributes match any of the MCRs are placed into the Pending Installation folder by default. This feature allows administrators to keep MOM from installing agents immediately following a scan. This setting, the Managed Computer Scan time, and Agent Service Account parameters can be changed.
Scanning a Single Managed Computer
If you change the configuration of an agent computer, or if you install a new computer onto the network, you can prompt the Agent Manager to scan only that computer instead of all managed computers. Scanning only the affected computer takes less time than scanning all managed computers. Changes occur when the service is restarted, or during the next scheduled scan.
You can run the tasks from either the Consolidator and associated Agent Manager computer, or from a remote MOM Administrator console computer. If you run the tasks from a remote MOM Administrator console computer, download and install the command shell-based Windows Script Host, version 5.1 (CSCRIPT.EXE) from the Microsoft Web site at http://www.microsoft.com. You do not need version 5.1 if you run the tasks from the Agent Manager computer.
You can also scan and install an agent on a new computer. For more information, see Chapter 8, "MOM Agent Management."
To create a task for scanning a single agent computer in the Managed Computers list
Start the MOM Administrator console from the Microsoft Operations Manager program folder.
Expand Microsoft Operations Manager (default) in the left pane, and then click Monitor.
Click Action on the menu bar, and then point to New.
Click Custom Task, and select the appropriate user name from the Task Available To list.
Select computer items from the Task Available For list, and then click Add.
In the Name box, type
Agent Manager scan this computer.
In the Description box, type
Causes the Agent Manager to scan an agent computer.
In the Command box, type:
CSCRIPT.EXE "$Agent Directory$\AMScanSingle.vbs" /a:AGENTMANAGER_COMPUTER_NAME /s:$Computer$
Where /a:AGENTMANAGER_COMPUTER_NAME specifies the name of the Agent Manager computer.
CSCRIPT.EXE "$Agent Directory$\AMScanSingle.vbs" /a:NYC_AM023 /s:$Computer$
To run the custom task to scan an agent computer in the Managed Computers list:
Start the MOM Administrator console.
Expand Microsoft Operations Manager (default) in the left pane.
Click Monitor in the left pane, and then click All Computers.
In the right pane, click the computer you want to scan.
Click Action on the menu bar, and then click Custom Tasks.
Click Agent Manager scan this computer.
The agent heartbeat defines how frequently agents scan for processing rule updates and report their availability to the Consolidator. By default, the heartbeat frequency is set to every 300 seconds (five minutes). However, this value can be changed under Configuration\Global Settings\Agents.
The Consolidator uses the agent heartbeat to determine whether or not agents are active and if active agents can communicate with the Consolidator. If the Consolidator fails to receive a heartbeat from a particular agent, the Consolidator assumes there is a problem with the network, the agent, or the managed computer itself. If the heartbeat fails, event 2040 will appear in the MOM Administrator console. This event is generated by the Agent Heartbeat Failed script. By default, the Consolidator runs a script every five minutes to watch for this event to determine the cause of the problem.
It is not recommended to rely on the agent heartbeat to monitor server availability. While the agent is configured to send a heartbeat to the Consolidator every 300 seconds, the Consolidator does not interpret an agent connectivity issue until 1800 seconds (30 minutes) after losing contact with the agent.
For more information about configuring heartbeat settings, see Chapter 8, "MOM Agent Management."