• Cluster network name resource 'Cluster Name' cannot be brought online, Unable to get Computer Object using GUID.

    SYMPTOM
    ==================
    You tried to bring Network Name Resources online but could not, following events are logged on cluster node:

    Log Name:      System
    Source:        Microsoft-Windows-FailoverClustering
    Event ID:      1207
    Task Category: Network Name Resource
    Level:         Error
    User:          SYSTEM
    Description:
    Cluster network name resource 'ClusterName' cannot be brought online. The computer object associated with the resource could not be updated in domain 'domain.com' for the following reason:

    Unable to get Computer Object using GUID.

    The text for the associated error code is: There is no such object on the server.

    The cluster identity 'ClusterName$' may lack permissions required to update the object. Please work with your domain administrator to ensure that the cluster identity can update computer objects in the domain.

    CAUSE
    ============
    There is inconsistency between the resource GUID recorded in cluster registry and AD computer object.

    RESOLUTION
    ============
    The following method assumes that the GUID data in registry is correct and AD object is incorrect and causing the issue.

    1. Make a note of the ObjectGUID for the CNO.  Using  ADSIEdit (located under Administrative Tools), locate the object corresponding to the CNO.  By default it should be located under CN=COMPUTERS.  Right-click on the object, select Properties and then on in the Attribute Editor tab locate the ObjectGUID entry and make a note of the GUID.  

    2. Next, on the cluster node, open the Registry Editor and locate the Cluster entry under HKEY_Local_Machine and expand it.  Select the top entry (Cluster) and notice the entry for the ClusterNameResource.  Locate the resource under the Resources entry under Cluster.  Find the correct resource by checking the Name entry, then expand the entry and select Parameters.  Note the ObjectGUID entry in the right-hand pane. 

    The GUID entry is the same as that in ADSIEdit but the arrangement of the alpha numeric entry is different.  Use the information below to decode the GUID.

    clip_image001

    3. We re-ordered GUID found in registry (for the two network name resource) and compared them with the ObjectGUID value found in AD, they are different.  This is causing the problem.

    4. We deleted the computer objects ‘ClusterName’ in AD (which holds incorrect ObjectGUID value) and use ADRestore tool to restore the correct object (by matching the calculated GUID) from CN=Deleted Objects container.

        ie: ADRestore -r ClusterName

    5. Once the object is restored, the object will be disabled.  Enable the object.

    6. For the cluster name account, open Failover Cluster Management console, click Manage a Cluster, and select or specify the cluster you want.

        In the center pane, expand Cluster Core Resources.

        Under Cluster Name, right-click the Name item, point to More Actions, and then click Repair Active Directory Object.

    7. Now we can bring the network name resources online

    REFERENCE
    ============
    How to recover a deleted computer object that supports a Network Name resource in a Windows Server 2008 or Windows Server 2008 R2 failover cluster http://support.microsoft.com/kb/950805/en-us

    Recovering a Deleted Cluster Name Object (CNO) in a Windows Server 2008 Failover Cluster http://blogs.technet.com/b/askcore/archive/2009/04/27/recovering-a-deleted-cluster-name-object-cno-in-a-windows-server-2008-failover-cluster.aspx

    Using ADRestore tool to restore deleted objects http://blogs.technet.com/b/asiasupp/archive/2006/12/14/using-adrestore-tool-to-restore-deleted-objects.aspx

    AdRestore v1.1 http://technet.microsoft.com/en-us/sysinternals/bb963906.aspx

  • 如何建立Answer file並搭配sysprep進行自動安裝 (Windows 7/Server 2008R2)

    適用OS: Windows 7/Windows Server 2008R2

    測試環境:

    - Windows 7 Enterprise

    - Windows Server 2003 ( 需要三個角色)

    • Domain Controller
    • DNS Server
    • DHCP Server

    - Windows 7光碟片

    - WAIK 安裝source

    http://www.microsoft.com/downloads/en/details.aspx?familyid=696DD665-9F76-4177-A811-39C26D3B3B34&displaylang=en

    Part 1. 安裝WAIK

    1. 放入WAIK光碟片執行StartCD.exe

    clip_image001

    2. 點選Windows AIK安裝程式

    clip_image003

    3. 按下一步繼續

    clip_image004

    4. 選擇我同意按下一步繼續

    clip_image006

    5. 按下一步繼續

    clip_image007

    6. 按下一步繼續

    clip_image009

    7. 按關閉完成安裝

    clip_image010

    Part 2. 建立類別目錄檔以及Answer File

    1. 將 Windows 7的光碟片中\source\install.wim 複製到本機電腦的資料夾

    clip_image012

    2. 選取Windows映像並指定到install.wim的路徑

    clip_image014

    3. 按下是建立類別目錄檔案

    clip_image016

    4. 建立好的類別目錄

    clip_image018

    5. 點選新建回應檔案

    clip_image020

    6. 建立好的空白Answer File

    clip_image022

    Part3. 新增類別目錄設定至Answer File

    1. 新增以下設定至Pass 7 oobeSystem(7)

    Amd64_Microsoft-International-Core_6.1.7600.16385_neutralclip_image024

    2. 新增以下設定至 Pass4 specialize(4)

    clip_image026

    Amd64_Microsoft_Shell-Setup_6.1.7600.16385_neutral

    3. 新增以下設定至Pass 7 oobeSystem(7)

    Amd64_Microsoft_Shell-Setup_6.1.7600.16385_neutral

    clip_image028

    4. 新增以下設定至 Pass4 specialize(4)

    Amd64_Microsoft_UnattendedJoin_6.1.7600.16385_neutral

    clip_image030

    Part4. 設定數值到answer file

    1. 在4 specialize的階段中Microsoft-Windows-Shell-Setup設定

    · ComputerName = *

    · TimeZone = Taipei Standard Time

    clip_image032

    2. 在4 specialize的階段中Microsoft-Windows-Shell-Setup\AutoLogon設定

    · Domain = mcse.lab

    · Enabled = true

    · Username = administrator

    clip_image034

    3. 在4 specialize的階段中Microsoft-Windows-Shell-Setup\AutoLogon\Password設定

    · Value = P@ssw0rd (密碼)

    clip_image036

    4. 在4 specialize的階段中Microsoft-Windows-UnattendedJoin\Identification設定

    · JoinDomain = mcse.lab

    clip_image038

    5. 在4 specialize的階段中Microsoft-Windows-UnattendedJoin\Identification\Credentials設定

    · Domain = mcse.lab

    · Password =P@ssw0rd

    · Username = administrator

    clip_image040

    6. 在7 oobeSystem的階段中Microsoft-Windows-International-Core設定

    · InputLocale = 0404-00000404

    · SystemLocale = zh-TW

    · UILanguage = zh-TW

    · UserLocale = zh-TW

    clip_image042

    7. 在7 oobeSystem的階段中Microsoft-Windows-Shell-Setup\OOBE設定

    · HideEULAPage = true

    · NetworkLocation = Work

    · ProtecYourPC = 1

    clip_image044

    8. 在7 oobeSystem的階段中Microsoft-Windows-Shell-Setup\UserAccounts\LocalAccounts設定

    · 按滑鼠右鍵選插入新的LocalAccount

    clip_image046

    9. 在7 oobeSystem的階段中Microsoft-Windows-Shell-Setup\UserAccounts\LocalAccounts\LocalAccount設定

    · Name = test

    clip_image048

    10. 在7 oobeSystem的階段中Microsoft-Windows-Shell-Setup\UserAccounts\LocalAccounts\LocalAccount\Password設定

    · Value = test

    clip_image050

    11. 全部輸入完畢後點選驗證回應檔

    clip_image052

    12. 下面的畫面表示沒有錯誤 (警告的訊息視情況可以忽略)

    clip_image054

    13. 點選檔案à儲存回應檔案 (如autounattend.xml)

    clip_image056

    14. 打開一個命令提示字元,並切換到 C:\Windows\System32\sysprep後輸入以下指令,如此以來就可以把這個image備份做大量佈署

    · Sysprep /generalize /oobe /shutdown /unattend:c:\autounattend.xml

    clip_image058

    Sysprep的語法請參考:

    clip_image059

    Part.5 驗證 image檔案

    1. 將image開機進行系統整備工作

    clip_image061

    2. 安裝進行中可以按下Shift+F10進入CMD並輸入簡單的指令查詢網路狀況

    · 如ipconfig/ping

    · 請確定此用戶端一定要可以連線到DHCP Server取得IP/MASK/DNS後才可進行自動加入網域的動作

    (安裝途中如有遇到錯誤會中斷作業並要求手動輸入)

    clip_image063

    3. 安裝完後進入DC檢查Windows7的電腦帳號已經被加入到Computers的資料夾中

    clip_image065

    4. 打開Windows 7的基本資訊檢查加入網域的資訊

    clip_image067

  • SCOM 2007 R2,Cannot resolve the collation conflict

    Environment:

    1. SQL Server 2008 SP2
    2. Operations Manager 2007 R2.

    Symptom:
    =======
    If a SQL Collation besides"SQL_Latin1_General_CP1_CI_AS" is specified when installing SQL OpsMgr will have  to be reinstalled as you will get errors after installing the product similar to the following:
    Cannot resolve the collation conflict between "SQL collation "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation.

    Workaround:
    ===========
    When installing SQL server be sure to select SQL collation SQL_Latin1_General_CP1_CI_AS. If OpsMgr has already been installed you will have to reinstall SQL and OpsMgr to change the SQL collation.

  • 在Windows 7下,如何讓非administrator的使用者可以安裝網路印表機?

    一般來講,如果沒有administrator權限的話,無法安裝網路印表機的驅動程式。您可以使用以下的方式來讓一般的使用者給予權限來安裝網路印表機。

     

    1.開啟Group Policy 編輯器(gpedit.msc或是gpmc.msc)

    2. 找到「電腦設定」>「系統管理範本」>「印表機」裏,將「指向並列印限制」改成已啟動

    3.安裝新連線的驅動程式時」選擇「不顯示警告或提高權限提示」

    4.更新現有連線的驅動程式時」選擇「不顯示警告或提高權限提示」

  • SCOM 2007 R2,Workflows for Unix/Linux monitoring are not running

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

    Event ID 1202|
    image

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