What to read on system administration?

Question

System administration

Hello. I'm interested in the question, but first I would like to talk about my knowledge
. Previously, I worked in technical support and as a field engineer. The essence of the work: Diagnostics of PCs and monoblocks, block repair, diagnostics of performance, hdd, memory, replacement of components and peripherals. I also dealt with the software part - remote diagnostics, software installation, superficial diagnostics of problems with 1C (clearing the cache, checking the database), setting up routers according to the knowledge base (several pieces, certain models, uploading the config, flashing, diagnosing the local speed a little, etc. ), threw vitukha, video surveillance.
I’m friends with my home PC at the next level: I’m ready to disassemble, clean, replace / upgrade components, clean the system, customize it to my needs, I’m also friends with the command line, I’m familiar with some commands, I can pile vbs / bat by googling.
Server administration skills - did not administer, except that the other day I rolled on VirtualBox - WIndows Server 2012, installed Active Directory services, made it a domain controller, added a couple of users and a couple of groups, shared a network folder, gave each user rights to personal folders , brought the main system into the domain, played around with group policies at the Google level and subsequently applied a couple of policies (added a shortcut and a folder to the desktops of the specified group in the domain, rolled up the wallpaper, and did some other little things). In general, as such, there was no practice in this matter.
I am not familiar with the TCP / IP network protocol, register the details, ping, there is a general understanding of what IP / Mask / DNS is, etc.
I am not familiar with printers and MFPs, I had to set up - there are no problems with this, with repairs - I didn’t have to repair in depth (repairs were carried out at the level of replacement, replacement of drama, jam removal, etc.)
Actually, the question is the following, I want to get a job as a system administrator in some some medium-sized office, whether this knowledge is enough as criteria for getting a job. Will they take with such knowledge? What to read to consolidate the material?
Previously, he worked in a large office, the division of duties was good, there were separate windows admins / telephony admins, etc. That is, with all this sign at the setup / google level.
In principle, I quickly pick up in practice, but when I watched the courses, nothing was postponed.
Sorry for such a detailed question and a working biography. Thank you.

Answer 1

I will not recommend literature, I will outline the main directions.
1. Knowledge on networks needs to be tightened up. The organization from the point of view of the administrator is primarily a local network and the organization of the work of many devices in this network. Often there is a geographically distributed network.
You have more repairs and maintenance of equipment.
At home, studying networks is problematic. The easiest way is to get a job in an office where there are already 1-2 admins and jointly solve specific tasks in specific conditions. Conditions in different organizations can be very different, and the way to solve problems depends on this.
2.Databases. They are in every organization. It even happens that the organization does not know about it.
Therefore, at some level, you need to know the database: configuration, backup, optimization. It is good to know SQL - it is really often useful. It's good to at least have an idea from which side to go to 1-2 common DBMS. For example, take 1 from the corporate sector (MS SQL) and one free (Postgre, MySQL). It is better to start with relational DBMS. Now there are a lot of other options, but relational ones are the most universal option and are suitable in almost any situation, besides, RDBMS are mainly used in the corporate sector. Specialized DBMSs may be more efficient in some ways than RDBMSs, but that's another story.
3.Study scripting languages ​​in relation to administrative tasks. You should start with the command shell languages ​​​​of the OS used (cmd, powershell, bash), after that it’s good to study any universal programming language (python). This approach can be facilitated by this approach: there is a certain task, you can solve it using a GUI utility, try to solve it without using GUI tools. It is worth remembering that command line administration tools are primary, and then they are already overgrown with GUI add-ons. Often tasks are solved only from the command line.

Answer 2

I want to get a job as a system administrator in some medium-sized office

In one average office (50-100 computers) to pull most likely it will not turn out. Look for a place where the staff of IT specialists is at least 2-3 people, so that there is someone to gain experience from.
And you can read everything in a row: Habr, books by O'Reilly, computer network theory, Oliferov. Although you can do without theory. "Time management of the system administrator" I recommend, soft skills will not be superfluous, because the system administrator must have the skills of a psychologist and an elementary school teacher.

Answer 3

More practice, go to interviews, try. Set yourself achievable goals and achieve them.
The book "Thomas Limoncelli: System and Network Administration" can help, put a lot in its place.
And also Goldratt's book - The goal is very useful. And then there is the Phoenix Project.

Answer 4

watch the video and decide whether you need to do something like this and which way is better to move:
https://www.youtube.com/watch?v=QT5cNrMQBGo

Answer 5

You don't have to read anything. This profession will die soon. You are just wasting your time. I spent it and now I regret it.

Answer 6

You don't have to read anything. Everything will be explained on the spot.