 |
|
|
Active Directory | A Wisdom Archive on Active Directory | | Active Directory A selection of articles related to Active Directory | |
| |
Active Directory, Active Directory - Naming, Active Directory - Notes, Active Directory - Structure, Active Directory - Trust, Active Directory - Forests, Trees and Domains, Active Directory - Objects, Active Directory - Physical structure and Replication, Active Directory - Trusts in Windows 2000 native mode, Active Directory Service Interfaces, Windows Open System Architecture, Directory Enabled Networks, Microsoft Directory Synchronization Services, Group Policy
| | | Page 1 Page 2 » Page 3 « More » | |
| |
| ARTICLES RELATED TO Active Directory | | | |  Active Directory: Encyclopedia II - Lightweight Directory Access Protocol - TerminologyBeware: The LDAP terminology one can encounter is quite a mess. Some of this is due to misunderstandings, other examples are due to its historical origins, others arise when used with non-X.500 services that use different terminology.
For example, "LDAP" is sometimes used to refer to the protocol, other times to the protocol and the data. An "LDAP directory" may be the data or also the access point. An "attribute" may be the attribute type, or the contents of an attribute in a directory, or an attribute description (an attribute type ...
See also:Lightweight Directory Access Protocol, Lightweight Directory Access Protocol - Origin and influences, Lightweight Directory Access Protocol - Protocol overview, Lightweight Directory Access Protocol - Directory structure, Lightweight Directory Access Protocol - Operations, Lightweight Directory Access Protocol - Search and Compare, Lightweight Directory Access Protocol - Bind authenticate, Lightweight Directory Access Protocol - Update operations, Lightweight Directory Access Protocol - Start TLS, Lightweight Directory Access Protocol - Abandon, Lightweight Directory Access Protocol - Unbind, Lightweight Directory Access Protocol - Extended Operation, Lightweight Directory Access Protocol - LDAP URLs, Lightweight Directory Access Protocol - Schema, Lightweight Directory Access Protocol - Variations, Lightweight Directory Access Protocol - Other data models, Lightweight Directory Access Protocol - Terminology, Lightweight Directory Access Protocol - Supporting vendors, Lightweight Directory Access Protocol - RFCs, Lightweight Directory Access Protocol - LDAP fora, Lightweight Directory Access Protocol - LDAP implementations Read more here: » Lightweight Directory Access Protocol: Encyclopedia II - Lightweight Directory Access Protocol - Terminology |
| |
| | | | | Active Directory: Encyclopedia II - DNS zone transfer - Limitations Whilst it is standardized, full zone transfer being described as one of the possible database replication mechanisms in RFC 1034 (with incremental zone transfer described in RFC 1995), zone transfer is the most limited of those database replication mechanisms. This is largely due to a mismatch of database schemata. Zone transfer operates in terms of "wire format" resource records, i.e. resource records as they are transferred using the DNS protocol via TCP and UDP. However, the schema of wire format resource records rarely matches the databa ...
See also:DNS zone transfer, DNS zone transfer - Operation, DNS zone transfer - Limitations, DNS zone transfer - Operational problems, DNS zone transfer - Serial number changes, DNS zone transfer - Serial number comparisons, DNS zone transfer - Multiple resource records, DNS zone transfer - Security, DNS zone transfer - Security through obscurity, DNS zone transfer - Denial of front-end service, DNS zone transfer - Denial of back-end service Read more here: » DNS zone transfer: Encyclopedia II - DNS zone transfer - Limitations |
| |
| | | | | Active Directory: Encyclopedia II - Lightweight Directory Access Protocol - Schema The contents of the entries in a subtree is governed by a schema.
The schema defines the attribute types that directory entries can contain.
An attribute definition includes a syntax, and most non-binary values in LDAPv3 use UTF-8 string syntax. For example, a "mail" attribute might contain the value "user@example.com". A "jpegPhoto" attribute would contain photograph(s) in binary JPEG/JFIF format. A "member" attribute contains the DNs of other directory entries.
Attribute definitions also include whether the ...
See also:Lightweight Directory Access Protocol, Lightweight Directory Access Protocol - Origin and influences, Lightweight Directory Access Protocol - Protocol overview, Lightweight Directory Access Protocol - Directory structure, Lightweight Directory Access Protocol - Operations, Lightweight Directory Access Protocol - Search and Compare, Lightweight Directory Access Protocol - Bind authenticate, Lightweight Directory Access Protocol - Update operations, Lightweight Directory Access Protocol - Start TLS, Lightweight Directory Access Protocol - Abandon, Lightweight Directory Access Protocol - Unbind, Lightweight Directory Access Protocol - Extended Operation, Lightweight Directory Access Protocol - LDAP URLs, Lightweight Directory Access Protocol - Schema, Lightweight Directory Access Protocol - Variations, Lightweight Directory Access Protocol - Other data models, Lightweight Directory Access Protocol - Terminology, Lightweight Directory Access Protocol - Supporting vendors, Lightweight Directory Access Protocol - RFCs, Lightweight Directory Access Protocol - LDAP fora, Lightweight Directory Access Protocol - LDAP implementations Read more here: » Lightweight Directory Access Protocol: Encyclopedia II - Lightweight Directory Access Protocol - Schema |
| |
| | | | | Active Directory: Encyclopedia II - Lightweight Directory Access Protocol - LDAP URLs An LDAP URL format exists which clients support in varying degree, and which servers return in referrals and continuation references:
"ldap://host:port/DN?attributes?scope?filter?extensions"
where most components after "ldap://" can be omitted.
scope can be "base" (the default), "one" or "sub".
attributes is a comma-separated list of attributes to retrieve.
extensions are extensions to the LDAP URL format.
As in other URLs, special characters must be escaped with %hex format.
The ...
See also:Lightweight Directory Access Protocol, Lightweight Directory Access Protocol - Origin and influences, Lightweight Directory Access Protocol - Protocol overview, Lightweight Directory Access Protocol - Directory structure, Lightweight Directory Access Protocol - Operations, Lightweight Directory Access Protocol - Search and Compare, Lightweight Directory Access Protocol - Bind authenticate, Lightweight Directory Access Protocol - Update operations, Lightweight Directory Access Protocol - Start TLS, Lightweight Directory Access Protocol - Abandon, Lightweight Directory Access Protocol - Unbind, Lightweight Directory Access Protocol - Extended Operation, Lightweight Directory Access Protocol - LDAP URLs, Lightweight Directory Access Protocol - Schema, Lightweight Directory Access Protocol - Variations, Lightweight Directory Access Protocol - Other data models, Lightweight Directory Access Protocol - Terminology, Lightweight Directory Access Protocol - Supporting vendors, Lightweight Directory Access Protocol - RFCs, Lightweight Directory Access Protocol - LDAP fora, Lightweight Directory Access Protocol - LDAP implementations Read more here: » Lightweight Directory Access Protocol: Encyclopedia II - Lightweight Directory Access Protocol - LDAP URLs |
| |
| | | | | | Active Directory: Encyclopedia II - Lightweight Directory Access Protocol - Origin and influences LDAP started out as an alternative access protocol to the more cumbersome Directory Access Protocol (DAP) for accessing X.500 directories.
The protocol was originally created by Tim Howes of the University of Michigan, Steve Kille of ISODE and Wengyik Yeong of Performance Systems International. Further development has been done via the Internet Engineering Task Force (IETF).
LDAP has influenced subsequent Internet protocols, including later versions of X.500, Directory Services Markup Language (DSML), ...
See also:Lightweight Directory Access Protocol, Lightweight Directory Access Protocol - Origin and influences, Lightweight Directory Access Protocol - Protocol overview, Lightweight Directory Access Protocol - Directory structure, Lightweight Directory Access Protocol - Operations, Lightweight Directory Access Protocol - Search and Compare, Lightweight Directory Access Protocol - Bind authenticate, Lightweight Directory Access Protocol - Update operations, Lightweight Directory Access Protocol - Start TLS, Lightweight Directory Access Protocol - Abandon, Lightweight Directory Access Protocol - Unbind, Lightweight Directory Access Protocol - Extended Operation, Lightweight Directory Access Protocol - LDAP URLs, Lightweight Directory Access Protocol - Schema, Lightweight Directory Access Protocol - Variations, Lightweight Directory Access Protocol - Other data models, Lightweight Directory Access Protocol - Terminology, Lightweight Directory Access Protocol - Supporting vendors, Lightweight Directory Access Protocol - RFCs, Lightweight Directory Access Protocol - LDAP fora, Lightweight Directory Access Protocol - LDAP implementations Read more here: » Lightweight Directory Access Protocol: Encyclopedia II - Lightweight Directory Access Protocol - Origin and influences |
| |
| | | | | Active Directory: Encyclopedia II - Lightweight Directory Access Protocol - Protocol overview A client starts an LDAP session by connecting to an LDAP server, by default on port 389. It then sends operation requests to the server, which sends responses in return. With some exceptions the client need not wait for a response before sending the next request, and the server may then send the responses in any order.
The basic operations are:
Bind - authenticate, and specify LDAP protocol version,
Search - search for and/or retrieve directory entries,
Compare - test if a named entry contains a given at ...
See also:Lightweight Directory Access Protocol, Lightweight Directory Access Protocol - Origin and influences, Lightweight Directory Access Protocol - Protocol overview, Lightweight Directory Access Protocol - Directory structure, Lightweight Directory Access Protocol - Operations, Lightweight Directory Access Protocol - Search and Compare, Lightweight Directory Access Protocol - Bind authenticate, Lightweight Directory Access Protocol - Update operations, Lightweight Directory Access Protocol - Start TLS, Lightweight Directory Access Protocol - Abandon, Lightweight Directory Access Protocol - Unbind, Lightweight Directory Access Protocol - Extended Operation, Lightweight Directory Access Protocol - LDAP URLs, Lightweight Directory Access Protocol - Schema, Lightweight Directory Access Protocol - Variations, Lightweight Directory Access Protocol - Other data models, Lightweight Directory Access Protocol - Terminology, Lightweight Directory Access Protocol - Supporting vendors, Lightweight Directory Access Protocol - RFCs, Lightweight Directory Access Protocol - LDAP fora, Lightweight Directory Access Protocol - LDAP implementations Read more here: » Lightweight Directory Access Protocol: Encyclopedia II - Lightweight Directory Access Protocol - Protocol overview |
| |
| | | | | Active Directory: Encyclopedia II - Lightweight Directory Access Protocol - Directory structure The protocol accesses LDAP directories, which follow the X.500 model:
A directory is a tree of directory entries.
An entry consists of a set of attributes.
An attribute has a name (an attribute type or attribute description) and one or more values.
The attributes are defined in a schema (see below).
Each entry has an unambiguous name: its Distinguished Name (DN). This consists of its Relative Distinguished Name (RDN) constructed from some attribute(s) in the entry, followed by the parent entry's DN. Think ...
See also:Lightweight Directory Access Protocol, Lightweight Directory Access Protocol - Origin and influences, Lightweight Directory Access Protocol - Protocol overview, Lightweight Directory Access Protocol - Directory structure, Lightweight Directory Access Protocol - Operations, Lightweight Directory Access Protocol - Search and Compare, Lightweight Directory Access Protocol - Bind authenticate, Lightweight Directory Access Protocol - Update operations, Lightweight Directory Access Protocol - Start TLS, Lightweight Directory Access Protocol - Abandon, Lightweight Directory Access Protocol - Unbind, Lightweight Directory Access Protocol - Extended Operation, Lightweight Directory Access Protocol - LDAP URLs, Lightweight Directory Access Protocol - Schema, Lightweight Directory Access Protocol - Variations, Lightweight Directory Access Protocol - Other data models, Lightweight Directory Access Protocol - Terminology, Lightweight Directory Access Protocol - Supporting vendors, Lightweight Directory Access Protocol - RFCs, Lightweight Directory Access Protocol - LDAP fora, Lightweight Directory Access Protocol - LDAP implementations Read more here: » Lightweight Directory Access Protocol: Encyclopedia II - Lightweight Directory Access Protocol - Directory structure |
| |
| | | | | Active Directory: Encyclopedia II - Lightweight Directory Access Protocol - RFCs LDAP is defined by a series of Request for Comments documents:
RFC 2251 - LDAPv3: The specification of the LDAP on-the-wire protocol
RFC 2252 - LDAPv3: Attribute Syntax Definitions
RFC 2253 - LDAPv3: UTF-8 String Representation of Distinguished Names
RFC 2254 - LDAPv3: The String Representation of LDAP Search Filters
RFC 2255 - LDAPv3: The LDAP URL Format
RFC 2256 - LDAPv3: A Summary of the X.500(96) User Schema for use with LDAPv3
RFC 2829 - LDAPv3: Authentication Methods for LDAP
RFC 2830 - LDAPv3: Extension for Transport Layer Secur ...
See also:Lightweight Directory Access Protocol, Lightweight Directory Access Protocol - Origin and influences, Lightweight Directory Access Protocol - Protocol overview, Lightweight Directory Access Protocol - Directory structure, Lightweight Directory Access Protocol - Operations, Lightweight Directory Access Protocol - Search and Compare, Lightweight Directory Access Protocol - Bind authenticate, Lightweight Directory Access Protocol - Update operations, Lightweight Directory Access Protocol - Start TLS, Lightweight Directory Access Protocol - Abandon, Lightweight Directory Access Protocol - Unbind, Lightweight Directory Access Protocol - Extended Operation, Lightweight Directory Access Protocol - LDAP URLs, Lightweight Directory Access Protocol - Schema, Lightweight Directory Access Protocol - Variations, Lightweight Directory Access Protocol - Other data models, Lightweight Directory Access Protocol - Terminology, Lightweight Directory Access Protocol - Supporting vendors, Lightweight Directory Access Protocol - RFCs, Lightweight Directory Access Protocol - LDAP fora, Lightweight Directory Access Protocol - LDAP implementations Read more here: » Lightweight Directory Access Protocol: Encyclopedia II - Lightweight Directory Access Protocol - RFCs |
| |
| | | | | Active Directory: Encyclopedia II - Lightweight Directory Access Protocol - Supporting vendors LDAP has gained wide support from vendors such as:
Apache (through Apache Directory Server)
Apple (through Open Directory/OpenLDAP)
AT&T
Banyan
eB2Bcom (through View500)
Fedora Directory Server
Hewlett-Packard
Identyx
IBM/Lotus
ISODE (through M-Vault server)
Microsoft (through Active Directory)
Netscape (now in Sun Microsystems and Red Hat products)
Novell (through eDirectory)
OctetString (through VDE server)< ...
See also:Lightweight Directory Access Protocol, Lightweight Directory Access Protocol - Origin and influences, Lightweight Directory Access Protocol - Protocol overview, Lightweight Directory Access Protocol - Directory structure, Lightweight Directory Access Protocol - Operations, Lightweight Directory Access Protocol - Search and Compare, Lightweight Directory Access Protocol - Bind authenticate, Lightweight Directory Access Protocol - Update operations, Lightweight Directory Access Protocol - Start TLS, Lightweight Directory Access Protocol - Abandon, Lightweight Directory Access Protocol - Unbind, Lightweight Directory Access Protocol - Extended Operation, Lightweight Directory Access Protocol - LDAP URLs, Lightweight Directory Access Protocol - Schema, Lightweight Directory Access Protocol - Variations, Lightweight Directory Access Protocol - Other data models, Lightweight Directory Access Protocol - Terminology, Lightweight Directory Access Protocol - Supporting vendors, Lightweight Directory Access Protocol - RFCs, Lightweight Directory Access Protocol - LDAP fora, Lightweight Directory Access Protocol - LDAP implementations Read more here: » Lightweight Directory Access Protocol: Encyclopedia II - Lightweight Directory Access Protocol - Supporting vendors |
| |
| | | | | Active Directory: Encyclopedia II - Microsoft Exchange Server - History Exchange 4.0 formed the initial foundation for Microsoft's Active Directory service, an LDAP-compliant directory server. Active Directory was introduced in 1999 with the release of Windows 2000 [1].
Exchange 5.5 comes in two editions, Standard ("5.5/S") and Enterprise ("5.5/E"). They differ in database store size, "connectors," and clustering capabilities. The Standard edition has a database size limitation of 16GB, the Enterprise edition has a limit of 16TB - effectively unlimited for all practical purposes. The Standard edition come ...
See also:Microsoft Exchange Server, Microsoft Exchange Server - History, Microsoft Exchange Server - Version history, Microsoft Exchange Server - Current version, Microsoft Exchange Server - Future, Microsoft Exchange Server - Licensing Read more here: » Microsoft Exchange Server: Encyclopedia II - Microsoft Exchange Server - History |
| |
| | | | | Active Directory: Encyclopedia II - AppleTalk - Addressing An AppleTalk address was a 4-byte quantity. This consisted of a two-byte network number, a one-byte node number, and a one-byte socket number. Of these, only the network number required any configuration, being obtained from a router. Each node dynamically chose its own node number, according to a protocol which handled contention between different nodes accidentally choosing the same number. For socket numbers, a few well-known numbers were reserved for special purposes specific to the AppleTalk protocol itself. Apart from these, all application-level protocols were expected to use dynamically-assigned socket nu ...
See also:AppleTalk, AppleTalk - Design, AppleTalk - Addressing, AppleTalk - Protocols, AppleTalk - AppleTalk Address Resolution Protocol, AppleTalk - AppleTalk Data Stream Protocol, AppleTalk - Apple Filing Protocol, AppleTalk - AppleTalk Session Protocol, AppleTalk - AppleTalk Transaction Protocol, AppleTalk - Datagram Delivery Protocol, AppleTalk - Name Binding Protocol, AppleTalk - Printer Access Protocol, AppleTalk - Routing Table Maintenance Protocol, AppleTalk - Zone Information Protocol, AppleTalk - Physical Implementation, AppleTalk - Networking Model, AppleTalk - Cross Platform Solutions Read more here: » AppleTalk: Encyclopedia II - AppleTalk - Addressing |
| |
| | | | | Active Directory: Encyclopedia II - AppleTalk - Physical Implementation The initial default hardware implementation for AppleTalk was a high-speed serial protocol known as LocalTalk that used the Macintosh's built-in RS-422 ports at 230.4 kbit/s. LocalTalk used a splitter box in the RS-422 port to provide an upstream and downstream cable from a single port. The system was slow by today's standards, but at the time the additional cost and complexity of networking on PC machines was such that it was common that ...
See also:AppleTalk, AppleTalk - Design, AppleTalk - Addressing, AppleTalk - Protocols, AppleTalk - AppleTalk Address Resolution Protocol, AppleTalk - AppleTalk Data Stream Protocol, AppleTalk - Apple Filing Protocol, AppleTalk - AppleTalk Session Protocol, AppleTalk - AppleTalk Transaction Protocol, AppleTalk - Datagram Delivery Protocol, AppleTalk - Name Binding Protocol, AppleTalk - Printer Access Protocol, AppleTalk - Routing Table Maintenance Protocol, AppleTalk - Zone Information Protocol, AppleTalk - Physical Implementation, AppleTalk - Networking Model, AppleTalk - Cross Platform Solutions Read more here: » AppleTalk: Encyclopedia II - AppleTalk - Physical Implementation |
| |
| | | | | Active Directory: Encyclopedia II - DNS zone transfer - Operation Zone transfer operates on top of the Transmission Control Protocol (TCP), and takes the form of a client-server transaction. The parties involved in a zone transfer are a client, the "slave" requesting the data from a portion of the database to be transferred to it, and a server, the "master" supplying those data from its database. (Some sources refer to the slave as a "secondary" server and the master as a "primary" server.) The portion ...
See also:DNS zone transfer, DNS zone transfer - Operation, DNS zone transfer - Limitations, DNS zone transfer - Operational problems, DNS zone transfer - Serial number changes, DNS zone transfer - Serial number comparisons, DNS zone transfer - Multiple resource records, DNS zone transfer - Security, DNS zone transfer - Security through obscurity, DNS zone transfer - Denial of front-end service, DNS zone transfer - Denial of back-end service Read more here: » DNS zone transfer: Encyclopedia II - DNS zone transfer - Operation |
| |
| | | | | Active Directory: Encyclopedia II - Windows 2000 - Total cost of ownership In October 2002, Microsoft commissioned IDC to determine the total cost of ownership (TCO) for enterprise applications on Windows 2000 versus the TCO of Linux on the same enterprise applications. IDC looked at security and other infrastructure tasks, and Web Serving. According to the report, Windows 2000 had a lower TCO for four infrastructure items and Linux had a lower TCO for web serving. IDC's report was based on telephone interviews of IT executives and managers of 104 North American companie ...
See also:Windows 2000, Windows 2000 - History, Windows 2000 - Architecture, Windows 2000 - User mode, Windows 2000 - Kernel mode, Windows 2000 - Common functionality, Windows 2000 - NTFS 5, Windows 2000 - Encrypting File System, Windows 2000 - Basic and dynamic disk storage, Windows 2000 - Accessibility support, Windows 2000 - Language & locale support, Windows 2000 - System utilities, Windows 2000 - Recovery Console, Windows 2000 - Server family functionality, Windows 2000 - Distributed File System, Windows 2000 - Active Directory, Windows 2000 - Volume fault tolerance, Windows 2000 - Versions, Windows 2000 - Deployment, Windows 2000 - Total cost of ownership, Windows 2000 - Notes Read more here: » Windows 2000: Encyclopedia II - Windows 2000 - Total cost of ownership |
| |
| | | | | Active Directory: Encyclopedia II - AppleTalk - Design The design fairly rigorously followed the OSI model of protocol layering. Unlike most other early LAN systems, AppleTalk was not built on the archetypal Xerox XNS system, as the intended target was not Ethernet and did not have 48-bit addresses to route. Nevertheless many portions of the AppleTalk system have direct analogs in XNS.
One key differentiator for AppleTalk was that the system contained two protocols aimed at making the system completely self-configuring. The AppleTalk address resolution protocol (AARP) allowe ...
See also:AppleTalk, AppleTalk - Design, AppleTalk - Addressing, AppleTalk - Protocols, AppleTalk - AppleTalk Address Resolution Protocol, AppleTalk - AppleTalk Data Stream Protocol, AppleTalk - Apple Filing Protocol, AppleTalk - AppleTalk Session Protocol, AppleTalk - AppleTalk Transaction Protocol, AppleTalk - Datagram Delivery Protocol, AppleTalk - Name Binding Protocol, AppleTalk - Printer Access Protocol, AppleTalk - Routing Table Maintenance Protocol, AppleTalk - Zone Information Protocol, AppleTalk - Physical Implementation, AppleTalk - Networking Model, AppleTalk - Cross Platform Solutions Read more here: » AppleTalk: Encyclopedia II - AppleTalk - Design |
| |
| | | | | Active Directory: Encyclopedia II - Windows 2000 - History Windows 2000 originally descended from the Microsoft Windows NT operating system product line. Originally called Windows NT 5, Microsoft changed the name to Windows 2000 on October 27th, 1998[1]. It was also the first Windows version that was released without a code name, though Windows 2000 Service Pack 1 was codenamed "Asteroid" and Windows 2000 64-bit was codenamed "Janus" (not to be confused with Windows 3.1, which had the same codename). The first ...
See also:Windows 2000, Windows 2000 - History, Windows 2000 - Architecture, Windows 2000 - User mode, Windows 2000 - Kernel mode, Windows 2000 - Common functionality, Windows 2000 - NTFS 5, Windows 2000 - Encrypting File System, Windows 2000 - Basic and dynamic disk storage, Windows 2000 - Accessibility support, Windows 2000 - Language & locale support, Windows 2000 - System utilities, Windows 2000 - Recovery Console, Windows 2000 - Server family functionality, Windows 2000 - Distributed File System, Windows 2000 - Active Directory, Windows 2000 - Volume fault tolerance, Windows 2000 - Versions, Windows 2000 - Deployment, Windows 2000 - Total cost of ownership, Windows 2000 - Notes Read more here: » Windows 2000: Encyclopedia II - Windows 2000 - History |
| |
| | | | | Active Directory: Encyclopedia II - Windows 2000 - Deployment Windows 2000 can be deployed to a site via various methods. It can be installed onto servers via traditional media (such as via CD) or via distribution folders that reside on a shared folder. Installations can be attended or unattended. An attended installation requires the manual intervention of an operator to choose options when installing the operating system. Unattended installations are scripted via an answer file, or predefined script in the form of an INI file that has all the options filled in already. The Winnt.exe or Winnt32.exe pr ...
See also:Windows 2000, Windows 2000 - History, Windows 2000 - Architecture, Windows 2000 - User mode, Windows 2000 - Kernel mode, Windows 2000 - Common functionality, Windows 2000 - NTFS 5, Windows 2000 - Encrypting File System, Windows 2000 - Basic and dynamic disk storage, Windows 2000 - Accessibility support, Windows 2000 - Language & locale support, Windows 2000 - System utilities, Windows 2000 - Recovery Console, Windows 2000 - Server family functionality, Windows 2000 - Distributed File System, Windows 2000 - Active Directory, Windows 2000 - Volume fault tolerance, Windows 2000 - Versions, Windows 2000 - Deployment, Windows 2000 - Total cost of ownership, Windows 2000 - Notes Read more here: » Windows 2000: Encyclopedia II - Windows 2000 - Deployment |
| |
| | | | | Active Directory: Encyclopedia II - Windows 2000 - Architecture Windows 2000 is a highly modular system that consists of two main layers: a user mode and a kernel mode. The user mode refers to the mode in which user programs are run. Such programs are limited in terms of what system resources they have access to, while the kernel mode has unrestricted access to the system memory and external devices. All user mode applications access system resources through the executive which runs in kernel mode.
Windows 2000 - User mode.
User mode in Windows 2000 is made of subsyste ...
See also:Windows 2000, Windows 2000 - History, Windows 2000 - Architecture, Windows 2000 - User mode, Windows 2000 - Kernel mode, Windows 2000 - Common functionality, Windows 2000 - NTFS 5, Windows 2000 - Encrypting File System, Windows 2000 - Basic and dynamic disk storage, Windows 2000 - Accessibility support, Windows 2000 - Language & locale support, Windows 2000 - System utilities, Windows 2000 - Recovery Console, Windows 2000 - Server family functionality, Windows 2000 - Distributed File System, Windows 2000 - Active Directory, Windows 2000 - Volume fault tolerance, Windows 2000 - Versions, Windows 2000 - Deployment, Windows 2000 - Total cost of ownership, Windows 2000 - Notes Read more here: » Windows 2000: Encyclopedia II - Windows 2000 - Architecture |
| |
| | | | | Active Directory: Encyclopedia II - Windows 2000 - Server family functionality The Windows 2000 server family consists of Windows 2000 Server, Windows 2000 Advanced Server and Windows 2000 Datacenter Server. They all have advanced functionality not found in Windows 2000 Professional, among these features are support for DFS, Active Directory and advanced fault-tolerant volumes.
Windows 2000 - Distributed File System.
Main articles: Distributed File System (Microsoft), and< ...
See also:Windows 2000, Windows 2000 - History, Windows 2000 - Architecture, Windows 2000 - User mode, Windows 2000 - Kernel mode, Windows 2000 - Common functionality, Windows 2000 - NTFS 5, Windows 2000 - Encrypting File System, Windows 2000 - Basic and dynamic disk storage, Windows 2000 - Accessibility support, Windows 2000 - Language & locale support, Windows 2000 - System utilities, Windows 2000 - Recovery Console, Windows 2000 - Server family functionality, Windows 2000 - Distributed File System, Windows 2000 - Active Directory, Windows 2000 - Volume fault tolerance, Windows 2000 - Versions, Windows 2000 - Deployment, Windows 2000 - Total cost of ownership, Windows 2000 - Notes Read more here: » Windows 2000: Encyclopedia II - Windows 2000 - Server family functionality |
| |
| | | | | Active Directory: Encyclopedia II - Active Directory - Trust To allow users in one domain to access resources in another, AD uses trust. Trust is automatically produced when domains are created, the forest sets the default boundaries of trust, not the domain, and implicit trust is automatic. As well as two-way transitive trust, AD trusts can be shortcut (joins two domains in different trees, transitive, one- or two-way), forest (transitive, one- or two-way), realm (transitive or nontransitive, one- or two-way), or external (nontransitive, one- or two-way) in order to connect to other forests or non-AD domains. AD uses the Kerberos V5 protocol, although NTLM is a ...
See also:Active Directory, Active Directory - Structure, Active Directory - Objects, Active Directory - Forests Trees and Domains, Active Directory - Physical structure and Replication, Active Directory - Naming, Active Directory - Trust, Active Directory - Trusts in Windows 2000 native mode, Active Directory - Notes Read more here: » Active Directory: Encyclopedia II - Active Directory - Trust |
| |
| | | | | Active Directory: Encyclopedia II - Active Directory - Naming AD supports UNC (\), URL (/), and LDAP URL names for object access. AD internally uses the LDAP version of the X.500 naming structure.
Every object has a Distinguished name (DN), so a printer object called HPLaser3 in the OU Marketing and the domain foo.org, would have the DN: CN=HPLaser3,OU=Marketing,DC=foo,DC=org where CN is common name and DC is domain object class, DNs can have many more than four parts. The object can also have a Canonical name, essentially the DN in reverse, witho ...
See also:Active Directory, Active Directory - Structure, Active Directory - Objects, Active Directory - Forests Trees and Domains, Active Directory - Physical structure and Replication, Active Directory - Naming, Active Directory - Trust, Active Directory - Trusts in Windows 2000 native mode, Active Directory - Notes Read more here: » Active Directory: Encyclopedia II - Active Directory - Naming |
| |
| | | Page 1 Page 2 » Page 3 « More » | |
| |
|
|
