Just a very interesting series of posts by Jorge on how the Active Directory clients determine which domain controller servers their logon request and which domain controller sends the GPO files over.
DC Locator process part 1
DC Locator process part 2
DC Locator process part 3
A small add-on: using start - run - cmd and execute "set" you can easily determine your logon server. Determining which DC sent the GPO's can be determined by running "gpresult /R" (Windows 2008) or "gpresult" (Vista)
The following Technet article is also a nice source of information: How DNS Support for Active Directory Works
0 comments
DC Locator process
Published on Thursday, February 5, 2009 in Active Directory, Windows 2003, Windows 2008
Related Posts
,
,
- Temporary Profiles and IIS Application Pool Identities
- DebugView 100% CPU In a Windows 2008 VM
- Domain controller: LDAP server signing requirements and Simple Binds
- Protected Users Group
- ADFS Alternate Login ID: Some or all identity references could not be translated
- Federating ADFS with the Belnet Federation
- Synchronizing Time on Azure Virtual Machines
- Failover Cluster: Generic Applications Fail with OutOfMemoryException
- Windows OS About To Stop Support For RSA Keys Under 1024 Bits
- Access Denied Using An Alias
- Waking Sleeping Beauty
- A security package specific error occurred(1825)
- MaxTokenSize Implications for HTTP.SYS
Subscribe to:
Post Comments (Atom)
No Response to "DC Locator process"
Add Your Comment