[問題描述] Windows 7 預設的語言列無法顯示, 僅有在安全模式可以啟動.

[狀況分析]

·         我們手動打開工作排程器, 發現無法正常啟動此程式, 出現錯誤訊息為”災難性的失敗 (發生例外狀況於 HRESULT:0x8000FFFF)(E_UNEXPECTED))”.

·         Windows 7的語言列以及工作排程器中的工作 ”TextServicesFramework” 有緊密的結合, 若此工作無法正常執行的話,語言列的顯示會不正常.

[解決方法]

·         手動將工作排程器相關的機碼值從另一台機器整個匯出來,然後匯入到此台有問題的電腦重新開機.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule]

[參考連接]

在 Windows Vista 中排定的工作的描述 (適用於Windows 7)

http://support.microsoft.com/kb/939039/zh-tw

InitLocalMsCtfMonitor Function

http://msdn.microsoft.com/en-us/library/aa966199.aspx

The InitLocalMsCtfMonitor function initializes TextServicesFramework on the current desktop and prepares the floating language bar if necessary. This function must be called on the application's desktop.

Problem
===========
Workflows for Unix/Linux monitoring are not running 

Event ID 1202|

Solution
===========
We removed this account (Remove WS-Management Action Account) and all appears to be working

SYMPTOM
=========
Wrong day time displayed while the report selection time is over 2010/1/1. 

CAUSE
========================
We have a date Dimension view (SC_DateDimension_View) in the DW database which contains the day definition (such as 2009 12 31). This table is populated with a stored procedure named as "p_populatedateDimesion.sql".
However, we defined a time limit t0 '1/1/2010 12:00 AM' in the stored procedure which means the latest day definition in the date Dimension view will be 2010 1 1. So if the incoming performance data (same to alert, event data) will be linked with a wrong day dimension while DTS job transferring data to the DW DB.

Sample code in the stored procedure:
------------------------
     IF @startDate IS NULL
         SET @startDate = '1/1/1998 12:00 AM'

        IF @endDate IS NULL
         SET @endDate = '1/1/2010 12:00 AM'
------------------------

DECLARE @MaxDate DATETIME
SELECT @MaxDate = MAX([Date]) FROM dbo.SC_DateDimension_View
IF (@MaxDate IS NULL)
BEGIN
    EXECUTE p_PopulateDateDimension
END
ELSE IF (@MaxDate < '1/1/2010 12:00 AM')
BEGIN
    SET @MaxDate = DATEADD(day, 1, @MaxDate)
    EXECUTE p_PopulateDateDimension @startDate = @MaxDate
END
GO

WORKAROUND
========================
As a workaround, we can modify the p_populatedateDimesion stored procedure to adjust the end time to a long value (say: 2020 1 1). Then allow the report be generated with correct date value. I have attached modified stored procedure. We can use the below steps to fix the issue:

1. Backup the current SystemCenterReporting database.
2. Connect to the SystemCenterReporting database, run the content in the p_populatedateDimesion.sql.txt file.
3. Run the below query:
    Exec p_populatedateDimesion @startdate = '1/2/2010 12:00 AM'
4. Run the below query statement to ensure the max date time is 2020 1 1:
    Select * from SC_DateDimension_View order by date DESC
5. Run the content in the fixdate.sql.txt file. This will re-link the performance, alert, event date to the accurate one.
6. Re-run the MOM report to see if the returned date value is correct now.

PROBLEMS

==========

DISK H cannot be mounted to DISK F

REASON

=======

The system account was lost in disk H.

ANALYSIS

=========

-     From the result of chkntfs, we find the disk F is not dirty. The disk can be accessed normally.

-     From the result of process monitor, we find VDS.exe report the one device IO control failed on the H drive. But we did not find any information related to disk F.

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

      47   7:57:13.4497193 AM    vds.exe  384  IRP_MJ_DEVICE_CONTROL   H:   UNSUCCESSFUL     Control: 0x560010 (Device:0x56 Function:4 Method: 0)

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

-     We find disk F does not have the SYSTEM account. The disk information in disk management is all under SYSTEM account. If we did not have this account, we cannot receive any information about this disk. So even we can access this disk, we cannot see the value of "file system" and cannot find this disk when we try to mount to this disk.

ACTIONS

=======

Manually add SYSTEM account to disk F

PROBLEM:
===========
Creating the rule and targeting the computer group

CAUSE:
=========
We cannot directly Target the custom group while creating the rule.

RESOLUTION:
=============
If we want to target the custom group to any rule then we have to First target any built in groups at the time of creating the rule and disable the rule. Then set the override for the custom group.

Regarding the editing the rule, the user must have permission on the built in group that we have selected in the beginning and the customer group.

The permission can be given from Administrator console\user roles

1. Create your group and add the members you wish to monitor.
2. Create your rule/monitor and target it at a suitable class. For example if the machines you wish to monitor are all SQL servers, you can use the SQL Computers class.
3. Ensure the rule/monitor is disabled by default. To do this, click the General tab in the Properties dialog box for the rule or for the monitor in question, then make sure that the Rule is Enabled check box is cleared (not checked).
4. Create an override for the rule/monitor targeted at your group and sets the Enabled property to True. To do this follow these steps:
a. In the Authoring pane in the Operations Console, locate the rule or the monitor.
b. Right-click the rule or the monitor, point to Overrides, point to Override the Rule or to Override the Monitor, and then click For a group.
c. Click the group that you want to use, and then click OK.
d. Click to select the Override check box, and then click True under Override Setting.