Explaining registry entries, service accounts, and dependencies (1.2.8)

In most cases, you will end up adding a new registry key or a registry value when you are fixing an issue, or adding a new feature to your Windows Server. No matter what, you should always be careful when working with the registry. In regard to services, the service account is the Windows Server's native account or an account created by you to manage the running services. From a security standpoint, the service account enables the services to access both local and network resources. From the perspective of the accounts that the services run, the following service accounts are available in Windows Server 2016:

• Local System: This is a built-in account with the most privileges in a Windows OS. It is also known as a superuser, and this account is more powerful than your admin account.
• NT Authority\LocalService: This is a built-in account with the same privileges as members of the Users group.
• NT Authority\NetworkService: This is a built-in account that has more privileges than members of the Users group.

As far as service dependency is concerned, what often happens is that applications use more than one service. So, if you try to stop a service, you need to stop a few others too. Conversely, if you try to start a service, a few others will need starting too. Thus, dependencies are created between the services.