The up.time IT Systems Management Blog

Archive for the ‘Systems Management’ Category

5 Tips for Evaluating IT Systems Management Software

Tuesday, August 3rd, 2010

First off, I apologize as it’s been a while since my last post. The allure of the summer patio and the beautiful weather has taken its toll. But I’m back and ready to roll…

As I chat with customers and prospects at uptime software, it became clear that most IT professionals would find a  “Systems Management and Server Monitoring Evaluation Guide” very useful. So with that in mind, this blog is themed around how to better evaluate systems management and server monitoring software. We’ve found that our mid-enterprise customers (companies that have between 50-2,500 servers) have some common best practices when it comes to  evaluating various packages to monitor and manage their environment. So, without further ado, here are my “5 Tips For Evaluating IT Systems Management Software:”

1. Applications are becoming dynamic and complicated. Can your monitoring and performance software handle it?

Historically, it’s generally been fairly easy to monitor applications.  They sat on individual pieces of hardware and were relatively siloed.  Nowadays, applications are increasingly componentized and are being abstracted from the underlying hardware platforms.  Witness the prevalence of virtualizationtechnologies such as VMware, AIX LPARs, and Solaris zones, all of which are making great strides in widespread adoption.  It is now incumbent on systems managementvendors to understand these virtualization technologies in great detail and how they impact application monitoring and performance. Remember, your systems management and application monitoring tool should make application monitoring easier for you, not more complicated.

2. Heterogeneous platforms (Virtual, Physical and even Cloud) are the new normal. Your systems management software needs to be able to scale across them all.

In a mid-enterpriseshop, it’s highly unlikely that you’re a single platform and OS.  You’ll need to deal with hardware platforms of many vintages and architectures (and add in the network too).  Mix in virtualization and cloud and if you don’t have a fully features management and monitoring tool, you’re in for a world of grief. (shameless plug -  up.time can oversee all the platforms and environments). So, it’s best to ensure that the tools you are considering can cover all your platforms, both today and tomorrow.

3. Are you future proofing?  What about new technologies?

As technologies change, is your systems management tool ready to grow with you?  Virtualization was, and continues to be, a big disruptor and yet many vendors took years to understand how to introspect and monitor virtual environments.  With the advent of cloud and its adoption, a very similar problem is occurring again.  Can you get a single pane-of-glass for monitoring and managing what we call P-V-C (the physical, virtual, and cloud worlds) together?

4. Can you quickly evaluate and deploy?  Do you need lots of professional services?  Is the tool administration costing you an FTE?

We appreciate that extra time is something you probably don’t have the luxury of. So, at uptime software, we designed up.time to get up and running in under 15 minutes  We want to help you solve problems right away, not send a flock of consultants on-site to bleed you to death.  If you’ve had any experience with consultants (or lawyers), you’ll know what I mean.  I’ve heard our customers and prospects say loud and clear, that they don’t want a full-time admin to babysit and administer their monitoring tool. Is the solution you’re evaluating going to save you time or cost you an FTE to manage it?

5. The Last Tip is the most important. Trial, trial and ….trial. Before you talk to salespeople.

Make sure you fully trial the software before you get too far in the buying process. Don’t get caught being sold to through fancy demos, vapor-ware, and PowerPoint’s. Trial the tool, see what it does and how it acts in your environment. Sure, the marketing says how easy the tool is to use and install, and how deep the metrics are. Believe that and I have some swampland in Florida you might be interested in. If the trial is complicated, frustrating, and doesn’t do what you want, don’t expect the purchased tool to be any better. In fact, in most cases, it’s worse. Remember, it’s up to you to ensure your systems management tool is the right fit for your environment and needs. This is exactly why we provide a free trial at up.time. You don’t need to talk to a salesperson to get it, just download it straight off our website. You’ll be able to get up.time monitoringand reporting in less than 15 minutes! We want to you trial up.time, test it, put it through the paces in your environment. So far, up.time has over 700 customers in 32 countries because our trial let’s people see how up.time works in real-life, not on some fancy and wishful thinking demo.

We know that selecting a Systems Monitoring and Management Vendor can be time consuming. It’s also difficult to determine how to prioritize your needs. Therefore, we created a Systems Monitoring and Management Evaluation Checklist. This checklist is designed to help IT Managers and Administrators as they search for the right solution. Rather than starting from a blank sheet of paper, you can adapt the checklist to fit your needs, as it’s intended to be a generic list that can be updated, expanded and customized depending on your requirements. Edit and modify each of the items as you see fit. Also – if you are evaluating up.time (hint, hint), we’ve pre-populated a checklist with everything up.time has to offer. Click here to download a pdf copy or word document.

