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.


And

Source:        Service Control Manager
Event ID:      7009
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Description:
A timeout was reached (30000 milliseconds) while waiting for the System Center Data Access service to connect.
A timeout was reached (30000 milliseconds) while waiting for the System Center Management Configuration service to connect.

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.

Problem
==========
SCOM Reporting Installation Hangs on SQL 2008 R2  

症狀
======
停在這一個畫面 ,無法”按下一步”

Solution
=========
Follow the steps mention in the KB http://support.microsoft.com/kb/2425714

How to install System Center Operations Manager 2007 R2 Reporting

Note You must follow these steps on the SQL Server Reporting Services server.

1. Open Computer Management.

2. In the Computer Management MMC snap-in, expand System Tools, expand Local Users and Groups, and then click Groups.

3. Locate the following group:
SQLServerReportServerUser$<hostname>$MSRS10_50.<SQLInstanceName>

4. Rename the group to the following by removing "_50" from the group name:
SQLServerReportServerUser$<hostname>$MSRS10.<SQLInstanceName>

5. Install System Center Operations Manager 2007 R2 Reporting.
For more information, see the following Microsoft TechNet Website:

http://technet.microsoft.com/en-us/library/bb432143.aspx (http://technet.microsoft.com/en-us/library/bb432143.aspx)

Important When you install System Center Operations Manager 2007 R2 Reporting, you should not install the Data Warehouse component.

6. After you install System Center Operations Manager 2007 R2 Reporting, rename SQLServerReportServerUser$<hostname>$MSSRS10.<SQLInstanceName> back to original name SQLServerReportServerUser$<hostname>$MSSRS10_50.<SQLInstanceName>

問題描述：如果您是使用Smart Card登入Windows 7，由於安全性的原因，您希望能做到移除Smart Card後，馬上鎖定電腦或是登出，請參考以下的做法。

1. 在群組原則裏，找到「電腦設定」>「Windows 設定」>「安全性設定」>「本機原則」>「安全性選項」>「互動式登入:智慧卡移除操作」的設定改成「鎖定工作站」或是「強制登出」。

2.在「服務」裏，將「Smart card Removal Policy」設定成「自動」，並且確認可以啟動。

3.確認Policy 生效即可

Symptom
========
RMS becomes unavailable every minute and then the Critical Alert.

Alert description:
=============
The root management server (Healthservice) has stopped heartbeating soon after 2011/12/31 上午 06:30:59. This adversely affects all availability calculation for the entire management group.

Cause
=======
SDK Service on RMS is missing the Missed Heartbeat threshold for Root health service by 1 heartbeat.

Solution
==========
1. Run Registry Editor.

2. Locate HKEY_LOCAL_MACHINE -> SOFTWARE -> MICROSOFT -> MICROSOFT OPERATIONS MANANGER -> 3.0 -> SDK SERVICE

3. Right click - New Key

4. Enter "RHS Watcher"

5. Right click "RHS Watcher" -> New -> DWORD

6. Enter "MinutesToWaitBeforeAlerting"

7. Double-click on "MinutesToWaitBeforeAlerting" and enter value of 5

8. Close regedit and open Services.msc

9. Restart System Center Management service, the System Center Management Configuration service, and System Center Data Access service.

Problem
=======
MonitoringHost.exe using large amount of memory

Solution
=======
Apply hotfix 968967

其他參考資料：
============
The CPU usage of an application or a service that uses MSXML 6.0 to handle XML requests reaches 100% in Windows Server 2008, Windows Vista, Windows XP Service Pack 3, or other systems that have MSXML 6.0 installed
http://support.microsoft.com/kb/968967/en-us