I don't think there is any MobiControl simple and direct user script commands that can support your requirements of targeting a virtual group and naming with non-repeated auto-incrementing index.  The latter requirement is complicated by the fact that devices in the virtual group folder can get on-line and processed at random order.

There are two possible solutions:

1.  Use various MobiControl RESTful API calls to search devices in the targeted virtual group not yet renamed and rename according to your auto-incrementing requirement.

2.  Export list of devices in the targeted virtual group into a CSV file for import to Excel or similar spreadsheet software, and append a new column of custom-attribute value with the required unique device name on each row.  This is then import to MobiControl for bulk configuring the custom-attribute values.  Then send script commands at the device-group level to this virtual group to rename all devices according to the custom-attribute value.  This approach is of course only applicable for those device platforms with rename script command that supports  custom attribute macro as argument.

Hi Demetrius Thornton,

Thank you for your post on SOTI Pulse. Raymond Chan thank you for responding to the post your expertise and willingness to help are greatly appreciated!

Based on your request, it appears you want to bulk update the device names. Once devices are enrolled in SOTI, it is not possible to change the device names in bulk. However, we have a workaround. You can use the Custom Attributes option to assign names to devices. This involves creating a CSV file with the following three fields: DeviceID, Custom_AttributeName, and Value.

You will need to manually populate the device names and corresponding IDs in the Excel file.

For additional guidance or assistance with this process, I recommend creating a support ticket. Let us know if you need further clarification.

I would like you to create a support case (click here) or call the SOTI Support team (click here)  to gain a better understanding of the issue. We can then determine whether to raise a Feature Request or troubleshoot to fix the issue.

Please let us know so we can proceed further accordingly.