|
<http://msdn.microsoft.com/library/en-us/dnactdir/html/efficientadapps.asp>
This article summarizes some techniques. Look towards the middle and end of the article. If you have control over a particular LDAP client application, consider building a debug version that uses the STATS control as part of its LDAP queries. That’ll give you exactly what you’re looking for.
For different applications, bumping a registry value on the DC’s can give you a lot of information.
Perf counters will let you know how long the last bind took, but not queries I don’t think.
Charles Oppermann, [EMAIL PROTECTED], http://weblogs.asp.net/chuckop/ From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Anyone found a clever way to monitor and alert on this stuff? J Counters maybe? |
Title: LDAP Query Response Time
- [ActiveDir] LDAP Query Response Time Marcus.Oh
- RE: [ActiveDir] LDAP Query Response Time Chuck Oppermann
- RE: [ActiveDir] LDAP Query Response Time joe
- RE: [ActiveDir] LDAP Query Response Time Eric Fleischman
- RE: [ActiveDir] LDAP Query Response Time Gil Kirkpatrick
- RE: [ActiveDir] LDAP Query Response Time Marcus.Oh
- RE: [ActiveDir] LDAP Query Response Time Centenni, Jason
