I have this situation where we are migrating from ILMT to Inventory. In early testing, I had servers in a state where I could not install, upgrade, or even run scans. The reason is relevance in some fixlets (such as uninstall) apply to both products so it’s very possible to get a computer into a state that isn’t relevant for anything ILMT or BigFix Scanner.
The solution in my test environment was to create a single folder that relevance was looking for and then re-apply the uninstalls.
To prevent this in production, I copied/modified the ILMT uninstall fixlet & BigFix Scanner Install to add a client setting at end of ILMT Uninstal. This is then required before the Scanner Install fixlet becomes relevant. This was also the recommended approach by professional services. It worked for most servers, but have a few that failed somewhere in the process.
At this point, I am looking to see if there is a fixlet that does a “brute force removal” so that I can remediate servers that failed the migration?… Similar to the BESRemoval functionality, but in this case, ideally it would need to be cross platform (Win/Nix/AIX) or even dedicated fixlets per OS is fine is well.
I have not put in a ticket yet but am planning to. Thought I would ask here.