SCOM 2007 Administration

The Author role in SCOM 2007 has permissions to create, edit, and delete tasks, rules, monitors, and views within a configured scope (such as a specific group). Read-Only and Report Operators cannot modify configurations.

Maintenance Mode in SCOM 2007 suppresses all alerts and monitoring for a computer during planned maintenance, downtime, or troubleshooting. This prevents false alerts during known service interruptions.

Audit Collection Services (ACS) in SCOM 2007 is specifically designed to collect security event log data from monitored computers and store it centrally for security auditing and analysis.

In SCOM 2007, tasks are predefined executable actions that administrators can launch to resolve alerts or perform diagnostic operations. Rules generate alerts, monitors track health state, and views display data.

The Ops action account in SCOM 2007 is used to perform agent deployment and run operations on agent-managed computers. This account requires appropriate permissions to install and configure agents.

Run As accounts in SCOM 2007 allow rules, tasks, monitors, and discoveries to run under different security contexts on different computers. This provides flexibility for workflows requiring specific credentials.

Rules in SCOM 2007 management packs are primarily used for data collection workflows, including event log collection, performance data gathering, and other information-gathering operations. Monitors track health state.

Sealed management packs in SCOM 2007 use the .MP file extension as they are compiled and digitally signed. Unsealed management packs exist as editable XML files before being sealed into the .MP format.

SQL Reporting Services (SSRS) is required for generating reports, IIS is needed for the web interface of Reporting Services, and the Management Server is a core SCOM component. All three are prerequisite components for enabling SCOM reporting functionality.

Windows PowerShell enables SCOM commandlets and automation, .NET Framework 3.0 is required for SCOM's core runtime, WS-MAN (WinRM) v1.1 enables remote management and agent communication, and SQL Server 2005 SP1+ is the database backend. All are mandatory prerequisites.

SCOM can monitor TCP ports through network device monitoring and TCP port checks. The question wording is ungrammatical ('monitors' instead of 'monitor'), but the intent is testing whether port monitoring is supported.

The Most Common Alerts report shows frequently occurring alerts to help reduce noise by tuning or suppressing them. The Agent Performance Report identifies agents consuming excessive resources, allowing optimization of the monitoring infrastructure.

SCVMM (System Center Virtual Machine Manager) 2008 integrates with SCOM 2007 through 'ProTips' (Provisioning Tips), enabling SCOM to monitor virtual machine provisioning and management activities from SCVMM. The other options are different System Center components that integrate differently.

A Monitor Override allows customization of default monitor behavior for specific targets, groups, or objects without modifying the underlying management pack. This enables tuning thresholds, disabling monitors for certain systems, or changing configuration without affecting the global definition.

The Operations Console should NOT be installed on the RMS (Root Management Server) as a best practice because it consumes resources that should be dedicated to core SCOM management functions. The console belongs on Gateway Servers, standalone servers, or ACS (Audit Collection Services) servers.

NOC (Network Operations Center) team members typically need Read-only access to view alerts and monitor infrastructure without making changes. This provides visibility while preventing unintended modifications to monitoring configuration or settings.

The MP (Management Pack) Converter is the specific tool used to convert MOM 2005 management packs to SCOM 2007 format. MP Viewer is for reading pack contents, HS Lockdown Tool is for security, and Ops Console is the management interface - none of these perform conversion.

MDOP (Microsoft Desktop Optimization Pack) includes App-V (Application Virtualization) error monitoring capabilities through AEM (Agentless Exception Monitoring). This provides immediate desktop error monitoring across locations at lower cost than full SCOM deployment. SCOM, MOM, and AEM alone don't meet the cost constraint.