As has been the case so many times before, this week I’m bringing you the direct result of a customer request. The customer in question needed to know how to run a .ps1 script. As you may or may not know, double-clicking the script defaults to editing the script. At any rate, here’s how you do it:
Category: Tech support
I’ve been using Adobe Premiere pro for a while now, but am finding that I can’t really defend the cost of Adobe Creative Cloud. While having multicamera support has been very nice, the product quite simply is cost prohibitive for me, especially as it really only offers a single feature I need; the ability to sync clips based on their audio. For my needs, iMovie will suffice.
Last week, I defined the three KPIs I believe are what you need to understand how well your support department is operating. Defining them, however, is just part of the job; if you don’t understand what they are telling you, you might as well not bother measuring at all. Let’s look at each in turn:
Metrics – often referred to as “Key Performance Indicators” or simply “KPIs” – are a necessity, regardless of your field. If nothing else, it’s nigh impossible to say anything meaningful about performance without them, and improving the performance is turned from something quite achievable. to a Sisyphean task.
An important principle of ITIL is that all requests should go through a single point of contact (abbreviated to SPOC). What this means, is that a single channel should be defined for the reception, classification, and distribution of a request or incident. Crucially, it does not mean that all contact with the customer should be done by tier one.
Every so often, a customer will call in, saying that they are unable to access one of the servers that are mapped through their login script. There are generally two reasons for this; either there’s an issue with the network connection, or the drive letter is already being used for another device. To troubleshoot the issue, then, we start by confirming that the computer is online, and then have the customer log off and back on again. ‘
Ask anyone who has a glancing familiarity with Kanban what they know of it, and one of the (if not the) first things they will mention, is the use of a kanban board. This is true; the kanban board, whether physical or digital, is one of the most visible parts of the Kanban method. It is an eminently visual way to represent WIP. So, how do you implement a kanban board in IT support?
One of the questions that pop up every now and again, yet not often enough for me to consistently remember how to do it, is some variant on “What user is blocking my file access?” A user will typically call in, complaining that they are unable to open/edit/delete a given file on a file share, and ask the support tech they reach to solve the issue.
The title of this post might seem a bit on the conceited side. After all, who am I to claim to be a DevOps practitioner, much less thinker? I will simply say that I am working to implement DevOps principles in my day to day life, am spending more than a little time reading, thinking, and writing about DevOps, and though I may not be considered a DevOps thinker today, I certainly aspire to join their ranks. The title, then, is a statement of aspiration, more than a statement of achievement.
My first IT job was a one day per week internship with a pharmaceutical company while I attended my last year of high school. It was the first time I was exposed to the constant stream of support and service calls that makes up a large part of the day to day life of a support technician. I remember having a distinct impression that the IT department was constantly over-worked, always having too many things to deal with.