You are a network administrator for your company. The network contains a Windows Server 2003 computer named Server1. Server1 has a single CPU, 512 MB of RAM, and a single 100-Mb network adapter.
All network users’ home folders are stored on Server1. Users access their home folders by using a mapped network drive that connects to a shared folder on Server1. After several weeks, users report that accessing home folders on Server1 is extremely slow at certain times during the day. You need to identify the resource bottleneck that is causing the poor performance.
What should you do?
A.
Capture a trace log that captures Page faults, File details, Network TCP/IP, and Process creations/deletions events.
B.
Configure Alerts on Server1 to log entries in the event logs for the LogicalDisk, PhysicalDisk, Processor, Memory, and Network Interface performance objects when the value of any object is more than 90.
C.
Capture a counter log by using LogicalDisk, PhysicalDisk, Processor, Memory, and Network Interface performance objects, and view the log data information that is captured during periods of poor performance.
D.
Implement auditing on the folder that contains the users’ home folders. Configure Network Monitor on Server1.
Explanation:
The problem is most likely to be caused by a hardware bottleneck. This could be a disk problem or a problem with the processor, RAM or network card. We can monitor these hardware resources by using a System Monitor counter log. The Windows Performance tool is composed of two parts:
System Monitor and Performance Logs and Alerts. With System Monitor, you can collect and view real-time data about memory, disk, processor, network, and other activity in graph, histogram, or report form. The output from the counter log will show us which hardware resource in unable to cope with the load and needs to be upgraded or replaced.Reference:
Craig Zacker, MCSE Self-Paced Training Kit (Exam 70-293): Planning and Maintaining a Microsoft Windows Server 2003 Network Infrastructure, Microsoft Press, Redmond, Washington, 2004, pp.
6: 25-28