Windows 11 24H2 detection fails on ZCM 23.4 with FTF 101 and Agent-Patch ZCM_23.4.0_FTF_Agent_Defect_768073_822002

Hi,

I just added the above mentioned patches to the Zone and followed (of cource) each step from documention, but within ZCC Summary page on a Windows 11 24H2 istays as Windows 11 x64.

The update worked fine on the bundle requirement setting for the operation System - Windows detection: "11.0.24H2 - Windows 11 Version 24H2" is available there.

Any ideas?

"The only two mistakes that can be done on ones way to championship is to not getting started and to not continue until the end."

  • Suggested Answer

    0  

    Here is a  Zip with a Custom_OSTargets.xml as well as a windowsVersionMappings.Properties file.

    24H2.zip

    Copy them to...

    ./etc/opt/microfocus/zenworks/windowsVersionMapping.properties

    and

    ./etc/opt/microfocus/zenworks/custom_ostargets.xml

    Then run....


    microfocus-zenworks-configure -c ZoneConfigUpdateConfigureAction
    microfocus-zenworks-configure -c SettingsConfigureAction -Dtype=CustomOSTarget -Dadd

    When the 2nd command runs, after a few minutes the screen should show the following...

    Note the Referenced to 24H2=2409 in the mapping file as well a 5 Operating Systems being added.

    2 for Mac Sonoma and 3 for the various flavors of 24H2.

    It's possible additional entries are needed for some flavors of 24H2, but this above should cover most.

    --

    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

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

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

  • 0 in reply to   

    Hey Craig,

    I did everything according documention and at the mentioned position, server answered:

    (/etc/opt/microfocus/zenworks/custom_ostargets.xml
    Following ostargets will be added :
    macOS Sonoma
    macOS Sonoma
    Windows 11 Professional N x64 Version 24H2
    Windows 11 Professional x64 Version 24H2
    Windows 11 Enterprise x64 Version 24H2
    Windows 11 Education x64 Version 24H2
    [2024.11.26-12:14:52] FINE: Updated 6 custom OS targets to database.)

    I remember Vikram saying, there is a device step to be done too.

    So I rather thing it is a problem in the Agent-Patch.

    "The only two mistakes that can be done on ones way to championship is to not getting started and to not continue until the end."

  • 0 in reply to 

    But of cource, I will run what is in your zip file ad give you a feedback Slight smile

    "The only two mistakes that can be done on ones way to championship is to not getting started and to not continue until the end."

  • 0   in reply to 

    Np Agent Patch required.....BUt the Version Mapping file is needed as well...

    --

    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

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

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

  • 0   in reply to   

    The agent patches are not needed for the Registration issue...The Agent Patches correct an issue where Windows will toss errors if certain files are not signed in 24H2 or later.

    --

    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

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

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

  • 0 in reply to   

    I just analysed your files from the zip archiv.

    Is this a typo in the following line?

    <ostarget>
    <name>windows11-240H2-pro-gen-x64</name>
    <product_name>Windows 11 Professional x64 Version 24H2</product_name>

    Apart from that, I can't find any differences - neither in windowsVersionMapping.properties, nor in custom_ostargets.xml

    "The only two mistakes that can be done on ones way to championship is to not getting started and to not continue until the end."