Turned OFF VM instances causing impact on ITOM licensing

[sbhayani]

Hello Experts,

We have a situation where Turned OFF VM instances are causing ITOM licensing impact. We need to run discovery on Vcenter to discover physical hosts (ESX/ ESXis). However along with it all VM instances also gets discovered.

We have turned OFF Vms due to various refresh, and upgrade or DR related things.

Question to you,

- Is there a way to exclude VM instances from getting discovered?

- Excluding turned OFF Vms will be even better.

Appreciate all your help in advance!

[Ram Devanathan1]

Terminate the VMs if you don't want them licensed in ITOM. or restrict the scope/permissions to specific clusters or VMware datacentres via vCenter user permissions so that VMs outside of these are not picked up.

Powered-off VMs are counted as they are still 'active' and can be powered on anytime.

[sbhayani]

Hello Ram,

Thank you for response. I understand why it is being counted. is there a way from ServiceNow side to restrict these from being discovered?

[Ram Devanathan1]

as i mentioned above -

Terminate the VMs if you don't want them licensed in ITOM. or restrict the scope/permissions to specific clusters or VMware datacentres via vCenter user permissions so that VMs outside of these are not picked up.