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.
Virtualized relationships not being updated on the server record when VM-instance is moved to different ESX server - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Virtualized relationships not being updated on the server record when VM-instance is moved to different ESX server
KB0718102

Virtualized relationships not being updated on the server record when VM-instance is moved to different ESX server


2131 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Symptoms


Virtualized relationship between the server and Hypervisor(ESX) not being updated when the VMware instance moves from one ESX to other.

Release


All releases

Cause


-"Virtual Computer check" is the business rule that is responsible for creating these virtualized relationships between the server and the ESX host. This business rule will run only when the record is inserted or when the serial number changes. When the VM instance moves from one instance to the other, none of these conditions will be satisfied and the business rule logic to correct the Server to VM instance relationship will not be triggered.

-Registered on relationship will be updated when discovery is re-run on the Vcenter and this will update the relationship between vm-instance and ESX. But the virtualized relationship is not touched here as the business rule will be run on the cmdb_ci_computer record when discovered via Ip address. 

// only process rec if just inserted or serial_number changed AND serial_number is non-nil

if (!(current.serial_number.changes() && JSUtil.notNil(current.serial_number)))

Resolution


 

-Navigate to business rule "Virtual Computer Check", modify the condition from

if (!(current.serial_number.changes() && JSUtil.notNil(current.serial_number)))

to

if (!(JSUtil.notNil(current.serial_number)))

-Re-run the discovery on the Ip address and this will correct the relationship between the Server and Hypervisor(ESX)

 


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.