Back to the Core: Server administration without a graphical interface

Published: May 8, 2025

---

As an apprentice in the field of IT / systems engineering, I learn daily how servers, networks and user management systems work.

At school, we prepare for exams – Active Directory, network technology, server services, rights management.

And almost everything runs through graphical user interfaces.

• Windows Server with GUI.

• Management consoles.

• Event viewer.

• Active Directory with one click.

But at some point I asked myself a simple question:

Do I truly understand the systems – or do I just know where to click?

So I set myself a challenge:

I will be working exclusively with the console for one week.

No server manager, no graphical explorer, no remote desktop interfaces

Commands only.

---

The beginning: uncertainty and frustration

The first few days were more difficult than expected.

At school you learn commands – but in everyday life you quickly reach for the mouse.

Especially in exercises like:

• Create user accounts

• Manage groups

• Check services

• Analyze logs

• Test network connections

  
  

The GUI allows you to navigate through the interface relatively quickly.

You need to know what you're doing with the console.

What I missed:

• The clear event viewer structure

• The visual representation of Active Directory

• Quick status indicators

• Drag & Drop for file sharing

Instead, I worked with commands like:

ipconfig; net user; Get-EventLog: systemctl ; ssh

No buttons. No safety nets. Just syntax.

And if you make a mistake – it simply won't work.

---

Studying for the exam – but this time properly

Especially in education, it's not just about solving tasks, but about understanding them.

I had to use the console:

• Manually create users and understand parameters

• Start, stop, and analyze services directly

• Filter log files yourself

• Carefully check network configuration

• Set permissions selectively

I couldn't just "click by instinct".

I had to understand:

• Which services are running in the background?

• Which ports are used

• How processes are interconnected

• How the file system is structured

  
  

This has completely changed how I study for exams.

---

The turning point: Structure in thinking

After a few days I noticed that I was working more calmly.

If something doesn't work, I proceed systematically:

1. Check process

2. Check service status

3. Analyzing log files

4. Test network

5. Check permissions

   
   

Before, I might have clicked around somewhere first.

Now I think in terms of processes.

And this structured thinking is precisely what is crucial in exams.

---

6 months later: Lasting effect

This week was just the beginning.

Today – six months later – I clearly notice how much this has changed me.

• More confident in using PowerShell and Bash

I no longer have to think about which command I need.

• Deeper understanding of Active Directory

I understand what's happening behind the scenes – not just the surface.

• More confidence in server work

Even a server without a GUI no longer scares me.

---

Was it more difficult? Yes.

Especially as an apprentice, when you don't yet have years of experience, the console feels like a risk at first.

But this very challenge has shown me:

Comfort is good.

Understanding is better.

Graphical interfaces make work easier – especially in everyday school life.

But the console demands precision.

And precision is what makes the difference in system administration.

---

Conclusion

The week without a UI was not purely a technical experiment.

It was a learning strategy.

As an apprentice, I not only improved my commands, I changed my thinking as a future system administrator.

Today I no longer work exclusively with systems.

I understand them.

And that's exactly what gives me confidence – for exams and for my future in IT.