Back from vacation & survived hurricane Irene

The family and I went out of town for the week of vacation one last time before everything goes back to a normal routine. We went to Pigeon Forge, Tennessee, stayed in a log cabin and did a lot of sight seeing. We really had a great time there.

But now I have a lot to catch up on now.

SCOM Zombie PSA#21: SCOM Agent Health “Not Monitored”

 

A while back a zombie pushed a large number of agents out to be installed. Without waiting until the job completed on the first management group, the zombie pushed the agents out to the same systems from another management group.

The end result was some of the systems showed up in one of the management groups as “Healthy”  while the other system either failed to install the agent or it showed up as “Not Monitored”.

Here is what Worked for me:

• Stop and disable the Agent Service (System Center Management). This also worked for some of the agents that I couldn’t successfully deploy a second agent on.
• From the management group with the “Not Monitored” agent I deleted the agent from my Agent Managed or from the Pending Management.
• if you delete the agent before the agent service is stopped/disabled it may reshow back up in the Pending Management. Even if you approve the agent, it will show back up as Not Monitored in the Agent Management.
• Next I rediscovered & redeployed the agent to the system (I did not uninstall the agent).
• My agent successfully installed and now it is properly reporting to multiple management groups with healthy status.

This worked for SCOM 2007 R2 and I bet SCOM 2012 it would resolve the same issue.

SCOM Zombie PSA#20: Web Console: HTTP Error 404.2 – Not Found

 

I’ve encountered this issue this afternoon, after re-building my OpsMgr2012. From my computer I received this “404 – File or Directory not found”. 

I tried to verify this from my server, which I showed a different error, just more details. Nothing populated into my event logs on either system.

What I really liked about getting this error was that It showed me how helpful the application is. The error populated a lot of information about causes, path that failed and some resolutions etc.It allow me to link Microsoft support site directly through the web console, where I was able to gather the resolution for the 404.2 error.

Nothing difficult, just something I thought was neat.

Made the changes, verified my work, tested and Bingo! working on both of my systems. I also verified the reporting as well just in case I broke something else.

SCOM Zombie PSA#19: OM12 VM Reverted back

 

Well, I did get my OM2012 operational and running with a couple of problems along the way. Resolved the issues and decided to revert my image to a staged starting point and go through the process again. Will I run into a problem this time? How well do I understand the process Microsoft provided from their documentation? What can I resolve if I come across that path?

Once I have this running, I will move on to other stuff with OM12 or OM02.

SCOM Zombie PSA#18: Monitored Item Capacity

 

Here is the recommended limits for OpsMgr 2012 from the Supported Configurations guide:

Monitored Item	Recommended Limit
Simultaneous Operations consoles	50
Agent monitored computers reporting to a management server	3,000
Agent monitored computers reporting to a gateway server	2,000
Agentless Exception Monitored computers per dedicated management server	25,000
Agentless Exception Monitored computers per management group	100,000
Collective client monitored computers per management server	2,500
Management servers per agent for multihoming	4
Agentless managed computers per management server	10
Agentless managed computers per management group	60
Agent-managed and UNIX or Linux computers per management group	6,000 (with 50 open consoles); 10,000 (with 25 open consoles
UNIX or Linux computers per dedicated management server	500
UNIX or Linux computers monitored per dedicated gateway server	100
URLs monitored per dedicated management server	3000
URLs monitored per dedicated management group	12,000
URLs monitored per agent	50

SCOM Zombie PSA#17: Operations Console Requirements

 

Straight from the Operations Manager 2012 Supported Configurations guide:

• Microsoft Report Viewer 2008 SP1 Redistributable Package
• Hotfix 976898
• Recommended processor speed: 2.8 GHz or faster.
• Minimum memory: not less than 2 GB.
• Drive space: %SYSTEMDRIVE% must have at least 512 MB free space
• File system: %SYSTEMDRIVE% must be formatted with the NTFS file system
• Server Operating System: must be Windows Vista, Windows 7, Windows Server 2008 or Windows Server 2008 R2
• Processor Architecture: must be AMD64 for servers and AMD64 or i386 for a client computer
• Windows Installer version: not less than version 3.1
• Windows PowerShell version: Windows PowerShell version 2.0
• Both .NET Framework 3.5 SP1 and .NET Framework 4 are required. For more information, see the following.
• .NET Framework 3.5 SP1 redistributable package
• .NET Framework 4 redistributable package

SCOM Zombie PSA#16: Server Error in '/' Application

 

As I monitored my OpsMgr console, I notice my Operations Web Console suddenly became unavailable. So I fired up the web console and received this error along with some details.

Details:

Could not load type 'System.ServiceModel.Activation.HttpModule' from assembly 'System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'

Resolution:

I came across Bruno Wouters post helping other with the exact same issue. The only difference was that I was running this in OpsMgr 2012.

use the ASP.NET IIS Registration Tool or ASP.NET Side-by-Side Overview and execute the “aspnet_regiis.exe –iru” utilizing the command prompt as an administrator and navagete to the systemroot\Microsoft.NET\Framework\versionNumber

After I completed that, my web console was back to normal.