In research done earlier this year, we looked at changing patterns of IT service management (ITSM) adoption across a population of 270 respondents in North America and Europe. One of the standout themes that emerged from our findings was the need for the service desk to become a more automated and analytically empowered center of authority across IT as a whole.
If you’re like me, you are increasingly becoming reliant on online shopping to replace the more arduous task of physical in-store shopping. I find this is particularly true during the holiday season when the idea of fighting traffic and elbowing crowds to desperately search numerous shops in order to find just the right gift for Aunt Phillis (who’s just going to hate whatever she receives anyway) gives way to the more idyllic setting of web-surfing multiple stores simultaneously from the privacy of your home while the dulcet tones of Nat King Cole playing gently in the background lull you into the holiday spirit (a little spiced eggnog on the side doesn’t hurt either).
IT administration is a thankless job. Let’s face it—the only time admins gain any recognition is when something goes wrong. In fact, the most successful IT administrators proactively manage very stable environments where very few failures and performance degradations occur. Unfortunately, though, this is rarely the case, and it is far more common for admins to get stuck in the break/fix cycle of reactive “firefighting”
In today’s Patch Tuesday, Microsoft released 12 security bulletins, five of which are critical. With this month’s patch load, we can count 105 updates
released so far this year which is only one update short of the total number of bulletins released back in 2013. We have already far-exceeded last year’s
total of 85.
Both the “rules” and the “roles” governing IT service management (ITSM) are evolving to support a far-broader need for inclusiveness across IT, and between IT and its service consumers. Recent EMA research, “What Is the Future of IT Service Management?” (March 2015), exposed a number of shifting trends that might surprise many in the industry.
Despite the launch of Windows 10 and all the talk about mandatory updates, today is still Patch Tuesday. And this month, everyone should pay attention. Microsoft shared a vulnerability smorgasbord today – offering a little something for everyone. From office and browser applications to desktops and servers, Microsoft covered them all with 14 bulletins.
As of August 1, ComputerWorld reported Windows 10 global usage had climbed to 2.5%. Not too shabby for the OS that was launched just three days earlier on July 29. Those numbers easily beat early adoption rates for Windows 8.1 but, I wonder how those users are faring? A quick read of headlines shows a lot ofheadaches ranging from overall privacy concerns to unwanted update files being delivered to networked machines still running Windows 7 or 8.1.
Last week, Microsoft issued an emergency patch in response to a critical flaw discovered by Google’s Project Zero and FireEye. While critical flaws rarely have a silver lining, there’s a big one for Microsoft here. An emergency patch just a week after July’s Patch Tuesday is the perfect outlier for Windows Update for Business (WUB) and 24/7 patching,
This is the first of a three-part series on change management. In this blog, I’ll try to answer the question, “What is change management?” from both a process and a benefits (or use-case) perspective. In the second installment, I’ll address best practices for both planning for and measuring the success of change management initiatives. I’ll also examine some of the issues that EMA has seen arise when IT organizations try to establish a more cohesive cross-domain approach to managing change.
It’s no secret that IT assets are incredibly valuable components of the corporate enterprise; yet, while many understand why acquiring these assets is essential, the value of effective asset lifecycle tracking often goes unrecognized. The reality is that corporate IT assets should never be “ignored” once deployed; rather, they must be understood and actively managed throughout their use.