SCOM 2012: Enable agent proxy on all agents

I kept on getting this alert on the SCOM 2012 console:
"Agent proxy not enabled"

Below is the resolution for enabling the agent proxy for all agents and setting the default value to enable agent proxy for all newly installed agents.

Turn on agent proxy for all agents where it is disabled:
get-SCOMagent | where {$_.ProxyingEnabled -match "False"} | Enable-SCOMAgentProxy

Turn on agent proxy as a default setting for all new agents to be deployed, never to have to mess with this again:
add-pssnapin "Microsoft.EnterpriseManagement.OperationsManager.Client";
new-managementGroupConnection -ConnectionString:scomserver.domain.com;
set-location "OperationsManagerMonitoring::";
Set-DefaultSetting -Name HealthService\ProxyingEnabled -Value True

Thanks to Kevin Holman for his post on this.

Hope that this post was helpful.

Windows Server 2012, SQL Server and System Center 2012

When designing a good System Center 2012 environments it’s obvious that SQL Server is key to the overall success of your design, implementation and functionality of it all.
When a bad decision is made or a good design decision is poorly executed, it has a direct negative impact on the overall experience and functionality of your System Center 2012 environment.

Microsoft System Center - Free eBooks

Microsoft Press has been releasing Microsoft System Center free ebooks this year in waves. All of these eBooks are being hosted from the Microsoft Virtual Academy website.

Download in all formats (PDF, Mobi and ePub).

Introducing Microsoft System Center 2012 R2

• Download the PDF file
• Download the EPUB file
• Download the Mobi for Kindle file

To Do List: Adding Additional SCOM Management Server To An Existing Management Group

When a SCOM Management Group (MG) is already in place for some time and an additional SCOM Management Server is added to it later on, their are quite a few steps one must do in order to get it working properly. When forgetting one of those steps it might result in a SCOM MG showing erratic behaviour.

Mind you, all these steps take place AFTER the new SCOM Management Server is installed. Also good to know, this To Do List is based on System Center Operations Manager 2012 SP1.

01. Antivirus exclusions
Please make sure the new SCOM Management Server uses the same AV policy as the other SCOM Management Server. So the correct folders and processes are excluded from AV scans. Check KB975931 for more information.

SCOM Reports Not Updated & Not Working

Issue
Bumped into an issue where the latest MPs contained Reports which weren’t uploaded at all to SCOM Reporting. Took me a while to crack it but finally I found KB2771934 which was the starting point of the solution to this issue.

Causes & Fixes
As it turned out there were multiple causes which joint forces in order to frustrate the SCOM Reporting process in many kind of ways.

1. The object Data Warehouse Synchronization Server was a goner. KB2771934 helped me in fixing that.
2. The SCOM Data Warehouse Read account was lacking proper permissions. TechNet has some good articles about it, like Account Information for Operations Manager and the Online Deployment Guide. Based on that information I set the permissions as required.
3. There were also multiple time outs where the Management Servers couldn’t write their information to the Data Warehouse database or read from it (important for SCOM in order to know what Reports to upload to the SSRS instance). After some tweaking and tuning the SQL server got a bit more space to operate which reduced these errors enormously.

Afterwards the Reports were updated again: the old outdated Reports removed since their related MPs weren’t present anymore and the newest Reports, based on the MPs which were imported lately, showed up in SCOM Reporting.

Hope that this post was helpful.