$h1t Engineers Say
Engineer1: Please give me the file name so I can work on the file.
Engineer2: \servername\folder1\folder2\file.csv
Engineer1: No, I just need the file name…
Yeah, That Server
There was a problem with a server generating to many tickets and the support team was having trouble keeping up. One server in particular was cited as being the offending server. In an effort to demonstrate the problem first line management spent days culling the list of tickets to show how many were being generated. They found upwards of 6000 tickets. Taking these tickets in to the meeting to present to the team that manages the alert generation system to get them to take action to turn down the frequency of alerts. While they are in the meeting they look at the list of tickets for the first time to find that the tickets are not for the server with the problem but contain the name of the server that generates alerts for the entire datacenter. They’ve presented all the tickets for all of the servers.
Oops, I suppose you should look at your data before you take it to a meeting to present it.
Don’t Click the Link
The security office for CompanyX forwarded an e-mail as a warning for a phishing scam and what to be on the look out for.
Wait for it.
Wait for it.
Wait for it.
The links in the forward of the phishing e-mail were all still intact despite having been forwarded from the original receiver and several other security personnel and managers before being handed down to every one else.
Ignore That Failure
A solution to a high profile problem is to add capacity by adding new servers to the environment. The directive, to run the quality assurance process but ignore any errors that are not hardware related. QUALITY ASSURANCE…..
Training, training, train-ing, TRAINING!
The company has now had 4 different and unique training systems in 3 years. It is impossible to maintain a transcript of all training taken or received. Attention deficit Inc.
PRODUCTION! English, do you speak it?
To preface this issue I will note that this is an anecdote from a long line of issues taking place with a workstation OS roll out.
Yesterday an update to the workstation OS upgrading from version 6.2 - 6.3 was rolled out. Initially the update did not call for rebooting the workstation. On booting up this morning I find a boot menu that has an added Linux kernel with notation indicating it’s beta. Why on Gods green earth am I receiving an update to my PRODUCTION workstation indicating that it is beta? I can’t wait to be in a critical situation only to receive a conceptual kick to the jublees when this thing kernel panics unexpectedly.
I can’t even fathom who in their right mind puts beta in production much less pushes it to the entirety of a user base doing production work.
You’re Doing It Wrong
The company required default OS build includes a mail and instant messenger application which come along with an application to forcefully kill each of those applications.
