how to configure the windows os servers pattern to classify windows 2025 server in sndiscovery
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @lekqa86,
To make sure Windows Server 2025 is classified correctly in Discovery, you need to adjust the Windows OS - Servers pattern. Here’s how I would do it:
- First, run Discovery on a Windows 2025 server and check what values come back from WMI. Pay attention to the Caption, Version, and BuildNumber. For example, you might see something like:
- Caption: Microsoft Windows Server 2025 Datacenter
- Version: 10.0.25398
- BuildNumber: 25398
- Go to Discovery Patterns > Windows OS - Servers in ServiceNow.
- In the pattern’s Classification section, add a new condition so Discovery knows how to recognize Windows Server 2025. For example:
- Caption contains:Windows Server 2025
- OR Version starts with : 10.0.253
- Map that classification so it creates or updates the correct CI class (cmdb_ci_win_server). If you want to track it separately, you can even create a sub-classification called “Windows Server 2025.”
- Run Discovery again on the Windows 2025 box to test your changes and make sure the CI gets created/updated with the right OS details.
- Finally, as a best practice, don’t change the out-of-the-box pattern directly. Instead, create an extension pattern or duplicate the classification rule. This way, your changes won’t get overwritten during upgrades.