In a perfect world, server administrators would only need to install, maintain, and troubleshoot hardware and software. We would have access to detailed manuals, walkthroughs, and capable support staff. Employers would give us the freedom we need to select and deploy the best options. Industries and verticals would have standardized on the most superior solutions, and each would accept and integrate public suggestions and solutions. We don’t live in that world. Instead, we deal with conflicting information, politically driven decisions, substandard products, incompetent vendors, and outsized egos. We have fought these problems since the beginning of our professional, and we will always struggle against them. Unfortunately, the battle has brought about poor solutions. This article discusses the challenges and provides a sustainable framework of decision making for server administrators and system architects.

Every new field we explore starts with the same basic question: “Where do I start?” Many of us worked with home computers before moving into the world of professional IT. The lucky ones enjoyed a smooth ramp-up. As the field continues to expand and consumer-grade systems require less knowledge to use, that transition becomes rougher. Furthermore, companies have long viewed technical staff as somewhat interchangeable, so they dislike hiring employees that require foundational training. Once upon a time, many companies would assign new hires to front-line help desk roles and allow them to grow into other roles. Nowadays, most treat IT positions like treadmills; an employee starts, works for a while, and then quits or gets fired. Employers expect applicants to show up with the skills necessary to succeed in the job. That means that if you want to improve your chances of finding a satisfying server administrator job without years of hopping through entry-level positions until you find an employer that will train you, you need to take matters into your own hands. You can take the formal education route, if you have the time and money. Either way, having a home lab will never hurt you. Let’s look at some tips to help you get going.

This site focuses on systems administrators, but everyone at every level, technical or not, needs to report problems. As the first point of contact, your trouble ticket (or e-mail, or problem report, or service ticket, or helpdesk request, or whatever your organization might call it) sets the tone for the future interactions necessary to get that problem solved. When you submit an effective trouble ticket, you increase your chances of skipping unnecessary intermediary steps and reaching resolution faster.