Active Directory Objects Flashcards
DC have 4 main partiitions:
- domain directory - users, groups and network resources fo the domain
- configuration directory - forests, domain and domain trees
- Schema directory - relating to control on objects and attributes that exist in an AD. network resources stored on the AD are known as AD objects and consist of users, groups, computers, security policies, printers, contacts and other network devices.
- Application directory - part of DNS and stores AD integrated zones (not replicated by the global catalog)
user accounts
also known as security principals
3 user accounts are created by default on a new domain
Administrator
Guest
HelpAssistant
InetOrgPerson class
used in LDAP and x.500 directory services to represent users in an organization, users on any platform can obtain directory information from LDAP
cope identifies how the group is applied to domain or forest, there are three groups
domain local - just permissions applied to domain
global - any domain in a forest
universal - can include other groups and accounts from any domain tree or forest.
2 types of groups AD DS - distribution and security.
Distribution lists cannot be added to the DACLs (Discretionary Access Control Lists)
addtl groups can be added by Account Operators, DC Admins, E Admins
Each Computer Account has the following components
SAM (Security Accounts Manager)
DNS Suffix - DNS host name
SPN (Service Principal Name
DNS name is the full name of the computer:
bsalt.internal.mesacounty.us
UPN
User Principal Name
(login name and suffix
linz. th@
mesacounty. us is the UPN suffix
Can import and export into AD DS two ways
LDIFDE -utility allows you to do AD objects along with passwords - files are saved with a .ldf extension
CSVDE - AD objects but not passwords
Admin group to perform this function
AD LDS doesn’t require a DC or DNS server
can be used to sync with directory servers and data management
cmd.exe prompt syntax:
ldifde [-i][-f filename][-s servername][-z]
[-b username domain password][-h]
ldifde Syntax commands
- i = specifies an import function
- v = enables the verbose mode
- u = unicode format
- t = port specifies ldap port. default is 3889 and global default 3268
- j = path of file
- s = server to bind with
- f = filename
- k = ignore errors during the import (constant violation and object already exist errors)
- c = FromDN toDN replaces all occurrences of the DN above, this is used to replace the distinguished name of the export domain with that of the import domain when importing data from one domain to another.
csvde syntax
- f = filename
- j = save a log file during import -j”C:\folder”
- d = RootDN root of the ldap seach for data export
- r = filter creates and ldap search filter for exporting data
- p = Search Scope base, onelevel or subtree
- l = list of attributes (if not specified all attributes are returned)
- o = list attributes to be omitted
- m = omits attributes that apply only to AD Objects
- n = binary values should not be exported
- a = userdistiguishedname password during import user name and password
- b = Username domain password during import username, domain and password
Using OUs
can reduce the number of domains used
Process for creating one includes:
assigning the OU owner
creating account and resource OUs
designing its structure
assigning the OU owner
forest ownder assigns an OU owner in a domain. owners manage data and control a subtree of objects int eh AD DS. it governs functions, (how to delegate admin contorl, apply policies to objects within their OU. can create new subtrees and delegate admin control to them.
creating account and resource OUs
Account OUs include users, groups and all computer objects. REsource are created to provide autonomy to the mgmt of data and computer equipment. Best practice is to create two separate OU structures in the domain
Resource OUs do not contain any default child OUs
designing the OU structure
documenting the structure is important. list of names of the OUs, type, owners and origin.
add an OU using cmd.exe
dsadd
dsadd ou Organizational UnitDN
ie: dsadd ou “OU=Tellers, dc=EasyNOmadTravel, dc=com”
three configurations you can apply to a group
- Modifying group membership
- Changing the group type
- Changing the group scope
dsmod group GroupDN -addmbr MemberDN
use addmbr to add the member to the group from the cmd.exe dsmod command
dsmod group”CN=US INfo, OU=Mangers,DC=EasyNomadTravel,DC=com”
-addmber “CN=Jennifer Westlein, CN=Users,DC=EasyNomadTravel,DC=com” -secgrp no
use secgrp parameter for security group yes or no. Same as above - dsmod gorup GroupDN -secgrp [yes|no]
change scope parameter L, G or U
Domain local, global or universal
dsmod group GroupDN -scope L|G|U
IF you are on a global catalog server, you can only go from a universal to a local scope
group policies can (GPOs)
modify permissions on a file system modify permissions on a registry object change settings in the registry change assignment of user rights configure and audit event logs set account and password policies
applied on three levels
Domain level - specifies common user security requirements, such as account and password policies, which are applied on all the servers present on the domain -user acct and psswd
Baseline Level - specify server security req that are applied to all the servers in a domain structure - user accts account policy- applied to users and computers in a domain
Role specific Level - specify the security req for specific server roles.
gpo default config
password policy
account lockout policy
kerberos policy
password policies contain the following options
1 enforce a password history - 0 and 24 default
2 configure a max password age - 42 days default
3 configure a min password age - 1 day default
4 configure a min password length (7 default)
5 ensure that a password meets complexity req
6 store a password using reversible encryption _passwords can be easily retrieved which is a security consideration
5 kerberos policy settings
Enforce user logon restrictions
max lifetime for service ticket - 600 minutes by default
max lifetime for user ticket -TGT 10 hours by default
max lifetime for user ticket renewal - TGT 7 days default
max tolerance for computer clock synch -5 min default
AD DS in 2008 have two new object classes
Password settings object - PSO has attributes that are used to define all the password settings, except kerberos for the default doamin policy
Password settings container - PSC contains PSOs (password settings objects) for a domain and is an object class created by default under the system container in the domain. You cannot modify and existing PSC but you can create addtl custom PSCs
PSOs have 3 lockout policies:
reset acct lockout counterafter,
account lockout threshold,
account lockout duration
PSO links (2 attributes)
- msDS-PSOAppliesTo Attribute - contains forward link to users or group objects, multivalue attr enables you to apply PSO to multi users or groups. use to apply one password policy to different sets of users or groups.
2 msDS-PSOApplied attribute - backward link to the PSO. added to user and group objects in 2008 to enable them to have multi PSOs applied to them.