Skip to main content

Hi Everyone,

I thought I would first of explain what inspired me to write this on a nice September morning. It was a dumb decision. I have made many dumb decisions in my life and sometimes, just for fun I repeat them. In this case it was agreeing to a dentist appointment at 7 am on a Friday morning. 

This all came about around the time of VeeamON. Some of you noticed there were times at VeeamON in Miami when I was walking around with a not so jolly expression on my face. The reason for this was because I was stuck in between benefits providers (read dental insurance) and precisely at that time one of my remaining wisdom teeth decided to cause Armageddon. I held out as best I could. I tried keeping Listerine in my mouth for long periods at a time, then going to the beach and holding salt water in my mouth as I read it has healing powers (although this caused some fellow beach dwellers to give me strange looks). Finally a few weeks after getting back home I was able to go to the dentist without massive financial pain and get my tooth removed. 

Upon leaving the dentist office that morning in a moment of pure stupidity I agreed to the 7 am appointment thinking “ha 6 Months away who cares”. 

Well 6 Months was up this morning, so in a horrendous mood I dragged myself to the dentist. One thing I have never understood is why the dentist receptionist asks “how are you this morning” at 7am to someone about to be lying with their mouth open with metal tools in it for an hour,, “I am great” l lied and then headed into the torture chamber. 

The next major annoyance is when you get a dental hygienist who asks you questions when your mouth is full of dental equipment, it reminded me of that scene in the movie “The King’s Speech” where the King tried to speak with his mouth full of rocks. I tried the old meditation technique in order for the time to go faster picturing myself on a sunny beach somewhere in the Caribbean, however, that was rudely interrupted when the hygienist gleefully found a tough stop and the tool that was being used started to emit some kind of a sawing noise. My Caribbean meditation turned into a flashback of that time when I was playing soccer on a beach in Mexico and kicked the ball not seeing the rock that was underneath it, breaking my middle toe in the process. I don’t remember what was worse, the toe pain or the amusement of my fellow high school students had in the fact that “Butcher Burke” as I was known on the soccer, football and rugby teams had a middle toe broken unlike the valiant injuries of other players, broken arms, knees elbows and so on.

Then there was the horror of turning and looking at the Dentist’s computer monitor and seeing Windows XP! Well at least I am not having a brain scan I thought!

 

But I digress. The most annoying thing that I find in IT are byzantine logs. Byzantine refers of course to the Byzantine Empire and because the latter was unique in its intrigue and complicated power struggles, the term Byzantine has taken on another meaning in English: 

Quote from Google Dictionary:

“(of a system or situation) excessively complicated, and typically involving a great deal of administrative detail.”

 

You have to wonder sometimes if developers are simply creating log messages for fun. My all time least favorite would have to be the Microsoft Event viewer. I don’t think I have ever found some cognitive meaning for the messages that one finds in there. Of course this is an exaggeration but honestly how many times have googled Event Viewer ID’s and walked away more confused than before you started searching? 

So folks what do you all find the most annoying in your IT work. Also let’s leave out some universal truths i.e. boss, end users and so one 😀?

The term: Single Pane of Glass. Because what tends to be forgotten is that if every product has a single pane of glass, I have dozens of ‘single panes of glass’ 

Microsoft changing the UI of Windows/Office products (what it seems like) every single update. 

 

 


Well because it’s fresh and happening a lot today, users sharing my phone number around to get past the service desk.

I regrettably helped a few too many people going the extra mile and trying to be a nice guy the first few times. I explained to them, “Please call the helpdesk going forward, as we have a desktop team, and I’m an Infrastructure Specialist, but let me take a quick look”.

The main issue is I always seem to fix their issues, and word spread fast. I’m assuming there were emails going around or my phone number is pasted on post-it notes all over now.  

I had a repeat offender just call me, and a few minutes later a different user called me saying the repeat offender TOLD THEM TO CALL me and that “I’m the guy to call”

Needless to say  I politely told him a different team would handle this and he needs to call the helpdesk for all tickets going forward. 

This didn’t even take into the account he was logged in as a different user, that had given him their credentials.  Sigh…. it’s Friday and a long weekend. I am so happy I give everyone the bare minimum access these days when I see things like that. 

Think positive….. The 100Summet will happen soon, It’s Friday afternoon, It’s going to be a nice weekend, and I didn’t have to go to the dentist this am 🤣


