Originally Posted by lakorai
Apple needs to do several things to help the iPhone make it in an enterprise market:
Inaccurate post. My Fortune 50 company already has these deployed in some of our units. May well overtake BB in time due to lower server-side costs - not having to deploy/manage BES units in our datacenters and depend on RIM NOC availability.
1: make an iPhone available on ANY network. Make it available for ATT, but also Sprint, Verizon, and yes even cruddy T-Mobile. Regional carriers, such as US cellular and AllTell need in on the action too. LOWER your outrageous cut that you demand from the bill every month.
>> We use specific/favored vendors all the time. The ubiquity argument is not a corporate deal-killer.<<
2: Make an enterprise deployment application, such as Blackberry Enterprise Server or Systems Management Server for Windows Mobile available for iPhones. The push features in Snow Leopard Server (which I just installed at our law office) work well, but they hardly can compete with Exchange ActiveSync (especially Exchange 2007/2010 which uses Exchange Web Services over WebDAV). You HAVE to make this application available for Windows Server 2003/2008 and various Linux flavors; making it only available for OSX Server is a bad idea, as enterprises are not going to spend thousands more on Snow Leopard server(s) just to manage iPhones.
>>You mean something like Windows XP Service Pack 3 with .NET Framework 3.5 Service Pack 1, or Windows Vista Service Pack 1 with .NET Framework 3.5 Service Pack 1. Which supports the iPhone Configuration Utility which in turn lets you create, encrypt, and install configuration profiles, track and install provisioning profiles and authorized applications, and capture device
information (including console logs). Also, since we are using Exchange Server 2007 we can initiate remote wipe using Outlook Web Access, the Exchange Management Console, or the Exchange ActiveSync Mobile Administration Web Tool.<<
I don't know if you guys have seen Blackberry Enterprise Server or SMS for WinMO, but they rock. I can lock down everything on a phone. I can do remote wipe. I can install and enforce applications and preferences. I can run firmware updates/OS updates. All from the Blackberry management console. I CANNOT do this with an iPhone.
>>Seen both, not impressed. Both problematic, neither one unique. Errr, you CAN. Actually.<<
Running with Exchange ActiveSync was a very smart move. Making remote wipe work is also a great plus.
3: Make iPhones available without a camera. Yes some companies, like Lockheed Martin, would never allow an Iphone due to the camera. Many courtrooms will not allow a cellphone in the courthouse unless if the phone is camera-less.
>>Camera can be disabled via profile.<< There were rumors also of special runs of iPhones made for the Feds to use under house rules (no camera installed), but I maintain that as rumor since I have no indication that that actually occurred.
4: Battery has to be user replaceable. It is unacceptable for a user to be without a phone for a week or two while they wait for a replaceable phone. If the battery was user replaceable (read: using a door), then this would be a non issue. I could, as an admin, with some extensive user interaction, have replacement $600 iPhones on hand and I could FedEX overnight one. But $600 is way more expensive than a $20 battery.
>>This is not an issue here. Units are swapped actively all the time for more than just battery issues. Battery issues actually comprise only 2% of mobile device failures - out of all classes of mobile devices in our enterprise.<<
5: Make it easy for the company (this would apply for large corporations) to deploy custom applications without having to pay a high fee to Apple to get it "approved". Apple actually has an application deployment tool and free development tools for the iPhone, but some companies may want to run a custom app.
>> Already deployed as a the corporate/enterprise part of the APP Store (something consumers do not see), we already have custom apps deployed using that.<<
Example: I used to work for a merchandising company called Mosaic Sales Solutions. They use Windows Mobile 6 HP and Symbol handhelds. They load a SQL syncing program called Qrelay that allows the reports to be filled out in the field by the rep. The rep then connects via Wifi and syncs to Mosaic so they don't have to enter in the reports by hand. This saves at least an hour or two of labor by the rep.
Mosaic would never consider the iPod touch or the Iphone because they cannot just make their proprietary program and deploy it. They are not going to expose their code (which is confidential) to Apple just to get it "approved".
>> Per your example, the app itself would only have to be the connector, not the proprietary app you seem to think is in need of protection from Apple's "prying eyes"<<
Windows Mobile may not be perfect (won't be really good until WinMo 7 Photon comes out), but at least you can write a program and deploy it without paying some sky high fee to Microsoft.