Many programs such as sequel Sara or ISIS contain services that you install on the server that hosts
the program.
These services typically run at server startup or are triggered by other events.
Services often run in the background and do not require any user interaction for a service to a startup
and awesome ticket.
You use a service account a service account maybe an account that is local to the computer such as the
built in local system local servers or network service accounts.
You also can configure a service account to use a domain based account located in 80 days to help centralized
administration and to timid programme requirements.
Many organizations choose to use a domain based account to run program services.
Although this does provide some benefit over using a local account there are several associated challenges
such as the following extra administration effort might be necessary to manage the service account password
securely.
This includes tasks such as changing the password and resolving situations that cause an account lock
out.
Service accounts also typically are configured to have passwords that do not expire which may go against
your organization's security policies and other challenges.
Difficulty in determining where a domain based account is used as service account.
You might use a standard user account for multiple services on various servers throughout the environment.
A simple task such as changing the password might cause authentication issues for some applications.
It is important to know where and how to use a standard user account when it is associated with a program
service and other challenges.
Extra administration effort may be necessary to manage the service principle name or SBN using a standard
user account may require manual administration of the SBA.
Is you log on account of the service changes the computer name is changed.
Alternatively if a DNS Host Name property is modified you may need to modify the SBN registrations manually
to reflect the change they are mis configured as being causes authentication problems with the program
service Windows Server 2016 supports an ADT as subject named managed service account or MSA which are
used to facilitate service account management and we'll be talking about it in subsequent topics will
discuss the requirements and use of MSA s in Windows Server 2016.