Didn't read about it on the WWW before upgrading, I take it? : )
Someone referred to it as a "Leap Pad" UI. Regards, Don Guyer Catholic Health East - Information Technology Enterprise Directory & Messaging Services 3805 West Chester Pike, Suite 100, Newtown Square, Pa 19073 email: [email protected]<mailto:[email protected]> Office: 610.550.3595 | Cell: 610.955.6528 | Fax: 610.271.9440 For immediate assistance, please open a Service Desk ticket or call the helpdesk @ 610-492-3839. [cid:[email protected]] From: [email protected] [mailto:[email protected]] On Behalf Of Adam Farage Sent: Thursday, September 19, 2013 1:21 PM To: <[email protected]> Cc: [email protected] Subject: Re: [Exchange] RE: iOS 7 I haven't seen any issues yet with my iOS device or exchange, other than the less than appealing UI. Reminds me of the old nexus days (nexus one). Hopefully my lumia 925 is here soon before I break my phone in two. Sent from my iPhone On Sep 19, 2013, at 1:18 PM, "Richard Stovall" <[email protected]<mailto:[email protected]>> wrote: I'm failing to see the downside. :) On Thu, Sep 19, 2013 at 1:06 PM, Maglinger, Paul <[email protected]<mailto:[email protected]>> wrote: We're telling people to hold off. Our IOS guy has told us there has been some reports of this update "bricking" the device when applied. From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Dave Vantine Sent: Thursday, September 19, 2013 11:51 AM To: [email protected]<mailto:[email protected]> Subject: [Exchange] iOS 7 Anyone experiencing any issues with iOS 7 and EAS? I am getting queries from some of the BYOD users regarding upgrading. Thanks Confidentiality Notice: This e-mail, including any attachments is the property of Catholic Health East and is intended for the sole use of the intended recipient(s). It may contain information that is privileged and confidential. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please delete this message, and reply to the sender regarding the error in a separate email.
<<inline: image001.jpg>>
