Not all directions are clear. Here is an example where Microsoft has less than perfect directions:
Just copy PsExec onto your executable path. Typing "psexec" displays its usage syntax."
First off, psexec won't display usage syntax until after the installation. If you are like me you are asking what is the executable path?
The answer can be found by opening PowerShell and typing this:
Get-ChildItem Env:Path | ft -wrap -AutoSize
Any of those semi-colon delimited results can be the destination of the files inside the PsTools.zip file. The files must not be in a subdirectory of the results shown by the above PowerShell command. They must be directly in the folder shown by the above PowerShell command.
It is an easy install because no services need to be recycled. No reboot is needed either. Psexec is useful because the other Windows servers on the network need no special configuration if you have a common administrator account. The other Windows servers do not need to be part of a domain. The network logon will be a Type 3 (as seen in the Event Viewer). This is considered safe by SANS.