Enrollment with %autonum% starting at a specific number

Solved
AM
Alex Münch
arismo GmbH

Hello SOTI Support,

We are planning a larger rollout with 950 pieces of SAMSUNG TAB A8 (SM-X205).

We would like to start the enrollment with a specific number folloging by the next number.

So we would like to start at „480-1500“ then „480-1501“ and so on…

How can we do that?

Thank you and best regards

Alex

2 years ago
SOTI MobiControl
ANSWERS
RS
Rafael Schäfer Platinum Contributor
2 years ago

Not as far as i know of (in the console or config).

You can only define how many leading zero's are placed in front:

Description Macro
Auto Incrementing Numbered Sequence

The default %AUTONUM% macro begins numbering at 00001

The customizable %AUTONUM:X%, where X = a number ranging from 0-9, allows you to specify a minimum number of padding of leading zeroes. %AUTONUM:3% would begin numbering with 0001.

Both %AUTONUM% macros increase in increments of 1.

%AUTONUM%

%AUTONUM:X%

But as this must be saved somewhere in the DB it could be that if you know which entry is relevant for this, just to edit it to the starting number (or maybe one less?). But this is only an assumption and maybe someone else has experience with this or ask Soti about it (recommended).

Also ensure to have a backup before you make any manual changes in the DB.

Ensure to use only a number (1500 in your case) only. Not any letters. Macro would be then like:
480-%AUTONUM%
or
480-%AUTONUM:3%


Another possibility would be to write an ini file to the device having this information stored, read by the mobicontrol agent and used for renaming then.

Solution
B
Bayo
2 years ago

Hi Alex,

Just as Rafael has stated, you may be able to find the table dbo.sequences in the DB to implement this change.

RC
Raymond Chan Diamond Contributor
2 years ago

Hi Alex,

Without verifying OFFICIALLY with SOTI SUPPORT TEAM for your particular case & mobicontrol server version,  I would not recommend directly modifying ANY element in ANY Mobicontrol database table.   Without knowing details of the schema and inter-relationships between different tables/table-columns and the meaning of the value represented, it is extremely dangerous to casually modify anything in the database directly.  The side-effect(s) or even damage to your system can be VERY significant.    Do NOT casually trust anyone (including me)  on this forum when you are told to modify any database table directly.  I always consider that sort of recommendations IRRESPONSIBLE.

In your case related to device naming for newly enrolled devices,  the safest and MOST RELIABLE approach is to do device renaming after the enrollment.  The reason is quite clear based on my past experience in many past projects.  For large-scale enrollment involving hundreds or more devices, it is not uncommon for some enrollment attempts to PARTIALLY fail (e.g. due to signal level, battery level, wrong on-screen configuration options selected, etc.) towards the end of the enrollment, and each subsequent retry can potentially result in the next sequential number for the macro %AUTONUM% being used, thus creating a gap in the device name sequence.  Thus, relying on the automatic numbering mechanism is not practical if a PERFECT device name sequence MUST be achieved.

RS
Rafael Schäfer Platinum Contributor
2 years ago

Yes, that's why i recommended to contact Soti maybe is the best way to investigate into this.

The rest was just a description of an idea to look into together with them.

M
MNMOD@SOTI Gold Contributor
2 years ago

Hi Alex,

Thank you for posting on SOTI Pulse!

I saw that you have created a support case and it has been resolved. Could you please  mark the post that solved this issue as solution.

Kind regards,

Technical Support Specialist | SOTI | +1 905.624.9828 | SOTI.net l Discussion Forum | Log a Case Online l Facebook l LinkedIn l Twitter