Latest Updates: scom RSS

  • Tick, Tick, Tick, … Boom!

    Mirco 8:05 on Wednesday, 3. December 2008 | View Comments Permalink | Reply
    Tags: , blaster, breach, , clean, cleaning, consultant, coordination, , infection, , , , , patch, patches, scom, , , symantec, update, , , , ,

    I still don’t know why I gave into my manager wanting me to postpone my scheduled vacation by a week, so he has some billable hours to report in December.

    So here I was, stumbling into the office after a terrible drive through heavy traffic and a 20km detour because of a roadblock caused by a serious accident. As expected most of my customers administrators where either still not in office or in a meeting. I start the computer and fire up Outlook and the Operations Manager Console, and… Uh-Oh, this can’t be good.

    I was looking at about 1000 critical alerts, all less than 36 hours old and of the same type.

    It turned out that a new Windows worm has appeared over the weekend, infecting computers without a previously released patch and/or old versions of Antivirus Software.

    To say I was surprised of this sort of fallout would be … a huge lie, since I kept telling every responsible stakeholder for months this could be happening anytime at the way they are handling update and patch distribution.

    And it continued to play out just as I had expected it would. Someone found the single patch that would prevent an infection, and everyone with an Administrator account jumped at any server they could get a hold on to install exactly this single patch manually, instead of installing the other 28 – 79 missing patches along the way.

    It also reminded some of them that I had published a process on how to identify and classify servers for automatic update distribution. After all this document was available to everyone for the last few months and presented to management for consideration.

    Two days later most of the monitored servers are responding again, which doesn’t imply they are no longer infected, just patched. But as far as I can tell we are only monitoring about 60% of all servers after all.

    Since there is no active WSUS on the network, all patches had to be downloaded from Microsoft to the servers which took hours. The worm was putting so much additional traffic on the network that the proxy servers collapsed several times. User where constantly complaining about service and accessibility.

    The last company I witnessed this kind of chaos after a virus out brake was during the Blaster era (2001). It took them less than a month after this incident to implement strict policies and processes to prevent this from happening again. And as far as I know it never has since.

    Knowing there are still companies like my current customer out there, that don’t have a clue about processes, security and management only fill me with the assurance that there is still a great potential for future business, if only they would listen to their consultants.

    That’s why the pay us, right?

     
  • SCOM Agent Trouble

    Mirco 13:16 on Thursday, 28. August 2008 | View Comments Permalink | Reply
    Tags: -2130771964, , console, , , install, , msi, , restart, scom, , solution, , troubleshooting, uninstall

    Two weeks ago I installed the KB954049 on our Operations Manager servers. This “allows” me to update all of our 1500 agents, that are currently deployed.

    Four days, some Alerts form the IDS and multiple retries later there are still 60 agents left and refusing every attempt to be updated to version 6.0.6278.32. I’m still not sure why a domain administrator gets an “Access Denied” when trying to initiate a remote installation but I will figure this out, eventually.

    Today I noticed something new. Several, already updated Agents are grayed out on the status view. The servers are up an running, according to ping. A short look at the Computer Management shows the Agent is running too, but when I try to restart the service I’m prompted with some error message and the ID: -2130771964.

    Unfortunately Google isn’t a great help finding this error. There are only a handful results that focus on installing agents, but I have trouble restarting the service.

    My next thought was to try the Change/Repair option in “Add/Remove Software”, which stopped with the same Error code as restarting the service. Somebody must have been very creative in defining error codes for these agents.

    OK, if I can’t repair it, maybe I can uninstall it… and it worked, with the slight limitation that the uninstaller was unable to remove the installation folder.

    The next step was redistributing the Agent from the OpsMgr console, which went through with no errors at all.

     
  • Getting the 100 biggest Agent Queues out of your Operations Manager Database

    Mirco 16:00 on Tuesday, 22. July 2008 | View Comments Permalink | Reply
    Tags: , , center, database, datawarehouse, , , , , , query, queue, scom, , , systemcenter, usage

    Getting a decent overview of you Operations Manager Agents sometimes is a bit hard. There’s a nice graph to display the “Send Queue % Usage” but you have to click through every agent status to find the interesting ones. Most likely the ones with a high percentage status.

    Another way, although with less current data would be to query your Data Warehouse with the following statement

    SELECT     TOP (100) vManagedEntity.Path,
                         vPerformanceRule.CounterName,
                         Perf.vPerfHourly.DateTime,
                         Perf.vPerfHourly.AverageValue AS Avg,
                         Perf.vPerfHourly.MinValue AS Min,
                         Perf.vPerfHourly.MaxValue AS Max
    FROM       Perf.vPerfHourly
    INNER JOIN vManagedEntity ON Perf.vPerfHourly.ManagedEntityRowId = vManagedEntity.ManagedEntityRowId
    INNER JOIN vPerformanceRuleInstance ON Perf.vPerfHourly.PerformanceRuleInstanceRowId = vPerformanceRuleInstance.PerformanceRuleInstanceRowId
    INNER JOIN vPerformanceRule ON vPerformanceRuleInstance.RuleRowId = vPerformanceRule.RuleRowId
    WHERE      (vPerformanceRule.CounterName LIKE N'%send queue % used')
    ORDER BY   Perf.vPerfHourly.DateTime DESC,
               Avg DESC

    This query returns the 100 Queue with the highest fill rate. Note, that data in the Data Warehouse DB can be several hours behind the Operations Database.

     
  • New Operations Manager 2007 Performance and Scalability Whitepaper

    Mirco 15:54 on Thursday, 17. April 2008 | View Comments Permalink | Reply
    Tags: , best practice, deployment, guide, manual, mgr, , , , scom

    This document describes performance and scalability guidelines to consider when planning a Microsoft System Center Operations Manager 2007 deployment.

    Download here.

    Sadly there’s still no new info on the release of the Operations Manager Model for System Center Capacity Planner 2007.

     
c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
esc
cancel