How Does Service Account Manager Deal With Dependencies?


When Service Account Manager examines a service or attempts to manipulate a service it also gathers information about what services depend on this service. This means if you stop/restart a service that has services that depend on it, and those services are currently running as well, Service Account Manager will stop those services from the top down until we get to the service you actually wish to manipulate. Then we will restart those services in the correct order from the bottom to the top.

Conversely, if you attempt to stop/restart a service that depends on other services, Service Account Manager will also attempt to start those required services automatically if they are not already running.

A simple example is the clipbook service. The clipbook service depends on Network DDE which in turn depends on Network DDE DSDM. If you set all of these services to manual but do not start them, then using SAM attempt to start clipbook service, you will then see that in order, Network DDE DSDM was started, followed by Network DDE, and ending with clipbook.

If you then restart Network DDE DSDM, you can watch our log, your task manager, or your event logs, and see that clipbook was stopped, followed by Network DDE, then Network DDE DSDM. Then during the startup process, we started Network DDE DSDM, Network DDE, and then clipbbok. We start the two services after restarting Network DDE DSDM because they had been running when you issued the restart command.

Was this article helpful?
0 out of 0 found this helpful


Powered by Zendesk