2
2
i frequently use remote desktop, gotoassist express and logmein to administer servers or end user terminals.
in certain circumstances there is significant latency or low bandwidth where a full console is either slow, superfluous (i.e. if i'm using powershell to administer exchange via rdp) or overkill (i.e. an end user would like to use the machine at the same time, and i need to use cmd, robocopy, wget, etc)
in this circumstances i'd like a simple facility for enabling remote administration via powershell or cmd. assuming i already have full access to the machine via gotoassist, logmein, etc, what would be the simplest method for enabling this?
winrm would be a superb technology, but it's far too messy to setup. something ad-hoc would be excellent, but the simpler the better. ideally something as simple as gotoassist's 'open the program, enter this code and we'll open the tunnel for you' would be perfect. needless to say this is over the internet and would have to be 100% secure and encrypted, however.
psexec
is not much more secure than Telnet. Both use plain text for everything except authentication. (Windows Telnet server and client use NTLM by default. Admittedly, they can't do Kerberos, whereas it is possible for SMB, which psexec uses.) – user1686 – 2011-04-08T14:47:11.047Also, re "copy a second batch file using Administrative shares":
\\server\ADMIN$
, the default forpsexec -c
, would be just a little better, in case the machine happens to not have aC:
. (99% of the time, this is something that only I worry about.) – user1686 – 2011-04-08T14:51:01.950i completetly agree using a ssh daemon. I use BitVise Winsshd. Its extremely simple to configure and very powerful at the same time. The responsiveness of the remote shell is perfect. – mjsr – 2011-04-10T22:21:45.960
Somehow managed to miss the "over-the-Internet" part of the last line. I would use SSH or a VPN to ensure security, as, yeah, the other methods are only feasible on a LAN. – Bacon Bits – 2011-04-10T22:59:53.997