VMware Workspace ONE Community
Tkdehass
Contributor
Contributor

Pushing Profiles to Ipad

Having some issues with pushing a specific profile to a group of iPad, basically when I go into a device on Workspace and then under profiles, the profile I want pushed to the iPad or iPads is sitting with a status of "Pending Install" but it never appears to make its way to the devices. Any assistance would be greatly appreciated, thank you!

7 Replies
DmitryKurdenkov
Enthusiast
Enthusiast

Hi.

Check one idea. Is it profile for supervised devices? Is your device supervised?

0 Kudos
JacquesPerrolle
Enthusiast
Enthusiast

I've started having this issue as well with our on-prem environment.

0 Kudos
chengtmskcc
Expert
Expert

Did you push the Hub app to this iPad? And is it just this iPad or other devices as well?

0 Kudos
JacquesPerrolle
Enthusiast
Enthusiast

Turns out that it was a problem with APNs for MDM cert.  The cert had been replaced and didn't match the cert that enrolled devices were expecting, so there was no communication between the Apple Push Notification servers and the devices.  Once I corrected this, the devices started being able to get profiles and apps and whatnot.

0 Kudos
chengtmskcc
Expert
Expert

JacquesPerrolle

Just so I understand, do you mean you upload the original APNs certificate to resolve your issue? Otherwise, existing devices will need to un-enroll and re-enroll to pick up the 'new' APNs certificate.

How to Renew APNs Certificate for Workspace ONE | Dell Costa Rica

0 Kudos
JacquesPerrolle
Enthusiast
Enthusiast

That is correct... given that I was facing the thought of having to re-enroll 8000 devices.

I was able to clear the cert that had been a replacement, and then generate a new cert (which is really just to get a new CSR), go to the apple site and login with the correct Apple ID, and then renew the cert that I knew to be the correct one (that matched the topic of the mdm enrolled devices), apply the CSR, get the new cert, install said cert.  Voila, the devices that were no longer functional from a console perspective started working.

The caveats are, there are certain devices that were likely enrolled between the cert replacement and the cert fix, and those will have to be re-enrolled unfortunately.

chengtmskcc
Expert
Expert

Bravo!!!

0 Kudos