CMDB Operating System choice list diminishes through extended tables

[Todd8]

Hello, I am failrly new to servicenow CMDB and have a question regarding the choices available when manually entering CI's. Whilst automated discovery is working quite well I've had to manually enter machines in a DMZ until I can get discsovery working in there. I can see using the CI Class Manager that 'Computer' in the hierarchy lists all available operating systems, but as I navigate to 'Server' then 'Windows Server' the list of operating systems available in the choice lists diminishes and I no longer have the lastest OS's to choose for my manually entered CI's. There's clearly someting that is filtering or qualifiying the choice list down when I manually select the correct class for the server. Is someone able to explain what is going on here?

Thanks, Todd.

[doug_schulze]

Todd,

That is the class Windows Server, this class can contain multiple types of Windows Server, 2012, 2016, 2016r2, ect ect.. The operating system is just an attribute of the primary class.

[Todd8]

Hi Doug, thank-you for the response, I am selecting Windows Server as my class for these manually entered CI however, the Operating System choice list for this class is whittled down to Operating Systems that only go as high as Windows 2008 R2. I need to be able to select 2016 abd 2012 versions of Windows Server, however, if I change the class back to 'Computer'  then I can see the lastest versions of Operating System. I want the full list of Window Server OS's to appear when I select the Windows Server class. Does that make sense?

Cheers, Todd.

[doug_schulze · Accepted solution]

And they should!  Seems like someone may have mucked with the works. The attribute 'os' starts at cmdb_ci_computer and is available to all extended classes. You might ask your platform admins to see if they put any restrictions on that field to lower classes and if not, open an incident with support. But what you're doing does work OOB, just gotta find the gremlin..

[Todd8]

Hi Doug, thanks for letting me know it should work like that and its onsite customisations that have prevented this from occurring. I'll chase this up and update when I've found the culprit. Cheers, Todd.