Psexec fails against windows 10 remote target

psexecremote-accessshellsysinternalswindows 10

Does psexec work against Windows 10 remote hosts? I'm running psexec from a Windows 7 machine. When the remote host is Windows 8.1, it works, when the remote host is Windows 10, it fails as below:

C:\Windows 7>psexec -h -u Admin -p passwordHere -n 280 \xxx.xx.xxx.xxx ipconfig

PsExec v2.11 – Execute processes remotely
Copyright (C) 2001-2014 Mark Russinovich
Sysinternals – www.sysinternals.com

Could not start PSEXESVC service on xxx.xxx.xxx.xxx:
The remote procedure call failed and did not execute.

Any clues appreciated.

Best Answer

Found this on a Microsoft forum, worked for me.

Open regedit from start. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System

Add REG_DWORD (32 bit) LocalAccountTokenFilterPolicy and set value to 1.

Related Solutions

How to copy a folder from remote to local using scp

scp -r user@your.server.example.com:/path/to/foo /home/user/Desktop/

By not including the trailing '/' at the end of foo, you will copy the directory itself (including contents), rather than only the contents of the directory.

From man scp (See online manual)

-r Recursively copy entire directories

Powershell – execute a batch file on remote machine

In you example, @David Candy pointed out even you had the connection go thru, it would not work as you have 'c:>hyp\' instead of C:\hyp\tom7_*
You seem to be using IP, but the message you got seems to be name resolution related, so not sure what's happening there. Maybe you should upgrade to the latest PsExec version.
If you want to use PowerShell you would use Invoke-Command -ComputerName {NameOfPC} -ScriptBlock {C:\Hyp\tom7_50080\bin\shutdown.bat}

Best Answer

Related Solutions

How to copy a folder from remote to local using scp

Powershell – execute a batch file on remote machine

Related Topic