Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 5 subscribers
  • Views 8695 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Task Bundle Bootstrap install failure

MaxOnions

When trying to deploy a task bundle, with bootstrap, e-mail, security and wifi profiles included, to iPhnes 4s/5s devices the Bootstrap profile sometimes hangs and prevents the rest of the profiles installing.

1. I send the task bundle to the device

2. In task view I can see the task running and the mdm boostrap profile start

3. The device receives the sms, I follow the link and install the profile which shows in the device profiles list

4. In Task view the mdm bootstrap task shows as 'successful' but does not then progress to 'installed'. In device view the device shows as being managed but the mdm bootstrap profile does not appear in the installed profiles list.

5. The other profiles in the task bundle are never started and show as 'not started' in the task view details.

I have:

Deleted the task and re-started it.

Rebooted the device and removed the bootstrap profile

Restarted the smc services on the MDM server

Eventually, the bootstrap profile will install correctly and the other profiles will be installed shortly after.

I cannot see any pattern of devices that this happens to and I have eventually been successful on all of them.

Sometimes I can provision a number of devices without any problem but oonce the above starts then I am unable to provision

any until it has cleared.

I am using SMC 3.6.0.5

Has anyone come across this problem?

:48108


This thread was automatically locked due to age.
  • 0

    Hi MaxOnions,

    is it possible that the affected devices are for example in a WLAN where the APNS port (5223) is not enabled?

    If the bootstrap tasks stays on successful, this indicates that the device cannot be reached via the APNS protocol.

    Please let me give you some more information how the whole enrollment process works.

    After the installation of the profile, the device does a check in at the SMC server. The device sends the information how it can be reached via APNS. The SMC server then uses this information and sends out an APNS message to this device. In this APNS messages it tells the device to contact the server again. If the device connects to the SMC server the bootstrap task will switch to the state "Installed" and additional profiles / tasks will be executed.

    Based on your description, I assume that the APNS message is not correctly send to the device. Please verify the suggestions above regarding the Wireless LAN and the APNS reachability.

    Furthermore, you can also install the patch 3.6.1 available in the download section. In this patch we also did some changes regarding the APNS trigger sent to the device after the profile installation.


    Best regards

    Stefan

    :48120
  • 0

    Hi SDU,

    Thanks for the reply, we had not yet applied the patch. I have done so now and will be testing with some new devices over the next few days.

    With regard to WLAN's, I had removed all wifi associations on the devices before pushing the task bundle to them and in some cases the wireless was off. Also, the same device would have problems for a while and then suddenly it would accept the profile. It was all very starnge. Hopefully the patch will resolve the issue. I will keep you posted.

    :48236
Unfiltered HTML