- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 03-26-2021 10:30 PM
DESCRIPTION
For Windows Classification, Discovery relies on OS Caption to classify different flavors of Windows Operating System. For some 2019 OS Servers, the caption lacks the year (ex: Microsoft Windows Server Standard), preventing Windows Classification from correctly classify these as Windows Servers instead of Computer. This happens for the latest OS build 10.0.19042. All other OS builds returning the expected Caption. Due to this change on Microsoft Side, we'll need to redesign our Classification logic to accommodate the change since genuine Windows Server 2019 change where Caption does not contain year anymore.
OBSERVATION
OUTPUT:
- CAPTION: Microsoft Windows Server Standard
- NAME: Microsoft Windows Server Standard|C:\Windows|\Device\Harddisk0\Partition3
- VERSION: 10.0.19042
CONCLUSION: It is a bug from Microsoft and since the substring is missing - "2019", it doesn't go through the "Windows 2019 Server" Windows Classification thus it classifies as Computer instead of Windows Server.
SCREENSHOT: Attached
WORKAROUND:
CUSTOM CLASSIFICATION: Attached the update set to create a custom classification specific to this Windows Server Standard 2019 build 10.0.19042.
FILENAME: sys_remote_update_set_d39cd87c87a2e0106197ffb2debb35a2.xml
- 10,171 Views
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Srikanth, are we accommodating this Microsoft bug in our future updates, or are we going to wait for Bill to fix his OS information? Also, do you have by chance the M$ft bug/KB link and ours in how we are going to manage this?
Thanks,
Doug
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hello Doug,
Thanks for your response. Surely! we don't wait for Bill to fix his OS information nor ship the fix straight away out of the box in the patch release. It's just that we found not more than 1 customer reported this issue (via Case) so not taken any decision on backporting yet. Above all, you can definitely request a backport by logging a backport request and I'm sure, none is stopping you.
I hope this helps. Thanks.
Srikanth N.