Managing Active Directory Performance

By Author: iris
Total Articles: 286
Comment this article

This chapter shows you how to monitor and troubleshoot Active Directory, tasks you'll perform CompTIA A+ Practical Application often as a system administrator. To effectively monitor and trouble-shoot, you must know how to interpret the directory and file replication service logs in the Event Viewer console to handle errors, warnings, and informational messages generated by Active Directory and the Pile Replication service (FRS). You must also be able to set up System Monitor to sample Active Directory and FRS replication performance by using the NTDS, FileReplicaConn, and FileReplicaSet performance objects, The practices and labs in this chapter help you gain the skills and confidence you'll need to effectively monitor and troubleshoot Active Directory and FRS replication.
Before You Begin
To complete the lessons in this chapter, you must
Prepare your test environment according to the descriptions given in the "Getting Started" section of "About This Book"
Complete the practices for installing and configuring Active Directory as discussed in Chapter 2, "Installing ...
... and Configuring Active Directory"
Learn to use Active Directory administration tools as discussed in Chapter 3,"Administering Active Directory"
What needs to be done to track accesses or attempts to access the folders containing Tailspin's confidential documents?
To track access attempts at the folder level, use auditing. The folders must reside on an NTFS partition, and Object Access auditing must be enabled. This can be accomplished using Group Policy directly, or by Network+ certification configuring our Security Template accordingly. A very important and often overlooked step is configuring the actual folder to be audited. Enabling Object Access auditing for the server is necessary, but by itself, will not cause anything to be audited! You must also configure auditing on the individual folders.
6.How should the file servers that contain confidential documents be configured to meet Tailspin's requirements regarding the security log?
Lisa Jacobson indicated that all attempts to access data must be audited without exception. She also indicated that the security log entries must never be overwritten. The appropriate setting for the Event Viewer security logs on these servers is Do Not Overwrite Events. By itself, this setting will cause the security log to fill up and a prompt to appear on the screen indicating that the log is full. While the log is full, no further access attempts will be audited. To alleviate this issue, raise the maximum size of the Event Viewer security log. Doing so allows more entries to be recorded. One last setting that should be considered is the Audit: Shut Down The System Immediately If Unable To Log Security Audits. Recall that if the security log fills up, and we don't allow events to be overwritten, no further audits can be made until an administrator intervenes. This setting gives up some stability in exchange for extra audit assurance. If this setting is made, it is critical that the comptia network exam logs are archived or cleared manually before they fill up. Otherwise, just as the setting says, the system will shut down.