IT Does Not Love iPads, and that's a good sign

I'm not normally in the business of going full-Macalope on stupid articles about iPad. After all, there aren't enough hours in the day. Having said that, one particular article has surfaced recently that I hear is being used by at least one local authority IT team in Scotland to justify an LA-wide ban on iPads.

The article by Michelle Fredette in Campus Technology entitled "IT Does Not Love iPads" is so completely off-balance that it's almost funny - until you realise that this kind of weak thinking is actually being taken seriously.

In case you don't make it to the end, here's an executive summary of the complaints:

  • iPads come in boxes
  • App licensing works differently from Microsoft's
  • Apple TV is finicky to deploy at scale
  • You need a whole new network for iPads

The only one of these that actually makes sense is the complaint about a device (AppleTV) that is, in fact, not an iPad.

Anyway, let's get into it.

Is there a higher ed institution in the United States that has not fallen into a swoon over iPads? Some colleges hand them out by the thousands to their entire student body. Others stockpile hundreds for use by faculty, staff, and administrators, or to be checked out of the library by students. On many campuses, iPads have taken over the hearts and minds of everyone.

Let's start by using words like "swoon", "stockpile" and "hearts and minds" to get it clear from the start that all this enthusiasm for iPad is just a mass delusion. Got it?

Everyone, that is, except the IT department.

Given our decades of experience with computers that the IT department love and staff and students hate, I think this can only be considered a good sign.

These sexy tablets might be the apple of faculty and students' eyes, but for IT directors and their staffs, working with iPads in an enterprise network environment is not the stuff of a love affair.

"Sexy". As we know, Real Serious Business can only be done on thick, black computers that people don't like.

To state the problem simply: iPads are designed for consumer use, and as such, they're not set up for large-scale implementations.

I hope someone told LAUSD, who just voted to roll out a $50m, 47-school iPad program. Or McAllen School District, who already have 25,000 units in the field.

They're not even set up for two users to share the same device, much less for sharing over a network.

It's 2013 and the fact that iOS is not a multi-user operating system is still coming as a shock to some people? Also, it turns out the iPad is not a mainframe computer.

For schools making a major investment in iPads on campus, the solution is a combination of new policies and investment in third-party tools for managing the devices.

So there is a solution!

For many other institutions, though, the devices are acquired as needed, or in small batches for specific purposes. In such cases, schools don't necessarily anticipate the additional tools and administration the iOS devices can require--until IT starts bumping up against the limitations of a device that's not easily managed under the school's existing network and resource management infrastructure.

So organisations that don't bother to try and understand what they're doing tend to have a hard time?

The differences between iPad device administration and that of desktop machines or laptops are apparent at all stages of their use, beginning the moment the machines arrive on campus.

You don't even get a minute's reprieve from the awful otherness!

Take, for example, the case of Seton Hill University, a school that has distinguished itself as a forerunner in campus iPad implementations, including being named a second time as an Apple Distinguished Program. In the spring of 2010, the Greensburg, PA, school ordered 1,850 iPads in anticipation of providing them to students for the following fall term. What IT faced was a giant pallet of the devices, individually wrapped or in boxes of 10.

iPads come in boxes! Unlike the Windows PCs that come on tear-off rolls and the Android tablets that come in sheets you can cut to size!

Phil Komarny, Seton Hill's vice president for information technology and CIO, says that his staff had to take each iPad out of the box, update the operating system to the most recent version, image tag it, and put it back in the box to be ready for deployment. "There was nothing else we could do, because this device that they built is completely consumer," Komarny shrugs.

To be serious for a moment, there is something else you could do: get your reseller to do this for you. I'm only leasing 120 iPads and I've had resellers falling over themselves to help us do these chores.

If I was buying 1,850, I'd think this would be the very least a reseller could do for me.

Thomas Hoover, associate vice chancellor and CIO at the University of Tennessee at Chattanooga (UTC), had a similar experience with iPads in a previous role at Pepperdine University (CA), where the IT group handed out several hundred of the devices to students, who turned them back in at the end of the year. "We'd have to manually go through and redo all the iPads," Hoover explains. "It's not like a computer device that you can configure automatically."

So once a year you had to touch every iPad once? Poor dears.

Two years after the first Seton Hill deployment, Apple brought out Apple Configurator, a free download from the Mac App Store that can be used to configure 30 devices at once. But for many campus CIOs, that's too little too late. Those with big iPad implementations tend to rely on mobile-device management (MDM) applications like MobileIron that enable enterprise-level configuration, security, and app management.

