System Center Monitoring Pack for System Center 2012 – App Controller: Complete Guide

Quick install steps — System Center 2012 App Controller Monitoring Pack

Prerequisites

• Operations Manager 2012 (with SP1 if your MP requires it) and administrative access to the SCOM console.
• Download the App Controller Management/Monitoring Pack (MP) and any dependent MPs (usually Windows Server, .NET, and generic SCOM libraries) from Microsoft or your vendor.
• A run-as account with rights to query App Controller and access to the App Controller web service (usually a service account).

Installation

1. Place MP files (typically .mp and .xml or .mpb) on the management server or a share accessible to the SCOM console.
2. Open the Operations Manager Console → Administration → Management Packs.
3. Click Import Management Packs → Add → Add from disk.
4. Select the App Controller MP file(s) and any dependencies; click Install.
5. Confirm import results in the console (no errors). If an MP bundle (.mpb) is provided, import the bundle.

Configure Run-As and Discovery

1. In Administration → Run As Configuration → Accounts, create a Run As account for the App Controller service account (Windows or Basic as required).
   7. Create a Run As Profile that maps the account to the App Controller MP’s profiles; distribute to management servers.
   8. In Authoring → Management Pack Objects (or under the MP’s documentation), locate the discovery rules for App Controller and enable them if not automatic.

   Configure Monitoring Targets and Overrides

2. In Authoring → Management Pack Objects → Monitors / Rules, verify App Controller monitors/rules are enabled and targeted correctly (e.g., the App Controller Web Service or App Controller server class).
   10. If needed, create overrides (Authoring → Overrides) for thresholds, discovery intervals, or to disable noisy rules — save overrides into a custom MP.

   Validate

3. Wait for discovery to run (or force discovery via PowerShell: Get-SCOMClassInstance / Start-SCOMDiscovery if available) and confirm App Controller objects appear in Monitoring → State Views.
   12. Verify alerts are generated or health state changes are visible; check Operations Manager event/logs for errors (Management Server and HealthService logs).

   Post-install tasks

   • Import any dashboards, reports, or views that ship with the MP.
   • Schedule/verify maintenance windows for expected changes.
   • Keep the MP updated with vendor/Microsoft rollups (import newer versions when released).

   Common troubleshooting

   • Missing dependencies: import listed dependent MPs first.
   • Discovery fails: check run-as account permissions and network connectivity to App Controller’s web endpoint.
   • MP import errors: ensure you import into the correct SCOM management group and that the console user has MP import rights.

   If you want, I can produce exact PowerShell commands and a sample Run As account mapping/config stored in a custom MP — tell me to proceed.