Allocated Not In Use

[Laurent Ricciar]

Hi, I don't quite understand how can we have a bunch of servers allocated and they come up as "not in use" once the reconciliation is completed. Any thought?

[Daniel Slocum]

Allocated Not in Use generally means one of a few things. The software wasn't found on the CI; Discovery hasn't scanned the CI or it has and the software isn't installed.  Or, there is a configuration issue with the Discovery Map chosen on the Software Model. The Discovery Map on the Software Model isn't picking up the Discovery Model related to the Software Installation. 

[Laurent Ricciar]

Hi Daniel, it makes sense yet that does not really apply for ESX/Virtualized environment - the license is Microsoft CIS DataCenter.

The software wasn't found on the CI - yes, that is probably normal because we license a VmWare ESX box core-base.

Discovery hasn't scanned the CI or it has and the software isn't installed. => the CI is there since I allocated it but there is no Windows on an these ESX box. So the ESX host is licensed core-base and, really, what we do need to discover are the VMs. How do you pull the VMs from the discovery?

[Daniel Slocum]

Hi Laurent,

You'll need to work with your ServiceNow Discovery folks to discover the VM's related to the ESX Host.  I've attached a white paper from 2018 that speaks to the discovery of VM's and License Keys. I think it should have the detail you are looking for. I'm much more knowledgeable in the ITAM space than I am in Discovery.