Automate Set PasswordSolved

Hello @clauss , 

Yes, you can schedule the Set Password action using the Automate tab in Hexnode UEM. Under Active Automations, create a new automation, select Android as the platform, choose Set Password as the action, then configure the Settings and Schedule. 

For time‑based triggers, you can specify exactly when the password should be enforced, for example, daily at a set time, weekly on chosen days, or monthly on a chosen date. You can also decide whether the action should run once, instantly (ASAP), or repeat on a set schedule. Once saved, the automation ensures that even if a user changes the password manually, Hexnode UEM will reset it back to the configured one at the scheduled time. 

Regards, 
Simon Scott
Hexnode UEM 

That’s perfect! Scheduling it on a weekly basis will help us enforce passwords without relying on users.

Can this action also be triggered when the device undergoes certain activities, like SIM swaps?

Thanks for reaching out. 

Yes, Hexnode supports activity‑based triggers as well. Instead of scheduling by time, you can configure the automation of Set Password action to run when specific events occur, such as: 

• On device enrollment or re‑enrollment
• On SIM insertion, removal, or switch
• On device compliance or non-compliance
• On location compliance or non‑compliance (based on Geofencing)

 

For example, if the SIM is removed from a device, Hexnode UEM will automatically enforce the configured password if you’ve selected the on SIM Removal trigger while setting up the automation.

We’ve had an issue where field devices often go offline and become inactive for days, and when they come back online, users have removed or weakened the password. Would automation help here?

Absolutely. In your case, you can configure the automation with the on Device Non-Compliance trigger. This way, if a device goes offline and becomes non-compliant, Hexnode UEM will trigger the Set Password action, and it will get executed successfully once the device comes back online and communicates with Hexnode UEM. So, if a device is offline for days, the enforcement will happen immediately once it reconnects to the network.

For better efficiency, you can also combine this automation with other Hexnode features: 

• Lock Device + Set Password: If a device is suspected to be compromised, automating both actions ensures the device is immediately locked and secured with a strong password. This prevents unauthorized access even if the device was left unattended.
• Enable Lost Mode + Set Password: When a device is reported lost, Lost Mode restricts usage, while the Set Password action enforces a secure lock. Together, they make sure the device cannot be accessed until it is recovered.

However, it is recommended to configure a Password policy to proactively prevent weak or missing passwords. By defining requirements such as minimum length, complexity, and password age, administrators can ensure that users cannot bypass security standards. 

Got it. This trigger and a policy association will be the right fit for our case.