SCOM 2007 Administration and Monitoring

SCOM monitors non-Windows devices (like Unix/Linux) through SSH on port 22. The agentless monitoring uses SSH to communicate with the target system. The other options are incorrect protocols/ports for this purpose.

SCVMM (System Center Virtual Machine Manager) 2008 is used for bulk agent deployment across large server environments. It integrates with SCOM for orchestrated agent pushes, which is more efficient than manual deployment through SCOM console or using SCCM (software distribution) or SCDPM (backup).

The Management Server communicates with SCOM agents primarily for health heartbeat and data collection. Typical agent communication is lightweight, involving small heartbeat signals and performance data at regular intervals. 500 bytes per second is the standard documented average bandwidth utilization for normal SCOM agent operations.

Synthetic Transactions are specifically designed in SCOM to monitor applications from multiple geographical locations by simulating user transactions. Unlike Unit Monitors which track individual health states, Synthetic Transactions actively test the full user experience path from different points, making them ideal for multi-location web application monitoring.

An agentless monitor in SCOM refers to a computer that does not have the SCOM agent installed but is still monitored remotely through a management server or proxy agent. This is different from agent-managed servers which have direct agent installation, and gateway servers which proxy agent communication.

The SDK (System Development Kit) Account in SCOM is the Windows account used by MonitoringHost.exe processes to collect data from managed providers and execute actions like scripts and batch files. This differs from Action Accounts which run responses, and Service Accounts which run the SCOM services themselves.

A Monitor in Operations Manager is a management pack element that contains the logic to determine and set the health state of a monitored object. Unlike Rules which collect data and generate alerts without health state changes, Monitors specifically evaluate state and can change health status to Healthy, Warning, or Critical.

Views in the Operations Manager Operations console are filtered data displays that pull specific information from the OperationsManagerDB database. Unlike Tasks which are executable actions or Rules which define data collection, Views simply organize and present filtered data for administrative analysis.

A SCOM Connector is a software component that enables bidirectional data synchronization between Operations Manager and external management systems. Unlike Providers which supply data within SCOM, Connectors integrate SCOM with other platforms like SCCM or third-party monitoring tools for centralized management.

A Management Pack in SCOM is a container that holds all the monitoring logic including rules, monitors, tasks, and views for a specific device, application, or service. Management Packages are the fundamental deployment units that extend SCOM's monitoring capabilities to new technologies and applications.

SCOM agents communicate with management servers on TCP port 5723, which is the default port configured for agent-to-server communication. This differs from port 5720 used for other SCOM communications, and standard ports like 80 or 1433 which are used for web and SQL traffic respectively.

Database Grooming in SCOM is the automated process that manages long-term data retention by removing old historical data from the Operational Database. This prevents database bloat while preserving configuration information, and is essential for maintaining SCOM performance over extended periods.

Agentless Monitoring in SCOM is typically used when the agent software is incompatible with the target operating system or when agents are not supported on certain platforms. It provides an alternative monitoring method through remote management rather than direct agent installation, though it is not primarily used to improve SCOM server performance.

In SCOM 2007, alert notifications require specific monitoring components to be configured first. Windows Service Monitoring and Synthetic Transactions are core prerequisites that must be set up before alert notifications can function properly. Unit monitors and dependency rollup monitors are monitoring types themselves, not prerequisites for alert notifications.

SCOM 2007 provides two primary approaches for monitoring services: Windows Service Monitoring and Synthetic Transactions. Windows Service Monitoring tracks the actual service state, while Synthetic Transactions simulate user actions to verify service functionality. Unit monitors and dependency rollup monitors are monitor types, not monitoring approaches.