Skip to main content
Druva Documentation

Quickstart for AD and non-AD integration with inSync

Overview

inSync can manage devices and users from both AD and non-AD/LDAP environments. This quick reference helps you to choose the best strategy to manage the following management tasks in both AD/LDAP and non-AD/LDAP environments with minimal administrator involvement:

  • inSync Client installation
  • Device activation
  • Device replacement
  • Device refresh 

Summary - user and device management

User and device management in AD/LDAP and non-AD/LDAP environments is summarized below.

AD/LDAP integration with inSync and mass deployment includes: inSync management of non-AD/LDAP users and their devices includes:

Device replacement using IMD for remote non-AD/LDAP users

The table below provides a quick reference to the integrated mass deployment (IMD) command versions to be used for device refresh/replace and client deployment in AD and non-AD/LDAP environments.

Activity Integrated Mass Deployment command version
Mass deployment of inSync Client on devices of users managed via Active Directory (AD) V2
Device replacement of users managed via AD using mass deployment command V2
Device replacement of users managed via LDAP or non-AD users using mass deployment command V2
Bulk replace devices of users managed via AD using mass deployment command V4

 

 inSync currently supports user and device management using IMD for Mac and Windows devices.

AD/LDAP integration with inSync and mass deployment  

Integration of inSync with AD/LDAP

Integration of inSync with AD/LDAP enables automated user and device management for inSync administrators. The integration is summarized in the steps below:

  1. Integrate AD/LDAP with inSync Cloud
    1. Install and configure inSync Connector - ensures secure connectivity between inSync Cloud and AD/LDAP.
    2. Register AD/LDAP with inSync - authenticates the access to AD/LDAP.
  2. Import users:
    1. Auto-import - periodically checks for new users and imports into inSync.
    2. Manual import - requires manual intervention.
  3. Create AD/LDAP mapping and set its priority - defines which details to import from AD/LDAP, assigns storage, decides the profile,  and manages users based on mapping priority
  4. Set user login mechanism:
    1. Create an inSync profile for users imported from AD/LDAP with login mechanism as AD/LDAP.
    2. Assign the profile to the imported users.
  5. Synchronize:
    1. Users - auto-updates user status inSync based on the user’s AD/LDAP status. 
    2. User details - tracks changes in user details in AD/LDAP and accordingly updates them in inSync.

Integrated mass deployment (IMD) of inSync Client

IMD command version: V2

Prerequisite: A registered AD/LDAP, an AD/LDAP mapping, and a user profile created on inSync Management Console

inSync performs mass deployment of inSync Client on Windows and Mac devices using:

  1. Registered AD/LDAP - inSync validates users against the AD/LDAP directory.
  2. AD/LDAP mapping - defines which details to import from AD/LDAP, assigns storage, decides the profile,  and manages users based on mapping priority. You can use an existing mapping or create a new one
  3. Mass deployment token - Authenticates client deployment on the user device
  4. Deployment parameters - Helps in communicating with inSync Cloud and controls client installation. 

Integrated Mass Deployment of inSync Client for AD/LDAP users requires just a few settings and running a command once all the above requirements are fulfilled. The deployment is summarized for you in the steps below. 

  1. Configure IMD settings
  2. Run the IMD Command based on the OS on the user devices
    • Windows
    • Mac - Ensure you use appropriate commands for inSync Client versions above 6.5 and below.

Device replacement using IMD for remote AD/LDAP users 

IMD command version: V2

The data from the old device is restored to a temporary location on the new device.

Steps to replace a device remotely:

  1. Mark the old device for replacement - changes devices status on the inSync Management Console
  2. Generate Mass deployment token - Authenticates client deployment on the user’s device.
  3. Deploy inSync Client using the IMD command - installs the client on the new device using the right parameters. 
  4. User logs into the client and restores:
    • Data from the earlier device
    • System settings and MAPI data (if backed up from the earlier device)
    • Data from the temporary location on the new device

Bulk replace devices of AD/LDAP users using IMD

IMD command version: V4

Bulk replace uses a CSV file as a reference to perform device replacement in bulk for multiple users. inSync verifies the CSV entries and replaces the devices associated with the valid entries. A sample CSV is also available for reference from the Map Devices window (Manage > Device Mappings > and click Import Device Map CSV).

To bulk replace devices of AD/LDAP users:

  1. Create and Import a device-map CSV file  - The CSV contains user details such as Email address, hostname of the device, device identifier, device identifier type, login user name, name of the old device, and  data to be restored (All, System, Only from existing device).
  2. Enable the Prompt user if device mapping not defined setting
  3. Generate a mass deployment token.
  4.  Run the IMD command with the appropriate parameters
  5. Optionally, activate the client on the user’s device.

inSync management of non-AD/LDAP users and their devices

Device replacement using IMD for remote non-AD/LDAP users

IMD command version: V2

Prerequisites:

  • The home directory path needs to be the same on both devices for user data stored on the source device in its home directory to be restored correctly.
  • Adequate disk space must be available on the C\: drive on the destination device 

Steps:

  1. Mark the old device for replacement - changes devices status on the inSync Management Console
  2. Generate Mass deployment token - Authenticates client deployment on the user’s device.
  3. Deploy inSync Client using IMD command - installs the client on the new device using the right parameters. 
  4. User logs into the client and restores:
    • Data from the earlier device
    • System settings and MAPI data (if backed up from the earlier device)
    • Data from the temporary location on the new device
  • Was this article helpful?