Commentary

Randy George
 

Ramming The iPhone Into The Enterprise

Whatever side of the fence you're on about supporting the iPhone in the Enterprise, you're probably going to have to do it eventually. The question is, can you appease your users and keep your data safe simultaneously? There might be a middle ground to be found.

Whatever side of the fence you're on about supporting the iPhone in the Enterprise, you're probably going to have to do it eventually. The question is, can you appease your users and keep your data safe simultaneously? There might be a middle ground to be found.There's a reason the iPhone is so popular. It's the same reason that Windows is so popular as a PC OS. It's the interface. Even your grandma can use an iPhone, with a little training of course. The iPhone is relatively fast and rarely if ever crashes, not something I can say about my Windows Mobile Device, or even my blackberry for that matter.

Today's reality is that many IT Managers have little control over what devices are used in their environments. If your CEO barrels into your office asking to have his email setup on his new iPhone, are you going to say no? I suppose you could say no, but that might be a career ending decision.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

But why are so many enterprises still reluctant to support the iPhone? The iPhone is actually more enterprise ready than you may realize. For example, you can push email to an iPhone via exchange activesync over an SSL encrypted channel. iPhone 2.0 supports Cisco VPN's, WPA, and 802.1x. Additionally, device lock and pass code policies can be set centrally and remote wipe signals can be sent over the air in the case of device theft.

You could make a compelling argument that the iPhone COULD be configured to be just as secure, if not more secure, then any other competing device. But alas, the iPhone is really a consumer device, and it's difficult to control the information and applications maintained on these devices, so is there an middle ground to be found? How about the new Citrix XenApp receiver for the iPhone. Forcing users into using terminal services to access internal corporate applications, email, etc., negates the concern that private data will fall into the wrong hands. Most importantly, concerns about application compatibility go out the window, because you're forcing users to access apps via Citrix.

Have you deployed iPhone's on a grand scale in a highly complex enterprise environment? Please educate us on some of the tools, tricks and gotcha's that you've run into during your travels. Your experience is sure to help me, and others, as we try to come up with some best practices for supporting iPhone's in our organizations.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links