Interested in finding out more?  Check out our NEW Evaluation Center!

Alex

Cheers to sysadmins

Friday, July 30th, 2010

I just wanted to send a quick little note to our favourite kind of individual: the sysadmin.  Congratulate yourselves today and enjoy “System Administrator Appreciation Day.”  Embrace the Green status on your NOC screen, cherish the idle service desk queue, and relax about the balanced workloads.

Get yourself a large coffee and kick up the shoes for a bit.

Cheers from us at uptime.

Alex

Netflow | Network Data You Can Actually Use

Monday, June 21st, 2010

In the latest release of up.time there are a whole bunch of goodies, but I’m going to take a moment to talk about one specific feature that you should all be aware about, our Netflow capabilities.

To understand Netflow, let’s first start with how we (as in anyone who cares about the network) would do diagnostics and troubleshooting any kind of network error in the past. Trust me, I used to do this as a junior network engineer to pay my way through school, and I know all too well the pain of what I describe below.

First, you would go to your console tools, run those, and examine point stats. Because the point stats are “just the state of the network at the point in time”, and because the consoles are so hard to navigate by text, trying to find out trouble areas or diagnose distributed outages would be like finding a “needle in a haystack”.

Second, ok we’ve figured out that the point in time stats are a pain, if we’ve figured anything out, maybe we would now switch to something with some historical stats like MRTG or Cricket. The bad thing about these tools, they display static graphs over fixed time periods, trying to do any ad-hoc analysis is impossible. Even worse, these tools sort of illuminate key metrics like throughput, capacity utilization, dropped frames, but once you get to that level of figuring out which connections are being flogged, what do you do next? You have zero visibility into the traffic, the applications or any context over why that port or set of ports is underperforming or saturated.

