Microsoft Windows 2000 Optimizing, troubleshooting

When it comes to system analysis, there are two primary components involved in tacklingperformance-related issues:

* Monitoring - This requires a thorough understanding of system components and their

behavior, as well as observation of those components and how they behave

on a regular basis

* Performance tuning - This activity consists of changing a system’s configuration systematically and carefully observing performance before and after such changes.

- Changes that improve performance should be left in place, those that make no difference – or that make things worse should be reversed

Windows 2000 does a remarkable job of tuning itself. It is capable of managing both its physical and virtual memory quite well.

Alerts

Is a watchdog that informs you when a counter crosses a defined threshold. Basically, an alert is an automated attendant looking for high or low values.

The possible actions of an alert are as follows:

* Log an entry into the application event log
* : You can view the event detail through Event Viewer Send a network message:
* A single NetBIOS name of a user, group, or computer can be defined. When an alert occurs, a message regarding the alert and the measured counter level is sent. Start performance data log:
* Starts the recording of a Counter log Run this program:
Used to execute a program with command-line options or to launch a batch file. When this action is used, a string of performance-related information can be included at the end of the defined command line in the form.

Event Viewer

* Is another useful tool for examining information about the performance and activities on a system
* Event Viewer tracks all events generated by the operating system, as well as security and application events.
* Failure of a device to load, an unsuccessful logon, or a corrupt database file can all be recorded by Event Viewer and viewed through one of three log files: System, Application, or Security.

Recognising and Handling Bottlenecks

A bottleneck is a condition in which a limitation in a single component slows down an entire system.

The first thing to remember about bottlenecks is that they will always exit in any computer.

Examples;

* Disk bottlenecks
* Memory bottlenecks
* Processor
* Network bottlenecks

Eight Ways to Improve Windows 2000 Performance

1. Buy a faster machine

It takes a year or so for a top-of the line PC to become obsolete. So if you planing on spending more than half the coat of a new machine, then buy a new machine, a faster machine
2. Upgrading an exiting machine

You might decide to keep a PC’s case, power supply and some of the adapter cards it contains, as long as the price stays below half the cost of a new machine, replacing a PC’s motherboard not only gets you a faster CPU, more memory capacity (both cache and main memory,But be sure to evaluate the costs of upgrading the disk controller and hard drives, especially if they’re more than twice as slow as prevailing access time.
3. Install a faster CPU

As long as you double the clock speed of your current CPU with a replacement unit, such an upgrade can improve performance for only a modest outlay. Be sure to review your memory configuration (cache and main memory) and your disk drives at the same time.
4. Add moreL2 cache

The CPU can access L2 cache in two CPU cycles, where as access to main RAM usually takes 8 to 10 CPU cycles which accounts for dramatic performance improvements
5. Add more RAM

For moderately loaded workstations (six or fewer applications active at once), 64 MB of RAM is recommended.

For heavily loaded workstations, 128 MB or more may improve performance significantly.
6. Replace the disk subsystem

Because memory access occurs at nanosecond speeds, and disks access occurs at millisecond speeds, disk subsystem speed can make a major impact on Windows 2000 performance.
7. Increase paging file size

Whenever System Monitor indicates that more than 10% of disk subsystem activity is related to paging, check the relationship between the Limit and Peak values in the Commit Charge pane in Task Manager.

If the Peak is coming any closer than 4096 KB to the limit, it’s time to increase the size of this file.
8. Increase application priority

On machines where a lot of background tasks must be active, you can use the Task Manager’s Processes tab to increase the priority of any already running process.

We recommend that you set only critical applications to realtime, because they can interfere with operating system’s ability to do its job.

 

-------

 

The first rule of troubleshooting is that you can never have too much information. In fact, information is your best weapons, not just for resolving problems, but also for preventing them in the first place.

Computer Information file (CIF) provides a detailed collection of all information related to the hardware and software products that compose your computer (and even your entire network).

Some of the important items to include in your CIF are:

* Platform, type, brand and model number of each component
* Complete manufacturer specifications
* Manuals, users’guides or configuration sheets
* Name and version of all software
* Network-assigned names, locations and addresses
* Warranty information such as phone numbers and e-mail address
* Date and location of last complete backup and other backup items
* Network layout and cabling map

However your CIF is not complete with only hardware and software details. You should also include the nonphysical characteristics of your system such;

* Plans for future service deployment
* Training schedule
* Maintenance schedule
* Backup schedule
* Authorship rights and restrictions
* Troubleshooting procedures

Common-Sense Troubleshooting Guidelines

* Be patient
* Be familiar with your system’s hardware and software
* Attempt to isolate the problem
* Divide and conquer
* Eliminate suspects
* Undo the most recent change
* Investigate the most common points of failure
* Recheck items that have caused problems before
* Learn from mistakes
* Experiment

Troubleshooting Tools

Event Viewer

Is used to view system messages regarding the failure or success of various key occurrences within the Windows 2000 environment

Troubleshooting Installation Problems

* Media errors

Are problems with the distribution CD-ROM itself or communications link between the installation and distribution file

* Domain controller communication difficulties

Communication with the domain controller is crucial to some installations, especially when attempting to join a domain eg mistyping name, password, domain name etc

* Hardware problems

If you failed to verify your hardware with the HCL (Hardware Compatibility List) and the only solution is to replace the device, however double-check the installation and configuration of all devices within the computer

Troubleshooting printer Problems

* Check that the physical aspects of the printer-cable, power, paper, toner and so on
* Make sure the printer is plugged in and online
* Make sure the printer server for the printer is booted
* Check the print queue for stalled jobs

 
 
This site was designed using Adobe Photoshop 7.0 and Dreamweaver 3 by Alex Trigueros for an ITT Tech Class on Microsoft Windows Operating Systems- Any Questions can be sent to GkDragon (AT) NetScape.Com