Now Available:

Featured Resource:

line

Newsletter

Email Address:


line

Ask the Expert

Have a question for our resident expert? Email your questions to Greg.

« Greg's MMS Interview for TechNet Edge | Main | UPDATE: Microsoft Announces Public Preview and Pricing for SBS 2008 and Windows Essential Business Server 2008 »

LOGMAN.EXE, a Great Tool for Managing PerfMon

I just got back from TechMentor where I again found myself spending a lot of time educating Windows administrators on the basics of performance management. There's been a problem with Windows administration over the past few years in that the needs of software hasn't kept up with the abilities of hardware. The end result is that we administrators find ourselves for the first time in the history of computing with vast supplies of resources and little demand.

Becuase of this, a generation of Windows administrators hasn't grown up needing to undertake the daily basics of performance management on servers. The basic concepts of performance management have gotten lost as the old guard moves on and the new guard takes over. What changes all of this, however, is the implementation of virtualization into the IT environment. WIth virtualization, your servers at 3% utilization find themselves "squished together" with others on a virtual host. For this architecture to work successfully, we now see a rebirth of the need for vigilance in watching and actioning on performance.

CC Hameed over at the Ask the Performance Team blog presents a comprehensive look at the command line tool LOGMAN.EXE. This tool provides a command-line approach to managing PerfMon that enables greater functionality, script and scheduled task-based exposure, and a better ability to manage performance logs.

Check out his LOGMAN Two Minute drill at this site: http://blogs.technet.com/askperf/archive/2008/05/13/two-minute-drill-logman-exe.aspx

TrackBack

TrackBack URL for this entry:
http://www.realtime-windowsserver.com/type/mt-tb.cgi/822

Comments

I created a performance counter log that queries some logical drive data from many systems, and I use logman to control when I'd like to collect the data. I initially had 42 systems I collected data from. But recently I increased the number of the systems to 96, and I started to get the following error:

C:\>logman start "DB Drive Space Monitor"
Error:
Collection "DB Drive Space Monitor" did not start, check the application event log for any errors.
C:\>

The counter log actually started OK, and the data collection went OK as well, with no error the event log. But why am I getting this error? How can I stop it? It appears to be a scalability issue of the tool.

Please assist. Thanks.
Ed

Post a comment

(All comments are approved by site leader before appearing here. Thanks for commenting!)

line

Greg Shields' Bio:

Greg Shields, is an independent author, instructor, and IT consultant based in Denver, Colorado, and a co-founder of Concentrated Technology. With nearly 15 years of experience in information technology, Greg has developed extensive experience in systems administration, engineering, and architecture specializing in Microsoft systems management, remote application, and virtualization technologies. Greg is a Contributing Editor for Redmond Magazine, MCPmag.com, and Virtualization Review Magazine and is the author of five books, including Windows Server 2008:  What’s New / What’s Changed. Greg is also a highly sought-after instructor and speaker, speaking regularly at conferences like TechMentor Events, and producing computer-based training curriculum for CBT Nuggets.  Greg is a recipient of Microsoft "Most Valuable Professional" award with a specialization in Windows Terminal Services.