NEWSLETTERS
 

CIO.com updates, insights and advice on technology, management and your career.

 CIO BlackBerry News and Tips
 CIO Research and Analysis
 CIO Microsoft
 CIO Insider
 
 
 
SUBSCRIBE TO CIO
 
Are you involved in setting the direction for your company's IT budget or strategy?

Apply today for a FREE subscription to CIO Magazine!

 


Thu, Jun 5, 2008 15:39 EDT

Smartphones in the Enterprise: No Love for Windows Mobile?

Topic: Infrastructure

Blog: Mobile WorkHorse

Current Rating: 5 Comments: 6

Modern corporations looking to deploy enterprise smartphones have three main options when it comes to infrastructure, platforms and mobile operating systems, if security is a concern—and it should be: Research In Motion's (RIM) BlackBerry, Microsoft Windows Mobile or a combination of both.

During the past months of covering mobile and wireless technologies for CIO.com, I've spent much of my time researching and writing about smartphones and related technologies. More specifically, I write about BlackBerrys. A lot. I squeeze some iPhone coverage in there. But Windows Mobile? Not so much, though I have penned the occasional Windows Mobile editorial.

Why? First of all, my readers, CIOs, IT executives and folks who want to become them, are largely BlackBerry users, so related coverage is valuable to them and their organizations. Secondly, as a result of the previous fact, BlackBerry how-tos, tips and tricks and tutorials turn a lot of digital pages, and let's face it, we have to cover what's popular. Finally, I'm a BlackBerry lover, a CrackBerry addict if you will, and as such, the world of RIM smartphones is my true area of expertise.

But as a number of readers have recently pointed out, many organizations use Windows Mobile and the Microsoft Exchange Server—either as standalone smartphone infrastructure or together with a BlackBerry Enterprise Server (BES)--and I'm not doing them any favors by focusing (almost) solely on BlackBerry. I agree, and I'm going to make it a point to dedicate some time to Windows Mobile users and the IT issues that are keeping them up at night.

Beginning that effort, I want to take a moment to ask you folks, namely the CIOs who make mobile infrastructure spending decisions, smartphone administrators, and handheld techs, why your organization chose BlackBerry over Windows Mobile, vice versa, or both? And if you could do it all over again, would you go the other route?

I'm curious about the ease of software deployment, cost comparisons, scalability, the variety of available handsets and what that means to you and your users. Are your support techs spending more time on BlackBerry maintenance than any other mobile device, as a suggested by a recent CompTIA survey? From an enterprise standpoint, which mobile platform has the better associated application development environment? Which is more secure?

Please, share you experiences, thoughts, opinions, endorsements, warnings and lessons learned.

I'm all ears...

AS

You do not have flash or javascript support.
Average (3 votes)
5
 
 
Fri, Jun 6, 2008 16:46 EDT
Posted by: MEK
Rating: 90

We have been using Windows Mobile Devices connected to an Exchange 2003 Server for a little over 3 years now and are in the process of deploying that solution globally. This was a “greenfield” deployment with little or no prior smart-devices in the field, so all products were judged without legacy considerations.

To answer some of your questions:

I was involved in the decision making process to go with Windows Mobile and we ended up making the decision of WM over Blackberry for the following reasons:

• Cost: 4 years back, the deployment and maintenance of BES was a significant expense and it was no secret that at the time RIM was generating most of revenue on the servers sales and support vs. device sales and support. The WM layer was built-in to the Exchange 2003 system, which meant no additional licensing costs or server costs. It also meant less training and overhead from an HR standpoint in an area where FTE’s were still a significant concern.

• Device/Wireless Provider flexibility: Historically, separating the software from the hardware has led to faster innovation and product development. We were intrigued by the development model that Microsoft had chosen to use, which was to make the software available and customizable by the hardware vendors and felt that this would ultimately give is a broader range of product to choose from and easier way to switch Wireless Providers (or even use many different Wireless Providers) should we wish to.

