O R G A N I C / F E R T I L I Z E R: 07.10

Jul 29, 2010

opalis: log files and locations

folder path file name description
\opalis software\opalis integration server\action server\logs opalisactionservice*.log

policymodule*.log
exceptions generated by the action server service (connection errors, etc)

note that failures in modules are logged in the policymodule logs. valuable if you're tracking down additional information during run failures.
\opalis software\opalis integration server\client\logs oisclient*.log log of client launch capturing configuration state at the time of launch (computer name, user name, etc)
\opalis software\opalis integration server\management service\logs actionserverwatchdog*.log
opalismanagementservice*.log
exceptions generated by the action server (useful for finding environmental problems e.g. database connect failures)

enabling the default location of trace logging creates log files in this location
\opalis software\opalis integration server\management service\components\logs *actionserver*.log
*foundationobjects*.log
*<ip pack>.log
installations of action servers, foundation objects, and integration packs (reflected msi logs)
\opalis software\opalis integration server\management service\console oismc*.log deployments of action servers, clients, and integration packs
<operator console>\server\default\log boot.log
server.log
log of operator console service for start up and operation.

trace logging: http://blogs.technet.com/b/opalis/archive/2010/05/12/enabling-trace-logging-in-opalis.aspx

Jul 27, 2010

granting remote wmi permissions

realizing that this information being embedded in an opalis blog post may prove obscure and difficult to locate, I'm reproducing it here.  this is basically a summary of how I managed to grant rights to the opalis action server account in order for it to have wmi query access to a windows server 2003 sp2 server.

 

  • dcom permissions adjustment (on the sccm server)
    • launch dcomcnfg.
    • navigate to component services \ computers \ my computer.  right-click my computer, choose properties.
    • under the com security tab, click edit limits in both sections.
    • grant the following rights to the ois action account:
      • remote access
      • remote launch
      • remote activation
    • navigate to the dcom config section under my computer, locate windows management instrumentation
    • right-click windows management instruction, choose properties. 
    • under the security tab, click edit under the launch and activation permissions section.
    • grant the ois action account the following permissions:
      • remote launch
      • remote activation
  • sccm permissions
    collections read
      read resource
    advertisement read
    deployment read
    package read

     

  • Jul 13, 2010

    scom: overloading the consolidation module (and how to avoid it)

    in a previous post titled using repeat count to detect a problem in a window of time I described a process whereby you can using consolidation settings, you can detect something happening in a window of time.  for example, event id 529 equals "bad password" basically.  if we alerted on every bad password, that'd be problematic.  however, if we looked at every one and then alerted whenever the count of bad passwords for a single user exceeded a threshold, that might be useful.

    apparently there's this concept called a "consolidation module".  this module has a limit of 128k.  if you go beyond this limit, you tend to overload the module and cause the event scraping to backlog.  on very active domain controllers, using a large sliding window, it's very easy to overrun this limit.  it results in odd errors like this:

    (event id 11105)

    The Microsoft Operations Manager Condolidator Module failed to save the state after processing and might loose data. 
    Error: 0x80070057
    One or more workflows were affected by this.
     
     
    The Windows Event Log Provider monitoring the System Event Log is 317 minutes behind in processing events. This can occur when the provider is restarted after being offline for some time, or there are too many events to be handled by the workflow.

    One or more workflows were affected by this.

    before you try to correct me, I copied and pasted that.  I know how to spell "consolidator" and "lose data".  I mentioned fixing this.  there are two ways.  the most obvious is by reducing your sliding window time frame so that you're not collecting as many events in a given period of time.  the second way is to simply set the storestate value to false.  the first one, you should be able to derive quite easily.  modifying the storestate value tells the agent not to store the internal state.  the problem here, albeit a small exchange, is that the state does not survive healthservice restarts.

    as for the second method, it's not available in the console (surprise, surprise!) and must be done by editing the xml (surprise, surprise!).  so, you'll need to export your rule, modify your xml, and import it again.  once you have your xml, locate an area of the xml that should look suspiciously like this:

    <Consolidator>
    <ConsolidationProperties>
    <PropertyXPathQuery>EventDisplayNumber</PropertyXPathQuery>
    <PropertyXPathQuery>PublisherName</PropertyXPathQuery>
    <PropertyXPathQuery>LoggingComputer</PropertyXPathQuery>
    <PropertyXPathQuery>Params/Param[1]</PropertyXPathQuery>
    <PropertyXPathQuery>Params/Param[2]</PropertyXPathQuery>
    </ConsolidationProperties>
    <TimeControl>
    <WithinTimeSchedule>
    <Interval>1800</Interval>
    </WithinTimeSchedule>
    </TimeControl>
    <CountingCondition>
    <Count>20</Count>
    <CountMode>OnNewItemTestOutputRestart_OnTimerSlideByOne</CountMode>
    </CountingCondition>
    </Consolidator>
     
     
    okay, now modify it to add this one entry noted below.
     
    <Consolidator>
    <ConsolidationProperties>
    <PropertyXPathQuery>EventDisplayNumber</PropertyXPathQuery>
    <PropertyXPathQuery>PublisherName</PropertyXPathQuery>
    <PropertyXPathQuery>LoggingComputer</PropertyXPathQuery>
    <PropertyXPathQuery>Params/Param[1]</PropertyXPathQuery>
    <PropertyXPathQuery>Params/Param[2]</PropertyXPathQuery>
    </ConsolidationProperties>
    <StoreState>false</StoreState>
    <TimeControl>
    <WithinTimeSchedule>
    <Interval>1800</Interval>
    </WithinTimeSchedule>
    </TimeControl>
    <CountingCondition>
    <Count>20</Count>
    <CountMode>OnNewItemTestOutputRestart_OnTimerSlideByOne</CountMode>
    </CountingCondition>
    </Consolidator>

    after making the modification, import it back in and the problems should go away.

    Jul 8, 2010

    new url for opsmgr management pack catalog

    this was just released.  if you’re familiar with microsoft pinpoint (affectionately dubbed pain point by some), then you know how horribly difficult it was to use.  well guess what?  they just revamped the site and have released it.  it promises a much easier, sortable method for finding the management pack you’re looking for.  time will tell.  here’s the link: http://pinpoint.microsoft.com/en-US/systemcenter.

    image