To integrate Active Directory with the Web Reports server. In this way you grant access to Web Reports according to the role definition. LDAP integration after. When Active Directory server integration is implemented and Windows integrated. Integrated login, follow the directions for integrating with an LDAP server. Server, users and groups are synchronized automatically at pre-defined intervals.
Contents. Notes SSL Notice that SSL is enabled in all examples. Your LDAP server may or may not require SSL. If you do not require SSL (if you set AD to not require signed communications), you can set that option to 'false'. Be aware that doing so will cause your domain user's passwords to be sent across the network in clear text, which makes your system susceptible to man in the middle attacks, replay attacks, and other nasty attacks. For SSL to work, you must install an SSL certificate on your LDAP server, your wiki's server must trust the LDAP server's CA, and the DNS name of your LDAP server must resolve to the CN field of the certificate issued to your LDAP server. Remember, if your web server does not use SSL (URL does not start with your password will be transmitted in clear text from the client browser to the web server.
This is independent of the SSL settings described below from the web server to the LDAP server. General Configuration Be sure to enable LDAP support within PHP. Make sure that you have installed the necessary packages for your distro. RedHat EL based distro (CentOS 4.3): yum install php-ldap. Make sure that /etc/php.d/ldap.ini contains extension=ldap.so. Ubuntu 12.04 and others: sudo apt-get install php5-ldap or possibly, for older versions eg 6.06.1 (Dapper Drake): sudo apt-get install php-ldap. Other distros: Modify php.ini, and uncomment the line:;extension=phpldap.so change to: extension=phpldap.so.
Windows: Verify if you have configured your PHP folder on your PATH Windows. Modify php.ini, and uncomment the line:;extension=phpldap.dll change to: extension=phpldap.dll Single Domain Requiring Straight Binding Only In this example, we have an Active Directory (AD) server, and we will be doing straight binds to the directory.
This is not how typical LDAP authentication operates as it does not attempt a search first, see. Configuration Our AD servers are 'exampleldapserver.example.com' and 'exampleldapserver2.example.com', and the domainname is 'EXAMPLEDOMAIN'. 'USER-NAME' is not to be changed as this string is replaced in LdapAuthentication.php. (In LocalSettings.php).
Requireonce ( ' $IP /extensions/LdapAuthentication/LdapAuthentication.php' ); $wgAuth = new LdapAuthenticationPlugin ; $wgLDAPDomainNames = array ( 'exampleADDomain' ); $wgLDAPServerNames = array ( 'exampleADDomain' = 'exampleldapserver.example.com exampleldapserver2.example.com' ); $wgLDAPSearchStrings = array ( 'exampleADDomain' = 'EXAMPLEDOMAIN USER-NAME' ); $wgLDAPEncryptionType = array ( 'exampleADDomain' = 'ssl' ); $wgLDAPUseLocal = false; $wgMinimalPasswordLength = 1; Extra configuration for AD to allow for preference pulling, group sync, etc. If you want to be able to pull preferences, and such, you'll need to set a couple other options. These other options will allow the plugin to bind as the user, and then search for the user's DN. Without a DN, any extras provided by the extension will fail. (In LocalSettings.php after your other LDAP configuration). $wgLDAPBaseDNs = array ( 'exampleADDomain' = 'cn=Users,dc=example,dc=com' ); $wgLDAPSearchAttributes = array ( 'exampleADDomain' = 'sAMAccountName' ); Single Domain Requiring Search Before Binding This is typically how LDAP authentication is performed. First, a search is performed for the identifier presented (username) and a DN is returned.
This DN is then used with the password provided to attempt a bind against the LDAP server. This is useful in cases when the username does not match anything in the DN or users are stored in multiple OUs. Configuration In this situation, you could use the 'Single Domain Requiring Straight Binding Only' as AD will search through multiple OUs for you anyway. Using the Straight Binding approach is generally recommended for AD. Our AD servers are 'exampleldapserver.example.com' and 'exampleldapserver2.example.com', and the domain is 'EXAMPLEDOMAIN'.
Our naming attribute for users is 'sAMAccountName', some users are kept in 'ou=accounting,ou=Users,dc=exampledomain,dc=example,dc=com', and other users are kept in 'ou=graphics,ou=Users,dc=exampledomain,dc=example,dc=com'. (In LocalSettings.php). $wgLDAPProxyAgent = array ( 'exampleNonADDomain' = 'cn=proxyagent,ou=Users,dc=exampledomain,dc=example,dc=com' ); $wgLDAPProxyAgentPassword = array ( 'exampleNonADDomain' = 'eX@mP1eP$$wRd' ); Multiple Domains Requiring Simple Binding Only Configuration If you are using multiple domains, this is your most likely scenario. In this example, we have two different domains that are not part of a single-sign-on enviroment. The AD domain is called 'ADDOMAIN', and has servers named 'exampleldapserver.example.com' and 'exampleldapserver2.example.com'.
The non-AD domain is called 'NonADDomain', has servers named 'nonadserver.example.com', 'nonadserver2.example.com', and 'nonadserver3.example.com', and users are stored in 'ou=people,dc=example,dc=com'. In this example, we do not require the ability to change passwords, or create new LDAP users through Mediawiki, just authentication. (In LocalSettings.php).
Active Directory ( AD) is a that developed for the networks. It is included in most as a set of.
Initially, Active Directory was only in charge of centralized domain management. Starting with, however, Active Directory became an umbrella title for a broad range of directory-based identity-related services. A server running Active Directory Domain Services (AD DS) is called a. It and all users and computers in a Windows domain type network—assigning and enforcing security policies for all computers and installing or updating software.
For example, when a user a computer that is part of a Windows domain, Active Directory checks the submitted password and determines whether the user is a or normal user. Also, it allows management and storage of information, provides authentication and authorization mechanisms, and establishes a framework to deploy other related services: Certificate Services, Lightweight Directory Services. Active Directory uses (LDAP) versions 2 and 3, Microsoft's version of,. Contents. History Active Directory, like many information-technology efforts, originated out of a using or RFCs.
The (IETF), which oversees the RFC process, has accepted numerous RFCs initiated by widespread participants. Active Directory incorporates decades of communication technologies into the overarching Active Directory concept then makes improvements upon them. For example, LDAP underpins Active Directory. Also directories and the preceded the Active Directory concept that makes use of those methods. The LDAP concept began to emerge even before the founding of Microsoft in April 1975, with RFCs as early as 1971.
RFCs contributing to LDAP include (on the LDAP API, August 1995),. Microsoft previewed Active Directory in 1999, released it first with Server edition, and revised it to extend functionality and improve administration in.
Additional improvements came with subsequent versions of. In, additional services were added to Active Directory, such as.
The part of the directory in charge of management of domains, which was previously a core part of the operating system, was renamed Active Directory Domain Services (ADDS) and became a server role like others. 'Active Directory' became the umbrella title of a broader range of directory-based services. According to Bryon Hynes, everything related to identity was brought under Active Directory's banner. Active Directory Services Active Directory Services consist of multiple directory services. The best known is Active Directory Domain Services, commonly as AD DS or simply AD.
Domain Services Active Directory Domain Services (AD DS) is the cornerstone of every network. It stores information about members of the domain, including devices and users,. The server running this service is called a. A domain controller is contacted when a user logs into a device, accesses another device across the network, or runs a line-of-business into a device. Other Active Directory services (excluding, as described below) as well as most of Microsoft server technologies rely on or use Domain Services; examples include,. Lightweight Directory Services Active Directory Lightweight Directory Services ( AD LDS), formerly known as Active Directory Application Mode (ADAM), is a light-weight implementation of AD DS.
AD LDS runs as a on. AD LDS shares the code base with AD DS and provides the same functionality, including an identical, but does not require the creation of domains or domain controllers. It provides a Data Store for storage of directory data and a with an LDAP Directory Service Interface. Unlike AD DS, however, multiple AD LDS instances can run on the same server. Certificate Services Active Directory Certificate Services (AD CS) establishes an on-premises. It can create, validate and revoke for internal uses of an organization. These certificates can be used to encrypt files (when used with ), emails (per standard), and network traffic (when used by, protocol or protocol).
AD CS predates Windows Server 2008, but its name was simply Certificate Services. AD CS requires an AD DS infrastructure. Federation Services. Main article: Active Directory Federation Services (AD FS) is a service. With an AD FS infrastructure in place, users may use several web-based services (e.g., ) or network resources using only one set of credentials stored at a central location, as opposed to having to be granted a dedicated set of credentials for each service.
AD FS's purpose is an extension of that of AD DS: The latter enables users to authenticate with and use the devices that are part of the same network, using one set of credentials. The former enables them to use the same set of credentials in a different network. As the name suggests, AD FS works based on the concept of. AD FS requires an AD DS infrastructure, although its federation partner may not. Rights Management Services.
Main article: Active Directory Rights Management Services ( AD RMS, known as Rights Management Services or RMS before ) is a server software for shipped with. It uses encryption and a form of selective functionality denial for limiting access to documents such as corporate, documents, and, and the operations authorized users can perform on them. Logical structure As a directory service, an Active Directory instance consists of a database and corresponding responsible for servicing requests and maintaining the database. The executable part, known as Directory System Agent, is a collection of and that run on Windows 2000 and later. Objects in Active Directory databases can be accessed via LDAP, ADSI (a interface), and services. A simplified example of a publishing company's internal network.
The company has four groups with varying permissions to the three shared folders on the network. Active Directory structures are arrangements of information about. The objects fall into two broad categories: resources (e.g., printers) and (user or computer accounts and groups). Security principals are assigned unique (SIDs). Each object represents a single entity—whether a user, a computer, a printer, or a group—and its attributes. Certain objects can contain other objects. An object is uniquely identified by its name and has a set of attributes—the characteristics and information that the object represents— defined by a, which also determines the kinds of objects that can be stored in Active Directory.
The lets administrators extend or modify the schema when necessary. However, because each schema object is integral to the definition of Active Directory objects, deactivating or changing these objects can fundamentally change or disrupt a deployment. Schema changes automatically propagate throughout the system. Once created, an object can only be deactivated—not deleted. Changing the schema usually requires planning.
Forests, trees and domains The Active Directory framework that holds the objects can be viewed at a number of levels. The forest, tree, and domain are the logical divisions in an Active Directory network. Within a deployment, objects are grouped into domains.
The objects for a single domain are stored in a single database (which can be replicated). Domains are identified by their name structure, the. A domain is defined as a logical group of network objects (computers, users, devices) that share the same Active Directory database. A tree is a collection of one or more domains and domain trees in a contiguous namespace, and is linked in a transitive trust hierarchy. At the top of the structure is the forest.
A forest is a collection of trees that share a common global catalog, directory schema, logical structure, and directory configuration. The forest represents the security boundary within which users, computers, groups, and other objects are accessible. Domain-Boston Domain-New York Domain-Philly Tree-Southern Domain-Atlanta Domain-Dallas Domain-Dallas OU-Marketing Hewitt Aon Steve OU-Sales Bill Ralph Example of the geographical organizing of zones of interest within trees and domains.
Organizational units The objects held within a domain can be grouped into (OUs). OUs can provide hierarchy to a domain, ease its administration, and can resemble the organization's structure in managerial or geographical terms. OUs can contain other OUs—domains are containers in this sense.
Microsoft recommends using OUs rather than domains for structure and to simplify the implementation of policies and administration. The OU is the recommended level at which to apply, which are Active Directory objects formally named Group Policy Objects (GPOs), although policies can also be applied to domains or sites (see below). The OU is the level at which administrative powers are commonly delegated, but delegation can be performed on individual objects or attributes as well. Organizational units do not each have a separate namespace; e.g. User accounts with an identical username (sAMAccountName) in separate OUs within a domain are not allowed, such as 'fred.staff-ou.domain' and 'fred.student-ou.domain', where 'staff-ou' and 'student-ou' are the OUs. This is because sAMAccountName, a user object attribute, must be unique within the domain.
However, two users in different OUs can have the same Common Name (CN), the name under which they are stored in the directory itself. In general the reason for this lack of allowance for duplicate names through hierarchical directory placement, is that Microsoft primarily relies on the principles of, which is a flat-file method of network object management that for Microsoft software, goes all the way back to. Allowing for duplication of object names in the directory, or completely removing the use of NetBIOS names, would prevent backward compatibility with legacy software and equipment. However, disallowing duplicate object names in this way is a violation of the LDAP RFCs on which Active Directory is supposedly based. As the number of users in a domain increases, conventions such as 'first initial, middle initial, last name' or the reverse (Eastern order) fail for common like Li (李), Smith or Garcia. Workarounds include adding a digit to the end of the username. Alternatives include creating a separate ID system of unique employee/student id numbers to use as account names in place of actual user's names, and allowing users to nominate their preferred word sequence within an.
Because duplicate usernames cannot exist within a domain, account name generation poses a significant challenge for large organizations that cannot be easily subdivided into separate domains, such as students in a public school system or university who must be able to use any computer across the network. Shadow groups. In Active Directory, organizational units (OUs) cannot be assigned as owners or trustees. Only groups are selectable, and members of OUs cannot be collectively assigned rights to directory objects. In Microsoft's Active Directory, OUs do not confer access permissions, and objects placed within OUs are not automatically assigned access privileges based on their containing OU. This is a design limitation specific to Active Directory. Other competing directories such as Novell are able to assign access privileges through object placement within an OU.
Active Directory requires a separate step for an administrator to assign an object in an OU as a member of a group also within that OU. Relying on OU location alone to determine access permissions is unreliable, because the object may not have been assigned to the group object for that OU. A common workaround for an Active Directory administrator is to write a custom or script to automatically create and maintain a user group for each OU in their directory. The scripts are run periodically to update the group to match the OU's account membership, but are unable to instantly update the security groups anytime the directory changes, as occurs in competing directories where security is directly implemented into the directory itself. Such groups are known as Shadow Groups. Once created, these shadow groups are selectable in place of the OU in the administrative tools.
Microsoft refers to shadow groups in the Server 2008 Reference documentation, but does not explain how to create them. There are no built-in server methods or console snap-ins for managing shadow groups. The division of an organization's information infrastructure into a hierarchy of one or more domains and top-level OUs is a key decision.
Common models are by business unit, by geographical location, by IT Service, or by object type and hybrids of these. OUs should be structured primarily to facilitate administrative delegation, and secondarily, to facilitate group policy application. Although OUs form an administrative boundary, the only true security boundary is the forest itself and an administrator of any domain in the forest must be trusted across all domains in the forest.
Partitions The Active Directory database is organized in partitions, each holding specific object types and following a specific replication pattern. Microsoft often refers to these partitions as 'naming contexts'. The 'Schema' partition contains the definition of object classes and attributes within the Forest. The 'Configuration' partition contains information on the physical structure and configuration of the forest (such as the site topology). Both replicate to all domains in the Forest. The 'Domain' partition holds all objects created in that domain and replicates only within its domain. Physical structure Sites are physical (rather than logical) groupings defined by one or more subnets.
AD also holds the definitions of connections, distinguishing low-speed (e.g., ) from high-speed (e.g., ) links. Site definitions are independent of the domain and OU structure and are common across the forest. Sites are used to control network traffic generated by replication and also to refer clients to the nearest (DCs). Uses the site topology for mail routing. Policies can also be defined at the site level.
Physically, the Active Directory information is held on one or more peer, replacing the / model. Each DC has a copy of the Active Directory. Servers joined to Active Directory that are not domain controllers are called Member Servers. A subset of objects in the domain partition replicate to domain controllers that are configured as global catalogs. Global catalog (GC) servers provide a global listing of all objects in the Forest. Global Catalog servers replicate to themselves all objects from all domains and hence, provide a global listing of objects in the forest. However, to minimize replication traffic and keep the GC's database small, only selected attributes of each object are replicated.
This is called the partial attribute set (PAS). The PAS can be modified by modifying the schema and marking attributes for replication to the GC.
Earlier versions of Windows used to communicate. Active Directory is fully integrated with DNS and requires —DNS. To be fully functional, the DNS server must support, also known as service records. Replication Active Directory synchronizes changes using. Replication by default is 'pull' rather than 'push', meaning that replicas pull changes from the server where the change was effected.
The Knowledge Consistency Checker (KCC) creates a replication topology of site links using the defined sites to manage traffic. Intrasite replication is frequent and automatic as a result of change notification, which triggers peers to begin a pull replication cycle. Intersite replication intervals are typically less frequent and do not use change notification by default, although this is configurable and can be made identical to intrasite replication. Each link can have a 'cost' (e.g., etc.) and the KCC alters the site link topology accordingly. Replication may occur transitively through several site links on same-protocol site link bridges, if the cost is low, although KCC automatically costs a direct site-to-site link lower than transitive connections. Site-to-site replication can be configured to occur between a bridgehead server in each site, which then replicates the changes to other DCs within the site.
Replication for Active Directory zones is automatically configured when DNS is activated in the domain based by site. Replication of Active Directory uses (RPC) over IP (RPC/IP).
Between Sites can be used for replication, but only for changes in the Schema, Configuration, or Partial Attribute Set (Global Catalog) GCs. SMTP cannot be used for replicating the default Domain partition. Implementation In general, a network utilizing Active Directory has more than one licensed Windows server computer. Backup and restore of Active Directory is possible for a network with a single domain controller, but Microsoft recommends more than one domain controller to provide automatic protection of the directory. Domain controllers are also ideally single-purpose for directory operations only, and should not run any other software or role. Certain Microsoft products such as SQL Server and Exchange can interfere with the operation of a domain controller, necessitating isolation of these products on additional Windows servers. Combining them can make configuration or troubleshooting of either the domain controller or the other installed software more difficult.
A business intending to implement Active Directory is therefore recommended to purchase a number of Windows server licenses, to provide for at least two separate domain controllers, and optionally, additional domain controllers for performance or redundancy, a separate file server, a separate Exchange server, a separate SQL Server, and so forth to support the various server roles. Physical hardware costs for the many separate servers can be reduced through the use of, although for proper failover protection, Microsoft recommends not running multiple virtualized domain controllers on the same physical hardware. Database The Active-Directory, the directory store, in Windows 2000 Server uses the -based (ESE98) and is limited to 16 terabytes and 2 billion objects (but only 1 billion security principals) in each domain controller's database. Microsoft has created NTDS databases with more than 2 billion objects.
(NT4's could support no more than 40,000 objects). Called NTDS.DIT, it has two main tables: the data table and the link table. Windows Server 2003 added a third main table for single instancing. Programs may access the features of Active Directory via the provided by Active Directory Service Interfaces.
Single server operations (FSMO, pronounced 'fizz-mo') operations are also known as operations master roles. Although domain controllers allow simultaneous updates in multiple places, certain operations are supported only on a single server. These operations are performed using the roles listed below: Role name Scope Description Schema Master 1 per forest Schema modifications Domain Naming Master 1 per forest Addition and removal of domains if present in root domain PDC Emulator 1 per domain Provides backwards compatibility for NT4 clients for PDC operations (like password changes). The PDC runs domain specific processes such as the Security Descriptor Propagator (SDP), and is the master time server within the domain. It also handles external trusts, the DFS consistency check, holds current passwords and manages all GPOs as default server.
RID Master 1 per domain Allocates pools of unique identifiers to domain controllers for use when creating objects Infrastructure Master 1 per domain/partition Synchronizes cross-domain group membership changes. The infrastructure master should not be run on a global catalog server (GCS) unless all DCs are also GCs, or the environment consists of a single domain. The Infrastructure Master role as described above is only for the domain partition (default naming context), netdom query fsmo and ntdsutil will only query the domain partition. However, every application partition, including Forest and Domain-level DNS domain zones has its own Infrastructure Master. The holder of this role is stored in the fSMORoleOwner attribute of the Infrastructure object in the root of the partition, it can be modified with ADSIEdit, for example one can modify the fSMORoleOwner attribute of the CN=Infrastructure,DC=DomainDnsZones,DC=yourdomain,DC=tld object to CN=NTDSSettings,CN=NameofDC,CN=Servers,CN=DRSite,CN=Sites,CN=Configuration,DC=Yourdomain,DC=TLD.
Trusting To allow users in one domain to access resources in another, Active Directory uses trusts. Trusts inside a forest are automatically created when domains are created. The forest sets the default boundaries of trust, and implicit, transitive trust is automatic for all domains within a forest. Terminology One-way trust One domain allows access to users on another domain, but the other domain does not allow access to users on the first domain.
Two-way trust Two domains allow access to users on both domains. Trusted domain The domain that is trusted; whose users have access to the trusting domain. Transitive trust A trust that can extend beyond two domains to other trusted domains in the forest. Intransitive trust A one way trust that does not extend beyond two domains. Explicit trust A trust that an admin creates.
It is not transitive and is one way only. Cross-link trust An explicit trust between domains in different trees or in the same tree when a descendant/ancestor (child/parent) relationship does not exist between the two domains. Shortcut Joins two domains in different trees, transitive, one- or two-way.
Forest trust Applies to the entire forest. Transitive, one- or two-way. Realm Can be transitive or nontransitive (intransitive), one- or two-way. External Connect to other forests or non-AD domains. Nontransitive, one- or two-way. PAM trust A one-way trust used by from a (possibly low-level) production forest to a ( functionality level) 'bastion' forest, which issues time-limited group memberships.
Forest trusts Windows Server 2003 introduced the forest root trust. This trust can be used to connect Windows Server 2003 forests if they are operating at the 2003 forest functional level. Authentication across this type of trust is -based (as opposed to ).
Forest trusts are transitive for all the domains the trusted forests. However, forest trusts are not transitive between forests.
Example: Suppose that a two-way transitive forest trust exists between the forest root domains in Forest A and Forest B, and another two-way transitive forest trust exists between the forest root domains in Forest B and Forest C. Such a configuration lets users in Forest B access resources in any domain in either Forest A or Forest C, and users in Forest A or C can access resources in any domain in Forest B. However, it does not let users in Forest A access resources in Forest C, or vice versa. To let users in Forest A and Forest C share resources, a two-way transitive trust must exist between both forests. Management solutions Microsoft Active Directory management tools include:. Active Directory Users and Computers,. Active Directory Domains and Trusts,.
Active Directory Sites and Services,. ADSI Edit,. Local Users and Groups,.
Active Directory Schema snap-ins for (MMC), These management tools may not provide enough functionality for efficient workflow in large environments. Some third-party solutions extend the administration and management capabilities. They provide essential features for a more convenient administration processes, such as automation, reports, integration with other services, etc. Unix integration Varying levels of interoperability with Active Directory can be achieved on most operating systems (including, or Java and Unix-based programs) through standards-compliant LDAP clients, but these systems usually do not interpret many attributes associated with Windows components, such as and support for one-way trusts. Third parties offer Active Directory integration for Unix-like platforms, including:. PowerBroker Identity Services, formerly Likewise (, formerly Likewise Software) – Allows a non-Windows client to join Active Directory.
ADmitMac (Thursby Software Systems). – Can act as a domain controller The schema additions shipped with include attributes that map closely enough to to be generally usable. The reference implementation of, nssldap and pamldap provided by PADL.com, support these attributes directly. The default schema for group membership complies with RFC 2307bis (proposed). Windows Server 2003 R2 includes a snap-in that creates and edits the attributes. An alternative option is to use another directory service as non-Windows clients authenticate to this while Windows Clients authenticate to AD. Non-Windows clients include (formerly Fedora Directory Server, FDS), ViewDS Identity Solutions - ViewDS v7.2 and Sun Microsystems.
The latter two both being able to perform two-way synchronization with AD and thus provide a 'deflected' integration. Another option is to use with its translucent overlay, which can extend entries in any remote LDAP server with additional attributes stored in a local database.
Clients pointed at the local database see entries containing both the remote and local attributes, while the remote database remains completely untouched. Administration (querying, modifying, and monitoring) of Active Directory can be achieved via many scripting languages, including,. Free and non-free AD administration tools can help to simplify and possibly automate AD management tasks.
Also since October 2017 Amazon offers integration with Microsoft Active Directory. See also. (implementing using nested groups). References. Retrieved 23 April 2014. 'Chapter 13'.
Microsoft Windows Internals: Microsoft Windows Server 2003, Windows XP, and Windows 2000 (4th ed.). Redmond, Washington:. ^ Hynes, Byron (November 2006). Active Directory Collection. 13 March 2003. Retrieved 25 December 2010.
Retrieved 2016-09-22. Retrieved 2013-11-26. Retrieved 2013-11-26. Retrieved 2013-11-26. Retrieved 2013-11-26. ^ Thomas, Guy.
Computer Performance Ltd. Windows Server 2012 R2 and Windows Server 2012 Tech Center. Retrieved 28 April 2009. Retrieved 25 February 2013.
Zacker, Craig (2003). '11: Creating and Managing Digital Certificates'. In Harding, Kathy; Jean, Trenary; Linda, Zacker. Planning and Maintaining a Microsoft Windows server 2003 Network Infrastructure. Redmond, WA: Microsoft Press. Retrieved 24 November 2015.
Retrieved 24 November 2015. Windows Server 2003: Active Directory Infrastructure. Microsoft Press. Distributed Systems Resource Kit.
An organizational unit in Active Directory is analogous to a directory in the file system. 4 January 2012. Retrieved 18 September 2013. Examples of how multiple AD objects can be created with the same sAMAccountName. Microsoft Server 2008 Reference, discussing shadow groups used for fine-grained password policies:. Microsoft Corporation.
23 January 2005. However, service administrators have abilities that cross domain boundaries. For this reason, the forest is the ultimate security boundary, not the domain. Andreas Luther.
Microsoft Corporation. Retrieved 26 May 2010.
The Active Directory is made up of one or more naming contexts or partitions. Microsoft Corporation. 21 January 2005.
A site is a set of well-connected subnets. Microsoft Corporation. 21 January 2005. member servers,. belong to a domain but do not contain a copy of the Active Directory data.
Microsoft Corporation. 10 December 2009. a domain controller can locate only the objects in its domain. The global catalog provides the ability to locate objects from any domain.
Microsoft Corporation. Microsoft Corporation. 26 August 2010.
The isMemberOfPartialAttributeSet attribute of an attributeSchema object is set to TRUE if the attribute is replicated to the global catalog. When deciding whether or not to place an attribute in the global catalog remember that you are trading increased replication and increased disk storage on global catalog servers for, potentially, faster query performance. Microsoft Corporation. 21 January 2005. Active Directory uses four distinct directory partition types to store.
data. Directory partitions contain domain, configuration, schema, and application data.
Microsoft Corporation. 28 March 2003.
Domain controllers request (pull) changes rather than send (push) changes that might not be needed. Microsoft Corporation. 28 March 2003. SMTP can be used to transport nondomain replication.
Retrieved 5 February 2014. Retrieved 5 February 2014. Posey, Brien (23 August 2010). Retrieved 5 February 2014. Whenever possible, your domain controllers should run on dedicated servers (physical or virtual). 7 January 2013.
Retrieved 5 February 2014. Degremont, Michel (30 Jun 2011). Microsoft SQL Server blog.
Retrieved 5 February 2014. For security and performance reasons, we recommend that you do not install a standalone SQL Server on a domain controller. 22 March 2013. Retrieved 5 February 2014. Retrieved 5 February 2014.
After SQL Server is installed on a computer, you cannot change the computer from a domain controller to a domain member. You must uninstall SQL Server before you change the host computer to a domain member. Retrieved 5 February 2014. Running SQL Server on the same computer as a production Exchange mailbox server is not recommended. Planning to Virtualize Domain Controllers. Retrieved 5 February 2014. You should attempt to avoid creating potential single points of failure when you plan your virtual domain controller deployment.frank.
^ efleis (8 June 2006). Retrieved 20 November 2011. Berkouwer, Sander., Microsoft. Microsoft Corporation. 28 March 2003. Trusts enable.
authentication and. sharing resources across domains or forests. Microsoft Corporation.
11 December 2012. Retrieved 29 January 2013. Defines several kinds of trusts. (automatic, shortcut, forest, realm, external). ^ Edge, Charles S., Jr; Smith, Zack; Hunter, Beau (2009).
'Chapter 3: Active Directory'. Enterprise Mac Administrator's Guide.
New York City:. SAMBA Project.
From the original on 15 November 2010. Retrieved 9 August 2016. SAMBA Project. 5 October 2009. Archived from on 13 October 2009. Retrieved 2 November 2009.
Archived from on 27 September 2011. Retrieved 20 November 2011. Retrieved 7 June 2011. Retrieved 22 May 2012. Retrieved 22 May 2012. Perl Open-Source Community. Retrieved 22 May 2012.
External links Wikiversity has learning resources about. Microsoft Technet: White paper: (Single technical document that gives an overview about Active Directory.). Microsoft Technet: Detailed description of. Microsoft MSDN Library: (part of the ). Microsoft MSDN:. Microsoft TechNet:. Microsoft MSDN:.
Microsoft TechNet:. Microsoft TechNet Magazine:.
Microsoft MSDN:. Microsoft TechNet.