I'm curious about this method myself as we've only recently started switching to leveraging AE as a default strategy over DA. I will say if you do figure out how to do this, watch out for the most recent 1662 release as this "feature" has caused a number of permissions issues with the B2B apps we deploy:

Hi, when I started the move to AE, I also couldn't get the agents to update, so yes, I had to approve the agent via the Google Play Managed Store and then added the agent to the Application Catalog as mandatory.

Hi John,

I tried this method yesterday and got this to worked too. Did you're device ask for the device security PIN or Pattern to be entered via the Pending Actions screen after updating?

James

Hi James,

Perhaps the device hadn't received or applied your authentication policy yet and was just catching up?

For my devices, after updating the agent, they don't display new pending actions.

John.

Hi John,

I can confirm the device had a PIN set before the update. It asked not for a Password or Pin to be set but credential re-entered.

I will attempt to find another device I can update.

James

Just a thought, if you are using Android 6+, I have found that some Samsungs persistently ask the user for the password to complete encryption even though device is encrypted, unless they set the option for Password on startup in the lock screen & security settings.

Probably not this but check out the link;

https://discussions.soti.net/thread/force-samsung-secure-startup-on-android-enterprise-devices/

Just upgraded a Work Managed Zebra MC93 and TC52 using this process to 1844. Worked like a charm! Happy to see kill_application and writesecuresetting scripting making a return.