One thing that annoys me is being the Architect for Veeam and you create multiple design documents and Wiki pages, but NO ONE follows them!  You then audit a site and find the IPs are wrong, server configurations are wrong, no extra drives for Veeam installation, etc.

As they always just RTFM and it makes things go smoother.  🤣


The term: Single Pane of Glass. Because what tends to be forgotten is that if every product has a single pane of glass, I have dozens of ‘single panes of glass’ 

Microsoft changing the UI of Windows/Office products (what it seems like) every single update. 

 

I don’t mind Windows UI changes so I’ll one-up that. 

It’s the Microsoft 365 Admin Center/Azure AD/Entra ID/Defender/InTune/Security Center/Compliance Center/Admin Portal and how all of those things move around or certain subsets of them move around, or Microsoft feels the need to update portals but not have them fully functional, etc.  Also, the need to change the names of everything all the time...although I will say that I know of a certain backup vendor that seems to like name changes as well….


One thing that annoys me is being the Architect for Veeam and you create multiple design documents and Wiki pages, but NO ONE follows them!  You then audit a site and find the IPs are wrong, server configurations are wrong, no extra drives for Veeam installation, etc.

As they always just RTFM and it makes things go smoother.  🤣

 

I would like to say that all of my designs are implemented by myself, but as I have gotten more and more busy, I’ve begun moving into a role where I design solutions and then my counterpart tasked with installing them doesn’t do it my way.  He’s also not quite as detail oriented, so the things I expect are no completed the way I would expect them, so he gets the bulk of the work completed so then I end up going back and performing all the little tweaks, etc.  The system isn’t great, but it works at least.


One thing that annoys me is being the Architect for Veeam and you create multiple design documents and Wiki pages, but NO ONE follows them!  You then audit a site and find the IPs are wrong, server configurations are wrong, no extra drives for Veeam installation, etc.

As they always just RTFM and it makes things go smoother.  🤣

 

I would like to say that all of my designs are implemented by myself, but as I have gotten more and more busy, I’ve begun moving into a role where I design solutions and then my counterpart tasked with installing them doesn’t do it my way.  He’s also not quite as detail oriented, so the things I expect are no completed the way I would expect them, so he gets the bulk of the work completed so then I end up going back and performing all the little tweaks, etc.  The system isn’t great, but it works at least.

Yes, I would implement them myself, but I am too busy, so the Veeam team is supposed to do it but follow my documentation.  😂


One thing that annoys me is being the Architect for Veeam and you create multiple design documents and Wiki pages, but NO ONE follows them!  You then audit a site and find the IPs are wrong, server configurations are wrong, no extra drives for Veeam installation, etc.

As they always just RTFM and it makes things go smoother.  🤣

 

I would like to say that all of my designs are implemented by myself, but as I have gotten more and more busy, I’ve begun moving into a role where I design solutions and then my counterpart tasked with installing them doesn’t do it my way.  He’s also not quite as detail oriented, so the things I expect are no completed the way I would expect them, so he gets the bulk of the work completed so then I end up going back and performing all the little tweaks, etc.  The system isn’t great, but it works at least.

Yes, I would implement them myself, but I am too busy, so the Veeam team is supposed to do it but follow my documentation.  😂

I suspect that’ll be one of my next roles.  My short-term dream is that I still design solutions as a presales engineer and lead our projects team and then we hire another Senior Engineer and have those two implement designs and handle escalations, and if it get’s really bad, I’m Tier 5 support.  


My biggest annoyance is in a word: Microsoft.

 

They are the giant, they can’t really gain any meaningful market share, only lose it. But we continue to see Microsoft attempt to generate more revenue by making an inferior user experience. More adverts and tracking in the OS, pre-loaded bloatware, removing the ability to decide when you want to install updates. When Microsoft adopted Chrome as its Edge engine it started well, now we have features we can’t easily remove if at all.

 

As Windows 10 ends support in 2025 and my windows 11 experience has been so poor, I’m considering making Ubuntu my daily driver and breaking the cycle.


One thing that annoys me is being the Architect for Veeam and you create multiple design documents and Wiki pages, but NO ONE follows them!  You then audit a site and find the IPs are wrong, server configurations are wrong, no extra drives for Veeam installation, etc.

As they always just RTFM and it makes things go smoother.  🤣

 

Writing documentation no one uses. The absolute worst! 
I try to help calm myself by remembering I write these docs so I remember tomorrow what I figured out today, but watching the team struggle with the same things because they didn’t RTFM? Uggg.


