To view the recorded webinar that goes along with this blog post, click here.
We all believe that the iPad has the potential to transform student learning – but as an IT administrator, it can be daunting to turn a stack of newly minted devices into engaging educational tools in the hands of your students. If you’re about to roll out over 50 iPads to your school district and have been avoiding the “D” word like the plague, have no fear. eSpark is here to ease your deployment and management woes!
iPad deployment includes all of the steps between buying an iPad and beginning to use the device. For an individual’s personal iPad, this is often a very fast and easy process lasting no longer than five minutes: You just open the box, turn it on, download the apps you want on your device, and go. But for a school, or district, with potentially hundreds of iPads–each one requiring a specialized list of apps that need to be purchased before protecting the devices with a case and sending them out to classrooms. As an administrator or teacher, there are a few things you will need to know before you deploy your iPads. Lucky for you, the eSpark Engineering team has created a five step road map to aid in this journey, highlighting the best practices and considerations relevant to deploying and supporting iPads in education environments.
Deployment Road Map:
It may take several days to several weeks to complete all the steps involved in iPad deployment depending on the size of your school/district and how many iPads you need to deploy. It is crucial to develop and communicate a detailed plan and timeline before diving into the deployment process. We recommend planning a minimum of three whole days of deployment, and then adding on three days for every 1,000 students in your iPad program. For example, if you are deploying iPads for 3,000 students you should plan on 12 days of deployment (use the equation 3+3x).
Step 1: Deployment Model
The first step in the iPad management process is to plan what type of model your district will implement with your devices. Some schools choose to go 1:1 and provide every student with their own iPad. Another option is to use a split class model in which half of the classroom will work independently on the iPad while the other half receives targeted instruction from the teacher, effectively lowering the teacher to student ratio. You could also implement an iPad centers model in which students rotate to an iPad center, enabling 5 or 6 iPads to be shared by an entire classroom of students. A mobile cart is also a good option for a group of iPads to be shared amongst classrooms in one building. Your deployment and setup process will differ depending on which iPad model you choose, so the earlier this is decided, the better.
Step 2: Mobile Device Management (MDM)
An MDM, or Mobile Device Management system, uses Apple Push Notifications to wirelessly collect and send information to iPads. There are currently about 50 MDMs on the market, but most have the same core functionality. While our largest client uses JAMF Casper, if you are new to MDM our engineers recommend starting with Meraki. It’s free and easy to use. Apple also has an MDM called Apple Profile Manager, which comes with the OSX server and is only $20 if you have a Mac Mini to run it on. Our engineers don’t recommend Apple’s product at the present time, however, as Apple’s server products are not the most efficient.
Step 3: Initial Preparation
When you’re working with hundreds of devices, a little planning will go along way during the year. Once all the iPads are stacked in a pile or in a sync cart, how will you know which device is which? Here’s an insider’s tip: Apple’s boxes have a barcode with the serial number of each iPad on the outside. Stickers can be a great tool to use to put an asset tag or your inventory code on the outside of both the iPad and the iPad case. You can use your MDM to help correlate all this information together. Naming devices in purposeful ways, like by building or class, will enable you to locate the iPad from your MDM. Name devices “Timothy Jones” or “BIRD-3A-2” instead of “Timothy’s iPad” or the default “iPad”.
Apple Configurator is a great tool for initial device setup. You can use it to upgrade to the latest version of iOS, configure the MDM, configure WiFi access with a profile, add device restrictions, and add any apps that are standard to all devices. We also recommend that schools make their devices supervised in Apple Configurator. This allows your district to have more security and control–however, the biggest downfall of this option is that the devices will be tied to a single computer.
Step 4: Purchase Apps (VPP)
With the App Store’s 50,000 educational apps for the iPad, it is possible to design a curriculum for any grade level in any subject. However, with a huge variety of apps, this can be an overwhelming challenge. There are several resources and services online that you can use to assist you in your search, or you can use eSpark and we’ll create the curriculum for you.
Once you have decided which apps to purchase, you’ll need to buy them all. Before you purchase, however, you need to know which apps will go on which devices (remember that organized deployment plan?). For example, if six students share one iPad, they can use the same apps without your organization having to buy the app six times over. However, if six students share two different iPads, you would need to buy an app for each iPad. This complies with Apple’s terms of agreement.
Once you know how many apps you need to buy, you can begin the purchase process. Most educational iPad apps can be purchased from Apple’s Volume Purchase Program for Education (VPP) store, which offers a discount of half off any order of 20 apps or more. When an app is purchased through the VPP store, you are given a code that can be redeemed for an app either through the iTunes Store or Apple Configurator. For more information on the VPP process, click here.
Step 5: Install Apps
Syncing is a term we use to describe the process of downloading the apps themselves onto an iPad. There are two methods used to sync iPads. In a wired solution, syncing is done from a computer that has all of the apps pre-downloaded. The apps are then transferred from the computer to the iPad via a USB cord. A wireless solution, on the other hand, is when apps are downloaded directly onto an iPad over the Internet. There are a variety of both wired and wireless methods that can be used to sync your iPad. We’ve outlined the most popular and included the advantages and disadvantages of each:
Apple Configurator – Wired
Apple’s official recommendation for iPad deployment is a wired solution that uses purchased VPP codes on a computer. As each iPad syncs, Apple Configurator redeems the VPP codes from an Excel spreadsheet and submits the information to Apple.
|Can prepare a set of new iOS devices that are configured only once and then deploy to users.||Loading VPP codes onto Excel spreadsheets is a tedious process that requires a lot of manpower and time.|
|Update device to latest version of iOS, install configuration profiles and apps, enroll the devices with your organization’s MDM solution, and go!||Paid app installment requires iPads to be “supervised” by one computer used for deployment so all future changes to the iPad must come from that specific computer.|
If you choose to use Apple Configurator, we recommend only using it for mass syncing and use an MDM for smaller changes and inventory.
iTunes – Wired
iTunes uses a different protocol for syncing where you redeem one VPP app code per iTunes authorized computer, and keep the rest on hand as proof of purchase.
||This method was built for personal use and does not have an elegant method of keeping track of apps on your computer, especially if you are using the different Apple IDs to purchase the apps and sync the iPads.|
If you have strong WiFi and dispersed campuses where central management is difficult, we recommend using an MDM for deployment.
|Manage everything centrally in one place||Can bog down WiFi network|
|Fewer site trips to collect iPads from classrooms||Still need an end user with an Apple ID and password to accept apps and changes to iPads (iOS7 fixes this but not in time for all deployment)|
With the roadblock of needing users to enter a password and accept changes, we use a wired solution to sync apps and an MDM to track license changes and check inventory–how many iPads a classroom has, which apps are installed on each, etc. While we still support major MDMs such as Casper and Airwatch, we recently built our own MDM to better integrate with our system so that we can quickly see which students are missing apps in the eSpark curriculum.
Want to learn more about iPad deployment and app management?
Be sure to check out our recently recorded webinar:
Easy iPad Management at Scale