And people with big Windows implementations certainly don't have to buy any additional software or services to manage those machines, am I right?

With the iPad, app management is a whole new ballgame for IT departments familiar with licensing and managing applications in bulk for desktop or laptop machines. Rather than selecting from software options hosted on the school's network, faculty and administrators download apps from the App Store, choosing from hundreds of thousands of options. Many schools simply haven't set up a good strategy for purchasing and tracking this new approach to apps. And in lieu of a policy, faculty often download an app using their personal Apple account, and then get the university to reimburse them. (Students are generally not reimbursed for their app downloads, which are considered a "books" expense.)

If you fail to plan, etc.

More than one CIO laments that the ad hoc nature of app downloads can lead to the school purchasing the same app repeatedly, especially if it's a popular one like Numbers. Hoover describes the problem like this: "You reimburse professor A for an app, and then they leave. IT wipes out the iPad because you don't want any sensitive information from the previous person, then yeah, you're going to have to buy that app again for professor B."

Layered model deployment. It exists for a reason.

Some schools have developed workarounds to avoid repeatedly purchasing the same apps. John Haverty, assistant director of user services at Washburn University (KS), says he started to recommend that departments create a generic account for their faculty members to use. "That way, if someone does leave, that software's not going to stay with them--it's going to move on to the next person," he points out.

Again, look at the layered model but you'd probably be cheaper just eating the cost of - what - $30-50 of apps when someone leaves. After all, how often do you turn over staff? The cost of processing their employment paperwork will probably outweigh the cost of the apps they need.

Haverty raises another app-related issue for tax-exempt universities, which is the time-consuming process for getting tax reimbursements on app purchases. "We had to go ahead and make the purchase, then contact someone at Apple to provide the tax ID to get the tax reimbursed." Haverty says that often departments don't bother.

Given that tax systems haven't really caught up with the internet yet, this is hardly a surprise.

Apple has a Volume Purchasing Program for education, released in 2011, which enables educational institutions to buy apps and books in volume at discounts and tax-free. And mobile-device management providers enable schools to manage their Apple volume licensing as part of the broader MDM. Indeed, MDM solutions solve just about all the major challenges presented by Apple devices, including network access, enterprise configuration, and device and app management, as well as security requirements like the ability to remote wipe a lost or stolen device.

OH WAIT - so all this complaining was actually for nothing because solutions to these problems already exist?

Apple, in fact, recommends that enterprises use them. But for schools like Washburn that have acquired devices like iPads and apps in a more informal manner, MDMs represent a time and resource sink that they haven't yet committed to.

If you fail to plan, etc.

But even if your school works with an MDM, there's still the problem of Apple TV working within the campus enterprise. Apple's media receiver is the ideal device for mirroring iPads onto a large screen because the two devices can connect wirelessly. Even better, Apple TV is configured to receive iPad input, so content looks like it should without tweaking.

Yup, Apple TV is great but calling it "the ideal device" and pretending it is essential for an iPad deployment is a great set-up for slamming it in the next paragraph.

Apple does provide a VGA adapter that can connect iPads to televisions and monitors, but, depending on the version of your iPad, you still often have to fiddle to get it to display apps.

The VGA adapter works great - especially with the Lightning port instead of the 30-pin - and I don't know what the "fiddle to get it to display apps" thing is about. I think that's just a lie.

So Apple TV seems like a natural choice for projecting iPad content. And faculty like Apple TV for features like the ability to stream Netflix. But as UTC's Hoover says, "making Apple TV work on the campus network is an abomination on a grand scale."

An abomination on a grand scale, eh?

Hoover may be a bit hyperbolic but he's captured the zeitgeist of IT's exasperation with Apple TV, which is the subject of a July 2012 petition posted on change.org by members of the Educause Wireless Local Area Networking Constituent Group. The petition notes that while Apple has created advertising that promotes the use of Apple TV in college conference rooms, auditoriums, and laboratories, "Apple TV, AirPlay, and Bonjour technologies make it very difficult to support these scenarios on our standards-based enterprise networks."

There's no doubt Apple TV and Bonjour can be finicky at large scale - this definitely needs some work - but I guess my question is what's so wrong with using the VGA adapter if AppleTV is simply impossible.

Issues with AppleTV are tangential to whether or not you should deploy iPad and are absolutely bogus as a justification for banning iPad from your school.

