SCOM 2007,Console cannot connect with error 1053

Symptom
============
When we start the SDK Service, it does not start and the following event is logged:
Could not start the System Center Data Access service on local computer. Error 1053: The service did not respond to the start or control request in a timely fashion.   

Cause
=========
SDK Service times out before starting

Solution
=========

To work around this problem, modify the registry to increase the default time-out value for the service control manager.

To increase this value to 60 seconds, follow these steps:

1.    Click Start, click Run, type regedit, and then click OK.

2.    Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

3.    In the right pane, locate the ServicesPipeTimeout entry.

Note If the ServicesPipeTimeout entry does not exist, you must create it. To do this, follow these steps:
   a.    On the Edit menu, point to New, and then click DWORD Value.
   b.    Type ServicesPipeTimeout, and then press ENTER.
4.    Right-click ServicesPipeTimeout, and then click Modify.

5.    Click Decimal, type 60000, and then click OK.

This value represents the time in milliseconds before a service times out.
6.    Restart the computer.
Note This workaround may resolve the problem where the service does not start. However, we recommend that you research this problem to determine whether it is a symptom of another problem.

 

SCOM 2007,How to Completely Uninstall SCOM Agent

1. Please download the Cleanmom utility from the Microsoft Download Center.
    http://www.microsoft.com/en-us/download/details.aspx?id=16775
2.unzip OpsMgrCleanup.zip
3. Based on the architecture of the machine you will have to use either CleanMom.exe or CleanMom64.exe respectively.
The command should look like this:

CleanMom.exe /CleanAgents

SCOM APM CSM如何收集數據？

CSM如何收集數據？

CSM是通過向你的應用程序的適當網頁中註入一個JavaScript來工作的（注意這種注入應用到.Net代碼中，靜態文件不會被注入）。由於瀏覽器端用戶和你的應用程序是相互作用的，這些適當的性能指標和異常指標會被發送到CSM收集器中，然後發送到OpsMgr的DB和DW中，作為其它監控指標顯現在OpsMgr控制台上。

當你使用OpsMgr的.​​NET Application Performance Monitoring模板來監控你的應用程序時，這個JavaScript會自動注入你的應用程序。

注意CSM不可能單獨開啟，當你運行.NET Application Performance Monitoring模板時Server-Side monitoring（服務器端監控）也必須開啟。 

.NET Application Performance Monitoring Template

http://technet.microsoft.com/en-us/library/hh457578.aspx

The Client-Side Monitoring feature uses the Response.Filter property to monitor pages. If the application web page contains the ASP.NET substitution control, changing the Response.Filter property is prohibited.

The recommended solution for this issue is to exclude the identified pages from monitoring. See section “excluding pages from monitoring” in this post.

Webpage contains calls to the HttpWebResponse.Flush() method

Client-Side Monitoring uses the Response.Filter property for monitoring purposes. If your application code calls Response.Flush(), this could lead to incorrect responses returned to the browser. This is a warning of a possible compatibility issue, and the recommended solution is to change your application code.

Note that the application may still work even if you do not update your code. See section “What if I have incompatibilities that I cannot change or do not want to change in my application?”

Webpage contains calls to the HttpWebResponse.End() method

Client-Side Monitoring uses the Response.Filter property for monitoring purposes. If your application code calls Response.Flush(), this could lead to incorrect responses returned to the browser. This is a warning of a possible compatibility issue, and the recommended solution is to change your application code.

Note that the application may still work even if you do not update your code. See section “What if I have incompatibilities that I cannot change or do not want to change in my application?”

Client scripting code overrides standard objects or functions

If standard objects or functions are overridden, this may cause incompatibilities with Client-Side Monitoring. This is a warning of a possible compatibility issue.

There are 2 recommended solutions for this issue

1. Exclude the identified pages from monitoring. See section “excluding pages from monitoring” in this post.
2. Manually check application compatibility for the identified pages by following the steps in section “What if I have incompatibilities that I cannot change or do not want to change in my application?”

SCOM APM query

SELECT * FROM [OperationsManager].[apm].[V_APPLICATIONSOURCEMACHINE]

where MACHINENAME like '%Jimmy-Agent%'

SELECT * FROM [OperationsManager].[apm].[V_EVENT]

where MACHINENAME like '%Jimmy-Agent%'

SELECT * FROM [OperationsManager].[apm].[V_EXCEPTIONEVENT]

where MACHINENAME like '%Jimmy-Agent%'

SELECT * FROM [OperationsManager].[apm].[V_PCCONFIG]

where MACHINE like '%Jimmy-Agent%'

SELECT * FROM [OperationsManager].[apm].[V_PM_EVENT]

where MACHINENAME like '%Jimmy-Agent%'

SELECT * FROM [OperationsManager].[apm].[VEVENTSYNC]

where MACHINENAME like '%Jimmy-Agent%'

SELECT *  FROM [OperationsManager].[apm].[VPERFHOURLYSYNC]

where MACHINENAME like '%Jimmy-Agent%'

SELECT * FROM [OperationsManagerDW].[apm].[V_APPLICATIONSOURCEMACHINE]

where MACHINENAME like '%Jimmy-Agent%'

SELECT *  FROM [OperationsManagerDW].[apm].[V_PM_EVENT]

where MACHINENAME like '%Jimmy-Agent%'

SELECT * FROM [OperationsManagerDW].[apm].[V_EVENTWINDOW]

where MACHINE like '%Jimmy-Agent%'