3 ms·
Note that Windows has had a similar capability to SSH for many years, but it's unfortunately not so well-known: https://docs.microsoft.com/en-us/sysinternals/do
by userbinator 8y ago
Note that Windows has had a similar capability to SSH for many years, but it's unfortunately not so well-known: https://docs.microsoft.com/en-us/sysinternals/downloads/psexec https://docs.microsoft.com/en-us/sysinternals/downloads/psex... ("ps" prefix is unrelated to PowerShell, in fact I think this utility predates it.)
It uses DCE-RPC which is not trivial, but I believe it is certainly more compact than SOAP and such. The main advantage is the server component is built-in.
- Something1234 8y agoFor the curious, https://en.wikipedia.org/wiki/Distributed_Computing_Environment https://en.wikipedia.org/wiki/Distributed_Computing_Environm... It sounds super complex to setup.
- xenophonf 8y agopsexec is trivial to install and use: just download and run. At worst you might need to enable the RPC ports in the Windows firewall, which is also easy (even at scale thanks to GPO).
- cm2187 8y agoBut is there anything to install or setup on a windows server other than opening a port? Also does it require the server to be domain joined?
- pjc50 8y agoNo, all it requires is that "file and print sharing" is turned on and accessible. Windows has a default, hidden share "Admin$" which is used for this (just as "c$" exists as a share even if you don't explicitly share anything)
- amaccuish 8y agoWindows only takes the wire protocol from DCE, and added a few things here and there. It's used extensively in Windows, e.g. the DNS MMC snapin. For NT Domains it was THE protocol, until Microsoft moved to AD with more standards-based protocols, but even AD still heavily relies on RPC, i.e. for replication. The annoying thing about MSRPC is that it uses a portmapper process, like sun rpc for NFS3, so it's a pain to use with firewalls, as ports are randomly assigned. But it's widely simpler than a DCE environment, it's been made to fit internet protocols.