More on Isolating Shared Services in Windows
Previously (Troubleshooting Performance Issues with Automatic Updates / How to Isolate A Shared Service Hosted by SVCHOST.EXE) I had detailed some steps that one could follow to isolate a shared service hosted by SVCHOST.EXE, in the context of the Windows Update Automatic Updates service. There are a couple of other ways to isolate a shared service, with different implications.
The intention / desire of a service to be “shared” or not is typically indicated when the service is created - the fifth parameter to CreateService is dwServiceType, which for our interests can be, among other things, SERVICE_WIN32_OWN_PROCESS (0×10) or SERVICE_WIN32_SHARE_PROCESS (0×20). Once a service has been created, the dwServiceType setting can be changed by calling ChangeServiceConfig with the appropriate parameters.
Windows XP and Server 2003 ship with a utility program called “SC.exe”. (I seem to recall using SC.EXE on NT 4.0, after it was included in some resource kit, but I could be mistaken. The DLL Help Database listing for SC.EXE puts the earliest version as having shipped with Visual Studio .NET 2002.) SC presumably stands for “Service Controller”. At any rate, one can use SC to change the configuration…
Click to continue reading "More on Isolating Shared Services in Windows"
Written by «/\/\Ø|ö±ò\/»®© on February 8th, 2007 with no comments.
Read more articles on SVCHOST and Shared Services and otherSoftware and automatic updates and Windows Update and Troubleshooting and Windows.















