4 ms·
It's been years since I last worked with Windows, but: 1) You can install an SSH server on Windows boxes just fine, then use Putty to SSH directly into PowerSh
by klibertp 9y ago
It's been years since I last worked with Windows, but:
1) You can install an SSH server on Windows boxes just fine, then use Putty to SSH directly into PowerShell. PowerShell is not a classical shell, but rather a REPL for a procedural, imperative and object-oriented DSL for system configuration and administration based on .NET, with much saner syntax than my beloved zsh. In short, it works quite well.
2) With PowerShell capabilities - I'm a bit fuzzy on the details here, was a long time ago - you don't even need the SSH server, you can issue remote commands from your local PS instance. It required a bit of configuration up front, IIRC, but then you could replace your local session with a remote one with a single command.
So, in my experience - and note that it was probably nearly a decade ago! - Unix-style remote management was absolutely possible and not that much less convenient. And PowerShell is really a solid tool, with easy access to all of .NET and all of the system; the only annoyance I remember was certificate/signature management, dunno if it got any better.
- scarface74 9y agoThe problem isn't a Powershell, remote administratoon is tightly tied into the Windows security framework which can really be a pain with tooling. But part of the problem is I have a real prejudice toward local agent based solutions with a central server coordinating everything.