Skip to main content

Best Practices for Activating Endpoint Devices Using Auth Keys to Avoid Snapshot Discrepancies

Overview

When deploying endpoint backup solutions, administrators must ensure that data is captured from the intended user's profile. This article outlines the recommended best practices for executing authentication keys (auth keys) during device activation. Following these guidelines ensures that Druva maps the correct user profile paths (such as Desktop, Documents, and Downloads) and prevents empty snapshots or missing data.

Best Practices for Device Activation and Profile Mapping

To ensure the correct user data is backed up successfully and to avoid profile mismatch issues, implement the following procedures during deployment:

1. Require End-User Execution for Activation

Always have the intended end-user log into the endpoint device with their own credentials before executing the auth key.

  • Why this matters: The backup software associates the configured backup paths with the profile of the user currently logged in. If an admin logs in with their own credentials (e.g., Admin) to run the key, Druva will back up

    C:\Users\Admin\Downloads instead of the intended C:\Users\Jane\Downloads.

2. Avoid Admin-Led Activations Under Admin Sessions

Administrators should not log into the endpoint device using their own admin credentials to execute the auth key for an end-user. While the backup will run successfully without errors daily, it will capture the admin's profile directory, resulting in empty or smaller-than-expected user snapshots.

3. Verify Profile Backup Paths

Before finalizing the activation, verify that the environment variables and user paths match the intended user. Ensure the active session points to the correct profile folder:

C:\Users\[username]

4. Remediation for Incorrectly Activated Devices

If a device was previously activated under an admin session and is experiencing missing data or empty snapshot discrepancies:

  • Log out of the admin session on the endpoint device.

  • Have the correct end-user log in.

  • Reconfigure and reactivate the device activation using the end-user's specific auth key to re-map the correct profile paths.

Did this answer your question?