# How to configure device passwords on Android devices remotely?

The **Set Password** remote action in Hexnode UEM allows IT administrators to instantaneously configure or override device and work profile passwords over-the-air to ensure endpoints remain secure against unauthorized access.

**Understanding the “Set Password” Action**
-------------------------------------------

Remote password configuration is a critical security enhancement that ensures a device is never left unsecured. Unlike a passive policy that mandates user action, this command actively enforces a specific password from the UEM console.

- **Security Enforcement:** Guarantees a strong password is in place without relying on user compliance.
- **Access Recovery:** Allows admins to reset credentials if a user is locked out.
- **Work Profile Isolation:** Specifically targets the work container in BYOD (Bring Your Own Device) scenarios.

**Prerequisites and Requirements**
----------------------------------

Before executing the **Set Password** action, ensure the following technical conditions are met to avoid command failure:

CategoryRequirement**App Version**Latest versions of **Hexnode UEM** or **Hexnode for Work** apps must be installed.**Android 7.0+**Devices must be enrolled in the **Android Enterprise** program.**Activation**The **Password Token** must be activated within the **Hexnode for Work** app.**Step-by-Step Guide: Configuring the Password**
------------------------------------------------

Follow these instructions to remotely push a new password to a managed Android device.

1. Log in to the **Hexnode UEM console**.
2. Navigate to the **Manage** tab and select **Devices**.
3. Click on the target device to open the **Device Summary** page.
4. Navigate to **Actions > Security > Set Password**.
5. Enter the new password in the prompt. 
    - **Minimum Length:** 4 characters.
    - **Character Support:** Standard **ASCII characters** (codes 32-127) only.
         Note: 
        Leading and trailing spaces will be truncated automatically.
6. **Verify** the password and click **Confirm**.

**User Experience and Device Behavior**
---------------------------------------

The impact of the remote action depends on the current state of the device and its enrollment mode.

- **Unsecured Devices:** If no password existed, the lock screen immediately prompts the user for the new credentials upon the next access attempt.
- **Existing Passwords:** The old password is overwritten; only the new remote password will grant access.
- **Profile Owner Mode (BYOD):** The action configures the **Work Profile Password** specifically. Users must enter this to access work-managed applications.

> **Best Practice:** Always notify the end-user before triggering a password change. Failure to do so will result in the user being locked out when they attempt to use their old credentials.

**Troubleshooting Guides**
--------------------------

ProblemPotential Root CauseResolution**Action Failed / Not Received**Device is offline or Hexnode app is outdated.Ensure the device has an active internet connection and update the **Hexnode UEM/Work** app to the latest version.**Command Ignored (Android 7+)**Password Token is inactive.Open the **Hexnode for Work** app on the device and ensure the **Password Token** is activated.**Password Truncated**Use of leading/trailing spaces.Avoid using spaces at the start or end of the password string, as Hexnode removes these during execution.**Invalid Characters**Use of non-ASCII characters.Ensure only standard ASCII characters (codes 32-127) are used. Avoid emojis or special regional symbols.**Frequently Asked Questions (FAQs)**
-------------------------------------

#### **Does this action override a Password Policy?**

Yes. The **Set Password** action functions independently of any associated **Password Policy**. It allows for an immediate, specific override regardless of general compliance requirements.

#### **Can the same password be set for all devices in bulk?**

While technically possible by selecting multiple devices in the **Manage** tab, it is **not recommended**. Using unique passwords for each device ensures that if one is compromised, the rest of the fleet remains secure.

#### **What is the maximum password complexity supported?**

Hexnode supports numeric, alphanumeric, and special ASCII characters. To increase security, it is recommended to use a combination of all three types with a significant character length.

#### **Will this clear the user’s biometric data (Fingerprint/Face Unlock)?**

In most Android versions, forcing a new password via MDM will require the user to re-authenticate with the new password before they can resume using biometric unlock methods.