• End-User comfort: While there was small and vocal group during testing and evaluation that preferred the simplicity of the Blackberry interface, most non-power users that we did our evaluations with preferred the “comfort” factor of the windows-like interface as well as the mini-Office applications. The WM version of Outlook was especially well-liked.

• Security/IP issues: There was a lot of discomfort (warranted or not) about the idea of email and discussions revolving around IP being moved through a centralized Blackberry network. Many of our CxO’s were more comfortable with the idea of the devices establishing a direct, SSL based connection to our mail servers and updating in that manner.

A little over 3 years after deploying the first of these devices on a fair-sized scale (about 1,000 Windows Mobile Devices in the field), it is possible to make a few broad observations here:

• Initial stability of the Windows Mobile O/S left a lot to be desired. Second-generation product (which was the first device we mass-deployed) typically had to be reset about once-a-week, battery life was poor, and all user settings got wiped if the battery was completely depleted.

• However, as frustrating as the First and Second-generation products were, the current generation of Windows Mobile devices are quite nice indeed, with very few issues overall. The range of design has also met expectations, with a WM design to fit almost every individual user need. The downside is that the quality of hardware and the implementation of the WM O/S on that hardware can vary widely. Testing new designs is therefore very important. (i.e. don’t assume that because all the devices are running WM 5.0, they will behave in same manner or have consistently reliability on different hardware designs).

• Wireless Provider support was (and still for the most part is) pitiful. An unanticipated side-effect of separating the O/S from the Hardware was the amount of interjections and interference that many of the major U.S. Wireless carriers inserted into the design and how often that they stifled innovation. In addition there was a complete lack of understanding of the Windows Mobile operating system, which has lead to tremendous amount of finger-pointing when design issues for a particular device are run into. The simplest way to solve this is to thoroughly test candidate WM devices and bitch like hell to the Wireless Carriers when you find features or capabilities that have been “turned off” or removed for one reason or another.

• Costs and support have been lower that what we have seen with similar sized locations running BES. We have found that after 3 years, the amount of support we have to provide for our Windows Mobile users has remained fairly low-level, with no FTE needed to support them. Basic support is provided through our help-desk and advanced support is provided through our Exchange Admin Team.

• The potential for broadening the types of devices and O/S’es beyond the Windows Mobile platform, while not fully realized yet, has great potential. Because of MS’s aggressive licensing of the ActiveSync layer to mobile device manufacturers, we are heading in a direction where it will be possible to deploy devices running on a non-MS platform that can still directly connect to the Exchange Server. This standardization of the communications layer brings us out of the locked communications system that is BES and will allow us to look at devices like the iPhone should we choose to do so.

If we could do all over again, I believe we would…

 
Sat, Jun 7, 2008 9:59 EDT
Posted by: Al Sacco
Rating: 10

Hi MEK,

Thanks VERY much for your insightful comment. Your response is exactly what I was looking for in writing this post, and I hope it sparks others to open up as well.

I find a number of your points very interesting. For instance, I hadn't really considered the potential headaches of IT complications that can arise from deploying a handful of various makes and models of Windows Mobile devices, some of which simply aren't as reliable due to issues with the software.

If you're interested, I'd love to speak with you some more about your experience with Windows Mobile and its associated IT infrastructure. If so, shoot me an e-mail at asacco[at]cio[dot]com.

Thanks again.

AS

 
Tue, Jun 10, 2008 11:26 EDT
WM
Anonymous user
Posted by: pcguy74
Rating: 10

I would agree with every one of your points. We were part of a much larger organization several years back and we/they operated BES and Blackberry devices. We found it necessary to have 2 FTEs to support the devices and recognized the cost was prohibitive. When we spun off from that company we spent one year evaluating Blackberry vs. the first generation WM devices and we ended up with WM. We have not been sorry for the decision, and would do it again too. There has been some pain along the way, but there was pain with Blackberry too. Thanks for the excellent post!

 
Sun, Jun 8, 2008 1:46 EDT
Anonymous user
Posted by: Justin Yao
Rating:

