|
Did you look at that article? Almost each "Headache" has a line in it that says "Choose a tool..." so this is obviously pulled from a sales brochure for some tool. However, let's look at these headaches. Most aren't exchange-specific and those that are are based on a poor knowledge of the product. Finally, when did midrange-l become a Microsoft bashing list? #1 - Fighting fires. OK, and how many of us fight fires on the AS/400? Oh, of course, we all have calm peaceful days where our users don't call us with problems. All our code is bug free and our requirements never change. #2 - Analyze not fix. It's hard to fix when you don't know why it's broken. Of course it's easy to tell why it's broken if you see my response to #3. #3 - No good way to analyze. Ever bring up Performance Manager? On my exchange server there are 11 different performance objects, each with 5 to 15 counters and some counters have multiple instances. I can measure bytes sent via IMAP or the current size of the notify queue in the event store, or the Disk file writes per second in the message transfer agent at the click of a button. If that isn't good enough I can turn up logging to three different logging levels in dozens of categories to the point that I can record every SMTP command that flows over the line and know each page split that occurs in the directory store. I can also keep a copy of every inbound and outbound message, track what message went where, when and through what connector. If all this doesn't give you a good way to analyze I'd like to see a machine that does more. #4 - Consolidating slows performance. Well no kidding. I'm loading more stuff onto a single box. Let's not forget that I'm probably also moving what was a local resource to a remote resource if I'm consolidating different geographic locations into one. This isn't an Exchange issue it's a consolidation issue. Of course you gain management advantages if you consolidate so it can be worth it. #5 - Every hacker gunning for MS. True. However the same would be true of Domino on NT, no? There are no "Exchange" viruses that I'm aware of. Outlook ones, yes, but Exchange, no. Also, isn't Lotus now pushing that you can use your Outlook client w/Domino? If so that setup will be just as virus prone. Of course, since there are so many people "gunning" for MS the problems are well know and there are a multitude of tools available to help. In Exchange land there are native antivirus solutions from Sybari, Symantec, MacAfee, CA, Trend and others. How many are there for OS/400? #6 - Tracking storage in distributed environment. Gee, what has that got to do with exchange? Ever track storage across 20 AS/400s? How about 20 Novell file servers? Perhaps 20 Linux boxes? This is why SANs are so nice. Of course I can't plug my AS/400 into my Shark, can I? #7 - Too little too late, too much too soon. Again, that isn't an Exchange problem. No one has ever mis-sized an AS/400? Or a Novell server? Or an AIX server. #8 - How to charge back. Ok, all those that have a good charge back solution for your AS/400 please raise their hand. Or their file server? Or their internet connection? #9 - When user problems arise Exchange manager is last to know. Well, then fire him/her. Isn't that there job? They have a plethora of tools to tell them when there is a problem if they don't know fire them. Also, do we as AS/400 people know all our user's problems? #10 - Exchange admin on an island. See #9. ------------ Walden H Leverich III President Tech Software (516) 627-3800 x11 (208) 692-3308 eFax WaldenL@TechSoftInc.com http://www.TechSoftInc.com -----Original Message----- From: jpcarr@tredegar.com [mailto:jpcarr@tredegar.com] Sent: Wednesday, March 06, 2002 08:26 To: midrange-l@midrange.com Subject: Top 10 Exchange management headaches FYI >From a list I some how got on. John Carr ---------------------------------------------------------------------------- -- WINDOWS 2000 IN THE ENTERPRISE: TECHNOLOGY STRATEGIES IN ACTION --------------------------------------------------------------------- TOP 10 EXCHANGE MANAGEMENT HEADACHES by Jan Stafford, searchWindowsmanageability.com site editor Question: Why is a Microsoft Exchange manager like a voodoo doll? Answer: Somebody is always needling him about a problem. Such black humor is common amongst Exchange administrators, who are always on pins and needles about when the next message system crisis will pop up. That's why the Exchange management headaches listed in this "top 10" list will sound all too familiar. To help managers solve these sticky problems, Kim Roy accompanies each headache with tips on Exchange management tools. In each case, choosing a tool with the right features will help managers ward off evil Exchange spirits, said Roy, product manager for Houston, Texas-based BMC Software. Headache #1: The technical staff is constantly fighting fires instead of working on projects. Dealing with unexpected day-to-day problems is "the nemesis of most administrators," said Roy. Some of these daily mishaps can be avoided if your Exchange management tool offers automated recovery actions. When a potential problem is detected, the recovery action is initiated and the problem can be solved without involving the administrator. Headache #2: When performance is degraded, the staff spends most of the time diagnosing the problem, not fixing it. When an Exchange glitch occurs, the administrator can easily see the symptom but not the cause, said Roy. Make sure that you choose a management tool that spotlights problem areas as soon as, or even before, errors occur. Headache #3: There's no good way to analyze the environment at any given point in time. "An immediate view into the Exchange server environment is imperative when solving problems," said Roy. Choose an Exchange management tool that allows the administrator to view the key system and application parameters on an ad-hoc basis. Having local performance data stored on that server assists administrators in getting a quick view of the entire server. Click here to read the remaining headaches: http://searchwindowsmanageability.techtarget.com/tip/1,289483,sid33_gci80224 5,00.html?FromTaxonomy=/pr/288028 ______________________________________________ This message is intended only for the person or entity to which it is addressed and may contain confidential material. If you are not the intended recipient, any use, distribution or other action taken in reliance on this message is prohibited. If you received this message in error, please contact the sender and delete the material from any computer. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
