How can the start up order of the Symantec DLP Services within a Windows environment be setup?
Within Windows you can set up dependencies on each Service.
This means that the Symantec DLP Service will only be started when the Service it depends on is succesfully started up.
In addition you can set up the startup order of services groups
You can set up dependencies via the command line in the following way:
sc config <epa service name> depend= <dependent services>
In this example, if the services name is 'edpa' and you want to make it dependent on 'TCPIP' service then the command would be
sc config edpa depend= tcpip
If you want to have multiple dependencies you would have to use / as a separator. For example, if you want to set a dependency to 'TCPIP' and to 'WMI' the dependency would be 'TCPIP/WMI' as in the following example.
sc config edpa depend= tcpip/wmi
- Before applying it, you should stop the Services you want to modify
- The space ' ' between the 'depend=' text and the first dependency service name has to remain! If you do not include this space the dependency will not be applied.
Service Group Start Order
In general you can setup services startup order via the registry.
These are the general rules how the startup order can be modified:
- Add the Endpoint Agent Service to a service group
- Open up regedit
- Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ServiceGroupOrder
- Double click on List
- Here you can modify the list that determines in which order the services groups will start
See as reference:
At a service level, the HKEY_LOCAL_MACHINE\CurrentControlSet\Services\ServiceName subkeys contain:
Group - this REG_SZ specifies the Service Group name that a service belongs to.
tag - this REG_DWORD specifies the service load sequence.
DependOnGroup - this REG_MULTI_SZ entry defines the Service Groups the service in question depends on
DependOnService - this REG_MULTI_SZ entry defines the service, which the service in question depends on
Please note: This will affect your setup. It may interfere with your individual environment and the specific dependencies within it. This needs to be reviewed and verified by your Windows admin team.