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?
How to learn Windows? Years of pain and torture of course.
What to learn? Powershell, learn powershell.
Then as you follow along any guides or howtos for administrative tasks, try to search how to accomplish the same things in powershell. Take notes on your own powershell learnings. I keep all my windows administrative powershell one liners, scripts, and notes in the same digital notebook for quick reference and updating.
If you're already experienced with bash, like I was, learning powershell might be tough. As it was for me, I had trouble understanding why PS cmdlets seemed to hide data when piped... Format-table(ft) and Format-List(fl) help tremendously
Powershell remoting is still a pain in my ass in most places, I rarely use it.
There's a windows admins discord group that's pretty savvy I asked and learned a lot along the way there. https://discord.com/invite/winadmins
YouTube! Don't necessarily look for YouTube powershell windows videos. Just the necessary tasks through the GUI will give you the correct direction to begin converting a process to PS. Learn how other Admins process tasks by watching them. Especially if it's an often repeated task try converting some or all of what they do in the video into PS equivalent.
With all of that said knowing powershell doesn't really help recovering from disasters. Knowing how to install windows and recover data from borked systems is a task best learned through battles. So, absolutely set up VMs and installed all manner of versions you'll be working with...that way you'll have familiarity with when things go wrong in them. I've yet to install windows 11 in a VM but I did try to install a copy onto a surface tablet only to learn the hard way that do ing so leaves the tablet without the drivers necessary for using the keyboard and touchscreen...weird need a custom built image or recovery image, great fun.
Nah you dont need a special image for the touchscreen and stuff. Check the advanced update settings for optional downloads and also give the surface app in the microsoft store a shot. It actually is not terrible for troubleshooting.
Other than that: Create your own custom image if you deeply wish to. Here is the help doc:
https://support.microsoft.com/en-gb/surface/download-drivers-and-firmware-for-surface-09bb2e09-2a4b-cb69-0951-078a7739e120
Pywin32 does fascinate me
I can have python on Windows with the power of Powershell
I love python. Even on windows but I tend to try to learn to live off the land and not prerequisite my admin skills on additional software that may not always be available or an option.
I only really use powershell for Windows administration. I refuse to use WinRM though as OpenSSH works fine.
So the big thing with remote Powershell sessions is that you can't hop around like you can with SSH, but it's super useful when troubleshooting complaints of frozen/misbehaving systems with less resource needs than rdp