iPad+Deployment+Model

= Apples 3 Ownership Models for iPad Deployment =
 * //1. Personal Ownership Model://**
 * In this model, the school would have no "control" over a students iPad. Essentially, we would hand students an iPad, and they would have to go through the Setup Assistant (which all of the teachers have already done with their iPad)
 * Deployment Workflow: Prepare the device with Apple Configurator (IT would do this- it would allow us to wipe an iPad clear if it was lost or stolen, and to track it [NOTE: I think the remote wipe capability comes from an MDM, like Apple Profiler or Casper - chris] ), and then deploy the iPad to the students, who would be instructed via email or a link to a wiki to enroll in MDM system. Students would then use their own Apple ID
 * We have no control over what is put on the iPad.
 * If we give students codes to redeem an app (or a link to redeem an app, etc.), the app would then be owned by the Apple ID (which would be the students Apple ID in this model). We would lose $$$ depending on how many paid apps we wanted students to have access to. We would have to purchase new VPP codes for apps every year.
 * IT wouldn't have to push out updates for apps or iOS
 * Students are able to completely personalize their iPad
 * Can "Supervise" the iPad as part of Configuration, so iPad can be put into 'Single App Mode" for high stakes testing
 * Questions:

//**2. Layered Ownership Model:**//
 * In this model the school would preload "required" apps (all of which are owned by the institution), and then the iPad is given to students, who can log on with their own personal Apple ID and download their own apps.
 * Deployment Workflow: IT would prepare the device, and preload required apps. Before going through the Setup Assistant, the iPad would be deployed to students, so they could use their own Apple ID or create their own (if they do not already have one).
 * Disadvantages:
 * Apps that the institution owns can not be updated throughout the year via wireless. If an app that the school owned (example: Pages) had an update half way through the year, students would have to go to a "Configuration" station, and plug in their iPad in order to get updates.
 * Need "Configuration Stations" (Essentially, an iPad Cart that they can plug into to get updates and such). One on each floor? "Office Hours"- maybe before school and during lunches? iPads can only be updated from the "Station" that "owns" it - the one it was originally prepared from.
 * Students can not plug their iPad into a home computer and "Sync" to iTunes. This means that 1) All backup must be done to iCloud, which allows for 5GB of storage (does not include apps; just data/content in apps), and 2) Cannot load music or video to Music/Video apps via iTunes.
 * Advantages:
 * The School could assign Apps that have been paid for to iPads. The school would always own these apps, so they could essentially be "reused" every year- the Apps would be a one time cost for the school district.
 * Students are still able to "personalize" their iPads. They can log on with their own Apple ID's and download their own apps.
 * If a teacher finds a free app part way through the year that they would like students to have, they can have them use their own Apple ID and download the App, rather then wait for the following school year to change the image of the iPad or have to schedule time for all students to plug into the "Configuration" station.
 * Can use iBooks for purchased content - the license requires a personal Apple ID
 * Can use iCloud to backup user content - this requires a personal Apple ID
 * Can "Supervise" the iPad as part of Configuration, so iPad can be put into 'Single App Mode" for high stakes testing
 * Questions:
 * If we go with this model, what happens when we have parents that do not want students to be able to download apps? Answer: We will have to have a "fleet" of iPads that are fully institutional for those students. They will have to set up times to meet with IT to update their iPad. (Beth)

//**3. Institutional Ownership Model:**//
 * In this model, the student has no ability to personalize their device- it is essentially on complete lock down, owned and run by the school. These iPads are usually directly attached to a cart for "shared" use (although they do not have to be).
 * Deployment workflow: Prepare Apple Configuration, Prepare master device, prepare additional devices with the master's back-up, and then optionally you can assign users.
 * Disadvantages:
 * Requires an Apple ID that is not necessarily tied to a person, but rather the institution (This can be both a pro and a con)
 * Students allowed no personalization, they may not go into iTunes and enter their own Apple ID to download apps or other content
 * Cannot use iBooks for purchased content - the license requires a personal Apple ID
 * Cannot use iCloud to backup user content - this requires a personal Apple ID
 * Advantages:
 * The Institution (School) would retain rights to all of the apps- they would be a one time cost.
 * Requires an Apple ID that is not necessarily tied to a person, but rather the institution (This can be both a pro and a con)
 * Saved cost of an MDM
 * Questions:

//**Overall Questions (Non-specific to an ownership model):**//
 * 1) iBooks? How does licensing work with iBooks? Answer: purchased content can be rolled out with VPP codes. However an institutional iTunes account CANNOT be the primary - the license requires a personal Apple ID. This limits the deployment model to Personal or Layered.