How to manage operating system field choices in CMDB when reviewing skipped upgradesIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } When reviewing skipped upgrades, some entries may have the file name sys_choice_cmdb_ci_computer_os, and some operating system (OS) field choices in the CMDB appear to be created by a MID Server user. This article explains how the OS choice list is populated and why you should not revert these skipped upgrades. To locate these skipped upgrades: Go to System Upgrade > Upgrade History.Filter out entries where [From] [=] [n/a] (these are plugin activations).Open the most recent upgrade.In the Skipped Changes to Review related list, search for [File Name] [=] [sys_choice_cmdb_ci_computer_os] The following image shows an example of the System Upgrades UI. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } All supported releases Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Do not revert these changes to default settings. The CMDB plugin's definition of the computer table contains only a few predefined choices, and that list is not maintained. While you typically should revert and then re-add custom entries when default choice lists are updated during an upgrade, this is a special case. The default Discovery code is customizing the choice list, not your manual configurations. The Discovery feature automatically populates the OS choice list (sys_choice, element "os") on the Computer [cmdb_ci_computer] table when it finds a Windows computer reporting a previously unknown OS. This process uses the Windows - Classify sensor with the OSChoice script include, which inserts new records after checking if they exist. Agent Client Collector's sensor uses the same Discovery script includes: WindowsOSNameHelperLinuxOSNameHelperMacOSNameHelper These scripts perform the same function, and properly written import set transforms should use similar methods. For example, the Integration - Microsoft SCCM 2016 plugin includes this script on the os field in the map that uses WindowsOSNameHelper script include: var osName = new WindowsOSNameHelper().formatWindowsOSName(source.u_caption); answer = ''+osName; Since MID Server related integrations run Sensor transactions as the MID Server user, changes appear to be made by this user. If you revert these skipped upgrades, all values added by Discovery and imports are deleted. This creates problems because: Computer CI records using those values will have invalid referencesInvalid values will appear blue in list viewsThe correct values won't appear in the OS field dropdown on forms