• 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

  • 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.

  • 如何建立answer file並搭配sysprep 進行自動安裝 (XP/Server 2003)

    適用OS: Windows XP/ Windows 2003

    測試環境:

    - Windows XP Professional

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

    •    Domain Controller
    •    DNS Server
    •    DHCP Server

    - XP光碟片以及產品金鑰

    Part 1: 建立Answer file

    1. 將光碟片中 Support\Tools\Deploy.cab的內容解壓縮到XP本機電腦的資料夾

    clip_image002

    2. 執行setupmgr.exe

    clip_image003

    3. 按下一步繼續

    clip_image004

    4. 確認選項為 建立新的” 按下一步繼續

    clip_image005

    5. 選擇 ”Sysprep” 安裝按下一步繼續

    clip_image006

    6. 選擇產品為 ”Windows XP Professional” 按下一步繼續

    clip_image007

    7. 選擇 是,完全自動化安裝工作” 按下一步繼續

    8. 輸入這台電腦的名稱和組織(例如):

    l 名稱: user

    l 組織: MCSE

    clip_image009

    9. 按下一步繼續

    clip_image011

    10. 選擇時區為 “(GMT+08:00)台北” 按下一步繼續

    clip_image013

    11. 輸入 產品金鑰” 後按下一步繼續

    clip_image015

    12. 選擇 自動產生電腦名稱” 按下一步繼續

    clip_image017

    13. 按下一步繼續

    clip_image019

    14. 選擇 一般設定” 按下一步繼續

    clip_image021

    15. 如要自動加入網域,請輸入以下資訊:

    l 網域名稱 (如: mcse.lab)

    l 使用者帳號 (一般來說請輸入Domain Admin或Power User的帳號)

    l 密碼

    l 確認密碼

    clip_image023

    16. 按下一步繼續

    clip_image025

    17. 按下一步繼續

    clip_image027

    18. 選擇 繁體中文” 按下一步繼續

    clip_image029

    19. 按下一步繼續

    clip_image031

    20. 按下一步繼續

    clip_image033

    21. 按下一步繼續

    clip_image035

    22. 按完成繼續

    clip_image037

    23. 按確定完成

    clip_image038

    24. 按取消把安裝管理員視窗關閉

    clip_image040

    25. 請檢查 C:\sysprep資料夾中,是否有產生sysprep.inf檔

    clip_image042

     

    Part2. 執行sysprep進行迷你安裝,清除SID並加入網域

    clip_image043

    1. 執行sysprep.exe進行準備工具,按下確定

    2. 確認以下選項後按下 ”重新封裝”

    a) 勾選 使用迷你安裝”

    b) 關機模式選擇 關機”

    clip_image044

    c) 最後按下重新封裝

    clip_image045

    3. 按下確定之後產生新的SID進行系統準備工作

    4. 執行完畢後系統會自動關機,接下來就可以把這個Image備份下來進行大量佈署

    Part3. 驗證Image檔案

    1. 直接將此Image進行開機

    clip_image047

    2. 迷你安裝進行中

    clip_image049

    3. 正在準備開始安裝程式並執行自動化安裝

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

    l 如ipconfig/ping

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

    clip_image051

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

    5. 安裝成功後,請至網域控制站(DC)檢查此台電腦的帳號是否有產生在Computers的資料夾

    clip_image053

  • 如何建立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

  • Windows Server 2003 Terminal Services - Certain printers are not redirected

    If the printer driver is not found while redirecting the printer then server registers following event ID

    Type: Error
    Event ID: 1111
    Description: Driver drivername required for printer printertype is unknown. Contact the administrator to install the driver before you log in again.

    POSSIBLE ACTIONS
    ==================
    1. The ideal way to recover from this situation is installing the same exact driver on the server for the printer that we are trying to redirect.

    2. In Windows Server 2003 SP1 machine If you don’t want to install the corresponding driver you can try using the Fallback Printer Driver Capability.

    The policy for this is Computer Configuration > Administrative Templates > Windows Components > Terminal
    Services > Client/Server data redirection > Terminal Server Fallback Printer Driver Behavior
    For more info refer: http://technet2.microsoft.com/windowsserver/en/library/2284b19b-30a6-42b5-9bd1-ff301f7248b01033.mspx?mfr=true

    3. The best tool for resolving issues similar to above is Terminal Server Printer Redirection Wizard Tool. The Terminal Server Printer Driver Redirection Wizard will help you to troubleshoot and replace printer drivers that were unsuccessfully redirected.
    This can be downloaded from http://www.microsoft.com/downloads/details.aspx?familyid=9AD27BE9-40DB-484F-862E-38A094EEEAF7&displaylang=en

    4. Sometimes multifunction print devices may not be redirected unless you are running Windows Server 2003 on your local computer because they use DOT4 ports. Only W2K3 redirects printer port names that do not begin with COM, LPT, or USB. If you are using an Xp machine use the workaround mentioned in article KB 302361
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;302361