• DNS AD整合Zone Missing

    DNS Zone missing,當重新建立AD整合Zone時會出現以下錯誤訊息

    "The zone cannot be replicated to all DNS servers in the (null) Active Directory domain"

    RESOLUTION
    To resolve this issue, follow these steps:
    1.  Change the DNS server to another DNS server that is available in the domain. To do this, follow these steps:
        a.  Right-click My Network Places, and then click Properties. 
        b.  Right-click Local Area Connection, and then click Properties. 
        c.  Click Internet Protocol (TCP/IP), and then click Properties. 
        d.  Type the IP address of any other DNS server in the Preferred DNS server box, and then click OK two times. 
        e.  Click Close to close the Local Area Connection Status dialog box. 
    2.  Disable the Kerberos Key Distribution Center service. To do this, follow these steps:
        a.  Click Start, point to Programs, click Administrative Tools, and then click Services. 
        b.  In the list of services, double-click Kerberos Key Distribution Center. 
        c.  In the Startup type list, click Disabled, click Stop, click Apply, and then click OK. 
        d.  Close the Services MMC snap-in. 
    3.  Restart the domain controller. 
    4.  Start the Kerberos Key Distribution Center service. To do this, follow these steps:
        a.  Click Start, point to Programs, click Administrative Tools, and then click Services. 
        b.  In the list of services, double-click Kerberos Key Distribution Center. 
        c.  In the Startup type list, click Automatic, click Apply, click Start, and then click OK. 
        d.  Close the Services MMC snap-in.

    參考資料

    Error message when you replicate an Active Directory-integrated zone from a Windows Server 2003-based domain controller: "The zone cannot be replicated to all DNS servers in the (null) Active Directory domain"
    http://support.microsoft.com/kb/938459/en-us

     

  • KCC一直出現事件1865,1311,1312

    當您的環境DC複寫正常,DNS解析也正常.但是卻有一台DC的事件檢視器中會不斷重複事件1865,1311,1312的情況.

    Symptom:

    事件類型:           警告

    事件來源:           NTDS KCC

    事件類別目錄: 知識一致性檢查程式

    事件識別碼:      1865

    日期:                     11/3/2009

    時間:                     15:31:14

    使用者:                NT AUTHORITY\ANONYMOUS LOGON

    電腦:          SBS2003

    描述:

    知識一致性檢查程式 (KCC) 無法產生一個完整的跨距樹狀目錄網路拓樸。因此無法從本機站台連接下列站台清單。

    站台:

    CN=ML,CN=Sites,CN=Configuration,DC=msft,DC=local

    事件類型:           錯誤

    事件來源:           NTDS KCC

    事件類別目錄: 知識一致性檢查程式

    事件識別碼:      1311

    日期:                     11/3/2009

    時間:                     15:31:14

    使用者:                NT AUTHORITY\ANONYMOUS LOGON

    電腦:          SBS2003

    描述:

    知識一致性檢查程式 (KCC) 已偵測出下列目錄磁碟分割發生問題。

    目錄磁碟分割:

    CN=Configuration,DC=msft,DC=local

    目錄磁碟分割:

    CN=Configuration,DC=msft,DC=local

    在 [Active Directory 站台及服務] 中沒有足夠的站台連線能力資訊,可供 KCC 建立跨距樹狀目錄複寫拓樸。或者,一些含有這個目錄磁碟分割的網域控制站無法複寫目錄磁碟分割資訊。這可能是因為網域控制站無法存取。

    使用者動作

    使用 [Active Directory 站台及服務] 來執行下列其中一個動作:

    - 發行足夠的站台連線能力資訊,這樣 KCC 可以判定這個目錄磁碟分割可到達這個站台的路徑。這是慣用的選項。

    - 從另一個站台中包含相同目錄磁碟分割的網域控制站上,新增一個連線物件到這個站台中包含目錄磁碟分割的網域控制站上。

    如果這兩個 [Active Directory 站台及服務] 工作都未修正這個情況,請參閱上一個 KCC 所記錄的事件,它識別無法存取的網域控制站。

    事件類型:           錯誤

    事件來源:           NTDS KCC

    事件類別目錄: 知識一致性檢查程式

    事件識別碼:      1312

    日期:                     11/3/2009

    時間:                     15:31:14

    使用者:                NT AUTHORITY\ANONYMOUS LOGON

    電腦:          SBS2003

    描述:

    指定下列傳輸的站台間訊息處理服務呼叫失敗。

    傳輸:

    CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=msft,DC=local

    因此,知識一致性檢查程式 (KCC) 無法設定正確的站台間複寫拓樸。

    使用者動作

    確認站台間訊息處理服務正在執行中。

    其他資料

    錯誤值:

    1722 無法取得 RPC 伺服器。

    Solution:

    由於Intersite Messaging服務被停用導致此問題

    需在DC上做以下設定:

    1. 點擊開始->運行,輸入services.msc按確定。

    2. 找到以下服務:Intersite Messaging

    3. 將啟動類型改為自動,並啟動此服務。

  • Security Database corrupted cause Policy failed to apply

    有時候,不管怎麼樣都無法套用policy,但是登入的動作都正常,SYSVOL的資料夾也可以正常訪問的話,看看下面的狀況,可能問題發生的情形相同。

    GPResults的資訊:

    MSFT\MSFT 的 RSOP 結果在 MSFT: 記錄模式
    ----------------------------------------------
    OS 類型:                     Microsoft Windows XP Professional
    OS 設定:                     成員工作站
    OS 版本:                     5.1.2600
    網域名稱:                  MSFT
    網域類型:                  Windows 2000
    站台名稱:                  Default-First-Site-Name
    漫遊設定檔:              
    本機設定檔:               C:\Documents and Settings\MSFT
    用低速連結來連線?: 否

    COMPUTER SETTINGS
    ------------------

        CN=MSFT,OU=Client,OU=WSUS,DC=MICROSOFT,DC=com,DC=tw

    上次套用的群組原則:     2009/3/10 at 上午 08:43:21
    套用的群組原則來自:     DC01.MICROSOFT.com.tw
    群組原則低速連結閾值: 500 kbps
    已套用的群組原則物件

    -----------

    Client WSUS Policy
    Client Admin Change Policy
    Software Deploy
    XP SP2 Policy
    Firewall Disable Policy
    Default Domain Policy
    本機群組原則

    看起來Policy套用是有的,但是期望的Policy還是沒有生效。

    不過我們從Winlogon.log 中發現以下錯誤:

    建立 \\MICROSOFT.com.tw\sysvol\MICROSOFT.com.tw\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine\Microsoft\Windows NT\SecEdit\GptTmpl.inf 的本機複本。

    GPLinkDomain GPO_INFO_FLAG_BACKGROUND )

    建立 \\MICROSOFT.com.tw\sysvol\MICROSOFT.com.tw\Policies\{30A020C9-8D63-44C7-9F78-B38F751BAB58}\Machine\Microsoft\Windows NT\SecEdit\GptTmpl.inf 的本機複本。

    GPLinkOrganizationUnit GPO_INFO_FLAG_BACKGROUND )

    建立 \\MICROSOFT.com.tw\sysvol\MICROSOFT.com.tw\Policies\{7F0629EF-1CAA-4DA1-9F67-36901C441328}\Machine\Microsoft\Windows NT\SecEdit\GptTmpl.inf 的本機複本。

    GPLinkOrganizationUnit GPO_INFO_FLAG_BACKGROUND )

    群組原則物件 \\MICROSOFT.com.tw\sysvol\MICROSOFT.com.tw\Policies\{9547A99D-B82F-4563-9B42-57228985C31E}\Machine 中並未定義範本。

    處理 GP 範本 gpt00000.dom。

    這不是最後一個 GPO。

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

    2009年3月1日 上午 02:43:03

    錯誤 1208: 發生延伸錯誤。

    建立 database 時發生錯誤。

    ----設定引擎初始化發生錯誤。----

    ----不初始化設定引擎...

    **************************

    和UserENV裡面發現大量以下錯誤:

    USERENV(404.218) 16:10:01:373 ProcessGPOs: Extension Security ProcessGroupPolicy failed, status 0x4b8.

    USERENV(404.f54) 16:27:29:091 ProcessGPOs: GetGPOInfo failed.

    USERENV(404.218) 17:51:08:265 ProcessGPOs: Extension Security ProcessGroupPolicy failed, status 0x4b8.

    USERENV(404.f54) 18:08:29:334 ProcessGPOs: GetGPOInfo failed.

    事件檢視器中也有相關錯誤:

    事件類型:  警告
    事件來源:  SceCli
    事件類別目錄:    無
    事件識別碼:       1202
    日期:         2009/3/10
    時間:         上午 08:43:30
    使用者:             N/A
    電腦: MSFT

    描述:
    安全性原則傳播中含有警告。 0x4b8 : 發生延伸錯誤。
    若要得到解決這個事件的最佳結果,請以非系統管理員帳戶登入,然後在http://support.microsoft.com 搜尋 "Troubleshooting Event 1202's"。

    請在 http://go.microsoft.com/fwlink/events.asp 查看說明及支援中心,以取得其他資訊。

    事件類型:  錯誤
    事件來源:  Userenv
    事件類別目錄:    無
    事件識別碼:       1085
    日期:         2009/3/10
    時間:         上午 08:43:30
    使用者:             NT AUTHORITY\SYSTEM
    電腦: MSFT

    描述:
    無法執行群組原則用戶端延伸 Security。請試著找出延伸先前是否有錯誤報告。
    請在 http://go.microsoft.com/fwlink/events.asp 查看說明及支援中心,以取得其他資訊。

    目前我們看到這樣的狀況,我們可以判斷這個問題是由於 secedit.sdb 資料庫損毀所導致的。

    接下來,請依照以下方案重建 Secedit.sdb:

    1. Open the %SystemRoot%\Security folder, create a new folder, and then name it "OldSecurity".

    2. Move all of the files ending in .log from the %SystemRoot%\Security folder to the OldSecurity folder.

    3. Find the Secedit.sdb file in the %SystemRoot%\Security\Database folder, and then rename this file to "Secedit.old".

    4. Click Start, click Run, type mmc, and then click OK.

    5. Click Console, click Add/Remove Snap-in, and then add the Security and Configuration snap-in.

    6. Right-click Security and Configuration and Analysis, and then click Open Database.

    7. Browse to the %TEMP% folder, type Secedit.sdb in the File name box, and then click Open.

    8. When you are prompted to import a template, click Setup Security.inf, and then click Open.

    9. Copy %TEMP%\Secedit.sdb %SystemRoot%\Security\Database.

  • SCOM 2007,Alert generated from WMI Probe Module Execution Failure rule

    PROBLEM DESCRIPTION:
    =====================

    You needed assistance in troubleshooting the “Module was unable to connect to namespace” and “WMI Probe Module Failed Execution” Error.

    Alert: WMI Probe Module Failed Execution
    Source: 123.com.tw
    Path: 123.com.tw
    Last modified by: System
    Last modified time: 2009/3/13 上午 00:00:00 Alert description: ExecQuery failed
    Query: 'SELECT DeviceID, Name, Description, FileSystem, Compressed, Size, DriveType, SupportsFileBasedCompression FROM Win32_LogicalDisk WHERE (DriveType=3 or DriveType=6) and FileSystem!=null'
    HRESULT: 0x80004005
    Details: 無法指出的錯誤
    One or more workflows were affected by this.
    Workflow name: Microsoft.Windows.Server.2000.LogicalDisk.Discovery
    Instance name: 123.com.tw
    Instance ID: {12345678-ABCD-A123-A1A1-2C3FA9235EE5}
    Management group: JimmyTest
    Alert view link: "http://Jimmytest-SCOM/default.aspx?DisplayMode=Pivot&AlertID=%11334ef13f2-6dc5-478c-aa18-c49cef097356%7d"
    Notification subscription ID generating this message: {12345678-6B9D-7CAE-8EEC-5535DB2E3F6F}

    CAUSE:
    ======

    This is related to a known Bug. The WMI Query looks for "SystemDrive" which apparently not present on the Windows 2000 Machines.

    RESOLUTION :
    ==========

    Please disabled the rule for Windows 2000 servers.

    RELATED KNOWLEDGE BASE ARTICLES :
    =========================

    Problems occur on a management server that is running System Center Operations Manager 2007 Service Pack 1 when certain management packs are installed
    http://support.microsoft.com/?id=951979

  • Unable to Monitor Analysis Services Servers

    事件類型:       警告
    事件來源:       Health Service Modules
    事件類別目錄:       無
    事件識別碼:   21406
    描述:
    The process started at 下午 00:00:00 failed to create System.Discovery.Data. Errors found in output:
    C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 4\710\DiscoverSQL2005ASDiscovery.vbs(944, 11) Microsoft VBScript runtime error: Type mismatch: '[string: ""]'
    Command executed:       "C:\WINDOWS\system32\cscript.exe" /nologo "DiscoverSQL2005ASDiscovery.vbs" {AAD43FAE-0F82-0499-51E1-B30B1344AF93} {B499003B-DC85-0A30-E227-478D01D4BF78} jimmyscom.123.tw jimmyscom.123.tw
    Working Directory:  C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 4\710\
    One or more workflows were affected by this. 
    Workflow name: Microsoft.SQLServer.2005.AnalysisServicesDiscoveryRule.Server
    Instance name: jimmyscom.123.tw
    Instance ID: {12345444-0A30-E227-478D01D4BF78}
    Management group: Jimmytest
    請在 <http://go.microsoft.com/fwlink/events.asp> 查看說明及支援中心,以取得其他資訊。

    Root Cause :
    ==========
    - SQL Management Pack version no 6.0.6460.0 DiscoverSQL2005ASDiscovery.vbs was having issues.

    Resolution :
    ============
    The name of the two scripts are as follows:
    Analysis Services: DiscoverSQL2005ASDiscovery.vbs
    Reporting Services: DiscoverSQL2005RSDiscovery.vbs
    The files are stored in the folder structure inside the Health Service State directory, so you'll need to perform a search (Windows Search or by running a dir /s /a /b from a command prompt) against the Health Service State directory eg. C:\Program Files\System Center Operations Manager 2007\Health Service State
    Once you've located the files, open them for editing
    Locate the following block of code, it's located near line 1343 for AS, and near line 1256 for RS:

    Public Function GetSQLServiceName(sInstance)
    If sInstance = SQL_DEFAULT Then
    GetSQLServiceName = SQL_DEFAULT
    Else
    GetSQLServiceName = "MSSQL$" & sInstance
    End If
    End Function
    Modify the highlighted code above as follows for each script:
    Analysis Services:
    Public Function GetSQLServiceName(sInstance)
    If sInstance = SQL_DEFAULT Then
    GetSQLServiceName = "MSSQLServerOLAPService"
    Else
    GetSQLServiceName = "MSOLAP$" & sInstance
    End If
    End Function
    Reporting Services:
    Public Function GetSQLServiceName(sInstance)
    If sInstance = SQL_DEFAULT Then
    GetSQLServiceName = "ReportServer"
    Else
    GetSQLServiceName = "ReportServer$" & sInstance
    End If
    End Function

    Now that the scripts have been updated, make sure not to restart the health service on this server, otherwise the script will be overwritten with the original version from the MP. This is one of the limitations of the workaround, as we aren't updating the script at the source (in the MP), so any time the health service is restarted, it will update it's configuration and check all files to make sure they
    match, and if they don't it will overwrite them.