Configure Autopilot devices using autopilot cli

This topic explains how to configure Autopilot devices using the autopilot CLI by providing a device CSV file as input. It includes command examples, file location requirements, and troubleshooting steps for resolving CSV format issues between Windows and Linux environments.

You can add user as part of csv to assign the same to imported device.

You need to provide device csv as a input to autopilotcli. The device csv has to be available in <MDM_HOME>/windows/config/

Device command

/var/opt/BESUEM/mdm-command.sh windowsmdm autopilotcli -d device.csv
/opt/BESUEM/mdm-command.sh windowsmdm autopilotcli -a device.csv16
Troubleshooting
Problem: If you have generated device hash csv file in windows format, and run the device configuration command in Linux, the command might fail and through the following error: panic: runtime error: index out of range [2] with length 1.
Solution: Convert the device hash csv file in windows format to Linux. To do that, complete the following steps:
  1. Install dos2unix software using the command "yum install -y dos2unix"
  2. Convert the generated csv from Windows to Linux using dos2unix using the command "dos2unix csvfile"
​​​​​​​Switch on the device and connect to the internet. Enter the password for the assigned user.