locked
nworks and not discovering using registry... RRS feed

  • Question

  • Hello, 

     

    I've problem with nworks/Veeam VWare management pack - but problem looks generic, not strict related with those MP. 

    In my environment don't work the simplest  discover based on registry (in that MP). I as for Veeam supoort but they claims that on their side evrything is ok. :(

    Following code don't discover anything (in that case: don't fill nworks.VMware.VEM.Collector properties): 

     

     <Discovery ID="nworks.VMware.VEM.Collector.Discovery" Enabled="true" Target="Windows!Microsoft.Windows.Computer" ConfirmDelivery="false" Remotable="false" Priority="Normal">
      <Category>Discovery</Category>
      <DiscoveryTypes>
       <DiscoveryClass TypeID="nworks.VMware.VEM.Collector">
       <Property TypeID="System!System.Entity" PropertyID="DisplayName" />
       <Property TypeID="nworks.VMware.VEM.Collector" PropertyID="VEMServer" />
       </DiscoveryClass>
      </DiscoveryTypes>
      <DataSource ID="DS" TypeID="Windows!Microsoft.Windows.FilteredRegistryDiscoveryProvider">
       <ComputerName>.</ComputerName>
       <RegistryAttributeDefinitions>
       <RegistryAttributeDefinition>
        <AttributeName>DisplayName</AttributeName>
        <Path>SYSTEM\CurrentControlSet\Services\nworksVIC\DisplayName</Path>
        <PathType>1</PathType>
        <AttributeType>1</AttributeType>
       </RegistryAttributeDefinition>
       </RegistryAttributeDefinitions>
       <Frequency>14400</Frequency>
       <ClassId>$MPElement[Name="nworks.VMware.VEM.Collector"]$</ClassId>
       <InstanceSettings>
       <Settings>
        <Setting>
        <Name>$MPElement[Name="Windows!Microsoft.Windows.Computer"]/PrincipalName$</Name>
        <Value>$Target/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$</Value>
        </Setting>
        <Setting>
        <Name>$MPElement[Name="nworks.VMware.VEM.Collector"]/VEMServer$</Name>
        <Value>$Target/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$</Value>
        </Setting>
        <Setting>
        <Name>$MPElement[Name="System!System.Entity"]/DisplayName$</Name>
        <Value>$Data/Values/DisplayName$</Value>
        </Setting>
       </Settings>
       </InstanceSettings>
       <Expression>
       <SimpleExpression>
        <ValueExpression>
        <XPathQuery>Values/DisplayName</XPathQuery>
        </ValueExpression>
        <Operator>Equal</Operator>
        <ValueExpression>
        <Value Type="String">nworks Virtual Infrastructure Collector</Value>
        </ValueExpression>
       </SimpleExpression>
       </Expression>
      </DataSource>
      </Discovery>
    

     

    Other MP (not only generic for Exchange, Windows, SQL but also custom with similar schema) discover properties ok. 

    Any idea hot to debug this? 

     

     

     


    http://ziembor.pl/
    Monday, May 16, 2011 3:34 PM

Answers

  • so start by checking if the keys exists and the value is set correct. if that is ok, create a wmi script to check read the key and log the stringvalue to a file. run this under the action account credentials.


    Rob Korving
    http://jama00.wordpress.com/
    • Marked as answer by Yog Li Wednesday, May 25, 2011 9:47 AM
    • Unmarked as answer by Ziemek Borowski Wednesday, May 25, 2011 9:49 AM
    • Marked as answer by Ziemek Borowski Wednesday, May 25, 2011 9:49 AM
    Monday, May 16, 2011 4:38 PM

