Collection Data Form Read Registry

Hi All

    I want to enable Collection Data Form (CDF) to read .net registry

then I create 2 custom attribute then add to CDF , I set display and editable to that me verify

the autofile I  set below:

first attribute be set HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full\Version

another attribute set HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full\Release

then inventory setting also enable CDF.

But even I run zac inv -f scannow....these attributes still not read registry...

I had tested it on ZCM10.x...then I did not set anymore...

who has similar experience on 2020.3 or provide suggestion that whether I make a mistake ?

Thanks!!

Wencheng

  • You need the CDF option for the CDF data to be collected.  It is not collected by default.

    "zac inv cdf"

    --

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks

  • Hi 

        I  had set registry no matter start with HKLM or HKEY_LOCAL_MACHINE ....the setting only work fine on ZCM Agent 2020.3 version.

    2017.2.0/2017.4.0/2017.4.1 these versions seem could not read registry.

    Wencheng

  • Hi  

        after I show my issue to case engineer....when primary server is 2020.3 version with FTF 662 ....the CDF only support 2020.3 agent....whenn agent are old agent (2017.2.0/2017.4.0/2017.4.1) ....the CDF work fail.no matter register or window env value.

    Wencheng

  • Suggested Answer

    The agent version should not matter since the code has not really changed in a long time.  However, ZCM 2017.x is no longer a supported product and has not been for many years.  It is important for many reasons to get upgraded to a supported version. ZCM 20.3 is simply the oldest supported version with 23.3 being the current version.

    To initiate the collection of "CDF" data from the command line you need to run "ZAC INV CDF"

    Furthermore, CDF data is NOT COLLECTED during the scheduled "Inventory Schedule".  One must configure the "Collection Data Form Schedule".    CDF Collection is a totally separate process and most likely is not being told to collect versus being a version issue.

    --

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks

  •   

         Because the all testing procedure was verified by case engineer...At the zone invventory setting , all 2020.3 agents could read registry , but 2017.x agent all failed. So it seem base on agent version issue.

         I want to do advanced CDF testing...could you kindly provide which file the CDF function use ?

        another question that you said "ZCM 20.3 is simply the oldest supported version with 23.3 being the current version." I do understand....because on SLD...I only see the 2020.2 version and could ger 2020.4 update and see FTF964 for 2020 update3....I do not see 23.3 version

  • Look under ZCM instead of ZPM, it should be there for ZPM but is likely an oversite.

    I'm not sure what you mean by which "FILE" the CDF Function uses? 

    Here is the link from ZENeworks 2017 Update 1 for collecting from the registry.

    https://www.novell.com/documentation/zenworks-2017-update-1/zen_inventory/data/ba6nmtv.html  It shows the same docs for reading the registry.

    --

    --

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks

  • HI  

        1.Thanks , Isaw the 23.3 version on ZCM product.

         2. I just want to know the file list (exe / dll files) when I run "zac inv cdf" , they will be use.

         3. about registry setting ....I try to start with HKLM or HKEY_LOCAL_MACHINE to read registry....but the CDF Windows (I select display), only 2020.3 agent could read registry , the CDF window is empty vaule in these columes.

    Wenchneg

  • #2 - It is built into the ZENworks Service Itself...No separate files.  

    In regards to the older agents, I always worked and there are not any bugs...but those versions are no longer supported in any fashion.  17.x agents in 23.3 zones are beyond unsupported because that is a never-supported scenario and never tested.  The testing is primarily limited to their ability to update to 23.3.  The expectation would be they would be updated to supported versions and versus testing the supportability of an unsupported configuration.

    --

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks

  • Hi

        you said for older agent , always worked and there are not any bug ...so your older agent include 2017.x version ?

    now  my primary server still keep 2020.3 with ftf964 not 23.3....

    Wencheng