Home About Blog Report & Survey Highlights Case Studies Q&A Interviews Services

Laura DiDio on…

Microsoft Azure Sphere chip for end-to-end IoT security from the Cloud to Network Edge

“MediaTek is a good partner [for Microsoft] to have for its Azure Sphere secure IoT chip,” said Laura DiDio, principal analyst with ITIC. “They will provide a Wi-Fi controller, the processor will run Microsoft’s Linux-based IoT OS and you’ve now got a highly secure, connected device at a decent price point.”

Channel Futures, April 17, 2018

Microsoft Reorganization:

“Microsoft has actually been moving away from Windows and more towards the cloud, analytics and AI for the past ten years,” explained Laura DiDio, an analyst at ITIC. “This did not happen overnight.” DiDio pointed out that Nadella has made major changes quickly during his tenure. “That’s the way you have to move,” to stay relevant, she said. “You’ve got to be agile to stay ahead of the game.”

The changes don’t mean that Microsoft is totally giving up on Windows, DiDio said. But they do mean that Nadella is focusing the company’s energies around stronger assets.

“They’re de-emphasizing Windows,” she said, in order to become a stronger “player in cloud and artificial intelligence, because that’s where the money is.”

CNN Money, March 29, 2018

Failure to deliver reliability and uptime:

“Time is money,” DiDio says. “Systems, networks and connectivity devices are subject to failure. If the downtime persists for any significant length of time, it can be expensive in terms of monetary losses. It can disrupt operations, decrease worker productivity and negatively impact the organization’s business partners, customers and suppliers.

“A security outage of any significant duration can also be a PR nightmare and damage the company’s reputation, causing lost business,” DiDio says. “Reliability and uptime go hand in hand with a comprehensive, detailed backup and disaster recovery plan that also includes an internal operational level agreement that designates a chain of command in the event of any type of service disruption.”

Every organization should have a disaster recovery plan that includes an itemized list of who to contact at vendor organizations, cloud and third-party service providers, DiDio says. “The CISO should also know what the company’s contracts stipulate as the response time from vendors, cloud, and third-party service providers to respond to and thwart security incidents and track down the hackers,” she says.

CSO Online, November 21, 2017

Cal State University and Hartnell College Launching Cohort Program:

“Since 2013, the two institutions have promoted this program as a way to attract minorities, women and students who are the first in their families to attend college to Computer Science and STEM subjects. The Cohort program nurtures these students by having them take their CS classes as a group.” DiDio says. It also helps them adjust more quickly to college life by providing them with group study and life skills classes to help them stick with CS as a major and graduate.

“So far, so good. A 75% majority of students enrolled in the CSUMB/Hartnell CS Cohort program graduate. This is well above the national average of about 30%,” DiDio notes.

ITIC Corp, November 17, 2017

Burger King Ad Creates Whopper of a Mess:

“In the Internet of Things environment, where you can have “an ecosystem or ecosystems of ecosystems interconnected, the attack vector universe is potentially limitless,” noted Laura DiDio, research director for IoT at 451 Research.

The risks are “everywhere, and what you can do is mitigate risk to an acceptable level,” she told the E-Commerce Times — but that requires vendors to make secure products.

E-Commerce Times, April 13, 2017

United Airlines Customer Service Snafus:

United’s behavior was “cavalier and callous,” said Laura DiDio, research director for IoT at 451 Research.

“The deck is stacked against passengers these days,” she told CRM Buyer.

However, this situation “is a PR nightmare for United Airlines,” DiDio added, “and it’s not going away.”

CRMBuyer, April 11, 2017

For the fifth year in a row, IBM servers delivered the highest levels of reliability and uptime among 14 server platforms.

Those are the results of the latest independent ITIC 2013 Global Server Hardware and Server OS Reliability Survey which polled C-level executives and IT managers at over 550 organizations worldwide from August 2012 through January 2013.

Among the high-end mainframe class systems, both the IBM System z and the Stratus Technologies’ ftServer 6310 delivered the highest inherent reliability: both had no instances – 0% – of the most severe Tier 3 outages lasting four hours or more of duration. Among the mainstream “work horse” servers, IBM’s Power Systems recorded the least amount of unplanned downtime, approximately 13 minutes per server/per year. By contrast, some 6 percent of organizations using Oracle (formerly Sun Microsystems) x86-based servers experienced of over four (4) hours of per server/per annum downtime. This was the highest percentage of lengthy Tier 3 server outages among the 14 platforms surveyed.

On the server operating system side, IBM AIX v 7.1, Ubuntu v 11.10, Windows Server 2008 R2, Red Hat Enterprise Linux 6 and SUSE Linux Enterprise 11(in that order) registered the least amount of unplanned downtime due to inherent flaws in the OS.

