Windows - Amazon EC2 incorrectly mark device as Virtual (Is Virtual checked) even if device is physical server - Known Error

Windows - Amazon EC2 incorrectly mark device as Virtual (Is Virtual checked) even if device is physical server Description When Windows - Amazon EC2 probe is run, probe checks if UUID of the target device starts with 'ec2' and if yes, sensor Windows - Amazon EC2 set "Is Virtual" on the server and proceed with further verification of AWS relationships. There is a small chance ( ~1/2000), but it happens, that a random, non-AWS machine UUID will start with EC2, and incorrectly mark CI as Virtual; "ec2" is also just a hex number after all.

This has been seen with Server Blade hardware.

Steps to Reproduce

This is difficult to reproduce on demand without happening to have some hardware with a UUID that starts "ec2..."

This has been seen with at least:

Cisco UCS B200 M5 blade server hardware, where the UUID started with EC2AEC17-... Hitachi Compute Blade 520HB3 Steps:

Ensure that Windows - Amazon EC2 is triggering in discovery Run discovery on physical Windows server whose UUID starts with "EC2" Observe that "Is Virtual" is set to true in the server CI Workaround As a possible workaround, you can disable "Windows - Amazon EC2" probe from running in discovery.

https:// .service-now.com/nav_to.do?uri=discovery_probes_wmi.do?sys_id=45c3bb40374112000e4d03488e41f1c5

This problem is currently under review. You can contact ServiceNow Technical Support or subscribe to this Known Error article by clicking the Subscribe button at the top right of this article to be notified when more information becomes available.