All replies

  • Lets explore what you mean when you say no simple registry discovery functions in your environment.  There in is probably the answer.

    I cannot think of an MP that doesn't start off by doing a registry key check.

    Can you look in the event log named Operations Manager on the agent involved and let us know if there are errors there?  How about on your RMS?  Anything suspicious about dropping a discovery?

     

     


    Microsoft Corporation
    Monday, May 16, 2011 3:40 PM
  • I say: other simple registy discovery works ok in my enviroment. It don't work only in that MP, I'm afraid. Also I check Overrides (even unload MP and load again - for make  sure that it will broke any overrides and so on). 

    I just create MP like in bellow and it found object

     

    <ManagementPack ContentReadable="true" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
     <Manifest>
     <Identity>
      <ID>dcs.zb.simpleWindowsAppRegistry</ID>
      <Version>1.0.0.1</Version>
     </Identity>
     <Name>dcs.zb.simpleWindowsAppRegistry</Name>
     <References>
      <Reference Alias="SC">
      <ID>Microsoft.SystemCenter.Library</ID>
      <Version>6.1.7221.0</Version>
      <PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
      </Reference>
      <Reference Alias="Windows">
      <ID>Microsoft.Windows.Library</ID>
      <Version>6.1.7221.0</Version>
      <PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
      </Reference>
      <Reference Alias="Health">
      <ID>System.Health.Library</ID>
      <Version>6.1.7221.0</Version>
      <PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
      </Reference>
      <Reference Alias="System">
      <ID>System.Library</ID>
      <Version>6.1.7221.0</Version>
      <PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
      </Reference>
      <Reference Alias="Performance">
      <ID>System.Performance.Library</ID>
      <Version>6.1.7221.0</Version>
      <PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
      </Reference>
     </References>
     </Manifest>
     <TypeDefinitions>
     <EntityTypes>
      <ClassTypes>
      <ClassType ID="dcs.zb.simpleWindowsAppRegistry.VIC" Accessibility="Internal" Abstract="false" Base="Windows!Microsoft.Windows.LocalApplication" Hosted="true" Singleton="false" />
      </ClassTypes>
     </EntityTypes>
     </TypeDefinitions>
     <Monitoring>
     <Discoveries>
      <Discovery ID="dcs.zb.simpleWindowsAppRegistry.VIC.Discovery" Enabled="true" Target="Windows!Microsoft.Windows.Computer" ConfirmDelivery="false" Remotable="true" Priority="Normal">
      <Category>Discovery</Category>
      <DiscoveryTypes />
      <DataSource ID="DS" TypeID="Windows!Microsoft.Windows.FilteredRegistryDiscoveryProvider">
       <ComputerName>$Target/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
       <RegistryAttributeDefinitions>
       <RegistryAttributeDefinition>
        <AttributeName>VICExist</AttributeName>
        <Path>SYSTEM\CurrentControlSet\Services\nworksVIC\DisplayName</Path>
        <PathType>1</PathType>
        <AttributeType>1</AttributeType>
       </RegistryAttributeDefinition>
       </RegistryAttributeDefinitions>
       <Frequency>120</Frequency>
       <ClassId>$MPElement[Name="dcs.zb.simpleWindowsAppRegistry.VIC"]$</ClassId>
       <InstanceSettings>
       <Settings>
        <Setting>
        <Name>$MPElement[Name="Windows!Microsoft.Windows.Computer"]/PrincipalName$</Name>
        <Value>$Target/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$</Value>
        </Setting>
       </Settings>
       </InstanceSettings>
       <Expression>
       <RegExExpression>
        <ValueExpression>
        <XPathQuery Type="String">Values/VICExist</XPathQuery>
        </ValueExpression>
        <Operator>ContainsSubstring</Operator>
        <Pattern>l</Pattern>
       </RegExExpression>
       </Expression>
      </DataSource>
      </Discovery>
     </Discoveries>
     </Monitoring>
     <LanguagePacks>
     <LanguagePack ID="ENU" IsDefault="true">
      <DisplayStrings>
      <DisplayString ElementID="dcs.zb.simpleWindowsAppRegistry">
       <Name>dcs.zb.simpleWindowsAppRegistry</Name>
      </DisplayString>
      <DisplayString ElementID="dcs.zb.simpleWindowsAppRegistry.VIC">
       <Name>dcs.zb.simpleWindowsAppRegistry.VIC</Name>
      </DisplayString>
      <DisplayString ElementID="dcs.zb.simpleWindowsAppRegistry.VIC.Discovery">
       <Name>dcs.zb.simpleWindowsAppRegistry.VIC Discovery</Name>
      </DisplayString>
      </DisplayStrings>
     </LanguagePack>
     </LanguagePacks>
    </ManagementPack>
    

     

    I see only one error/warning on that machine OpsMgr eventlog (that machine is RMS also :()

     

     

    Log Name:  Operations Manager
    
    Source:  HealthService
    
    Event ID:  1103
    
    Task Category: Health Service
    
    Level:   Warning
    
    Description: Summary: 122 rule(s)/monitor(s) failed and got unloaded, 122 of them reached the failure limit that prevents automatic reload. Management group "DCSOM". This is summary only event, please see other events with descriptions of unloaded rule(s)/monitor(s).

    with neighbored 

     

    Log Name:  Operations Manager
    Source:  Health Service Modules
    Date:   5/16/2011 6:11:58 PM
    Event ID:  21406
    Task Category: None
    Level:   Warning
    Description: The process started at 6:11:58 PM failed to create System.PropertyBagData. Errors found in output:
    
    E:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 4\76529\CollectLogicalDiskStatistics.vbs(94, 9) (null): Data error (cyclic redundancy check). 
    
    Command executed:	"C:\Windows\system32\cscript.exe" /nologo "CollectLogicalDiskStatistics.vbs" false
    
    Working Directory:	E:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 4\76529\ 
    
    One or more workflows were affected by this. 
    Workflow name: Windows.LogicalDrives.CollectTotalMFTSize.Rule 
    Instance name: E: 
    Instance ID: {4C0A7916-DF32-529F-67A8-F4350AF5476D} 
    Management group: XYZ
    

     

     

     

     


    http://ziembor.pl/
    Monday, May 16, 2011 4:17 PM
  • so start by checking if the keys exists and the value is set correct. if that is ok, create a wmi script to check read the key and log the stringvalue to a file. run this under the action account credentials.


    Rob Korving
    http://jama00.wordpress.com/
    • Marked as answer by Yog Li Wednesday, May 25, 2011 9:47 AM
    • Unmarked as answer by Ziemek Borowski Wednesday, May 25, 2011 9:49 AM
    • Marked as answer by Ziemek Borowski Wednesday, May 25, 2011 9:49 AM
    Monday, May 16, 2011 4:38 PM
  • Your suggestion was quite good: problem was with AA rights. :/.

     


    http://ziembor.pl/
    Wednesday, May 25, 2011 9:49 AM