Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Discovery: A Windows virtual server discovered both via IP and vCenter could have different RAM values in each CI - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Discovery: A Windows virtual server discovered both via IP and vCenter could have different RAM values in each CI
KB0755051

Discovery: A Windows virtual server discovered both via IP and vCenter could have different RAM values in each CI


1037 Views Last updated : Mar 13, 2025 public Copy Permalink
KB Summary by Now Assist

Issue

If a Windows VM is being discovered as a server (cmdb_ci_win_server) and, at the same time as a VMware Instance (cmdb_ci_vmware_instance) because vCenter discovery is enabled, the RAM values might not match.

 

If you log into the VM and vCenter, both show the same amount of RAM.

Release

All

Cause

If RAM is added dynamically to a Windows VM through vCenter while it is running the Win32_PhysicalMemory class isn't updated. As the ServiceNow Windows probes use this class to recover the memory information it appears incorrectly in the cmdb_ci_win_server CI.

 

It appears correctly on the server because the Win32_OperatingSystem class is used to retrieve the information. 

 

You can verify this by running the following command against the target server as per the documentation provided here: Manage ECC Queue content

powershell.exe 'Get-WmiObject -Class Win32_OperatingSystem -ComputerName <TARGET_SERVER_NAME_OR_IP> -Property FreePhysicalMemory'

 

NOTE: This is not a platform limitation, this is a consequence of how Windows WMI and dynamic memory assignment interact.

Resolution

The correct value will show in Win32_PhysicalMemory after the VM is next rebooted. 


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.