To set up Apple TV, says Jeff Kell, a member of UTC's network services, "you have to enable wireless multicast/broadcast traffic. Such traffic is sent out over every access point on campus, tying up airtime." This means that in an "enterprise setting, every access point will get a copy of every device's advertisements or discoveries in the entire enterprise." Not only is this a huge waste of airtime and bandwidth, Kell says, but it is "a disaster incident waiting to happen, such as some dorm kid streaming porn onto a classroom projector."

I might be old fashioned but I think of "disaster incidents" as being a bit more serious than this. Regardless, anyone who has actually deployed an AppleTV will know that you can turn on an on-screen code that any user must enter on their device to gain access to the Apple TV. For exactly this reason.

Also: don't these massive enterprises have VLANs?

In a blog post, Matthew Libera, performing arts technology consultant at the University of North Carolina at Greensboro, described the steps he took to use Apple TV in his classroom, which included creating his own network and sacrificing access to the internet on his iPad. While it was doable, Libera wrote, "there is no way in heck that I'll be able to convince any of my faculty here that this is a worthwhile undertaking."

Correct. If you have to do this, just get a VGA adapter and get on with your job. This is still nothing to do with iPad per se.

Indeed, many schools just forbid the use of Apple TV on campus. Or they turn to companies like Aruba Networks, which offers a solution for managing Apple TV and other Bonjour protocol-reliant devices in a university enterprise network. But again, this takes an investment in a third-party toolset that's generally attractive only for institutions that are all-in when it comes to iOS devices.

Banning Apple TV isn't actually that unreasonable in its current form. Still nothing to do with iPad.

All-in schools like Seton Hill say that that its iPad program would have been impossible without a major investment in a state-of-the-art network, which included replacing wiring for full campus coverage and upgrading both the wired and wireless networks. The latter, which provides campuswide 802.11n technology, was essential to support the demands of an iPad-oriented university population.

Dunno. I'd say campus-wide WiFi is essential to support the demands of any population of people born after about 1955, regardless of the computer they're using.

With the help of Enterasys network solutions, Seton Hill also revised its approach to managing the network. Now, the school handles network traffic on three virtual LANs: one for iOS devices, one for Mac OS X traffic, and a third for Windows and guest traffic. This approach streamlines network management, but also enables IT to manage network traffic at a more granular level.

OH WAIT - so there actually is a solution to these problems? I'm starting to notice a pattern in this article.

Lynn University (FL) is another iPad-committed campus that will roll out an iPad mini program to all freshman and transfer students this fall. It was able to create a robust campus network as a windfall from hosting one of the presidential debates last October. While the school had to pick up the tab for the new network, it got good deals on some of the technology from participating companies.

Note the subtle - and untrue - inference that you have to buy a new network to support an iPad program.

According to Lynn's CIO, Chris Boniforti, the school had to provide a completely new network environment for up to 6,000 media personnel attending the debate, and it had to be totally isolated from the university's network. Lynn essentially created a whole new network, roughly the size of its existing network, with the understanding that the school would bring it in to replace its aging network once the debate was over. The school estimates that process would otherwise have taken several years and pushed back its iPad mini initiative.

So Lynn got a new network faster because they hosted a presidential debate. Not clear how this is related to iPads.

For schools like Lynn and Seton Hill that have invested heavily in what Boniforti calls the Apple ecosystem, there seem to be fewer hiccups in using enterprisewide iPads. But IT directors who want to incorporate iOS products into their campus ecosystem without making such full-scale investments say they would like a little more support from Apple.

Let's be clear: what the author means here by investing heavily in the "Apple ecosystem" is actually "taking the time to understand how these devices work".

As one Educause wireless LAN constituent mused on the group's listserv: "This is where I daydream about the likes of several Apple engineers reading this list, thinking 'Gee, maybe we should consider how to make our toys work in the actual enterprise.'"

Aaaaannd there's the "toys" canard. It's amazing to me that the FAA approved American Airlines pilots to fly with toys in the cockpit.

So this article boils down to four actual complaints:

  • iPads come in boxes
  • You don't buy apps like you bought them from Microsoft
  • Apple TV is tricky to manage at scale
  • You need to buy a whole new network for your iPad program

The first complaint is just utterly bizarre. The second is true but, as the author actually points out, there are multiple existing solutions. The third complaint is the one that's actually true. Unfortunately, it's just nothing to do with iPad. The last is just false.

The entire article follows the pattern of building up small issues (and non-issues) to be insurmountable obstacles, then quietly admitting that a solution actually exists.

Using articles like this one to justify iPad bans is pathetic and embarrassing.