If it helps, we started by stuffing everything into the Server class and created custom attribute for OS Family. Pretty quickly we realized that it was much better all round to use the class (which is a field already there) as a proxy for OS Family. We eventually [3 years later] found the budget and will to migrate all our integrations and data etc to the child classes as there was a strong business case to do so including being able to plug in OOB dashboards without any customisation required, as well as OOB modules just working without much tweaking etc. There are massive efficiencies to be gained later on by follow OOB as much as possible [obviously] and this is just one of those cases.