One thing that annoys me is being the Architect for Veeam and you create multiple design documents and Wiki pages, but NO ONE follows them!  You then audit a site and find the IPs are wrong, server configurations are wrong, no extra drives for Veeam installation, etc.

As they always just RTFM and it makes things go smoother.  🤣

 

Writing documentation no one uses. The absolute worst! 
I try to help calm myself by remembering I write these docs so I remember tomorrow what I figured out today, but watching the team struggle with the same things because they didn’t RTFM? Uggg.

 Automation is the key and the future. Too many human errors even if you RTFM. Even if you WTFM...


One thing that annoys me is being the Architect for Veeam and you create multiple design documents and Wiki pages, but NO ONE follows them!  You then audit a site and find the IPs are wrong, server configurations are wrong, no extra drives for Veeam installation, etc.

As they always just RTFM and it makes things go smoother.  🤣

 

Writing documentation no one uses. The absolute worst! 
I try to help calm myself by remembering I write these docs so I remember tomorrow what I figured out today, but watching the team struggle with the same things because they didn’t RTFM? Uggg.

 Automation is the key and the future. Too many human errors even if you RTFM. Even if you WTFM...

Absolutely.  If I had more time for automation this would be something I could help eliminate. 😋


My biggest annoyance nowadays is the sentence:

“If it works, don`t touch it”

The last years, this sentece has always track and target me at some point,

Windows Server versions, SQL instances, ESXi Servers, also Veeam B&R Servers…

I would say, keep it up to day, and, if it breaks cause of an update, follow best practices and keep everything at the highest level, just for patching and lifecycle proposes.

Its a hard task, but has became a must in my daily operations!

cheers.

Luis.


My biggest annoyance nowadays is the sentence:

“If it works, don`t touch it”

The last years, this sentece has always track and target me at some point,

Windows Server versions, SQL instances, ESXi Servers, also Veeam B&R Servers…

I would say, keep it up to day, and, if it breaks cause of an update, follow best practices and keep everything at the highest level, just for patching and lifecycle proposes.

Its a hard task, but has became a must in my daily operations!

cheers.

Luis.

Ah yes the “if it works, don’t touch it” one of my all time favourites. Plus one that has a very strong will to survive. I heard it when I started my IT career, and I still here it now. My other favourite is when a Windows shop declares “we are a 24/7 business, we can’t reboot our servers”, I call those “dummypots” as opposed to honeypots since honeypots are intentional but the others are self inflicted. 


Half the time “if it works, don’t touch it” does translate to “we don’t know how this works, don’t break it”, and let me tell you, that is not a position one wants to be in.

 

Second day of a new job, and the company’s fax system failed, it was supposed to forward all faxes to email. There wasn’t an internal IT team, just an outsourced IT company that didn’t know how it worked, so there wasn’t any documentation.

In that day I learned EXACTLY how that system was put together, and spoiler alert, it was DNS! But it was DNS in the most unexpected way possible, and my troubleshooting saved the supplier from a massive outage!

 

It turned out the supplier’s Name Servers for their domain were from an ISP that had been merged with another ISP. The supplier never migrated to the new name servers, so when the old ones got shut down, they got cut off. The DNS records were still in the cache of Google DNS so not many people had noticed, but as we didn’t use Google DNS for public resolution, we were impacted! And it broke for us because of an anti-spam policy that meant because we couldn’t look up smtp.<supplierdomain>.com to confirm it matched the emailing IP address, it was blocked!

 

I then spent the next day documenting the entire process end to end 😂


My biggest annoyance nowadays is the sentence:

“If it works, don`t touch it”

The last years, this sentece has always track and target me at some point,

Windows Server versions, SQL instances, ESXi Servers, also Veeam B&R Servers…

I would say, keep it up to day, and, if it breaks cause of an update, follow best practices and keep everything at the highest level, just for patching and lifecycle proposes.

Its a hard task, but has became a must in my daily operations!

cheers.

Luis.

Otherwise rephrased as: “We’re going to build up a lot of technical debt and let future us deal with this growing problem when its no longer easy to handle.”

 

Developers say “Release early, release often”.
Admins should be saying “Update early, update often”. 


Lack of documentation.

Lack of patching/security updates.

 

9 AM, already dealing with both of the above. 


fax

Well there’s your problem right there!

 

I know…..we have a division that handles business phone systems….fax is a common topic of hate….


Comment