Tokenupdate

Hi,

if you're storing the tokens in a database (e.g. MySQL) you can set the SQL UNIQUE constraint for the column containing the tokens; this prevents a token from being stored twice. The UNIQUE constraint exists in MySQL, SQL Server, Oracle and MS Access databases. The following SQL statement creates a UNIQUE constraint on the 'Token' column when the "DeviceInformation" table already exists:

ALTER TABLE DeviceInformation
ADD UNIQUE (Token)

All the best,

Alex

Hi,

the problem is not, that we have that tokens twice - the problem is, that at the time where the devices sent their tokenupdate at a mdm re-enrollment in the background, the server was under such a high load, that many of that requests were fallen over.

So the devices had sent their token to us (so far, they think....) but the server didn't save that and now we have in the database the old, wrong value and each time we push a device we see on the device-console the message, that the magic string is wrong and he ends mdm now.

Thanks

Juergen

So it's some kind of a DoS-Problem, isn't it? Usually your server shouldn't be overloaded due to tiny requests like storing tokens in a database. I'm using a similar infrastructure which works perfectly. Maybe I can help you if you provide some more information. What kind of a web server do you use (Apache, for instance)? Assuming that you're talking about device tokens for the APNs; how do you push the messages to the devices? Using a PHP script? What kind of database system do you use?

Hi JuergenR,

Did you find any solution to this? I think we're having quite a similar problem. :-/

Although, I would have expected the device to try again, if it does not get a successful reply from the server, e.g., (HTTP 200).

I would also be interested in the solution. My direct question would be how can a MDM system update the stored device token if it becomes out of sync with the device. In this example it was because the server failed to process the tokenupdate message but what if the MDM server never received the packet?

Exactly guys! This is the same problem our MDM faces too. The devices updated their OS's outside MDM server's network (an unfortunate network setup, yes). So all the tokenUpdate was lost, and thus all the push magic too! Have you guys found out how to handle this yet?