• Windows XP SP3遠端連線錯誤[連線已終止,因未收到遠端電腦的意外伺服器憑證。請嘗試重新連線]

    [問題描述]︰

    Windows XP SP3 外部user 透過 Terminal Server Gateway 進行遠端連線,不定時出現 [連線已終止,因未收到遠端電腦的意外伺服器憑證。請嘗試重新連線]訊息,造成連線中斷。

    [解決方法]︰

    新增credSSP機碼與安裝kb953760以解決此問題。

    [說明]:
     
    CredSSP 是Windows XP SP3 中新的 Security Support Provider (SSP),預設未被啟用。CredSSP enables a program to use client-side SSP to delegate user credentials from the client computer to the target server.
    kb953760 則是修正Windows XP Kerberos authentication 的已知問題。
     
    [如何設定]:
     
    變更credSSP機碼

    1) Click Start, click Run, type regedit, and then press ENTER.

    2) In the navigation pane, locate and then click the following registry subkey:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

    3) In the details pane, right-click Security Packages, and then click Modify. In the Value data box, type tspkg. Leave any data that is specific to other SSPs, and then click OK.

    image003
    4) In the navigation pane, locate and then click the following registry subkey:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders

    5) In the details pane, right-click SecurityProviders, and then click Modify. In the Value data box, type credssp.dll. Leave any data that is specific to other SSPs, and then click OK.

    image004
    6) Exit Registry Editor and restart the computer.

     
     
    2.       安裝Hotfix
     

    When you enable SSO for a terminal server from a Windows XP SP3-based client computer,
    you are still prompted for user credentials when you log on to the terminal server
    http://support.microsoft.com/kb/953760

     
    [參考資料]:


    951608 Description of the Credential Security Service Provider (CredSSP) in Windows XP Service Pack 3
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;951608
    說明:
    CredSSP 是Windows XP SP3 中新的 Security Support Provider (SSP)
    CredSSP enables a program to use client-side SSP to delegate user credentials from the client computer to the target server.


    Technet Magazine:http://64.4.10.145/en-au/magazine/hh750380
    說明:
    Windows Server 2008 R2: Why Use Network Level Authentication?

    When you connect to an RD Session Host server with an RDC 6.x or later client, you might have noticed you don’t connect directly to the RD Session Host server logon screen to provide your credentials. Instead, a local dialog box pops up to take your credentials on the client. This dialog box is the front end of CredSSP.
    When you type your credentials into this dialog box, even if you don’t choose to save them, they go to CredSSP. This then passes the credentials to the RD Session Host server via a secure channel. The RD Session Host server will only begin building a user session once it accepts those credentials.

    When you enable SSO for a terminal server from a Windows XP SP3-based client computer,
    you are still prompted for user credentials when you log on to the terminal server
    http://support.microsoft.com/kb/953760

  • 修改Shadow Copy存放位置時出現錯誤訊息: 0x8004231d

    問題描述
    =================
    C槽的Shadow Copy先前透過修改將其存放於D槽
    後續嘗試修改磁碟機Shadow Copy的存放位置成C槽時 , 會出現錯誤訊息: 0x8004231d
    image

    image

     

    解決方式
    =================

    1. 執行底下指令進行Shadow Copy的大小調整 (此動作會刪除原有的Shadow Copy)

    vssadmin resize shadowstorage /for=c: /on=d: /maxsize=2000mb

    2. 手動透過UI方式再次進行調整即可

  • Hyper-V Host上進行VM備份時會造成部份VM進入Save狀態


    問題狀況
    ===================
    Hyper-V Host上進行VM備份時會造成部份VM進入Save狀態

     

    問題原因
    ===================
    有問題VM其C槽的Shadow Copy存放區是沒有存放在C槽本身 , 而是存放於D槽

     

    解決方式
    ===================
    將C:的Shadow Copy存放區改成C:本身即可
    image

    參考資料
    ===================
    http://blogs.technet.com/b/virtualization/archive/2008/08/29/backing-up-hyper-v-virtual-machines.aspx

    要進行online backup時VM的需求如下

    clip_image002

  • 無法建立NLB , Error 0x80041008

    問題狀況
    =================
    OS: Server 2008 R2

    無法建立NLB , Error 0x80041008

    image

     

    問題原因 & 解決方法
    =================

    經過確認此問題可能是當下網路卡驅動程式有問題所導致 , 透過底下方式處理即可已經正常

    1. 透過裝置管理員將網卡進行移除

    2. 重新開機讓網卡自動被偵測並安裝 , 手動設定相關IP設定

    3. 嘗試建立NLB即可正常

  • Clarify the location of 100MB system partition described in KB937251

    KB937251: The disk drive numbers may not correspond as expected to the SATA channel numbers when you set up Windows Vista, Windows Server 2008, Windows Server 2008 R2, or Windows 7 on a computer that has multiple SATA or RAID disks

     

    In addition to notify readers that the disk numbers and SATA channels numbers may not match, this KB took a step further to explain the creation of 100MB system partition.

    This is its original content:

    Additionally, when you install Windows 7, the installation creates a 100MB system partition alongside the Windows partition by default. The system partition is created to accommodate a Bitlocker requirement. Bitlocker requires that the boot files and Windows files are located on separate partitions. By default, the 100MB system partition is created on the disk that is detected as Disk 0. If you install Windows to a disk other than Disk 0, the 100MB system partition will still be created on Disk 0 during the installation.

     

    Content to clarify:

    The 100MB system partition will only be created on Disk 0 during the installation, if the user didn't change any of the pre-selected default settings. This by default definition includes: language selection, what type of installation do you want, which disk to install the Windows operating Sytem to...etc. If the user changes any of the pre-selected default settings, then this 100MB system partition is not guarantedd to be installed on Disk 0 as described in this KB.

    Example:

    I have a customer that chose "adanved options" and selected Disk 1 to install the Windows Operating System. Then he found out that the 100MB system partition is created on Disk 1 instead of Disk 0. This is because when he chose "advanced options" to make a selection change, this is no longer considered "by default", hence, the 100MB system partition is not guarantedd to be installed on Disk 0 as result.