Does Computer CI's further classification to LAPTOPS and DESKTOPS possible?

anilkumarkarams · ‎03-30-2015

Hello All,

We are planning to install discovery and we are working on our development phase.

When we performed a discovery scan , the Service Now instance has created records for laptops and desktops in COMPUTERS ci table. Our customer has asked us to further classify the computer cis as desktops and laptops.. We tried searching in wiki and community but did not find any helpful information.

Can anyone help us with some information on this?

Regards,

Anil Karamsetty

tdf · ‎03-30-2015

I'd agree that a separate classification is overkill. The approach I've generally used is to use the Chasis Type to record this data. I've always thought it would be better to track this on the model table since it doesn't change on an CI by CI (or asset by asset) basis, however I'd rather not add a field on model, so I stick with the the Chasis on cmdb_ci_computer. You could use the suggestions above to get the query from discovery.

View solution in original post

Stijn Verhulst3 · ‎03-30-2015

Hi Anil,

checking whether a computer is a laptop or a desktop is something I've never done before. For Windows computers; definitely check the following page (official page of Microsoft): https://technet.microsoft.com/en-us/library/cc180825.aspx

It tells you how to detect laptops. Hopefully it will help you forwards...

If this is actually usuable you do the following setup in Discovery (this is how I would do it; simple & clean):

(1) Create a new field on computer level: for example a Choice List with the options 'Laptop' & 'Desktop'

(2) Create a new probe containing the WMI script.

(3) Parse the outpout in a newly created sensor linked to the previously created probe so the value of the choice list is correctly set for the CI.

Important note ::: an actual seperate classification might be overkill in the end as laptops & desktops share commonly the same configuration data. Also it would make the implementation in Discovery more complex as a new classification in this case means new CMDB classes/CI Identifiers...

Kind regards,

Stijn

tdf · ‎03-30-2015

I'd agree that a separate classification is overkill. The approach I've generally used is to use the Chasis Type to record this data. I've always thought it would be better to track this on the model table since it doesn't change on an CI by CI (or asset by asset) basis, however I'd rather not add a field on model, so I stick with the the Chasis on cmdb_ci_computer. You could use the suggestions above to get the query from discovery.

anilkumarkarams · ‎03-31-2015

Hi,

Thanks a lot tim i believe Chassis type field will help us , Instead of creating classes we will create new modules .

Thanks,

Anil Karamsetty