Inside the blog there are several article about this argument with different examples and implmentation.
here is command string that I utilize to execute, on remote pc, .vbs:
psexec \\PC_ Name -w -u <\User\> -p <\Password\> c:\ -h cscript.exe "c:\windows\system32\vbsname.vbs"
Scripting - Eseguire .vbs ed installazioni programmi su pc remoti in un dominio o un workgroup con PSEXEC
Silently Install Windows patch on remote client
Enable Remote Desktop on remote client
Execute remote command examples
Hacker - Give SYSTEM user administrative right on Patched Windows System with PSEXEC
I proceed to copy and paste latest version info from microsoft website:
http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx
PsExec v2.4
https://learn.microsoft.com/en-us/sysinternals/downloads/psexecIntroduction
Utilities like Telnet and remote control programs like Symantec's PC Anywhere let you execute programs on remote systems, but they can be a pain to set up and require that you install client software on the remote systems that you wish to access. PsExec is a light-weight telnet-replacement that lets you execute processes on other systems, complete with full interactivity for console applications, without having to manually install client software. PsExec's most powerful uses include launching interactive command-prompts on remote systems and remote-enabling tools like IpConfig that otherwise do not have the ability to show information about remote systems.Note: some anti-virus scanners report that one or more of the tools are infected with a "remote admin" virus. None of the PsTools contain viruses, but they have been used by viruses, which is why they trigger virus notifications.
Installation
Just copy PsExec onto your executable path. Typing "psexec" displays its usage syntax.Using PsExec
See the July 2004 issue of Windows IT Pro Magazine for Mark's article that covers advanced usage of PsExec.Usage: psexec [\\computer[,computer2[,...] | @file]][-u user [-p psswd][-n s][-r servicename][-h][-l][-s|-e][-x][-i [session]][-c [-f|-v]][-w directory][-d][-
| -a | Separate processors on which the application can run with commas where 1 is the lowest numbered CPU. For example, to run the application on CPU 2 and CPU 4, enter: "-a 2,4" |
| -c | Copy the specified program to the remote system for execution. If you omit this option the application must be in the system path on the remote system. |
| -d | Don't wait for process to terminate (non-interactive). |
| -e | Does not load the specified account’s profile. |
| -f | Copy the specified program even if the file already exists on the remote system. |
| -i | Run the program so that it interacts with the desktop of the specified session on the remote system. If no session is specified the process runs in the console session. |
| -h | If the target system is Vista or higher, has the process run with the account's elevated token, if available. |
| -l | Run process as limited user (strips the Administrators group and allows only privileges assigned to the Users group). On Windows Vista the process runs with Low Integrity. |
| -n | Specifies timeout in seconds connecting to remote computers. |
| -p | Specifies optional password for user name. If you omit this you will be prompted to enter a hidden password. |
| -r | Specifies the name of the remote service to create or interact with. |
| -s | Run the remote process in the System account. |
| -u | Specifies optional user name for login to remote computer. |
| -v | Copy the specified file only if it has a higher version number or is newer on than the one on the remote system. |
| -w | Set the working directory of the process (relative to remote computer). |
| -x | Display the UI on the Winlogon secure desktop (local system only). |
| -priority | Specifies -low, -belownormal, -abovenormal, -high or -realtime to run the process at a different priority. Use -background to run at low memory and I/O priority on Vista. |
| computer | Direct PsExec to run the application on the remote computer or computers specified. If you omit the computer name, PsExec runs the application on the local system, and if you specify a wildcard (\\*), PsExec runs the command on all computers in the current domain. |
| @file | PsExec will execute the command on each of the computers listed in the file. |
| cmd | Name of application to execute. |
| arguments | Arguments to pass (note that file paths must be absolute paths on the target system). |
| -accepteula | This flag suppresses the display of the license dialog. |
psexec \\marklap"c:\long name app.exe"
Input is only passed to the remote system when you press the Enter key. Typing Ctrl-C terminates the remote process.
If you omit a user name, the process will run in the context of your account on the remote system, but will not have access to network resources (because it is impersonating). Specify a valid user name in the Domain\User syntax if the remote process requires access to network resources or to run in a different account. Note that the password and command are encrypted in transit to the remote system.
Error codes returned by PsExec are specific to the applications you execute, not PsExec.
Examples
This article I wrote describes how PsExec works and gives tips on how to use it:The following command launches an interactive command prompt on \\marklap:
psexec \\marklap cmd
This command executes IpConfig on the remote system with the /all switch, and displays the resulting output locally:
psexec \\marklap ipconfig /all
This command copies the program test.exe to the remote system and executes it interactively:
psexec \\marklap -c test.exe
Specify the full path to a program that is already installed on a remote system if its not on the system's path:
psexec \\marklap c:\bin\test.exe
Run Regedit interactively in the System account to view the contents of the SAM and SECURITY keys::
psexec -i -d -s c:\windows\regedit.exe
To run Internet Explorer as with limited-user privileges use this command:
psexec -l -d "c:\program files\internet explorer\iexplore.exe"
[update Dicembre 2014]
Per maggiori info sull'utilizzo di psexec potete fare riferimento al seguente articolo: https://turbolab.it/407
[update 2017.04.28]
You can execute psexec via powershell too.
You can review this article about some explanation and powershell usage too.
https://4sysops.com/archives/psexec-vs-the-powershell-remoting-cmdlets-invoke-command-and-enter-pssession/
