Hi Matt, 

As I have told you months ago , I don't have similar hardware as yours.  So I can't do any experiment to verify what I'm going to say.  They are partly wild guess and partly educated guess.

From your attached screenshots, I just can't be sure whether your device is non-compliant because it has been disabled. or your device is disabled because there is something non-compliant.  

For the former case, you probably need to check if any of your physical device actually takes up two MobiControl device licenses (i.e. two device icon consuming two licenses but with the same IMEI/Wifi-MAC).  If so, is it possible that the old device icon (i.e. before your device re-enrollment) get disabled, and so MobiControl marked the device (the new device icon after re-enrollment now) as non-compliant?  If this is the cause, the possible solution is to remove the old device icon, and free up one device license as a side effect.  

For the latter case, have you checked device not reported as non-compliant to see if the agent binary is actually performing perfectly in the older firmware version after the downgrade?   If not, you have to trace the true non-compliant source.  If it works perfectly OK, you might have to check  possibly wrongly reported non-compliant source such as:

-  device agent version falls out of range (within the table dbo.AgentCompatability  in the SQL defining what range of device agent version of each agent of specific bundle-ID is supposed to be compatible to the current server and need not be upgraded)

etc. (<- I actually have to think through in my dream tonight if there is any other possibility)

Hi Matt,

I ran into this same thing, you need to run the Factory Default for the WT6000, then re-enroll the device and that removes the "Non-compliant" message.

There must be something lingering on the device after the downgrade that is making it report "Non-compliant".