1
00:00:07,000 --> 00:00:15,220
Many programs such as sequel Sara or ISIS contain services that you install on the server that hosts

2
00:00:15,310 --> 00:00:16,350
the program.

3
00:00:16,360 --> 00:00:23,860
These services typically run at server startup or are triggered by other events.

4
00:00:23,920 --> 00:00:32,150
Services often run in the background and do not require any user interaction for a service to a startup

5
00:00:32,150 --> 00:00:33,930
and awesome ticket.

6
00:00:33,940 --> 00:00:41,980
You use a service account a service account maybe an account that is local to the computer such as the

7
00:00:41,980 --> 00:00:48,280
built in local system local servers or network service accounts.

8
00:00:48,280 --> 00:00:57,700
You also can configure a service account to use a domain based account located in 80 days to help centralized

9
00:00:57,700 --> 00:01:01,250
administration and to timid programme requirements.

10
00:01:01,300 --> 00:01:07,410
Many organizations choose to use a domain based account to run program services.

11
00:01:07,660 --> 00:01:16,300
Although this does provide some benefit over using a local account there are several associated challenges

12
00:01:16,300 --> 00:01:24,640
such as the following extra administration effort might be necessary to manage the service account password

13
00:01:24,640 --> 00:01:25,840
securely.

14
00:01:25,840 --> 00:01:33,520
This includes tasks such as changing the password and resolving situations that cause an account lock

15
00:01:33,520 --> 00:01:34,120
out.

16
00:01:34,120 --> 00:01:41,890
Service accounts also typically are configured to have passwords that do not expire which may go against

17
00:01:41,890 --> 00:01:46,840
your organization's security policies and other challenges.

18
00:01:46,970 --> 00:01:53,390
Difficulty in determining where a domain based account is used as service account.

19
00:01:53,530 --> 00:02:01,960
You might use a standard user account for multiple services on various servers throughout the environment.

20
00:02:01,990 --> 00:02:09,750
A simple task such as changing the password might cause authentication issues for some applications.

21
00:02:09,760 --> 00:02:17,980
It is important to know where and how to use a standard user account when it is associated with a program

22
00:02:17,980 --> 00:02:20,060
service and other challenges.

23
00:02:20,230 --> 00:02:29,440
Extra administration effort may be necessary to manage the service principle name or SBN using a standard

24
00:02:29,470 --> 00:02:35,110
user account may require manual administration of the SBA.

25
00:02:35,430 --> 00:02:40,190
Is you log on account of the service changes the computer name is changed.

26
00:02:40,540 --> 00:02:50,560
Alternatively if a DNS Host Name property is modified you may need to modify the SBN registrations manually

27
00:02:50,860 --> 00:02:58,420
to reflect the change they are mis configured as being causes authentication problems with the program

28
00:02:58,420 --> 00:03:09,190
service Windows Server 2016 supports an ADT as subject named managed service account or MSA which are

29
00:03:09,190 --> 00:03:17,580
used to facilitate service account management and we'll be talking about it in subsequent topics will

30
00:03:17,590 --> 00:03:24,510
discuss the requirements and use of MSA s in Windows Server 2016.