Skip to main content

How can we help you?

Druva Documentation

Import the device map .csv file into inSync Management Console

After creating the device map .csv file, containing the user and device details, you must import it into inSync Management Console. inSync verifies the email-ids imported through the device map .csv. If a matching email-id is not found, inSync does not import the relevant user and device details into inSync and saves a list of such users to a file. You can download the file at the end of the import. The file contains the list of user and device details and the reason for which the import failed. You need to rectify the issue for the user and again import the device map .csv file. inSync incrementally updates the details when you import the file again.


Make sure you have the device map .csv file ready before you perform this procedure.

To import the device map .csv file in inSync Management Console:

  1. On inSync Management Console menu bar, click Manage > Deployments > Non AD/LDAP. Non AD/LDAP Deployment page is displayed. 
  2. Click Import Device Map CSV
    Map Devices dialog box is displayed.

  3. Under Select CSV tab, click  and select the device map .csv file that you want to import. The Upload Mappings tab displays the total number of succeeded and failed device maps. A Download failed device maps link is displayed if there are any failed device maps. Click this link to download a .csv of failed device maps and rectify the issues mentioned in its error column.
  4. Click Done. The mapped devices are displayed on the Non AD/LDAP Deployment page. You can see the Device Name, Device ID, Device ID Type, User Email and Status.

 Download failed device maps link downloads a .csv of devices that inSync could not map to the registered users. The .csv contains errors relevant to each device and displays them against the respective device IDs. You can rectify those errors and again import the original device map .csv. inSync increments the devices and displays them on the Non AD/LDAP Deployment page.

  • Was this article helpful?