
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-29-2017 04:14 PM
I'm still quite new to Service Now so first off, I hope this is the right place to be logging this.
We are using SCCM to discover our devices. and I have turned on the "Enforce CI verification" for devices discovered as Windows Server (99% of our virtual devices are windows servers), so with the Enforce CI verification turned on, most of our virtual devices aren't creating an asset.
However this leads to a couple of other issues, if we did setup a physical Windows server, then no asset would be automatically created - not a big issue as the chances of this happen in my environment are remote and if it did we could manually create an asset for the CI. The bigger problem comes when we spin up a virtual desktop for testing purposes as these are corrected discovered as a computer and as Enforce Ci verification is off for this class of CI, the virtual device creates an asset. It isn't practical to turn on Enforce CI verification for the computer CI class.
So how are others stopping assets being created for virtual devices, what is the best way to stop any device with a serial number that starts VMware from creating an asset but still have it create the CI?
Thanks in advance,
John.
Solved! Go to Solution.
- Labels:
-
Best Practices
-
Scripting and Coding
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-29-2017 05:00 PM
Please note that the answer originally marked as correct in that post was later found to be incorrect. This solution, however, did work for that question:
Look at the Model assigned to the VMs that are discovered. It should be a Virtual Machine Model of some sort. In the Model record, you can set the Asset tracking strategy to Don't create assets. That will override the Model Category creation of the assets for the virtual CIs you discover.
This should get you what you are looking for, John.
Ben

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-29-2017 04:46 PM
Hi John,
Check out the solution mentioned on this tread: Exclude Virtual Servers from Creating Assets
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-29-2017 05:00 PM
Please note that the answer originally marked as correct in that post was later found to be incorrect. This solution, however, did work for that question:
Look at the Model assigned to the VMs that are discovered. It should be a Virtual Machine Model of some sort. In the Model record, you can set the Asset tracking strategy to Don't create assets. That will override the Model Category creation of the assets for the virtual CIs you discover.
This should get you what you are looking for, John.
Ben

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-29-2017 05:17 PM
Ben,
Thanks for the prompt reply, after a quick test this looks to be exactly what I am after.
So simple when you know how.
Regards,
John.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-29-2017 05:52 PM
Simple solutions are my favorite kind. Glad we were able to help you out, John.