Team, At the end of devices staging my customer deploys a agent30 settings object, via a provisioning policy, to remove the package delete and exit options from the MSP3 client UI. After some period of time, on some devices, the settings object seems to be ignored as these options re-appear on the UI. We assume that the other options set in the settings object, such as check-in interval, are also set back to whatever the debug30 settings package has defined in it. As a result, we beleive that we have a lot of customer devices not checking in as the field users inadvertently exit the UI, effectively disabling the client. We definitely remove the debug30 package before we put our MSPsecurity settings object on the device. I have seen this a number of times over the years but have not come up with a reason. Has anyone else seen this and, if so, do you have any idea why it is happening? We have upgraded to 3.3.1 to try to resolve this, without success. We opened a case with Moto back in March but still do not have a fix. My customer desperately want to resolve this.  Thanks, Damian