Does Windows Server 2025 already work as a managed device, even if it is not officially supported?
Has anyone created a custom_ostargets.xml for Windows Server 2025, or are these no longer necessary?
Cybersecurity
DevOps Cloud
IT Operations Cloud
If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more
Does Windows Server 2025 already work as a managed device, even if it is not officially supported?
Has anyone created a custom_ostargets.xml for Windows Server 2025, or are these no longer necessary?
Since 2025 came out after the planned release for ZCM 24.4, it is not in the OS Targets and not officially supported.
It will fail to register with an -21 error.
I did create a Dev Ticket to get support added.
--
I have not yet made an OSTarget to allow it to register.
I "SUSPEC"T it will work just fine on once registered with a 24.4 agent as it should be highly similar to Win 11 24H2.
Custom_Ostargets.xml CAN still be used and created, though Server Side patches now often add the support w/o the need for that.
There WAS a defect in the On-line Docs around the process of creating the customer_ostargets.xml.....Somewhere along the lines, one command was missed. I'm not sure if its been added back....
If I get a chance...I will try and work up something....while also crossing my fingers dev moves quickly on official support....
I might suggest an SR if you possibly can...then it can be associated with the current Dev ticket...
The more folks that proactively ask for it...the higher the priority..
If you honestly care about Windows 2025 Support in the VERY NEAR TERM...try making a ticket and ask to reference OCTIM40D827083
Otherwise, support will no doubt be added but possibly with a lesser priority versus over other issues...
--
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
Hi
About Win23.4...whether support Win2025 on FTF101 or future ?
I check FTF101 seem support win11 24H2...but seem no Win2025 in list
I build a new win2025...install agent package...it seem register fail..and I test manual register...got return code: -21 Could not determine device type
Wencheng
Windows 2025 came out after 24.4. It should be supported in later versions. You can use the steps for creating a Custom OS Targets so it will register. I would not expect a code issue beyond the need to add a Custom OS. Support should most likely be manually added in a future updtae.
--
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
Hi Craig Wilson
I add a section for windows server 2025 like below:
=======================
<ostarget>
<name>windowsserver-2025-24H2-std-gen-x64</name>
<product_name>Windows Server 2025 Standard Version 24H2</product_name>
<version>11.0.2409</version>
<arch>x86_64</arch>
<vendor>Microsoft</vendor>
<pkgmgr>msi</pkgmgr>
<primary_role>Server</primary_role>
<platform>Windows</platform>
<support_pack>0</support_pack>
<build_number>26100</build_number>
<detect><![CDATA[<OSVersion substring="Windows Server 2025 24H2 Standard (Build 26100)" />]]></detect>
</ostarget>
==========================
then run the"
microfocus-zenworks-configure -c ZoneConfigUpdateConfigureAction" &
microfocus-zenworks-configure -c Start
but windows server 2025 still register fail (error code:-21)
Whether my setting parameters are incorrect ??
Thanks!!!
Wencheng
Hi Craig Wilson
I try to use customOS to let win2025 register...but still fail.
I created a case #03042011 for support help to modity my setting about win2025.
but support engineer sied the 23.4 does not support win2025 , even I use customerOS...
23.4 lifecycle until 30 Nov 2026...I believe it sould be upgrade its support matrix.
Could you help me about this case ?
Wencheng
HI All
I modify my customOS xml and add to DB as screenshot (I uuse 24.4 lab)
then restart ZCM Service, but agent still register fail
Note: I made a KB on how to do it.
https://portal.microfocus.com/s/article/KM000037835?language=en_US
There are tips on how to identify the required string in the event it is slightly different than the ones I included.
--
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
HI Craig Wilson
my case engineer provide the same customOS setting to me...then I did your procedure
microfocus-zenworks-configure -c ZoneConfigUpdateConfigureAction microfocus-zenworks-configure -c SettingsConfigureAction -Dtype=CustomOSTarget -Dadd
after command perform...both win2025 item show in the message.
then I restart ZCM Service...
But still got -21 message, engineer let me modify two line as below
=============(remove "Datacenter Edition" and "Server Datacenter Edition"
)===========
<detect><![CDATA[<OSVersion substring="Windows Server 2022 24H2 64 (full installation) (Build 26100)"/>]]></detect>
and
<detect><![CDATA[<OSVersion substring="Windows Server 2022 24H2 64 (Build 26100)"/>]]></detect>
then rerun import procedure...still got the same result.
Now this case still open
Wencheng
CustomOS.zip