Run batch scripts on a remote server (windows) from jenkins

If Jenkins on Windows, remote on *nix, use plink.exe (which is essentially command line PuTTy)

If Jenkins on Windows, remote on Window, use psexec.exe

If Jenkins on *nix, remote on *nix, use ssh

If Jenkins on *nix, remote on Windows, (update 2015-01) Ansible http://docs.ansible.com/intro_windows.html has support for calling Windows commands, eg powershell, from a unix/linux machine, https://github.com/ansible/ansible-examples/blob/master/windows/run-powershell.yml

Tell me what OSes are involved (both on Jenkins and remote), and I will flash this out further.

Edit:
The download page for psexec.exe lists all command line options. You will want something along the lines of:

psexec \\remotecomputername -u remoteusername -p remotepassword cmd /c <your commands here>
Replace <your commands here> with actual commands as you would execute them from command prompt.

Note that psexec first needs to install a service, and required elevated command prompt/admin remote credentials to do so.
Also, you need to run psexec -accepteula once to accept the EULA prompt.

Following Slav's answer above, here is a simpler solution for Jenkins (*nix) to remote (windows):

1. Install an SSH server on your remote windows (MobaSSH home edition worked well for me)
2. Make sure your Jenkins user, on your Jenkins machine, has the required certification to open an SSH connection with your remote (you can simply open a terminal and ssh to your remote once, then accept the certification. Make sure it is saved for the Jenkins user).
3. You can now add an execute shell build phase in your Jenkins job which can SSH to your remote windows machine.

Notes :

1. The established connection might require some additional work - you might have to set windows environment variables or map network drivers in order for your executed commands or batch files to work properly on your windows machines.
2. If you wish to run GUI related operations this solution might not be relevant (Following my work on running automation tests which require GUI manipulation).
3. Using Jenkins SSH plugin is an issue, as seen here.

I ended up going with a different approach after trying out psexec.exe for a while.

Psexec.exe and copying files over the network was a bit slow and unstable, especially since the domain I work on has a policy of changing password every months (which broke the build).

In the end I went with the master/slave approach, which is faster and more stable. Since I don't have to use psexec.exe and don't have to copy files over the network.