-
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #33 from ty-abbott/ty-abbott-patch-1
Create create-and-manage-ad-objects.md
- Loading branch information
Showing
1 changed file
with
28 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
## Define Users, groups, and computers | ||
In AD DS, you must provide all users that require access to network resources with a user account. | ||
With this user account, users can authenticate to the AD DS domain and access network resources. | ||
|
||
A user account is an object that provides information that defines a user: | ||
- username | ||
- password | ||
- groups the user is a member of | ||
|
||
Managed Service accounts are used to run services on a server for an application. | ||
Services typically run at service startup or are triggered by a specific event. | ||
Services often run in the background and don't require any user interaction. | ||
For a service to start up and authenticate, you use a service account. | ||
A service account might be an account that is local to the computer, such as the built-in Local Service, Network Service, or Local System accounts. | ||
You also can configure a service account to use a domain-based account located in AD DS. | ||
|
||
To help centralize administration and to meet program requirements, many organizations choose to use a domain-based account to run program services. | ||
While this does provide some benefit over using a local account, there are a number of associated challenges, such as the following: | ||
- Extra administration effort might be necessary to manage the service account password securely. | ||
- It can be difficult to determine where a domain-based account is being used as a service account. | ||
- Extra administration effort might be necessary to manage the service principal name (SPN). | ||
|
||
Windows Server supports an AD DS object, named a managed service account, which you use to facilitate service-account management. | ||
A managed service account is an AD DS object class that enables: | ||
- Simplified password management. | ||
- Simplified SPN management. | ||
|
||
Group managed service accounts |