09.02.2014 Views

Windows sysinternals

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

296 Part II Usage Guide<br />

You can script AdExplorer to create a snapshot by starting it with the –snapshot commandline<br />

option. The option requires two parameters: the connection string and the snapshot<br />

path. Connection string is just the server name, or you can use a pair of double quotes to<br />

specify the default directory server. It is not possible to specify alternate credentials for the<br />

connection. To snapshot the default domain using current credentials, use this command:<br />

adexplorer -snapshot "" c:\snapshots\snapshot1.dat<br />

AdExplorer Configuration<br />

AdExplorer’s configuration settings are stored in two separate registry keys. The EulaAccepted<br />

value is stored in HKCU\Software\Sysinternals\Active Directory Explorer. The rest of<br />

AdExplorer’s settings—including Favorites, snapshot paths, and other dialog box settings—<br />

are stored in HKCU\Software\MSDART\Active Directory Explorer.<br />

AdInsight<br />

AdInsight is a real-time monitoring utility that tracks LDAP API calls. Because LDAP is the<br />

communication protocol used by Active Directory, AdInsight is ideal for troubleshooting<br />

Active Directory client applications.<br />

AdInsight uses DLL injection techniques to intercept calls that applications make in the<br />

Wldap32.dll library, which is the standard <strong>Windows</strong> library that implements low-level LDAP<br />

functionality, and upon which higher-level libraries such as ADSI (Active Directory Service<br />

Interfaces) rely. Unlike network monitoring tools, AdInsight intercepts and interprets all<br />

client-side APIs, including those that do not result in transmission to a server.<br />

AdInsight monitors any process into which it can load its tracing DLL. It works most reliably<br />

when it is executed in the same security context and on the same desktop as the application<br />

being monitored. If the client application does not have administrative rights, AdInsight<br />

should not either.<br />

To monitor <strong>Windows</strong> services, AdInsight needs to execute in Terminal Services session 0. On<br />

<strong>Windows</strong> XP and <strong>Windows</strong> Server 2003, this is typically the case when the AdInsight user<br />

has logged on at the console. However, on <strong>Windows</strong> Vista and newer, the interactive user<br />

desktop is never in session 0. You can start AdInsight in session 0 by running the following<br />

PsExec command with administrative rights:<br />

psexec -d -i 0 adinsight.exe<br />

AdInsight will then be able to inject its tracing DLL into other processes in session 0, including<br />

<strong>Windows</strong> services.<br />

www.it-ebooks.info

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!