MSP Blog Logo

BDR

Business Growth

Cybersecurity

Help Desk

MDM

RMM

Sales & Marketing

Subscribe

Empowering Your MSP Business to Grow and Prosper—One Post at a Time

5 Ways to Improve Your MSP Service Level Agreement (SLA)

Featured Post

5 Ways to Improve Your MSP Service Level Agreements (SLAs)

SLAs are the foundation of your MSP business. They are essential to building strong client relationships and must be clear, reasonable and well-constructed.

Read Now

What Are Your IT Superstitions? The Top 4 Responses from Your Peers!

Posted March 13, 2015by Stephanie Moncayo

It’s Friday the 13th, most commonly recognized as the day on which no four leaf clover, rabbit’s foot or wishbone stands a chance. Although the origins of this superstitious day can’t technically be proven, its reputation as the unluckiest day on the calendar has lasted for over 100 years.

Recently, we reached out to online communities like Reddit and Spiceworks to ask members what their IT superstitions are. Here are the top four responses from your fellow techs and MSPs!


Hardware has feelings too

Play nice with your hardware. Whether you’re giving a server an awesome nickname or assigning an even number to a domain controller, do not mess with your hardware. Many techs have experienced better luck naming servers with odd numbers greater than one because apparently, redundant systems like odd numbers. Most importantly, never name your servers after villains, only heroes.

Ultimately, apply the Golden Rule when it comes to the treatment of your hardware or become a victim of resentful technology like this CD Burner...ScreenShot2015-03-12at11.14.55AM


The Unluckiest Hour 

I'm not referring to the paranormal hour of the night known as the witching hour, between 3:00-4:00 am. I'm talking about Friday right before quit time. For most of you this would be between 5 and 5:30 PM, and it's the unluckiest time/day of the week for techs to get any new tasks started, no matter how painless it appears to be. Basically starting anything on a late Friday afternoon is like asking for something to go wrong. Many of you learned this the hard way and have responded with a very clear warning:

The ticket that will bring misery and doom will arrive on a Friday at 4:45, disguising itself as a simple task that will take about 5 minutes. Don’t do it. It will actually take you at least 3 hours.

Furthermore, if the ticket has a subject line that reads “printer,” then don’t even think about it. Some of your fellow techs would refer to this as the “evil incarnate” or the “physical embodiment of bad luck/karma.” One Spiceworks poster suggested the following...though we can't recommend it ourselves...

ScreenShot2015-03-12at11.33.40AM


Murphy’s Law

Most of you are probably familiar with the infamous adage, “anything that can go wrong, will go wrong” also know as Murphy’s Law. This could not be truer in the world of IT. Most of our technicians would agree that everything waits to break after the lead tech leaves for a vacation or if you accidentally miss a backup. Something will for sure fail. That's why you need a fully integrated BDR solution in place to avoid a data disaster. Otherwise, you could take the advice of the Reddit poster below and uninvite Murphy to your party.

ScreenShot2015-03-12at1.40.25PM


The calm before the IT Storm

“It’s quiet…too quiet.” These are a tech's last words before alarms go off. Never underestimate a project by saying things like, “This job is a quick fix.” or “This will only take a couple of minutes” because you’re asking for it. Techs agreed that the "B" word (bored) or the “Q” word (quiet) are big IT no-nos. Also, don't jinx yourself by waiting for something to go wrong. If an old server is still kicking, don’t challenge it. A tech on Spiceworks shared a story about how someone in his department said:

“I’m surprised that old server is still running, wouldn’t it suck to have the RAID die out on something that old! We would never find parts.”

Sure enough a week later, the RAID did die along with two drives that ended up with mechanical failure. Luckily, this tech has backup OCD and had a RAW data backup from the previous week. 

Remember: With the right RMM solution, however, you don't have to wait for everything to fall apart. If there's an issue you can detect and correct it with your client being none the wiser.


Keep these tips in mind and your Friday the 13th will hopefully be just any other Friday. Special thanks to the online IT community for all of your humorous responses! Make sure you check out the full Spiceworks and Reddit threads, and feel free to share some of your own IT superstitions in the comments below.

If there’s one thing I have learned from reading through these responses, it's the need to BACK UP! It's critical that you offer a reliable backup and disaster recovery (BDR) solution to clients and keep their sensitive data safe should an IT calamity occur. 


Hope for the Best, Plan for the Worst: The Keys to Effective Backup & Disaster Recovery  

 

Stephanie Moncayo is an Inbound Marketing Consultant at Continuum. Stephanie works with the programs team, assisting with content creation and strategy. A recent graduate of Northeastern University, Stephanie is passionate about dancing and traveling, as well as studying market trends and behavior.

RMM 101: Must-haves for Your IT Management Solution
MSP Guide to Managed Services SLAs  [white paper]
comments powered by Disqus