From time to time, the need to automate actions on a remote Windows machine arises. There are several approaches we've used in the past with varying degrees of success, simplicity and reliability.
1) Windows telnet server - we have found the telnet server to be useful, but it requires proper configuration. This is more difficult than it sounds, as the configuration has changed several times over the years, and enabling stream mode is a necessity, as iTest doesn't work well without it
2) netsh commands using the remote option - this is easy to use and provides much of the needed capabilities as far as configuring wifi or other network properties. However, the output does not get stored in iTest responses. The reason is that the output is usually sent to stderr, and redirecting stderr to stdout does not appear to work for this program.
3) psexec - similar results as netsh, but you can execute any program. Same problem with output redirection, though.