I bought an iPhone 5 because I was out of contract, but for work reasons a cheap iPhone pay-go plan wasn't an option. That meant all of my fees were going to AT&T, instead of paying off half a new phone. On the other hand, if I bought a $700+ contract phone for $300 down then my 4S could go to my daughter and spare me the cost of an iPod Touch while serving as a reserve phone in case I lose the 5.
So I got the standard white 32GB. Very soon I'll get a 2nd cable then wait for the 3rd party adapters to arrive, pick up a cheap case and look for a good one in a month or two.
This post isn't about that however, and it's not about how light and thin it is, or the silly address book that can't be searched by source, or the over-saturated Calendar colors, or the cable, or the maps, or the Podcast app from Hell. it's about how the upgrade works when you go from one corporate Exchange Server authenticated device to a new one.
The corporate authentication process changes the way the phone works and it may make a backup/restore trickier. Among other things that are mandated (I can't change):
- The phone will wipe with 10 pw errors
- It auto-locks at 5 minutes (so many bicycling apps don't work well any more)
- Mandatory 6 digit passcode.
To add an extra annoyance, post phone update I have to wait a few days for the company to reauthenticate the new device. I can't complain though, they pay much of my bill.
I picked up the phone at the AT&T store so I wouldn't have to worry about home delivery; they activated it at 6.0 and I started the corporate account process. That locked down the phone, which is perhaps why the next step didn't work.
After I updated the 5 to 6.01 (among other bugs, 6.0 messes up some Outlook appointments) it showed in iTunes as 'iPhone'. Then I attempted a restore from my 4S -- but it stopped at a partial restore.
So I wiped it completely then tried again. Since my 4S backup was encrypted I expected it to store and restore my credentials. It worked with some quirks.
The restore had two phases. In Phase I it requested my iCloud account credentials (not same as my store credentials) and I had to set a "secure" 6 digit PIN. Then the phone restarted and went into Phase II, restoring about 150 apps, etc. This took about 2 hours.
The restore went pretty well, except for Reeder.app! As usual I had to reenter all my credentials. I think this is a Reeder.app bug, no matter what I do I seem to always have to start over. I also had to redo Google's barely functional and almost forgotten multi-calendar ActiveSync configuration via http://m.google.com/sync (from iPhone) but I expected that. It hasn't been updated in years, and it's awkward and all-bug-forgotten, but it still works. That meant I had to do my calendar color assignments too; fortunately I wrote down the rules I use to assign colors across the 13 calendars I currently sync.
It could have been worse.
PS. In my haste I swapped digits when I set my new passcode (twice). I got through 6 of my 10 tries before I made a wild-guess at what I did wrong and got in. I almost had to wipe the phone and start over again. Be careful!
Post a Comment