iOS Devices

  • warning: Creating default object from empty value in /var/sites/e/ on line 33.
  • strict warning: Only variables should be passed by reference in /var/sites/e/ on line 61.
  • strict warning: Only variables should be passed by reference in /var/sites/e/ on line 61.
  • strict warning: Only variables should be passed by reference in /var/sites/e/ on line 61.
  • strict warning: Only variables should be passed by reference in /var/sites/e/ on line 61.
  • strict warning: Only variables should be passed by reference in /var/sites/e/ on line 61.
  • strict warning: Declaration of views_handler_field_user_name::init() should be compatible with views_handler_field_user::init(&$view, $data) in /var/sites/e/ on line 61.

MDM APNS push notification problem.

Shivam's picture
Your rating: None (2 votes)

We are trying to enroll iPhone devices with our 3rd party server,I downloaded the APNS certificate in the PEM format form the portal and installed it in the keychain access. I selected the APNS certificate (APSP:an23.....) and the private key that is associated with the MDM vendor certificate(Am i doing any mistake here???) and exported those into .p12 file. Using this .p12 file i am sending the wakeupcall to the iOS devices by sending push notification using python-apns library. I am getting feedback that the message is been delivered but the iOS device is not hitting back to the Checkin-url with the Idle status.Help is appreciated.

iOS update/upgrade behavior with supervised iOS devices

Tonyb72's picture
Your rating: None (3 votes)


We want to be able to supervise corporate-issued iOS devices via Apple Configurator but reduce/eliminate the need to re-tether the devices using an MDM product (MobileIron)

We have the day-to-day OTA configuration, policy enforcement, and app deployment processes addressed but we are not sure what happens when an iOS update becomes available on a supervised device.

Does an iOS update require a supervised device be re-tethered to the supervising Mac in order for the update to proceed? We've been unable to test since supervision via AC automatically updates the OS to the latest version and we don't have any devices that were placed under supervision prior to 8.1.2.


Upgrading iOS devices enmasse...

TechTimm's picture
Your rating: None (2 votes)

All, I have an oddity that hopefully someone has some ideas.

My infrastructure does not support traditional IP structures.
When we set up Apple Server to do Caching it instantly disables and errors out that we are using a public network. Which we are not, we just (as I said) don't use the traditional 10.*.* approach.

We need to upgrade multiple devices in multiple locations and don't / can't tie up the bandwidth needed to do them all over the air.
Here is an example:
One location may have 300 iPads.
iOS 8 is going to come in ~1.7 gb.
You don't have to be a network genius to see that 510gb of data, is going to drop traffic to a crawl!
Especially when other traffic gets the majority of the bandwidth and these device scavenge for what they get.

Has anyone tackled this, if so... please elaborate.
Are there other offerings Casper or SCCM come to mind in my quandry.

Any and all assistance is a boon at this point,

Let the App Migration start in the enterprise

Your rating: None (3 votes)

Apple, Inc. quotes “The iPhone is being used in 97% of Fortune 500, and the iPad is used in 98% of Fortune 500 and 93% of the Global 500 companies”.

What these numbers really mean? This means either employee bought their own devices (iPads, iPod Touch, iPhones) to connect to corporate network for checking emails or employee got their iPhone through corporate mobility programs or few brave companies deployed iPads for a specific use case.

What is their potential use? Mainly to use corporate emails, phone calls, imessages and other personal stuff.
While the devices are perfectly capable of handling many complex corporate applications that are in use as intranet applications or windows applications they are still restricted for several reasons until now. Even intranet sites are not mobile optimized to be viewed in iPhone or iPads. If you ask the question why, here are some obvious answers…

• We can’t manage iOS devices similar to how we manage windows laptops
• User experience is bad when they need to login through each App individually
• Data is not secured or encrypted on the device
• Secure connectivity to corporate network cannot be easily configured or managed
• App distribution is not easy – Users need to manually download the app and upgrade them
• Cost is high to develop enterprise Apps due to limited developers with Objective-C experience

At WWDC, Apple has clear response and answers for all these questions. With the introduction of new programming language “Swift”, opening up Touch ID and keychain to 3rd party Apps, App extensions, and B2B Apps they made adoption to enterprise easy and quick. There were several sessions focused on enterprise app development and deployment and dedicated resources to provide additional information. This will accelerate the migration of boring, non-intuitive windows applications and intranet sites to iOS Apps which will be secured, silently installed and managed by corporate programs.

Here are the details if you still think the questions are not answered…


Within the next few years this will change where new applications, functionality and use cases will be developed specifically for iOS devices once ROI (Return On Investement) can be justified through increase in employee productivity.

Stay tuned for more updates and feel free to add your comments…!

Introducing our handy Database of iOS Devices — Identifiers, IPSW links, etc.

Your rating: None (2 votes)

Quick quiz: How many iOS devices have ever been released? Not counting colors here, but boards. (Answer: only 35.)

I know that because today we launched our Database of iOS Devices. This is a pretty simple table of each iPhone, iPad, iPod touch and Apple TV Apple's released since 2007. It has introduction dates, model identifiers (i.e. "iPhone 6,2") and links to the latest firmware updates.

We're leveraging the API from Just a Penguin, which has done the dirty work of compiling the firmware versions (probably by a clever script).

But we're also able to add additional details to our database. What would you like to see?

Recent Activity