• The Override Properties dialog box does not appear on Windows Server 2008 R2

     

    Problem
    ==========

    The Override Properties dialog box does not appear
    My customer want to override a monitor. But, "Select destination management pack: " is missing and  MP drop-down menu and "new" button are missing.

    Operating System: Windows Server 2008 R2 (Traditional Chinese) is RMS Server.

    clip_image002

    And I install SCOM console on a Remote Server (English version OS) , I can see MP drop-down menu and "new" button.

    clip_image004

    Workaround
    ============
    Install Traditional Chinese SCOM console.

    clip_image006

  • Join Domain Fail

    癥狀

    1.用戶端無法Join Domain

    2.透過Terminal Server無法遠程登入伺服器,錯誤:存取被拒

    3.RMS Server無法開啟檔案

    解決方法

    確認設置HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\DefaultSecurity\SrvsvcDefaultShareInfo

    使用net share IPC$ 確認沒有人有權限存取

    刪除HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\DefaultSecurity\SrvsvcDefaultShareInfo重新開機後解決

    請參考以下分析報告

    用戶端加入Domina 時錯誤訊息如下

    加入網域的操做不成功。可能因為名為 ”%” 的現有電腦帳戶先前是使用不同的認證所建立。請使用其他電腦帳戶,或是聯絡系統管理員,已移除舊用戶的衝突帳號。錯誤是: 存取被拒

    clip_image002[4]

    2008 Server Join 失敗錯誤

    08/18/2011 10:20:31:564 NetpSetComputerNamesOffline: Setting Hostname to COMPUTERNAME

    08/18/2011 10:20:31:564 NetpSetComputerNamesOffline: Setting Domain name to DC.msft.com

    08/18/2011 10:20:31:564 NetpSetComputerNamesOffline: Setting NetBios computer name to COMPUTERNAME

    08/18/2011 10:20:31:564 NetpDoInitiateOfflineDomainJoin: status: 0x0

    08/18/2011 10:20:31:564 NetRequestOfflineDomainJoin: Successfully initiated the offline domain join

    08/18/2011 10:20:31:564 NetpJoinDomainOnDs: Setting netlogon cache.

    08/18/2011 10:20:31:564 NetpSetNetlogonDomainCache: DsEnumerateDomainTrustsW failed 0x5

    08/18/2011 10:20:31:564 NetpJoinDomainOnDs: status of setting netlogon cache: 0x5

    08/18/2011 10:20:31:564 NetpJoinDomainOnDs: Function exits with status of: 0x5

    08/18/2011 10:20:31:564 NetpJoinDomainOnDs: status of disconnecting from '\\DC.msft.com': 0x0

    08/18/2011 10:20:31:564 NetpDoDomainJoin: status: 0x5

     

    Windows XP Join失敗錯誤

    08/18 09:43:19 NetpDoDomainJoin

    08/18 09:43:19 NetpMachineValidToJoin: 'ComputerName'

    08/18 09:43:19 NetpGetLsaPrimaryDomain: status: 0x0

    08/18 09:43:19 NetpMachineValidToJoin: status: 0x0

    08/18 09:43:19 NetpJoinDomain

    08/18 09:43:19     Machine: Computer

    08/18 09:43:19     Domain: DC.msft.com

    08/18 09:43:19     MachineAccountOU: (NULL)

    08/18 09:43:19     Account: msft.com\Administrator

    08/18 09:43:19     Options: 0x27

    08/18 09:43:19     OS Version: 5.1

    08/18 09:43:19     Build number: 2600

    08/18 09:43:19     ServicePack: Service Pack 3

    08/18 09:43:19 NetpValidateName: checking to see if ' msft.com ' is valid as type 3 name

    08/18 09:43:19 NetpCheckDomainNameIsValid [ Exists ] for ' msft.com ' returned 0x0

    08/18 09:43:19 NetpValidateName: name ' msft.com ' is valid for type 3

    08/18 09:43:19 NetpDsGetDcName: trying to find DC in domain ' msft.com ', flags: 0x1020

    08/18 09:43:23 NetpDsGetDcName: failed to find a DC having account 'ComputerName$': 0x525

    08/18 09:43:23 NetpDsGetDcName: found DC '\\DC.msft.com ' in the specified domain

    08/18 09:43:23 NetpJoinDomain: status of connecting to dc '\\DC.msft.com ': 0x0

    08/18 09:43:23 NetpGetLsaHandle: LsaOpenPolicy on \\DC.msft.com failed: 0xc0000022

    08/18 09:43:23 NetpGetLsaPrimaryDomain: status: 0xc0000022

    08/18 09:43:23 NetpJoinDomain: initiaing a rollback due to earlier errors

    08/18 09:43:23 NetpJoinDomain: status of disconnecting from '\\DC. msft.com ': 0x0

    08/18 09:43:23 NetpDoDomainJoin: status: 0x5

    封包分析

    469 11:44:20 2011/8/18 15.672178 System {TCP:37, IPv4:22} 10.10.14.114 fisc-dc1.fisc.com.tw SMB2 SMB2:C TREE CONNECT (0x3), Path=\\DC.msft.com \IPC$, Mid = 3

    470 11:44:20 2011/8/18 15.673031 System {TCP:37, IPv4:22} DC.msft.com 10.10.14.114 SMB2 SMB2:R TREE CONNECT (0x3), TID=0x1, Mid = 3

    551 11:44:20 2011/8/18 15.783159 System {SMB2:53, TCP:37, IPv4:22} 10.10.14.114 DC.msft.com SMB2 SMB2:C CREATE (0x5), Name=NETLOGON@#551, Mid = 4

    552 11:44:20 2011/8/18 15.784966 System {TCP:37, IPv4:22} DC.msft.com 10.10.14.114 SMB2 SMB2:R , Mid = 4 - NT Status: System - Error, Code = (34) STATUS_ACCESS_DENIED

    563 11:44:20 2011/8/18 15.994402 System {TCP:37, IPv4:22} 10.10.14.114 DC.msft.com TCP TCP:Flags=...A...., SrcPort=49241, DstPort=Microsoft-DS(445), PayloadLen=0, Seq=264687530, Ack=4278783574, Win=509 (scale factor 0x8) = 130304

    603 11:44:20 2011/8/18 16.081317 System {SMB2:67, TCP:37, IPv4:22} 10.10.14.114 DC.msft.com SMB2 SMB2:C CREATE (0x5), Name=NETLOGON@#603, Mid = 5

    604 11:44:20 2011/8/18 16.081986 System {TCP:37, IPv4:22} DC.msft.com 10.10.14.114 SMB2 SMB2:R , Mid = 5 - NT Status: System - Error, Code = (34) STATUS_ACCESS_DENIED

  • Windows-Backup Hyper-V VM Fail

    backup 失敗event log

    Log Name:      Application

    Source:        Microsoft-Windows-Backup

    Date:          2011/8/5 上午 11:48:26

    Event ID:      521

    Task Category: None

    Level:         Error

    Keywords:     

    User:          SYSTEM

    Computer:      Computer.domain.com

    Description:

    Backup started at '2011/8/5 上午 03:47:56' failed as Volume Shadow copy operation failed for backup volumes with following error code '2155348129'. Please rerun backup once issue is resolved.

    事件中有發現以下事件,懷疑用VM的integration services版本比較舊

    Log Name:      System

    Source:        storvsp

    Date:          2011/7/13 下午 03:48:17

    Event ID:      6

    Task Category: None

    Level:         Warning

    Keywords:      Classic

    User:          N/A

    Computer:      Computer.domain.com

    Description:

    A storage device in 'Computer' loaded but has a different version from the server.  Server version 4.2  Client version 2.0 (VMID 0B9A3B2E-90D5-4571-B7B5-E50AA67F7DAB).

    若是請協助更新VM Computer上的Integration Services

    請先移除Integration Services並重裝

  • Backing up VM on Hyper-V triggering PlugPlayManager Event 12

    KB 958669 說明備份 VM 會觸發 PlugPlayManager Event 12 事件,備份過程 VSS Snapshot 會產生相對應機碼在 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\ 下面
    KB 982210 說明這個機碼若是不手動刪除會持續長大,這會延長伺服器啟動的時間甚或是會導致伺服器停留在 "Welcome" 畫面

    若是伺服器有啟動 ASR (IBM Automatic Server Restart or HP Automatic Server Recovery) 機制,ASR 就有機會判斷伺服器 Hang 住,強制將伺服器重新啟動

    SUGGESTION
    ================
    1. 對 Windows 2008 R2 的 Hyper-V 可以安裝 KB 982210  解決機碼持續成長問題
    2. 對 Windows 2008 的 Hyper-V 則暫無 Hotfix,但是可以手動/排程執行 "devnodeclean /r" 來刪除多餘的機碼 (請參考 KB 982210 下方的 Workaround 資訊)

    ANALYSIS
    ================
    我們比對了有問題跟目前沒有問題的 SYSTEM Hive,有問題的 SYSTEM Hive 下的 Enum 機碼是沒有問題的三倍大(21MB versus 6MB),而這些大出來的資訊都在 ENUM\SCSI\Disk&Ven_Msft&Prod_Virtual_Disk 下。跟 PlugPlayManager Event 12 的事件內容裡的裝置描述是一致的。

    Log Name:      System
    Source:        PlugPlayManager
    Event ID:      12
    Level:         Error
    Description:   The device 'Msft Virtual Disk SCSI Disk Device' (SCSI\Disk&Ven_Msft&Prod_Virtual_Disk\2&2282554&0&000000) disappeared from the system without first being prepared for removal.

    參考知識文件:
    The startup time increases or hangs at the logon “Welcome” screen if you frequently backup Hyper-V virtual machines on a Windows Server 2008 R2 system
    http://support.microsoft.com/kb/982210

    Event ID 12 is logged in the System log when you back up or compact a Hyper-V virtual hard disk on a Windows Server 2008-based computer
    http://support.microsoft.com/kb/958669

  • About Hyper-V Failover Cluster and “Refresh Virtual Machine Configuration”

    SYMPTOM
    =================
    將 Virtual Machine "ABC" 從 Node1 Live Migrate 至 Node2,進度到 90% 的時候失敗

    CAUSE
    =================
    從 Cluster Log 中發現失敗的原因是 'ABC' Microsoft Synthetic Ethernet Port (Instance ID {346984E3-8736-441E-9806-03F726E6B109}): Failed to restore with Error 'The system cannot find the path specified.' (0x80070003).

    Microsoft Synthetic Ethernet Port 跟 Virtual Switch/Network 有關,錯誤是 'The system cannot find the path specified.'

    經檢查 Node1& Node2 的 Hyper-V Virtual Network 設定,兩邊的 Virtual Switch 命名一致,比較可能的原因是 Failover Clustering 裡面的 VM Configuration 資訊跟 Hyper-V 不一致所導致。

    RESOLUTION
    =================
    Refresh the Virtual Machine configuration.

    To do this, follow these steps:
        a) Expand Services and Applications
        b) Select a Virtual Machine.
        c) Right click the Virtual Machine or click Actions, point to More Actions and select "Refresh Virtual Machine Configuration"

    以下BLOG說明 "Refresh virtual machine configuration" 這個功能的重要性

    BLOGS
    Cluster Resource Type options for Hyper-V - Ask the Core Team - Site Home - TechNet Blogs
    http://blogs.technet.com/b/askcore/archive/2008/08/27/cluster-resource-type-options-for-hyper-v.aspx

    Windows Server 2008 R2 Live Migration – “The devil may be in the networking details.” - Ask the Core Team - Site Home - TechNet Blogs
    http://blogs.technet.com/b/askcore/archive/2009/12/10/windows-server-2008-r2-live-migration-the-devil-may-be-in-the-networking-details.aspx

    Help 檔裡也有這個 "Refresh virtual machine configuration" 功能的說明

    Refresh the Configuration of a Virtual Machine

    Important 

    • If you cluster your virtual machines and then use Hyper-V Manager to change the configuration of one of those virtual machines, be sure to follow the procedure described in this topic. Otherwise, the settings of the virtual machine might not be up-to-date in the failover cluster, which could cause problems during the next move, migration, or failover of that clustered virtual machine.
    • We recommend that you use Failover Cluster Manager instead of Hyper-V Manager when you change the settings of a clustered virtual machine. For more information, see Modify the Virtual Machine Settings for a Clustered Virtual Machine.

    To refresh the configuration of a virtual machine

    1. In the Failover Cluster Manager snap-in, if the cluster that you want to configure is not displayed, in the console tree, right-click Failover Cluster Manager, click Manage a Cluster, and then select or specify the cluster that you want.
    2. If the console tree is collapsed, expand the tree under the cluster that you want to configure.
    3. Expand Services and Applications, and then click the virtual machine for which you want to refresh the configuration.
    4. In the Actions pane, scroll down, click More Actions, and then click Refresh virtual machine configuration.
    5. Click Yes to view the details of this action.

    Additional considerations

    You can also perform the task described in this procedure by using Windows PowerShell. For more information about using Windows PowerShell for failover clusters, see http://go.microsoft.com/fwlink/?LinkId=135119 and http://go.microsoft.com/fwlink/?LinkId=135120.

    clip_image002

    參考知識文件:

    以下連結包含如何 Troubleshoot Live Migration 問題

    Hyper-V: Using Live Migration with Cluster Shared Volumes in Windows Server 2008 R2 - Flowcharts for troubleshooting a live migration
    http://technet.microsoft.com/en-us/library/dd446679(WS.10).aspx

    以下連結包含如何設定 Network for Live Migration

    System Center Data Protection Manager 2010 Hyper-V protection: Configuring cluster networks for CSV redirected access
    http://support.microsoft.com/kb/2473194

    這篇 KB 2473194 重點如下:

    1. Hyper-V Failover Cluster 應該要 Dedicate 網卡給 CSV & LM 兩個資料流

    2. 所以使用 iSCSI 的 2008 R2 Hyper-V Failover Cluster應該每個 Node 至少具備五張網卡 (若是使用光纖則是四張)

    If you added two networks (one for CSV and one for Live Migration), you run these two commands:

    PS C:\Windows\system32> Get-ClusterNetwork "CSV Cluster" | %{$_.Metric=800}
    PS C:\Windows\system32> Get-ClusterNetwork "LM Cluster" | %{$_.Metric=900}

    You should manually set it to lower than 1000 so that it does not have a chance to conflict with anything else new that might come in later.  Now when you run the command to see what it configured, you see this:

    PS C:\Windows\system32> Get-ClusterNetwork | FT Name, Metric, Role

    Name                            Metric     Role
    ---------------------------------------------
    iSCSI Storage Network    10100      0
    Heartbeat Cluster             1000      1
    Host Access Cluster        10000      3
    CSV Cluster                      800      1
    LM Cluster                        900      1

    So based off of the Metric, the CSV Traffic will now be set for the CSV Cluster network because it is the lowest matric.

    以下連結包含如何設定 ISO 檔案分享

    How to Enable Shared ISO Images for Hyper-V Virtual Machines in VMM
    http://technet.microsoft.com/en-us/library/ee340124.aspx