You need to identify the Lightweight Directory Access Protocol (LDAP) clients that are using the largest amount of available CPU resources on a domain controller

Your network consists of a single Active Directory domain. All domain controllers run
Windows Server 2008 R2.
You need to identify the Lightweight Directory Access Protocol (LDAP) clients that are using
the largest amount of available CPU resources on a domain controller.

What should you do?

Your network consists of a single Active Directory domain. All domain controllers run
Windows Server 2008 R2.
You need to identify the Lightweight Directory Access Protocol (LDAP) clients that are using
the largest amount of available CPU resources on a domain controller.

What should you do?

A.
Review performance data in Resource Monitor.

B.
Review the Hardware Events log in the Event Viewer.

C.
Run the Active Directory Diagnostics Data Collector Set. Review the Active Directory
Diagnostics report.

D.
Run the LAN Diagnostics Data Collector Set. Review the LAN Diagnostics report.

Explanation:
http://servergeeks.wordpress.com/2012/12/31/active-directory-diagnostics/
Active Directory Diagnostics
Prior to Windows Server 2008, troubleshooting Active Directory performance issues often
required the installation of SPA. SPA is helpful because the Active Directory data set collects
performance data and it generates XML based diagnostic reports that make analyzing AD
performance issues easier by identifying the IP addresses of the highest volume callers and
the type of network traffic that is placing the most loads on the CPU.
Download SPA tool: http://www.microsoft.com/en-us/download/details.aspx?id=15506
Now the same functionality has been built into Windows Server 2008 and Windows Server
2008 R2 and you don’t have to install SPA anymore.
This performance feature is located in the Server Manager snap-in under the Diagnostics
node and when the Active Directory Domain Services Role is installed the Active Directory
Diagnostics data collector set is automatically created under System as shown here.

When you will check the properties of the collector you will notice that the data is stored
under %systemdrive %\perflogs, only now it is under the \ADDS folder and when a data
collection is run it creates a new subfolder called YYYYMMDD-#### where YYYY = Year,
MM = Month and DD=Day and #### starts with 0001 . Active Directory Diagnostics data
collector set runs for a default of 5 minutes. This duration period cannot be modified for the
built-in collector. However, the collection can be stopped manually by clicking the Stop
button or from the command line.

To start the data collector set, you just have to right click on Active Directory Diagnostics
data collector set and select Start. Data will be stored at %systemdrive%\perflogs location.

Once you’ve gathered your data, you will have these interesting and useful reports under
Report section, to aid in your troubleshooting and server performance trending.

Further information:
http://technet.microsoft.com/en-us/library/dd736504%28v=ws.10%29.aspx
Monitoring Your Branch Office Environment
http://blogs.technet.com/b/askds/archive/2010/06/08/son-of-spa-ad-data-collector-sets-inwin2008-andbeyond.aspx
Son of SPA: AD Data Collector Sets in Win2008 and beyond



Leave a Reply 0

Your email address will not be published. Required fields are marked *

10 − seven =