In Windows Server 2003, the WMIC PROCESS command can reveal which specific service is causing problems. However, I don't know of an elegant way to identify what services are consuming resources within the services.exe process in Windows 2000. So I would suggest stopping services one-by-one, starting with the least necessary services. If one of the services refuses to stop, or if the processor utilization drops after stopping a service,...
you've identified your culprit.
Dig deeper on Microsoft Active Directory
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.