The fact that Blackberry came way before WM gave it a huge advantage in the US and Europe, making "Blackberry" a symbol of mobile emailing. To fairly compare market performance of these two technologies you need to look beyond the developed world, into places where RIM doesn't have a first mover advantage.

I was involved in selling Exchange/WM solutions in China for a couple of years and there were only two possible outcomes: 1) client chose Exchange/WM solution, or 2) client decided mobile emailing was not for them. As our competitor in most of the engagements, Blackberry never made it beyond POC.

Reasons why clients choosing WM over Blackberry were common:

1. Cost. WM solutions are cheaper in implementation, maintanence and supporting. One CIO told me that "It's ridiculous to have to pay them ahead and afterwards."

2. Security and controllability. In earlier version of RIM solutions (I'm not familiar with the latest ones) the BES server had to store the user's domain credential to retrieve messages from Exchange. Besides, managers concerned about data flowing to and from RIM server - even if they trust RIM, there's no way to tell their users, "because the cable between Asia and the US is broken, you can't get your emails from your Chinese customers".

3. Choice of devices. Apparently WM shops have much more device choices ranging from $150 smartphones to $450 PDA's. On the opposite all Blackberry looks similar.

4. Ease of development and availability of applications. There're simpy more ISV's working on WM platform than on Blackberry. Even if you choose to develop your own applications, WM is cheaper and easier.

There're more Blackberry shops in the US, simply because it's already there before WM is good enough.

 
Tue, Jun 10, 2008 11:49 EDT
Anonymous user
Posted by: Philip Andreae
Rating: 10

I was wondering what your opinion is of the Palm Treo series of devices. I have had both a 650 and 680 and am very comfortable. I accept and relish the fac tthat it is pull mail and has all sorts of software availabel for it. Maybe not copletely compatible with Microsoft office but more than adequate.

Post new comment

* Subject:
* Username:
* E-mail:
The content of this field is kept private and will not be shown publicly.
Homepage:
* Body:
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <img> <blockquote> <strike> <p> <br>
  • Lines and paragraphs break automatically.
More information about formatting options

* Denotes required field.

About this Blog

Al Sacco writes about (and drools over) anything and everything mobile or wireless as it applies to the global workforce--with a focus on BlackBerry smartphones.

Got tips? Send 'em Al's way.

Follow this blog on Twitter: @MobileWorkHorse.

Start a Conversation
Click to post

Got something to say? We want to hear it! Click the Post button to get started. GO»

EXPERT ADVICE
See our roster of experts.

Advice & Opinion from more than 113 of IT's most insightful thinkers.

  PARTNERS       WEBCASTS    
 

Windows 7 Webcast Series

There's a lot of buzz about Windows 7 out there. Each month in our webcast series, listen to analysts and customers discuss how Windows 7 and the Windows Optimized Desktop is impacting large companies around the world. Learn how they evaluated Windows 7, including the cost of deployment, deployment strategies, and tangible benefits.

Sponsored by Microsoft  Listen to on-demand Recordings »

 

Service Level Management Best Practices Life Cycle Overview - Improve Service Levels

Best practices for Service Level Management (SLM) is a process for consistently meeting customer requirements and delivering on IT's promises. See the steps required to ensure high-quality SLM.

Sponsored by Compuware  Read this White Paper »

 

Keeping Your Members Safe from Online Scams and Predators

In order to keep fraudsters out, romance sites must deploy effective solutions that look at information independent of what is supplied by users. A device fingerprinting solution such as iovation ReputationManager™ provides unique insight into the computers being used to create multiple accounts and exposes hidden device-account relationships that identity-based fraud solutions often miss.

Sponsored by iovation  Read this White Paper »

Resource Alerts

Get instant email notifications by topic when white papers, webcasts, and case studies are added to our library.

Resource Alerts

Get instant email notification when white papers, webcasts, and case studies are added to our library. Don't just be up-to-date—be up to the minute with our new Resource Alerts.

Defend Against Blended Threats: What You Need to Know

Blended Web and email threats are becoming increasingly complex and represent a huge...  View Now »

 

Prescriptive Actions to Reduce Risk

In this Webcast, learn best practices for effective systems management in a heterogeneous environment and keep client systems cost under control.   View Now »

 

Webcast- Vantage 11: Redefining Application Performance Management

Compuware's latest release, Vantage 11, is a major advance in end-to-end application performance management--bringing together proactive issue identification, quantification of business impact and problem resolution into a single solution. Tune in to learn how Vantage 11's top-down approach helps you make better decisions and dramatically lower operations costs.  View Now »

Resource Alerts

Get instant email notification when white papers, webcasts, and case studies are added to our library. Don't just be up-to-date—be up to the minute with our new Resource Alerts.

 
NEWSLETTER

Sign-up for the Blogs & Discussion Newsletter

 
FEATURED SPONSORS
 
 
 
SPONSORED LINKS
 

Return on Information: Google Enterprise Search pays you back. Get the facts.

VMware. The source for Business Infrastructure Virtualization.

ShoreTel tells businesses to untangle from competitors' complexity and turn to its brilliantly simple UC solution

See how AT&T can help protect your network.

Streamline IT Costs. Boost Performance with WAN Optimization.

Build your 1st app FREE with Force.com

TDWI checklist helps define data readiness for analytics. Download report.

A Clear View Toward Virtualization

Virtualization Technology as a Business Solution

The rules of infrastructure management just changed.

A Clear View Toward Virtualization

Interactive Q&A helps you discover key ways to maximize IT assets.

Ready to virtualize tier one applications? Check your virtualization maturity.

Think you can't afford a Cisco Switch? Cisco Catalyst Switches are now more affordable.

Five minute business analytics assessment. Immediate results.

The Case for Investing in Business Analytics Technology. Read white paper.

Upgrading to VMware vSphere with vWire

Top 10 Lessons Learned for Corporate 3G Mobile Broadband Deployments

CRM Built for IT: The Executive Guide to Selecting CRM that Meets IT Needs

Return on Information: Google Enterprise Search pays you back

ROI of Application Delivery Controllers

Making Consumer Two-Factor Authentication Simple and Cost-Effective

Mining the Cloud to Ease the Enterprise Compliance Burden

Solve Five Key IT Security Challenges with Cloud-Based Authentication

White Paper: Right-Sizing Your Power Infrastructure

AT&T Synaptic Storage as a Service. Expand on demand

Trend Micro ranked #1 against real-world malware. Read more.

Webinar: Jump-start your in-house e-discovery with Ringtail QuickCull from FTI Technology

Top Five CIO Challenges

Read the RSA report: Security for Business Innovation

64-page prescriptive guide to security, compliance, and IT operations.

Increase UPS efficiency without sacrificing protection.

eZine: A Roadmap to Reducing IT Complexity

Reduce risk, gain agility. See how Progress can help your business.

Virtualization Technology as a Business Solution

eZine: A Roadmap to Reducing IT Complexity

World-class trading technology solutions from NYSE Technologies.

If You're Paying for Telecom, You're Paying Too Much. Contact Asentinel Today.

Trade-In your old printer and save up to $1,000 plus free recycling!

infoBOOM! - The Mid-Sized Company CIO's Exclusive Community

Live Webinar: Applying Business Analytics. Click here to learn more

Removing Barriers To Better Server Virtualization Efficiency

4G Revisited. The Continued Evolution of Wireless Mobility.

What's Next for Enterprise Resource Planning?

Maximizing website Return on Information with high-quality search

Gartner Magic Quadrant, Application Delivery Controllers 2009

Authentication as a Service by Forrester Research

Cloud-Based Authentication for Next-Generation Extranets

Cut Costs & Green Your IT Operations with PC Power Management

White Paper: 4 Customer Service Myths