This is the policy I would like to adopt. Unfortunately, the people driving this decision are of sufficient management level that I will get sucked into going beyond the written policy.
I have a meeting next Tuesday. I don't do Powerpoint, but I am putting together a dog and pony show with regard to costs, reliability, remote data transfer, etc. My hope is that once I am done, they will (1) be embarrassed to spend the money, and (2) afraid that things that used to be correctable OTA, while they were traveling, will be unavailable. On Wed, 2010-07-21 at 13:07 -0400, Jonathan Barker wrote: > We've chosen to support BlackBerry, BlackBerry devices and Exchange > ActiveSync. > > We don't support non-BlackBerry devices. > > This means that if a user gets an EAS phone that doesn't fully support > EAS and our security policies, and it doesn't work, they are out of > luck. Many Android devices don't support EAS security policies > correctly, and will not sync. iPhones had this issue when they first > came out too. > > By supporting EAS, but not the phones, then IT won't spend more than a > few minutes assisting a user with initial setup. > > Security issues obviously are not addressed, but top management made > that decision. We evaluated Good and found that it wasn't what we > wanted. -- Art Alexion Infrastructure Engineering Group (IEG) _______________________________________________ Bes-Admins mailing list [email protected] http://www.dataoutages.com/mailman/listinfo/bes-admins http://www.dataoutages.com http://www.dataoutagenews.com RSS Feed: http://feeds.feedburner.com/Bes-admins --------------------------------- Bes-Admins mailing list is sponsored by Dataoutagenews.com. http://www.dataoutagenews.com
