performance monitor

I would like to set up a baseline for a windows 2000 server with AD. I am not sure which counters to include under which perfomance object.

Any help would be appreciated.

 

Sue - excellent question and a good idea but an answer that would fit on here isn't likely. The last book I read on perf monitor ran to around 800 pages and pretty much took 750+ of those pages giving the sort of information you are asking for.

Could you give an idea of what areas worry you and what/when you plan to use the information? Gotta narrow the focus some here or the problem becomes impossible.

If server performance is bad/slow/not right at this point, knowing exactly what isn't working to suit you would also allow a troubleshooting answer.

 

There is such an overload of performance montior info.... My systems are working extremely well right now, so I would like to get a baseline to set standards by. With all the info available, I cannot decide what would be good one to monitor. I would just like to be prepared.

Thanks

 

What will the server be doing for a living? Completely different concerns with a DC vs. a file server vs. an app server.

If an app server, also makes a huge difference which apps.

 

It is a DC

thanks

 

OK. Given that a DC is not ever going to work very hard and you mostly want to track stuff that may indicate a failure down the road - server or network - here are a few things you could baseline.

I'm assuming you aren't going to use terminal services, RAS, or similar. If you do, maybe pick an item or two from each of them as well.

Also, while you are setting these up, pick any others that look interesting.

- Memory - page reads/writes/faults, available bytes (or Kb or Mb)

- Network Interface - current bandwidth, output queue length, packet errors

- Processor - % processor time, interrupts per second

- Processor Performance - power consumption

- Physical Disk - Average Disk Queue Length

- Server - pool failures for paged and nonpaged