問題:在MOSS Server上，在使用資訊版權管理設定時，使用SCP或是直接指向RMS Server正確位置都失敗，無法完成設定。另外在MOSS Server上，會看到5092或是5145的錯誤。

1. Stop the Windows SharePoint Services 3.0 Web application by running the following command at the command prompt.

iisreset /stop

2. On the Windows SharePoint Services 3.0 front-end Web server, navigate to the %allusersprofile%\Application Data\Microsoft\DRM\Server\ folder

3. Delete all folders named after the Windows SharePoint Services 3.0 application pool identity account. The application pool identity is the user account that Windows SharePoint Services 3.0 is running under.

4. Restart the Windows SharePoint Services 3.0 process by running the following command at the command prompt.

iisreset /start

參考資料：

Event ID 5092 (Windows SharePoint Services health model)

http://technet.microsoft.com/en-us/library/cc561103.aspx

Event ID 5145 (Windows SharePoint Services health model)

http://technet.microsoft.com/en-us/library/cc560972.aspx

相信最近更新VISTA SP2的朋友們會發現，以往大家說的10個網路連線數量的限制悄悄的不見了。這點是獲得證實的，這個限制在VISTA SP2中被取消了，很多人一定很好奇，為什麼以往要限制這個連線數量呢？理由主要指有一個：

當發生大量病毒Break Out的時候，有些種類的病毒(蠕蟲)會在系統中建立大量的連線數並且嘗試感染或是工及其他電腦，為了減低這樣的危險性，我們以往的Clinet作業系統都會加上相關的限制。但是這樣也造成了其他的問題，例如P2P程式或是網路電視的程式，需要同時多點傳訊的當下，就會透過"竄改的" TCPIP.SYS系統檔案來達到這個目的。對使用者來說，看起來似乎網路是變快了，但是這個被"竄改"的TCPIP.SYS極有可能裡面會有有心人士加入的後門系統，這個部分反而成為系統安全性的大漏洞。

因此，在SP2裡面，預設這個10個連線數量的限制已經取消，使用者再也不需要使用"竄改的" TCPIP.SYS來得到更好的網路連線效能。但是，如果您還是需要這個限制的話，還是有方法可以做得到：

請您開啟登錄檔編輯程式(regedit.exe)並且找到以下的機碼：

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
名稱：EnableConnectionRateLimiting
值：1

最後也請大家儘快升級VISTA SP2，獲得新的安全性更新和更好的效能。

The command line is documented in the WSUS Operations Guide on page 65.
WSUS operation guide - Microsoft Download Center

Here is the process you would need to follow:
1. Create a folder called "content" on the new partition (e.g. E:\content)
2. Then use the following command: %drive%\Program Files\Update Services\Tools>
    wsusutil movecontent E:\content C:\movecontent.log
This command will move the content folder from its current location to E:\content and create a log file called movecontent.log on the root of your C:\ drive.

CAUSE
===================
When "UseDomainNameDevolution" is configured to 0, a single default entry is placed in the DNS suffix search list, for example "sub.domain.com.tw"

However, a devolutionized DNS suffix search list is populated if the entry is configured to 1, for example:
"sub.domain.com.tw"
"domain.com.tw"
"com.tw"

This is normal and a by-design behaviour

SUGGESTION
===================
Normally the client would uses domain name devolution to resolve an unqualified query. So it is normal be observe multiple DNS suffix entries under DNS suffix search list returned by ipconfig command.

We may manually disable it by:
1. Setting "UseDomainNameDevolution" (HKLM\Software\Policies\Microsoft\Windows NT\DNSClient) to 0
or
2. Manually populate the search list as described in Q275553 http://support.microsoft.com/KB/275553

問題描述︰
Performance counters display as a number on W2K8

解決方式︰
ANALYSIS
=======

After checking the server’s configuration and registry, the cause of missing performance counters is due to the registry has been revised and some performance counters are lost. The revised registry is located in “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib”.

ACTIONS
=======
To get the OS performance counters back, please follow the steps below on each problematic server:

1. Backup the registry

- Run “regedit.exe” and navigate to  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib.

- Right click it “Perflib” and select “匯出”. Then save as a .reg file.

2. Rebuild the performance counter

- Click “start”, right click ”命令提示字元” , choose “以系統管理員身份執行”。

- In the command line , type “lodctr /r” , press enter. Wait for the successful information.

- After finishing the action , you should see the OS performance counters in the performance monitor.   

To get all exchange performance counters back, a reboot of the computer was required and performed after rebuilt all counters.

SUGGESTION
==========

If you find the registry key “Configuration Flags” in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib has not been set to 0. That means the perflib file will allow revise some important performance counter registry key manually or by some applications which may cause revise the performance counters by mistake. By default, this key doesn’t exist. So we suggest to set the key value to 0.