For customers using AMP in monitor only mode, they would have to import settings if they make changes to controllers in their network if they care about using AMP for configuration auditing. Scripting a way to automate mismatch mitigation takes away the usefulness of the configuration audit feature.
The 'Mismatched' configuration states is shown in several places: the top header stats, the configuration column (on all list views), device audit pages, and in the configuration audit report..
Depending on the customer's usage case; if they only want to use AMP to monitor device up/down status and client associations, then they could ignore mismatches and hide almost all signs of configuration auditing.
To hide mismatches from view:
1. AMP Setup -> remove 'mismatched' from the top header stats
2. AMP Setup -> set automatically repair misconfigured devices = no
3. Group, Basic Tab -> set audit configuration on devices = no
4. Report, Definitions -> unschedule or delete the Daily Configuration Audit report
5. Any list view -> choose columns, remove configuration (if you leave configuration, it will display as ' - ')
--this only leaves the device audit page visible
I don't normally recommend this because I think the visibility of mismatches for large networks is key feature of AMP. But there are several customers who don't want to see mismatches, so this is a way to hide it from view. Though it shouldn't take much more than 10 minutes once a week to maintain mismatches in the single digits.