Overview
To perform a mass deployment in a non-AD/LDAP environment, you need to create a device map file in a .csv format. Each entry in the device map .csv file is called a mapping. A device-map .csv file contains the user and device mapping details, which ensures controlled device and user activation of the client and prevents the addition of rogue or unauthorized devices.
Procedure
You can create a device map .csv file by downloading a sample device-map file from the Endpoints page and adding data to it. To download the sample device map .csv file:
On the Endpoints page, click Device Mappings from the left navigation pane.
Click the Import Device Map CSV button located on the top left of the page. The Import Device Map CSV dialog box appears.
📝 Note
If the CSV file that you import includes users who have enabled data privacy, we will notify those users and server administrators about the new device mapping. Sending email notifications would mitigate a potential threat when a rogue administrator attempts to gain access to user data. To disable email notifications, contact Support.
The device mapping do not support special characters or Ascii characters.For example: @, ,`~,$,&
Click the Download Sample CSV File link. A sample .csv file is saved to your local drive. You can update this sample with the data specified in the table below and use it as your device map file.
The following table lists the attributes in the device map .csv file.
Value | Description | |
1. | email id | Email ID of the user. This is validated against the list of user email-ids registered. Multiple authentic devices and user names can map to the same email ID. The .csv file may have multiple entries for the same email-id to show multiple mapped devices and users. However, we recommend having one user per registered email ID. |
2. | hostname | The hostname of the new device. |
3. | device Id | Value of the device ID.
The following commands for Mac and Windows devices will display the device identifiers such as the Serial Number and UUID of the respective device. You can use anyone as a device identifier in the device map .csv file. The device identifier must be unique and must map to a single email ID.
Another option to find the Serial Number:
Another option to find hardware UUID:
|
4. | user-name | User name used to log on to the device. |
5. | device-id-type | The type of the device identifier, for example, Serial Number or UUID. |
6. | old-device-name | The hostname of the old device.
❗ Important
Use this field if you are replacing the old device.
|
7. | data-restore | Type of data to be restored on the new device.
❗ Important
Use this field if you intend to replace the old device and restore data from the old device.
|
You can view the created device mapping details in theAdmin Audit Trail( Activity Type->Others ).
Additional information
A mapping is displayed on the Device Mappings page and deleted automatically after the device replace activity, and the Client is activated.
Attributes such as email-id, device-id, and username identify the user device in Endpoints.
If a mapping is not found for a non-AD user, the mapping is searched using the username and device ID.
If the device-map .csv file contains old device details that are specified in the old-device-name attribute, the old device is replaced with the new device and the data is restored if the data-restore attribute is set.
If a mapping is found that does not have the value defined in the old-device-name attribute, the device is added as a new device.
If a mapping is not found when the user is present and the optional setting - Prompt user if device mapping not defined is enabled, the administrator/user can add or replace a device.
Next
After creating the device map .csv file, you need to import the device map .csv file. For more information, see ImportDevice Mappings.