Exchange admins who are not developers should buy a product. But it's becoming more and more rare because of the requirement to be able to build powershell scripts in Exchange 2007 and beyond.
Many of us that have come and gone here built perl-based tools to analyze message tracking logs and prior to that the IMC logs, etc. You can use sawmill to get data on IIS logs too among all the previously mentioned tools. MOM/SCOM from Microsoft both have Exchange reporting packs that will give you usage data about Exchange too. The idea that perl isn't natively supported is absurd. You have to install it. Just like you have to install Access or SQL or Quest or Visual Studio. The idea that not everyone is a developer is correct. The idea that some developers know different tools is correct (although true developers are syntax agnostic and can build you a solution in whatever language you throw at them). -----Original Message----- From: bounce-51093267-750...@intm-dl.sparklist.com [mailto:bounce-51093267-750...@intm-dl.sparklist.com] On Behalf Of Brett Fernicola Sent: Thursday, February 12, 2009 12:22 PM To: Exchange Discussions Subject: RE: Exchange reporting tools Your missing the point Chris. You and I may fully understand Perl and programming in general, but that's because we are developers. I am trying to steer Exchange Admins who are obviously not developers or even scripter's towards the simplest easiest solution. If an admin needs to ask how to analyze his exchange logs then I'm assuming he's not up to the task of writing his own solution. Therefore suggesting a custom Perl scenario may be out of reach for most people; hence why I recommend people to look at MS Log Parser because they will find already ready working scripts to answer their ?'s. Those scripts will also be in a much easier to understand format thus allowing novices to alter and edit them to fit their needs. Nothing against Perl, it just doesn't fit well for the average exchange admin. Brett Fernicola Systems Engineer STEALTHbits Technologies, Inc. (201) 447-9356 -----Original Message----- From: bounce-51090709-3785...@intm-dl.sparklist.com [mailto:bounce-51090709-3785...@intm-dl.sparklist.com] On Behalf Of Chris Scharff Sent: Thursday, February 12, 2009 11:06 AM To: Exchange Discussions Subject: RE: Exchange reporting tools -----Original Message----- From: bounce-51080486-1429...@intm-dl.sparklist.com [mailto:bounce-51080486-1429...@intm-dl.sparklist.com] On Behalf Of Brett Fernicola Posted At: Wednesday, February 11, 2009 4:28 PM Posted To: swynk Conversation: Exchange reporting tools Subject: RE: Exchange reporting tools #1 Windows does not natively support Perl So I guess if installing ActiveState Perl on my box is insufficient I'll use my Ubuntu box. What is that FUD supposed to mean? #2 Making a custom report in Perl is much harder then using SQL Code and VB. Source? Examples? What does that even mean? I can state with 100% certainty that for me your assertion is untrue. #3 Have fun researching and finding help with Perl in regards to Exchange Metric log crunching. I still don't know what an Exchange Metric log is, but I'm relatively new to Exchange. What would I need help with exactly? Parsing a log file in Perl? It's one of Perl's core strengths. Would I need to ask a Perl developer what a log field or value meant if I didn't know or could anyone with a working knowledge of Exchange answer that? Is a Perl developer going to have a more interesting take on message counting standards than a C# developer? Why can't I debate that with both? #4 There is already a user base of people using MS log parser to crunch exchange Logs, they will help and share their scripts with you. I doubt you will find this level of support with Perl. I assume the 'you' here is the generic you. Because I could have a half dozen Perl samples in my inbox with a single email. #5 Again if you want support, help, & samples use SQL and VB, which are all understood by windows natively. I've helped build Exchange log parsing tools in Java. Got plenty of support, had developers smart enough to understand samples written in other languages and I think it was running on some damn Solaris box for all it matters. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange To subscribe: http://e-newsletters.internet.com/discussionlists.html/ To unsubscribe send a blank email to leave-51090709-3785410.edab4f1289b098e322e75545dbe85...@intm-dl.sparklis t.com Exchange List admin: lc...@jupitermedia.com To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange To subscribe: http://e-newsletters.internet.com/discussionlists.html/ To unsubscribe send a blank email to leave-51093267-750975.a7d02cd2879c9e54ab55079021e8e...@intm-dl.sparklist.com Exchange List admin: lc...@jupitermedia.com To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange To subscribe: http://e-newsletters.internet.com/discussionlists.html/ To unsubscribe send a blank email to leave-51095579-93384.d3786cf277f52d7b092b75655b561...@intm-dl.sparklist.com Exchange List admin: lc...@jupitermedia.com To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
