The biggest issue is the key generation. The hardcore security of iOS is that only signed apps are allowed to run on your devices, unless you've jailbroken it and installed a package to bypass this, typically for non-licensed deploying or app pirating.
You need to generate a key based on Apple's certificate authority, or CA. Then you upload it to the portal and Apple approves it, provided you're a paid developer. Whenever you deploy an app, be it to the store or to your device for testing, you sign the app with your digital signature, which is backed by Apple. This tells your device, or your testers' or customer's devices, that the app is from a developer who is who he says he is. Since the main way to get an app on your device is through the store, you have the confidence that it is not tampered with (since the developer's signature is invalid with the flip of a single bit in the app) and that it's passed through Apple's checks by being hosted on the store. This is a two-fold assurance of the security.
Provisioning profiles are a whole other beast. Previously, Apple would let you "sideload" an app to any number of devices you wanted. This meant that you could bypass the App Store and sell apps yourself as a download, no different than desktop apps. Apple didn't approve of this and has since limited it to 100 devices per year being listed on a single developers account. You add your devices to the portal by it's UDID, it's unique fingerprint, and you would need to get this from any devices you wish to beta test your app or adhoc deploy to. Since it costs roughly $0.99 / year / device, it's prohibitively expensive to sell apps this way, but it allows you to have plenty of beta testing slots. Of course, a provisioning profile is the list of which devices can run which apps signed by who developer.
In recent Xcode's, once you've established your key (which would be difficult to automate from inside Xcode), you can plug in any iDevice, open the organizer and click "Use for Development". Xcode will prompt for your credentials and then automatically add the device to the portal and create a provisioning profile for you. Once you've done the initial setup, it's basically one-click to add an extra device. I don't think Apple is as worried about the initial setup being automated, since it's only a one-time process.
(Sorry, I'm trying to work on my long-windedness.)
The data being deleted is in reference to the data already stored on the phone (e.g. the sister's contacts). An iPhone can only be synced to one PC at a time, and if you want to setup syncing with this new PC, you will need to delete all of the data on the iPhone.
If your wife wants her sister's contacts, then she shouldn't sync and wipe the data before she has a copy of all that info. One way to to get the info on to the iPhone is to sync it with outlook (via iTunes) on the sister's PC. Then export the contact's from Outlook, copy the file to the wife's PC, import into Outlook. Then proceed ahead with the sync that will wipe all the data, and set it up to sync with Outlook. This way your wife will have all the original contacts.
If your wife does not care about her sister's contacts, then you can go ahead with the initial sync that wipes all the data.
When the phone is synced with Windows 7, it will use the following folder for backups: \Users\(username)\AppData\Roaming\Apple Computer\MobileSync\Backup\
. Therefore, you should back up that folder if you want to keep a second copy on your computer.
If the most important data that will be used on the phone is Contact information, I would recommend that instead of using Outlook, that your wife use Google Sync. This will allow her to store all of her contacts in Gmail, such that if anything happens to the phone, the contact info can easily be accessed again online, all without ever having to sync or backup (or double backup) the phone. Google Sync can also sync your Calendar. If you setup a Google account as IMAP, you could even have the Notes synced to the cloud as well.
Keep in mind that when the data gets wiped, everything on the phone will be deleted. This includes, but is not limited to, the following:
- Music
- Videos
- Podcasts
- Address Book and Address Book favorites.
- App Store Applications and their data.
- Application settings, preferences, and data.
- Autofill for webpages.
- CalDAV and subscribed calendar accounts.
- Calendar accounts.
- Calendar events.
- Call history.
- Camera Roll (Photos, screenshots, images saved, and videos taken.)
- In-app purchases.
- Keychain (this includes email account passwords, Wi-Fi passwords, and passwords you enter into websites and some other applications.)
- List of External Sync Sources (Mobile Me, Exchange ActiveSync).
- Location service preferences for apps and websites you have allowed to use your location.
- Mail accounts.
- Managed Configurations/Profiles.
- Microsoft Exchange account configurations.
- Network settings (saved wifi spots, VPN settings, network preferences).
- Nike + iPod saved workouts and settings.
- Notes.
- Offline web application cache/database.
- Paired Bluetooth devices.
- Safari bookmarks, cookies, history, offline data, and currently open pages.
- Saved suggestion corrections.
- SMS and MMS (pictures and video) messages.
- Trusted hosts that have certificates that cannot be verified.
- Voice memos.
- Voicemail token.
- Wallpapers.
- Web clips.
- YouTube bookmarks and history.
(This list was slightly modified from Apple's page)
Best Answer
Well, I guess you don't want to be distracted by yourself constantly touching you phone right? That's what I need too.
My way to do this is totally not recommended, but that's the only way I have in mind. Get a passcode, do like 11 false attempt, and you can lock yourself out for 15 minutes or more. It's something extremely stupid to do, and I don't recommend doing that or anything similar.
Just in case some emergency happened, and you need to contact someone. You picked up your phone, and, ya. It's up to you.