System Center Guide

We briefly encountered the following problem today:

 

Discovery data couldn’t be inserted to the database. This could have happened because  of one of the following reasons: 

                - Discovery data is stale. The discovery data is generated by an MP recently deleted.                - Database connectivity problems or database running out of space.                - Discovery data received is not valid. 

 The following details should help to further diagnose: 

 DiscoveryId: 42f5646a-0574-3ee8-77dd-aadc86bc9902 HealthServiceId: 5f8a3709-8375-12c9-a16b-e40fe69a6477 Health service ( 5F8A3709-8375-12C9-A16B-E40FE69A6477 ) should not generate data about this managed object ( 9C305C53-83AC-A466-C8E4-0FD118606A3C ).. 

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

This was easily resolved by configuring the Exchange Server that is generating the alert to act as a Proxy Agent. You can do this by selecting the target agent in the Managed Agents section of the Administration node. Highlight the agent, select Properties and click the Security tab. Tick the checkbox to “Allow this agent to act as a proxy and discover managed objects on other computers“.

After tripping the OpsMgr Health Service on the Exchange Server everything started coming into the console very nicely.

Issue: If you install reporting and then install a secondary MS then it will not be able to write DW data as profiles are not created by setup.

Symptoms: You get alerts that say the 2^nd management server can’t write to the DW using the server action account – but we’re using the same server action account on both management servers. 

Fix: So to fix this manually you have to open the Console then Navigate to Administration View expand the security node. Select the Run As Profiles option, in the right hand view select the Data Warehouse Account and right click and choose Properties then select the Run As Account Tab. See if the Second Management server name is listed (most probably no) if not click New and specify the name of the second management, this should fix the issue. You should see Event ID: 31554 when this is successful. Note: This bug is fixed in Service Pack1 of OpsMgr 2007

Running the OpsMgr Agent on Light Processor Hardware

Summary: CPU utilization spikes to 100% on Agents with 1.3Ghz or lower processors.

Full article: http://cameronfuller.spaces.live.com/blog/cns!A231E4EB0417CB76!1015.trak

Confirmed: http://momcommunity.com/forums/p/3472/10851.aspx#10851

If you experience problems using the registration form to download the HP Proliant management packs, you can FTP the HP website at ftp.compaq.com and download the file hpProliantServerMPKits1_0.zip. While I normally wouldn’t post means of avoiding a vendor’s registration process, the CGI form that processes the registration for download has been broken for days.