I have seen that as well. Are you using the MobiControl Stage app for enrollment? My running theory is that the devices perform some kind of soft enrollment first with that Agent and then re-enroll after they've downloaded the full Agent. When they re-enroll the previously enrolled version gets cleaned out and removed, but the auto-incremening device name reflects an N+2. I haven't fully proven this out because it hasn't really produced any adverse effects for me, but thats at least what I think might be happening based on my observations. 

I have used Mobicontrol Stage in the instances I have seen this happen, yes.  I may try enrolling via another method to see if that enrollment behavior changes, but i would think Mobicontrol's own staging app would not cause issues like this?

Hi Aaron, 

How did the other methods of enrollment go?  Hopefully they were successful with out the same issue.

I would like to believe our own application MobiControl Stages does not produce issues like this but sometimes one improvement in the application can cause another to behave in a an unexpected manner.   I have searched for other cases with regards to this and have not found any other situations where this has been reported. 

If this is causing you some inconvenience perhaps you can open a case with Technical support where we can review your setup to ensure the configuration has been done correctly.  If it is found to be correct we can create an internal ticket to resolve the action that is causing this discrepancy for you.   

You can open a case by emailing us at support@soti.net or by selecting the following link.

Regards,

 Auto Incrementing Numbered Sequence Question:

Is this number assigned a primary key or will it be overwritten when it is removed and another device added?

 Our current Setting is %MODEL% %AUTONUM:3%

Example: If TC52 010 is sent out for repair and we remove it from Production Folder. When it is bar scanned back in will it be assigned the same number?

Suzan

---

Hi Aaron, 

How did the other methods of enrollment go?  Hopefully they were successful with out the same issue.

I would like to believe our own application MobiControl Stages does not produce issues like this but sometimes one improvement in the application can cause another to behave in a an unexpected manner.   I have searched for other cases with regards to this and have not found any other situations where this has been reported. 

If this is causing you some inconvenience perhaps you can open a case with Technical support where we can review your setup to ensure the configuration has been done correctly.  If it is found to be correct we can create an internal ticket to resolve the action that is causing this discrepancy for you.   

You can open a case by emailing us at support@soti.net or by selecting the following link.

Regards,

Technical Support | SOTI Inc. |1.905.624.9828 | support@soti.net | soti.net |

Auto Incrementing Numbered Sequence Question:

Is this number assigned a primary key or will it be overwritten when it is removed and another device added?

 Our current Setting is %MODEL% %AUTONUM:3%

Example: If TC52 010 is sent out for repair and we remove it from Production Folder. When it is bar scanned back in will it be assigned the same number?

Suzan

---

Hi Aaron, 

How did the other methods of enrollment go?  Hopefully they were successful with out the same issue.

I would like to believe our own application MobiControl Stages does not produce issues like this but sometimes one improvement in the application can cause another to behave in a an unexpected manner.   I have searched for other cases with regards to this and have not found any other situations where this has been reported. 

If this is causing you some inconvenience perhaps you can open a case with Technical support where we can review your setup to ensure the configuration has been done correctly.  If it is found to be correct we can create an internal ticket to resolve the action that is causing this discrepancy for you.   

You can open a case by emailing us at support@soti.net or by selecting the following link.

Regards,

Technical Support | SOTI Inc. |1.905.624.9828 | support@soti.net | soti.net |

Hello Suzan,

All the device information is stored in a table called devinfo in mobicontrol's database. Every enrolled device has a unique entry and has a primary key called ad devid which is a unique string for each device. The device name can be changed manually using the devrename script and multiple devices can have the same name.

If you want to preserve a device's name then there is an option available when you create an enrollment rule. In the advanced settings of enrollment rule you will find a check box that says preserve device name on re-enrollment.

I hope that helps.

I have the same question that Suzan had regarding "Example: If TC52 010 is sent out for repair and we remove it from Production Folder. When it is bar scanned back in will it be assigned the same number?"

I see your response "If you want to preserve a device's name then there is an option available when you create an enrollment rule. In the advanced settings of enrollment rule you will find a check box that says preserve device name on re-enrollment."

However, when I look for that option in the advanced settings I do not see it. I see the options shown in the screenshot below. Am I not looking in the correct location? I'm currently working on creating the configuration for our new devices and have noticed that my test device gets reassigned a new name, via the %Autonum% sequence I've specified, every time it is wiped and re-staged into the system.

You looked in the right place.  Howerver, your MobiControl server may be a bit old.  You'll have that "preserve device name on re-enrollment" option  after our upgrade to a newer version.  I can't remember exactly when that option was added.  You can probably check MobiControl release notes.   Below is the screenshot for MC v14.4.5.1048.

I guess that is the issue. We are on version 13.4.0.5389.

However, our when our WindowsCE devices are re-staged (for instance after being sent out for repair) they retain the device name they had before. So I wonder why the Android devices behave differently?

Hi,

I face also this problem is there now a solution?

I'm on Version: 15.1.0.3416(Soti MobiControl)