Microsoft® Windows® 2000 Scripting Guide
« Previous | Next »
Service management is complicated by service dependencies. For example, many Internet services including the FTP Publishing Service, the World Wide Web Publishing Service, and the Simple Mail Transfer Protocol (SMTP) Service are dependent upon the Internet Information Services (IIS) Admin Service. If the IIS Admin Service is not available, none of these dependent services can run.
Conversely, you cannot stop the IIS Admin Service without first stopping the dependent services. If this were allowed, stopping the IIS Admin Service would cause all its dependent services to fail because those services cannot run unless IIS Admin Service is also running. The IIS Admin Service is therefore antecedent to its dependent services.
The relationship between the dependent and antecedent roles is as follows:
Figure 15.3 maps these service roles to the Dependencies property page found in the Services snap-in.
Figure 15.3 Dependent and Antecedent Roles
Dependent and Antecedent Roles
To determine service dependencies, you need a script that specifies the service to be enumerated and its role. The Win32_DependentService class provides a means to identify the particular role played by that service.
Note
For example, to list all the services that depend on the Remote Access Connection Manager, you need to create a script that:
Send us your feedback | « Previous | Next » |