Ten Reasons to Use OpsMgr 2007

So where have we been, you might ask? Finishing content on our forthcoming book, Microsoft System Center Operations Manager 2007 Unleashed! Its off to production now.

In August 2006, we published an article titled In a Nutshell: 10 Compelling Reasons to use MOM. As a precursor to our OpsMgr 2007 Unleashed book, we are listing ten reasons to use OpsMgr 2007. (While some of the reasons may sound familiar, the fact that many have changed only points to the large architectural differences between the two versions of Operations Manager!)

Ten reasons to use OpsMgr 2007:

  1. The bulk of your department’s budget goes towards maintaining current systems and services, rather than using the bucks to hire people to manage those assets or develop new systems.
  2. You realize system monitoring would be much easier with a single view of the health of your environment, including the applications and services running in production.
  3. You feel stuck in the IT version of the movie Groundhog Day – you solve the same problems over and over again every day in exactly the same way, except unlike in the movie, here you and your systems can really die. Plus, this is not a particularly efficient way to maintain operations.
  4. You don’t have enough internal manpower (or brainpower) to solve problems as they come up, and consultants aren’t cheap.
  5. You find out there are problems when users (or upper management) start calling you. While this mechanism is actually quite effective in getting your attention, it’s somewhat stress inducing and definitely not proactive.
  6. You realize that even though your servers are humming along just fine, you have no idea how your client applications are actually performing against what is running on those servers. This makes it tough to know if there are latency issues.
  7. Complying with regulations such as Sarbanes-Oxley takes up all the time you once used to do your real job.
  8. You would be more productive if you weren’t monitoring your production environment all day … and night. Plus during lunch and vacation.
  9. Your production environment is so diverse and widespread that when there’s a problem, you don’t even know where to start looking!
  10. You don’t have the time to write down all the troubleshooting information that is in your brain, and your boss is concerned you might be hit by a truck (or want to take that vacation). This probably is not the best way to run a production environment.

While these ten points contain some humor and a bit of satire, if any of these themes resonate with you, you really owe it to yourself to investigate OpsMgr 2007. These "pain points" are common to almost all users of Microsoft technologies, and System Center Operations Manger 2007 resolves them to a great degree.

With SP1 close to release – including 20 fixes and usability improvements (as of the RC, see the fix list at http://support.microsoft.com/kb/944443) – you will want to read about how to use OpsMgr 2007 for monitoring your enterprise and solving your operations management challenges. Check out our forthcoming book, listed on Amazon at http://tinyurl.com/27mqnm.

This entry was posted in Operations Manager 2007. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s