Maintain Hardware Inventory customizations made to configuration.mof during upgrades
Currently, upgrading to 1602 blows away any customizations made for extending hardware inventory in configuration.mof, requiring you to manually back up the settings and restore them after the upgrade.
Make that go away, or at least less of a problem.
Some suggested solutions in order of perceived difficulty:
- Add a warning to pre-req checker if you don't have a standard configuration.mof so you know to re-implement your changes.
- Merge the changes into the customer's existing configuration.mof instead of wiping/replacing it.
- Remove the need for configuration.mof entirely - build a GUI for adding customizations, especially registry customizations
Thanks for your help!
This is in SCCM 1606 Production
In the big picture this is trivial but we can't keep taking features that have never required us to do anything and on a whim decide to make it a user responsibility. Have I backed up my configuration.mof, always... have I had to restore it before, never. MBAM integration and the edits that are required to that file alone should have been worth parsing and creating on-the-fly...
Nash Pherson (MVP) commented
Maybe between the first and second option: Make a backup of the configuration.mof before you blow it away so it is easier to copy/paste the changes back.
And maybe right before the last solution: Make the default stuff in configuration.mof stored internally in the database, and have the file only hold customizations.