How is the Choice List for the OS field of the CMDB populated, and should I revert skipped upgrades?Issue The skipped upgrade has file name "sys_choice_cmdb_ci_computer_os". You can find it here: System Upgrade -> Upgrade HistoryFilter out all the From=n/a ones, which are just 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 You may be wondering if you should revert that. If you look directly at the sys_choice table records, you may wonder why some choices have been created by a MID Server user. ResolutionDo not revert this to out-of-box. The CMDB plugin's definition of the computer table only has a handful of predefined choices, and that list is not maintained. In general, where out-of-box choice lists have been deliberately customised, then each time that out-of-box choice lists gets updated by an upgrade, you should revert and then re-add your custom entries. But this is a special case, because it is the out-of-box Discovery code that is customising the choice list, and (probably) not you. The Discovery feature has always populated the OS choice (sys_choice, element "os") list on Computer (cmdb_ci_computer) if it find a windows computer that reports a previously unknown OS. This is the "Windows - Classify" sensor using the "OSChoice" script include, which is what inserts the record. It queries the table, and then inserts if it is not there. Agent Client Collector's sensor re-uses the Discovery script include WindowsOSNameHelper to do the same thing, and it would be expected that any properly written import set transform would either re-use this or do something similar. e.g. The "Integration - Microsoft SCCM 2016" plugin has a script on the "os" field in the map that uses WindowsOSNameHelper script include. As with any MID Server related integration, the Sensor transaction runs as the MID Server user, so changes will look like they were done by the MID Server user. If you reverted this, you would cause all the values added by Discovery to be deleted, which is bad because you will have computer CI records using those values. In list views those invalid values will appear blue. On forms you will not be able to see the correct value in the OS field dropdown.