In Windows Server 2003, you may experience high CPU
usage. For example, you notice the following behavior:
- The CPU usage may be constantly greater than 60 percent.
- In Task
Manager, you find that the Svchost.exe process is using the CPU resources constantly. This process is used by the File Server Resource Manager (FSRM)
- The CPU that is consumed by the FSRM service increases
when you start the Quota FSRM Manager.
- The Quota FSRM Manager takes a long time to open and it takes a long time for the objects to be loaded.
When this problem occurs, the performance of the
system is affected.
This problem occurs because of a known bug in Windows Server
2003 that is fixed in Windows Server 2008. The FRSM service has a
polling thread that attempts to refresh the Distributed File System (DFS) cache
every hour. This is because the FSRM service reads the DFS mappings for the
local shares so that they can be displayed in the FSRM console. To troubleshoot quota issues if you are an administrator, review the DFS path to determine the local share that is being connected to.
This section, method, or task contains steps that tell you how to
modify the registry. However, serious problems might occur if you modify the
registry incorrectly. Therefore, make sure that you follow these steps
carefully. For added protection, back up the registry before you modify it.
Then, you can restore the registry if a problem occurs. For more information
about how to back up and restore the registry, click the following article
number to view the article in the Microsoft Knowledge Base:
How to back up and restore the registry in Windows
To resolve this problem, change the value data of
the DisableSearchDfs registry entry in the following registry subkey to