IBM’s AIX v 7.1 running on Power Systems, averaged approximately 10 minutes of per server/per annum downtime and recorded the least amount overall downtime due to Tier 1, Tier 2 and Tier 3 outages for the best reliability among survey respondents. Canonical Ltd.’s Ubuntu v 11.10, which has been steadily gaining mainstream adoption, came in a close second to IBM, averaging about 12 minutes of annual server downtime. Hot on its heels was Ubuntu’s chief Linux server OS rival Red Hat Enterprise Linux 6 (which also runs on IBM Power Systems) and Microsoft’s Windows Server 2008 R2 both of which registered about 12.5 minutes of unplanned yearly downtime. SUSE Linux Enterprise 11 (which also runs on IBM Power Systems) rounded out the top five logging just under 13 minutes of unplanned server OS downtime. On the other end of the spectrum, Oracle x86 and HP ProLiant servers had the highest percentage of systems that experienced more than four hours of per server annual downtime, with six percent of Oracle x86 systems and five percent of HP ProLiant systems experiencing a high degree of downtime.

Overall, 52% of IBM server hardware users reported experiencing 1 to 5 minutes of per server, per annum downtime, which is the equivalent of 5.25 minutes of downtime equaling 99.999% uptime. By comparison, just 41% of Oracle server users and 39% of HP servers recorded 99.999% or five nines of uptime.

Dell received the highest marks for customer satisfaction with technical service and support and product performance. Three-quarters or 75% of Dell survey respondents rated its service and support as “excellent” or “very good” followed by 70% of IBM survey participants and 69% of Stratus users who gave those servers “excellent” or “very good” ratings. Oracle’s customer satisfaction ratings were the lowest in the survey: only 45% ranked its technical service and support as “excellent” or “very good. However, Oracle had the highest percentage of dissatisfied customers with seven percent giving the company’s technical service and support a “poor” grade and 9% calling it “unsatisfactory. This is the third year in a row that Oracle service and support has had the dubious distinction of having the highest percentage of businesses that are unhappy with its technical service and support.

None of the survey participants gave IBM or Stratus service and support “unsatisfactory” ratings for technical service and support. Likewise, only one percent of respondents gave Dell, HP and Fujitsu an “unsatisfactory” and just two percent of Toshiba customers rated its technical service and support unsatisfactory.

Among server operating system vendors, Microsoft scored the highest marks for customer satisfaction with 71% of respondents rating the Redmond, Washington software firm’s technical service and support as “excellent” or “very good.”
In fact, Windows Server 2008 R2’s reliability renaissance continues to impress. Microsoft’s Windows Server OS noticeably lagged behind the majority of the UNIX, Linux and Open Source distributions in ITIC’s 2008 and 2009 Server Reliability surveys. In 2008, Windows Server 2008 survey respondents experienced 3.77 hours of downtime; that figure dropped to 2.42 hours of annual downtime in the 2009 survey. In the latest 2013 survey, Windows Server 2008 R2 has reached parity with the top tier server OSes, recording 13.2 minutes of unplanned per server annual downtime.

New Questions, Revealing Answers

ITIC also updated the 2012-2013 Reliability survey with several new questions to reflect the continuing changes in the industry, gaining further insights into user and system behavior:

  • IBM server administrators spend the least time rebooting their server OS, including planned reboots to add or reconfigure system resources. Three-quarters – 75% of IBM administrators – “rarely or never” reboot the server compared with 66% of HP managers and 51% of Oracle administrators. Microsoft administrators spend the most amount of time rebooting the Windows Server 2008 and 2008 R2 servers; approximately one-quarter or 24% of respondents said they rebooted Windows weekly or daily to add or reconfigure system resources. The need for IT managers to take Windows servers offline to apply patches and reconfigure system resources remains a weak point for Microsoft.
  • IBM Power VM, Stratus ftServer, Dell servers w/Windows Hyper-V and HP ProLiant iVirtualization (in that order) were the four most reliable hardware virtualization platforms. Virtualization market leader VMware was in the middle of the pack with respectable reliability rankings. Surprisingly, 60% of Dell Virtualization systems running Microsoft Hyper-V experienced one to 10 minutes of unplanned downtime compared to the 54% of Dell Virtualization systems running VMware.
  • Some 31% of businesses don’t provide for hardware failover and redundancy which puts them at greater risk for system downtime. It also potentially lengthens the duration of an outage when something goes awry.

Share This Content:
4 Discussions

Laura DiDio on Facebook
Laura DiDio on LinkedIn
Laura DiDio on Skype
Laura DiDio on Twitter