Be Careful Not to Take Your Systems Administrator for Granted. They Are More Important Than You Think

Be Careful Not to Take Your Systems Administrator for Granted. They Are More Important Than You Think

Share

The Systems Administrator is the person responsible for installing, configuring, maintaining, monitoring and documentation a business’ IT systems and ensuring that they are always functioning correctly. Do you really think that this person should be spending their time trying to print out a PowerPoint presentation for your midday meeting, just because you don’t know how to set up the printer on your PC? While part of a sysadmin’s job is to provide support and respond to user requests, they do much, much more than just this.

For most standard businesses, the systems administrator is responsible for communications(e-mail, phones, internet, instant messaging, videoconferences, etc.), servers (that host the ERP and CRM systems, website and e-commerce services), security (monitoring, backups and restore points, antivirus, firewalls and contingency plans) and other tasks that range from regulatory compliance to software licencing. They are tasked with taking care of all this and making sure everything is up to date and functioning correctly, 24 hours a day, 365 days a year.

As result, we can probably say that the sysadmin is the most transversal role in the business. They are ultimately responsible for ensuring that daily operations function normally. and they are particularly important for sales marketing and operations. Without their help, many departments would be unlikely to know how to use the available technology to stay competitive.

So why is it that the systems administrator is so taken for granted?

Don’t you think so?

Why is the IT budget generally not considered a priority? Why does the IT manager often not have the final say in decisions relating to their own department?

Why are IT teams generally understaffed, meaning that a significant number of systems administrators need to work extra hours?

Influence of the systems administrator and hours worked

Influence of the systems administrator and hours worked

It is often said that ERP is a business’ brain, information is the most important asset for most companies, digitalisation and e-commerce as the future… and that e-mail, the internet and having a website are absolutely basics if you want to be taken seriously as a business. So, who has to take care of all this? Who is responsible for making sure that everything runs like clockwork?

The reality is that systems administrators are forever taking on more and more responsibilities. Business systems are becoming increasingly complex and security is more vital than ever. Furthermore, the need for new technological solutions continues to grow in all areas of the business. Is it honestly fair to see the sysadmin as someone who can set up a printer for us? Or should we be trying to see their role a bit differently? I think we all need to give this some serious thought.

There is always someone behind the scenes making sure that everything works correctly… So let’s show a bit more appreciation for our systems administrators.

Category:Sysadmin

Other posts that may interest you

9 de August de 2024
Choosing the right cloud service provider is a critical decision that can impact the quality of your software, customer
3 de July de 2024
Here at Jotelulu, we have designed our Disaster Recovery service specifically with SMEs in mind. But what arguments should
2 de July de 2024
In today’s article, we will explain some of the basic concepts that are important to understand about Jotelulu’s Disaster

Fill out the form and one of our Sales team will contact you soon.

growth@jotelulu.com  |  jotelulu.com 

You can unsubscribe from these communications at any time. For more information,  check our Privacy Policy.

 

We make the difficult easy

Existing Disaster Recovery tools often require advanced knowledge to manage, demanding expertise that is difficult to acquire.

Jotelulu’s Disaster Recovery aims to make the difficult easy and offers a very simple deployment based on a three-step configuration:

Origin (Primary Site)
Determine the origin location of the subscription on which the Disaster Recovery service will be established.

Destination (Recovery Site)
Set the destination location (availability zone) where you want the Recovery Site to be deployed.

Replication characteristics
Specify the data related to the number of copies to be kept and the frequency at which the replication will be performed.