Third, we bring out the BFG (Big !@#$%^& GUN). The passive network profiling tool. You configure the spanning port on the switch or router, you hook up a big honking expensive passive network profiler and what do you do? You WAIT. You wait for this network data to get collected, then you spend hours pouring over the ultra granular network profiling data in hopes of figuring out what is happing on your network.

Does the above sound like sanity or insanity? By the time you deploy the BFG, maybe your users are done watching the world cup viral videos, or maybe the DDOS attack is over.

Let me tell you what you need instead:

You need to be able to alerted on general network outages and performance issues in as they occur
You need to be able to drill down into network traffic breakdowns on network devices AND servers
You need to be able to pro-actively have a network dashboard that focuses less on profiling type operations, and more on network threats, misconfigurations and common applications that cause trouble on the network
You need to be able to perform ad-hoc analysis at will, on demand to rapidly gain insight into what’s going on.

This is what up.time’s netflow capabilities provide. If you want to see more, join one of our what’s new webinars and I’ll be happy to take you on a tour. Click here to register.

Here’s some eye candy to whet your appetite:

up.time NetFlow Monitoring up.time NetFlow Dashboard

Joy is up.time

Monday, June 7th, 2010

This morning I’ve decided to rip BMW’s new tag line “Joy is BMW”. As any of you who follow my blog posts, you know I eat tag lines for breakfast.

So what’s the question Alex? Yes, my old antics – what could this possibly have to do with systems management?

It’s amazing how the typical car history of any fire breathing male on the planet matches the buying patterns for systems management tools. Ok trust me, I haven’t graduated to hardcore drug use, this actually makes a lot of sense if you follow me.

In the case of the car buying,  just like purchasing a systems management tool, you are making a huge investment and hoping that your purchase meets your needs. If the purchase results in a solution that  isn’t reliable or isn’t practical for your needs, you are potentially putting yourself in a “hard place” because you won’t have budget to get yourself into another “vehicle” for a while.

Let’s use my personal car history (don’t judge me, I like fast 2 door cars) and analyze what each car would represent in terms of the systems management world.

Vehicle Representative Monitoring Solution
Ford Probe GT
“fully customized fast and furious style - custom giant turbocharger”
Probe GT Freeware tools
Hyundai Tiburon GT
“Bone stock – reliable – not very fast”
Tiburon Niche Tools
BMW 335i Coupe
“Break Neck Fast, Well Built, Beautiful aesthetics,practical,  just works”
335i up.time
Audi R8
“Fast on a track, Well Built, Super Expensive, Impractical”
(** no I don’t own this car yet, this is for illustrative purposes)
  Big 4/Legacy Vendors

So just how does the maturity process in buying cars map to the maturity process in buying systems management tools?

Take my first car. I had a lot of time on my hands at that point in my life. First job, on top of the world, no responsibilities, I was content to take my stock Ford Probe GT  and customize it like there was no tomorrow. I had to totally rewire the engine, add a turbocharger and make it the envy of wannabe racers world wide. You could find me customizing something, painting something, tuning something on any given weekend. The real problem – reliability of the vehicle suffered, and I started to run out of time maintining the mods, and slowly the shiny afterglow of having a totally “customized” solution wore off.  This is exactly what happens when you use freeware tools as your monitoring tool, inevitably the tooling just can’t keep up as your needs grow, you end up scripting or modding conf files till you are pulling your hair out. Suddenly you’re yearning for a more mature solution.

So in my quest for the perfect car, I turned to my next car purchase. The Hyundai Tiburon. I vowed never to be modding or doing huge maintenance, this next car would have boy racer DNA. Well unfortunately I got tricked by the marketing, the Tiburon was a “fast looking” car. To it’s credit it was very reliable, and got the job done in terms of looking the part. But ultimately it didn’t meet my needs, which was the desire to have a VERY FAST vehicle, that was a joy to drive, was reliable, wasn’t flashy and didn’t require modifications of any kind. Live and learn. In this way, some people graduate from freeware to niche tools that only meet some of their needs, yes they are careful to avoid the maintenance headaches, but maybe they end up with a platform that can ONLY monitor Microsoft solutions for instance. Eventually you’ll realize you got half way there but your needs aren’t being met. You need the right systems and server monitoring tool that can grow with your needs.

They say 3 times is a charm, and when it comes to my car history, I can happily say this cliche is totally right. The 335i is the perfect balance of practicality, reliability, and breakneck speed. The 2 turbochargers under the hood growl when I want them to, or the car runs deceptively quiet if I’m going through your grandmas neighbourhood. It’s got plenty of trunk space, and it doesn’t cry out “I want attention” (like cars made by Audi these days IMHO). So not only is the vehicle a joy to drive, everything fits my needs, it just feels right every time I get into the drivers seat. This is exactly what it feels like when you install up.time. If you don’t believe me give it a try.

So what’s the future for this boy racer? Have I found my dream car? Yes, for now. But, you can bet, as with those big 4 frameworks, that if I were to buy an Audi R8, I’d be dropping a wad of cash for a car that just isn’t practical for everyday use. Sure it would be great to have everything the R8 has to offer today, but it’s more than my needs (I’m not having my mid life crisis yet for instance). Frankly, it would require me to have multiple vehicles and I would end up keeping my 335i as my daily driver. Sound familiar? Why have a best of breed/fragmented/patchwork of solutions when we all want to rationalize our garage/toolsets?

Don’t make the mistake of buying the R8 before you are ready to have a 4 car garage, get up.time and find out what real joy in systems management and monitoring is all all about.

In The Modern Data Center Adaptability is Key

Monday, May 10th, 2010

Lately the hype around “virtual blades” has been picking up.  For instance this article here at InfoWorld is just one of the many articles that describes using ‘small disk-less servers without any storage’.

This whole paradigm shift towards using more “embedded” clusters of low servers gets even more interesting when you consider the number of projects out there that are thinking of using low power mobile processors to build ‘clouds’.  For instance, this article talks about using Netbook chips to create a “Low-Power Cloud out of Wimpy Nodes”.

The moral of the story is, that as memory and network bandwidth capabilities and cost decrease exponentially, the proliferation of these very wonderful and creative solutions to complex data center problems will continue to emerge. It’s not a surprise that many of these capabilities arise out of the need to address the special challenges of massive virtualization (think VDI), and massive density to reduce power consumption and physical space requirements.

The question that should be in your mind is, with all of these great new paradigms emerging for hardware, how am I going to monitor it all?

The answer definitely doesn’t lie in locking yourself into a vendor that only has an interest in monitoring their own stack effectively (legacy, crusty, old guard vendors).

Clearly from the trends described above, having the ability to place probes across any hardware/virtual/software stack will continue to be important in these situations. Of even great importance is the ability to flexibly create, re-use, swap probes as the technology platform changes and still retain the context of how each of these components affect the performance and availability of the application services that power our enterprise.

The other answer that looks tempting, but that is equally dangerous, is the urge to select a new niche vendor for these new tool sets and stacks. The problem with this is that again you end up with a “stained glassed window” of point tools that force you to do “screen level integration”. As well, many of these solutions will become obsolete as these new server paradigms change rapidly. (Does anyone use a Leostream connection broker for VDI anymore for instance?)

Let’s avoid all of this, especially in a time when efficiency and “tools rationalization” is top of mind.

Any monitoring solution that expects to be able to survive this massive change must have an extensible plug-in architecture to allow for the rapid incorporation of  new metrics and allow for those metrics to be used in the context of the monitoring logic (no bolt-ons). Wouldn’t it be a bonus if the plug-in architecture was easy enough for your own staff to use to extend the platform without having to wait for your vendor?

Come join us on a webinar and see what a truly adaptable monitoring solution might be able to do for you.

The uptime difference “we make this look good”

Monday, May 3rd, 2010

MIB - I make this look goodThat’s right, I’m biting a line out of the movie Men in Black. You know, the moment when Will Smith turns to Tommy Lee Jones and he says “You know what the difference between me and you is? … I make this look good.”

What could this possibly have to do with Systems Management? (I use this question a lot in the blog…. it’s my signature line).

Follow me here people. Will Smith represents the new guard - he’s minty fresh, the good looking new guy, full of new ideas, full of new capabilities, and most importantly full of life. Tommy Lee Jones represents the old guard, sure he’s got lots of experience, sure he’s seasoned, but he’s so stuck up on how the MIB do things procedurally, the heritage of the MIB that he can no longer innovate. Does agent Smith have something to learn from the old guard in this movie… absolutely, but once learned, he runs the show.

Apply this to Systems Management, the old guard is too busy doing things the old way, with product offering that’s old, outdated and a mish mash of fragmented perspectives, weighed down by all the product ‘baggage’ that comes with too many cooks in one very old pot. When it comes to servicing their clients and prospects, when it comes to product improvements and enhancements, these old dogs have to jump through flaming hoops of fire, getting anything done at those organizations is like steering the Titanic.

That’s why I love working at uptime – our clients and prospects get results. This morning I demoed  new product enhancements that one of our clients wanted to see, enhancements the client asked for just 2 weeks ago. Guess what? It’s going to be an awesome week, because I get to deliver the good news to 2 other clients as well. This is the difference between the old guard and the new guard… we’re agile, we’re ready and we’re hungry.

People forget, that when evaluating products, you should be careful to not just evaluate the toolset, but to evaluate the people you will be investing in. Ask yourself the following questions:

  1. How reactive is the company to your needs and desires in simple interactions?
  2. What is the quality of the support offering?
  3. How flexible is the vendor to listening to your needs? How is the organization able to deliver to you the functionality that you and the rest of the market needs in a timely manner. Is there an agile product management process in place?
  4. Was the organization just bought or part of a major Old Guard vendor, will your feature requests get lost, or not be heard about for 12 to 24 months?
  5. Are the people you are working with true technologists, do they understand the market, do they understand your technical needs or are they ‘yet another salesman’ asking you ‘how many licenses do you need?’

Once you’ve had a long hard look at these questions, and realized that you’re with the old guard… don’t feel too down, get with the minty fresh program. Trust me, we don’t just make this look good – we make it feel good.

Here’s the clip of Will Smith from MIB, and ya, he sure makes it look good.

The “Real” Secret to IT Success

Monday, April 19th, 2010

So I swung over to Infoworld this morning over my cup of coffee and saw a headline that said “The real secret to IT success”. Wow! I thought – today I’m going to learn about fairies and unicorns! I couldn’t wait to learn the secret, so I excitedly clicked on the link….

Unfortunately at that point reality hit – Eric Knorr of Infoworld does an interview of Bob Lewis… of – you guessed it – Infoworld. Maybe Unicorns don’t exist after all.

Ok, so I’ll say, I am really not a fan of Bob Lewis. Not to be harsh on the guy, but he seems to really be promoting this whole “concept” that IT shouldn’t be thought of as a service. On the surface this seems like it could be plausible, dig a little deeper on the topic and you might start to feel like those theories are just picking at semantics. Want a sample of this stuff? Head over and read his article on the whole “concept” here (Run IT as a business — why that’s a train wreck waiting to happen).

So, is this blog post going to be totally about the merit of Bob Lewis’s theories? No… because in Bob’s article about the “The Real Secret to IT Success” there’s pretty much only one idea I really agree with –  and that’s his assertion that regardless of any process, the number one barrier to success in IT is a lack of communication and a lack of trust across silos.

Bob actually says it best himself:

“I know this is going to sound like I’m channeling Dr. Phil, but it’s still the right answer: In spite of all the panaceas out there — ITIL, COBIT, CMMI, and so on — relationships and trust come first. Without positive relationships and trust among participants, no process can work, all governance will be ineffective, and even the best employees will be hamstrung — tied up in conflict, bureaucracy, and rework”

Not sure why Bob thought he was channeling Dr. Phil… but he was channelling a whole lot of common sense.

This is where I totally diverge from Bob Lewis, I believe the conversation and trust comes from “visibility“. Having a toolset that allows your teams to quickly find the problem across the entire stack, and stop the internal finger pointing is the “key” to trust.

Just like a hockey team (sorry I’m Canadian), if your player’s on the ice are the best in their positions but can’t trust the other players to deliver, they won’t pass the puck.

In IT we do the same thing, when a call comes in we need to be able to pinpoint the area where the trouble is occuring. Let’s avoid the 30 minutes of all of our teams saying “Talk to network”, “talk to database”, “talk to firewall”, “talk to virtualization team”. Even worse, you have to tell the person who is calling to tell you that something is wrong with your infrastructure that you “don’t know what the problem is”, and that you have to call 5 different people in 5 sub departments to find out what’s going on.

Let your management solution tell you via alerts which team needs to be mobilized, with the data that the team needs to get the problem fixed ASAP.

On a longer term basis, you need reporting that accurately depicts the availability of the system, and clearly denotes which team is contributing the most to recorded outages against the app-stack. The point of this is not to promote a culture of “blame and shame”, it’s about having hard data to back up a real productive internal discussion about how to move forward. When the data is real, and everyone can agree on the source, it’s amazing how trust and pro-activity kick in across silos.

Make sure you have a systems management solution that eliminates the hand-waiving, make sure your teams can deliver systems that satisfy the business – without the finger pointing. Your management solution should be a catalyst for breaking through cross silo barriers and ensuring that no one team (database, firewall, network, or virtualization) becomes the new victim of the scapegoat syndrome we are all used to in this industry.

With uptime, always be sure your star players are ready to “pass the puck”.

Just in case your one of the rare few who actually want to RTFA – the original “Secret of IT Success” article at Infoworld is here.

Find Your Inner Fighter Pilot

Monday, April 12th, 2010

In systems management, we can learn alot from the mentality of a fighter pilot. What – you say, Ken’s been smoking the good stuff over the sunny Toronto weekend? What could a fighter pilot possibly have in common with someone in IT systems management?

A lot more than you think.

Think about it, what is a datacenter? A highly tuned combination of hardware and software designed to deliver services to the business. What is a Jet Fighter? A complex combination of millions of hardware components with a highly tuned set of software components designed to defend the pilot and provide the services nessecary for him to project his will at command. Wow, not so different?

So where have we gone wrong? What can we learn from the Jet Fighter Pilot? The difference is in approach. Just like the pilot and his cockpit we have huge arrays of data available to us through gauges, niche software, profiling tools, scripts… you name it we have it.  Guess what? When the pilot is in the heat of an engagement, he’s assessing his threats, he’s not sitting there fixating on a particular gauge. We need to stop fixating on niche tools, profilers and other specific metrics, we need something similar to a Pilot’s heads up display that will us to assess the biggest threats to the IT organization.

Worse, you’ve bought a tool that claims to do this, but rather than having a nice seamless HUD display or ”single pane of glass“, you have a “stainglass window” comprised of dozens of individual applications poorly duct-taped together.

Good thing uptime has a very specialized set of reporting capabilities to allow you to figure out where your major IT problem hotspots are, which infrastructure is suffering  infrequent downtimes, and where constant “5 minute problems” are sapping your team’s productivity.

All of the above issues ARE the major threat to IT, those are the things that make people wonder “Why aren’t we outsourcing this service? it NEVER works!”, this is the equivalent of having your jet fighter shot down.

Join me on one of our upcoming webinar series and find out how to unleash your inner fighter pilot.

Fall in Love for All the Right Reasons

Monday, March 15th, 2010

That’s right, this morning I decided to bite the slogan of E-Harmony. What does E-Harmony have to do with systems management?

Ever notice that picking a software vendor to do a major software rollout is much like trying to find a soul mate? You have all the same processes, all the same risks, and all the same possibilities for financial ruin. (Like my positive view on dating? Guess why I’m still single – ‘technically’).

The Lure – Just like meeting someone, the initial attraction is what meets the eye, it’s all about the flashy sell features, the nice collateral and the teaser features that stick in your mind.

The Dance – The vendor demos, the RFI’s, the bakeoffs, the sweet talking. You decide to check out some of her friends to make sure they can vouch for her, referrals are always reassuring.

The Pot Commit – You’ve become the internal champion for the product, no matter what’s wrong with things, you’re going to make a determined internal sell. Despite all the recommendations and feedback from your friends and family – your heart is set, you’ve found the apple of your eye.

The Fireworks – After a tumultuous courtship you finally get to the good part, and you sign on the dotted line. You “Shake Hands”.

The Honeymoon – You’ve not just bought the 1$ of software, you’ve also made sure to get the 10$ of training, so the implementation kickoff is happening and everyone is in love with your vendor. A few great kickoff meetings and everyone is excited about the vision of the future. Everything smells like a bed of roses.

The Reality Check – 12-24 months later, no more bed of roses, your entire team wonders where the dream of the single pane of glass went, all those sexy features you once were so excited about bore you and don’t meet your needs. You have that gutt-wrenching feeling that maybe this wasn’t what you had signed up for.

Your wondering where all your dreams of server monitoring have gone, how much of yourself you’ve lost in the process….

Luckily you’re strong, you’ve got a good team, you pick yourself up assess the damage, and get ready for the next adventure. Guess it’s time to log back into E-harmony and find another vendor?

Don’t get caught up in the cycle above, ditch e-harmony vendor dating, download uptime – install it in 7 minutes, and see what a real-life, healthy, and comfortable Server Monitoring initiative really feels like.

It’s OK, if you’re not convinced, go play the field first, when you’re done, come meet your match. You’re heart (ehem career) will thank you.

CA buys Nimsoft, not such a good deal for everybody

Thursday, March 11th, 2010

Wow, big news yesterday!  CA acquired Nimsoft for $350MM to access the MSP/cloud markets and to blend them into their portfolio of cloud offerings.  This acquisition is interesting for many reasons, most notably for CA’s stance that they will use Nimsoft’s offerings to access the mid-market (or emerging enterprises in CA parlance).

Mid-enterprises (under $2 Billion in revenue) are struggling with how to monitor their physical, virtual and cloud resources with minimal budget and staff. Nimsoft has aggressively marketed itself to large enterprises as a ‘Big 4’ replacement and its price and complexity reflect this.  CA’s acquisition of Nimsoft pushes them further out of reach for mid-enterprises and we expect them to be even less competitive in this market moving forward.

If you are a mid-enterprise company here are a number of reasons  why this is not a good deal for you:

1.       Increased Risk: There is risk investing in a product that doesn’t have a clear future. We question if this product will even remotely resemble itself in 12 months.

2.       It’s now a CA Product: Companies are no longer buying Nimsoft, they are buying a CA product. Anyone looking to move away from a Big 4 framework because of cost, complexity or support reasons should take care.

3.       Focused on MSP: CA’s plans moving forward involve using Nimsoft for their MSP offering. If companies are looking at Nimsoft as an all-in-one solution, it looks like Nimsoft may be forced to focus on MSP by CA. If you aren’t an MSP, there might be reason for concern.

4.       Nimsoft isn’t a Mid-enterprise Product: They focus on ‘Big 4’ enterprise replacement, just visit their website to see their market positioing on that. Accordingly, their complexity and cost is closer to ‘Big 4′ than mid-enterprise. As a part of CA, Nimsoft will move even further out of reach of the mid-market.

5.       CA doesn’t Sell to the Mid-enterprise Market: Mid-enterprise solutions need to be complete, easy-to-use, value priced and have great support. You should be skeptical that CA can provide that, given their track record.

All in all, the excitement in the system’s management space continues to be interesting (and shrinking).

Alex