- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2025 12:21 AM
HI all - Hope everyone is doing good.
Our customer has started deploying windows server 2025 in the environment. We use ServiceNow discovery but it unable to identify the OS as 2025 or classify the servers as servers.
The article says that 2022 is the last version that is supported yet.
How have you resolved this issue at your workplace ?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2025 07:09 AM
Hi @ravikamma
We have the same problem and open a case on servicenow support.
They confirm that Windows Server 2025 is currently not supported.
their answer:
Issue:
Windows server 2025 discovery
Investigation Summary:
I have reviewed the below:
Windows Classifiers:
https://<instancename>.service-now.com/discovery_classy_windows_list.do?sysparm_userpref_module=a521...Currently OOB, we don't have a classifier for Windows Server 2025 Standard.
Solution Proposed:
Windows Server 2025 is not yet supported by discovery as per the latest documentation:
https://www.servicenow.com/docs/bundle/xanadu-it-operations-management/page/product/discovery/refere...Currently supported Windows versions:
For IPv4 discovery:
Windows Workstation 7, 8, 10
Windows Server versions:
2008
2008R2
2012R2
2016
2019
2022For IPv6 discovery:
Windows 2019 (10.0.17763)
Windows Server 2016
Windows Desktop 10
Windows 2019 DatacenterHowever, if you wish to discover 2025 devices:
As the PowerShell/WMI stays the same, you will most likely have to create a custom classifier for it until one comes to OOB.
If we are getting the data in the pattern, the new classifier along with the Classification Criteria can be created that aligns with the OOB Windows 2022 Server classification. The CI should be updated successfully with the Windows 2025 server data.
Below is some background and how-to if needed from the community for the 2022 version before it was added OOB
https://www.servicenow.com/community/itom-blog/2022-is-that-an-operating-system-already/ba-p/2273324We expect to cover the new version in future releases, and it will be updated in the release notes.
Please try the above in a sub prod environment and let me know if you need any help in creating a custom classifier, but please note that this is out of the scope of support and I will do my best to help you reach the goal.
Hope this helps.
Regards,
Karine
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-04-2025 12:10 PM
When 2022 came out we were able to go to the Windows Classifications discovery_classy_windows and add an entry for 2022 that was basically a copy of the of the 2019 classification with 2022 specified instead of 2019.
That is not working with 2025. Has anyone figured out what is different on 2025?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-04-2025 12:26 PM
Actually I found that when I created my 2025 classifier it was initially inactive. Once I activated it worked. So if you follow the example for 2022 it will work for 2025.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2025 01:49 PM
Windows 2025 was released as GA on 11/1/2024. How is it that after 8+ months ServiceNow hasn't updated the discovery pattern. Before it was GA there was a preview version so I don't see any reason why this wouldn't have been updated along with Microsoft's GA release.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-23-2025 03:57 AM
@StephenM There is an update set fix provided by ServiceNow in the below KB until the Patterns gets the update.
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2008561
