Powershell remoting is still a pain in my ass in most places, I rarely use it.
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
A real world cursed config a friend who works at an MSP told me about is a domain controller with HyperV setup on it. You read that right, the DC is on the HyperV host. Apperently they’ve been wanting to fix it for a few years but haven’t gotten the go ahead on the hours or downtime to fix it
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:
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”
Generally desktop hardware is surprisingly power efficient, especially with lower-midrange components. Right now my home server is running on an ewaste HP Elitedesk.
For software, I’d really go for a config that uses ZFS over EXT4 for the data storage. ZFS is so battle-tested that anything you might find you want or need to fix or change, someone else has already documented the same situation multiple times over. Personally I went with a config like Apalrd’s with using proxmox for a stable host OS with good management and to create the zfs pool, then a container running cockpit for creating and managing the shares.
Currently that server has a 800GB Intel Datacenter SSD for boot and VM storage, and 2x 4TB HDDs in a ZFS mirror for NAS storage, an with a i5-4590 it’s running 6 Minecraft servers via Crafty Controller, Jellyfin, the Samba shares and I’ve spun up other random servers and VMs as desired/needed without trouble. Basically all of the services which run 24/7 are in LXCs because running Debian VMs on my Debian host seems too redundant for my tastes.