Although technology continues to evolve, the processes that support Information Technology Service Management (ITSM) have remained relatively unchanged for several decades. One of the main challenges to delivering high-quality IT services in this long-established approach is reactivity – that is, focusing on incident management as a means to resolve something that should never have happened in the first place.
Onboarding is a critical moment in the employee life cycle. It is the unique opportunity companies have to engage their new hires, excite them and provide assurance and confidence that they have joined a great company. Making the life-changing decision to move to a new employer should not be followed by disappointment at the start of the journey. People need to feel that they have made the right choice from the very beginning, and this creates a strong bond with the company, the new team and a sense of common purpose. Find out more about creating an amazing onboarding experience.
Patching Windows 10 doesn’t always go as planned. As noted by CNet, the OS has a bad habit of automatically updating devices to the latest version — even when users are in the middle of something else. Sure, there’s potential benefit for IT here since network-connected desktops and laptops will always be up-to-date but since the update process halts any work-in-progress, resets the device and can take hours to complete, end-users won’t be happy.
Every organization looking at using network function virtualization (NFV) needs to consider monitoring. If you’re going to deploy a service, it’s really important that you know if it’s working — and what’s wrong if it’s not. That’s why monitoring — often called assurance — is a key part of every request for information, every request for proposal, every proof of concept, every NFV deal.
Here’s the challenge: the economics of on-premises monitoring are all wrong for the NFV business cycle.
We've been talking for years about running IT as a business. Multiple industry standards have taken their shot a guiding customers down this golden path, with varying degrees of success. The latest, and possibly most promising, is called IT4IT. This blog is meant as a quick introduction to IT4IT and our suggestions on how to get started.
In the article “Data Masking as Part of Your GDPR Compliant Security Posture” over on DEVOPSdigest, Zenoss talks about how to mitigate your application’s level of compliance by employing data masking or other pseudonymization techniques of personally identifiable information (PII) like names and email addresses. Zenoss suggests giving it a quick read to better understand how that strategy relates to GDPR.
Incident management means restoring normal computing services as quickly as possible to minimize the impact to the business. Yet, ironically, in a technology industry where innovation is the driving force, key elements of incident management have not been updated for some time.
Behind the scenes here at ServiceNow, the Knowledge Management and Multimedia teams work closely with subject matter experts to disseminate critical information to our customers. We've found that certain topics come up frequently, in the form of best practices that can help you keep your ServiceNow instances running smoothly.
To quote the late Rodney Dangerfield, IT systems “get no respect.” We all rely on them to accomplish our jobs, pay our bills and carry on with our day-to-day activities, without giving them a second thought – until they stop working.
IT organizations often find themselves monitoring effectively at small scale, but few have implemented solutions with the flexibility and capability to operate in elastically scaling environments.