問題描述
===============
這些Ghost OS設定了雙CPU
Ghost OS ping Ghost ping 值很高，檔案複製超慢
重新開機Guest OS可以暫時解決

解決方法
==============
目前有一個已知問題無論是AMD或是Intel CPU都有發現症狀相同，若是CPU是dual core作業系統是2003，有可能導致Ping值很高
請於Boot.ini加上 /usepmtimer參數

範例

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows 2003" /fastdetect /usepmtimer 

重新開機Host

問題
===============
安裝HP5100安裝過程有問題，應該是說無法新增任何IPP列印伺服器

狀態
======================
安裝過程還未到提供driver的步驟就會報錯

Error: Windows cannot connect to the printer. Make sure that you have typed the name correctly, and that the printer is connected to network.
中文: Windows 無法連線到印表機，請確定您輸入正確的名稱，且印表機已連線至網路。

由收集封包來看不到IPP protocol 有往外的封包發出

解決方法
==============
On Windows Server 2k8, you need to install the ‘Internet Client Printing’ feature to enable using IPP to connect and print to printers on the networks or Internet. And a restart is a must. The 2k8 server is not installed with this feature by default. I found on blr2b05-m1, the feature is installed, but you may have not reboot the server. After I restarted it, IPP can work now.

To enable Internet printing on Windows Srv 2k8, what you need to do is to install ‘Internet Client Printing’ feature and restart the server.

在安全模式下面，作業系統基本上只會啟動開機需要的一些相關服務，其他的服務預設是不會啟動的。

但是在某些情況下，可能會需要在安全模式下面安裝一些程式，但是如果剛剛好這個程式是Windows Installer的Package的話，我們預設.MSI的檔案是不可以在安全模式下面裝的。如果真的有需要該怎麼辦？

注意：微軟並不會為以下的動作做任何進一步的技術支援，也不會提供更進一步的資訊，如果您的服務啟動會有問題我們也將不會進行任何的疑難排除，這個部分主要是要解釋在安全模式下面服務是否啟動的機制!!

1.基本上，在系統中，有一個機碼控制安全模式中啟動服務或程式的列表，這個機碼位置如下：
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot
 
清楚明瞭…Minimal就是指一般安全模式，而Network就是指安全模式含網路功能

2.接下來，我們到Minimal的機碼下，裡面就會列舉所有會執行的程式或是服務。

3.如果我們要增加特定的服務讓這個服務在安全模式下啟動，就直接把機碼設定起來，我們以Windows Installer為例：

a.新增一個機碼叫做MSIServer

b.在預設值裡面，設定資料為 "Service"

c.重新開機，Windows Installer 服務在安全模式裡面就會啟動了。

再次聲明…這個動作不見得可以啟動所有的服務，只是給大家展示一下到底安全模式怎樣控制服務是否要啟動的機制!!!

以下是預設 OS Base MP "Logical Disk Free Space" Monitor 須知:

1. 該 Monitor 只會對 "Critical State" 產生 Alert

2. 該 Monitor 的觸發條件是 % Free Space 以及 MByte Free Space 兩個條件必須同時成立

3. 預設的偵測 Interval (間距) 是 3600 秒 (1小時)

所以當您認為該 Monitor 沒有正常運作、發警訊通知您時，請確認:

a. 您要看的是 "Critical" 或是 "Warning" 警訊?

b. 是否兩個觸發條件都成立?

c. 是否預設間距太長? 嘗試透過 Override 去縮短間距成 10 分鐘

d. 您是否可以用 Performance Monitor 工具在該 Agent 上收集的到 Logical Disk 計數器資料?

主要的步驟如下:

1. 使用 AdsiEdit.msc 工具去把 AD 裡的 CA 相關資料刪除，詳細步驟請參考下面的 "Cleanup the original CA information from Active Directory"

2. 讓 Site 裡的 DC 進行立即同步複寫

3. 安裝新的伺服器，伺服器名稱 "必須" 跟之前的 CA 一模一樣，加入網域

4. 安裝CA 原件，詳細步驟請參考下面的 "To restore the root CA"

To restore the root CA

========================

If you have the backup of the original root CA certificate and the private key, we can rebuild the root CA using the original root CA certificate.

To do that, please perform the following steps:

1. Rebuild the server with the same computer name and IP address. Open add/remove program to install the certificate service again.

2. On the Windows Components Wizard, select the check box of the certificate services and click next.

3. Select stand-alone Root CA radio box on the CA type dialog box, make sure you select the "use custom settings to generate the key pair and CA certificate" check box and click next.

4. On the public and private key pair dialog box, select "use an existing key" check box. Click the import button to import the original private key (.pfx file).

After the key is listed, click it, make sure "use the certificate associated with this key" check box is selected and click next.

5. On the CA Identifying Information dialog box, type the name of the root CA the same as the original one and click next. Follow the wizard to install the certificate service.

6. Use NT backup to backup the system status. The certificate service and the CA database will be backed up.

Cleanup the original CA information from Active Directory

=========================

When Microsoft Certificate Services is installed on a server that is a member of a domain, several objects are created in the configuration container in Active Directory. These objects are the following:

  - certificateAuthority object

    Located in CN=AIA,CN=Public Key Services,CN=Services,CN=Configuration,DC=ForestRootDomain. 

    Contains the CA certificate for the CA. 

    Published Authority Information Access (AIA) location. 

  - crlDistributionPoint object

    Located in CN= ServerName ,CN=CDP,CN=Public Key Service,CN=Services,CN=Configuration,DC=ForestRootDomain. 

    Contains the CRL periodically published by the CA. 

    Published CRL Distribution Point (CDP) location.

  - certificationAuthority object

    Located in CN=Certification Authorities,CN=Public Key Services,CN=Services,CN=Configuration,DC=ForestRootDomain. 

    Contains the CA certificate for the CA. 

  - pKIEnrollmentService object

    Located in CN=Enrollment Services,CN=Public Key Services,CN=Services,CN=Configuration,DC=ForestRootDomain. 

    Created by the enterprise CA. 

    Contains information about the types of certificates the CA has been configured to issue. Permissions on this object can control which security principals can enroll against this CA.

1. Please use the ADSIEDIT.msc from Windows Support Tools to remove all references to the crashed CA. Please pay attention to this operation as you only need to remove the CA references but NOT the containers themselves.

2. When you finish the above operation, please force the Active Directory replication to occur among your domain controllers to ensure the cleanup operation is replicated properly.