Should Windows Server operating systems be populated in cmdb_sam_sw_install by Discovery?

[Gary Ault]

Hi,

We are taking a look at Software Discovery, particularly what software data is collected.

Discovery correctly populates the os and os_version fields on our Windows Server CIs. However, when we group active cmdb_sam_sw_install records by discovery_model, we do not see Windows Server OS discovery models with counts that match our server population. We do see the software that we would expect to find in the Windows installed-software inventory.

Is the Windows operating system itself expected to be inserted into cmdb_sam_sw_install by horizontal Discovery or ACC Visibility?

My assumption is that the table is populated from the installed-software inventory returned by the OS, and Windows does not normally report itself as an installed application. Does SAM manage things such as OS versions and EOS dates differently from installed software?  Note we have not yet purchased SAM so I can't just look it does or does not handle OS as software. 

Sincerely,

Gary A.

[dreinhardt · Accepted solution]

Hi @Gary Ault,

yes, Windows Server is discovered and processed as SW install and discovery model.

Please add the column "install count" to your discovery model list view and search in column product (norm_product) for "Windows Server" this should give you an good overview about the amount of detected installs.

Edit: I saw your note about not having SAM Pro. Of course this could be a reason due to missing SAM content service data for discovery model normalization.

Best, Dennis

[Gary Ault]

Thank you for sharing that.  It shows me what is possible.

We are considering SAM, but I want to be sure ready for SAM should that decision be made.  I'm betting it is something in our discovery configuration. I wouldn't expect adding SAM to change the discovery itself and we are getting all the other installed software via discovery.  However, you never know. I may have to open a ticket to be sure.

Thank you again,
Gary A.