Hey all!

I’m a long time Linux user, and I’ve been avoiding it for the good part of the last ~15 years. Most of my Windows experience is from the XP times.

I’ve changed careers from agriculturing to ICT a few years ago (almost done with school), and while I can say I know my way around Linux pretty well, Windows is an alien landscape to me.

I got a job a few years ago as sysadmin (not so much, but still) / IT-support (more), and I find myself struggling to help customers with Windows / handle Windows servers. I would like to change that.

I have no intention on moving my personal computing to Windows due to privacy concerns, which is a bit contradictory to my goals, because AFAIK learning things this way is the “best” approach. It was the case with Linux for me, at least.

While i do learn Windows at my job, I’d like to compliment it with another approach, too.

Do you guys have any suggestions how I could learn Windows (the whole ecosystem, not just end-users computers)? I’d like it to be fun, as I get bored easily (breaking my Linux time and time again was really fun learning method) Maybe fire up some VMs and go from there, somehow? What do you think are the most essential skills for a Windows sysadmin? Active Directory, sure, but what else?

  • Trainguyrom@reddthat.comEnglish
    2·
    7 months ago

    From an admin perspective one of the best things to lab out is setting up a standard SMB server stack, which is 2x domain controllers, 2x DHCP servers, a file server, and a couple of desktop VMs, then practice setting it up to be nicely locked down like in a standard corporate environment. For example:

    • redirect user directories to the file server and set permissions so only the user, admins and departmental managers can access files
    • setup departmental directories on the share with departmental and managerial permissions
    • setup group policies to lock down the desktops so that users just get a standard experience

    But also make sure to set this up both in Windows Server with the full “Desktop Experience” as well as on Windows Server Core, and try to do so while following best practices with redundancy, network segmentation, etc. you could even get fancy and setup a remote site with redundant servers and replication to the remote site as well to experiment with how that works.

    Then of course, once you have your virtual SMB network setup, try to break it. Fill up some of the VMs so it’s out of disk space, corrupt one of the VMs and try to recover it, power off the servers when you shouldn’t, cut some important virtual Ethernet connections and leave them severed for a while, or degrade the virtual ethernet connection and see what happens, delete the only domain controller and see what the best path to business continuity is, etc.

    This covers a lot of the tickets and critical failures you’ll see on a standard SMB network and will give you a good amount of exposure to a lot of what you’ll work with in the “real world”