2

PsExec (v2.11) can take up to a minute to invoke a process, either locally or remotely.

I'm using the following command line:

psexec.exe -u domain\username -p mypassword -accepteula -d -h \\machinename C:\path\to\myapp.exe

I have the firewall disabled on all machines.

What else can I look at?

UPDATE: I used procmon to highlight the delay:

enter image description here

Mark Richman
  • 296

2 Answers2

0

On windows server (2008 to 2019) there are 3 default rules that need to be enable:

  • Go to: windows defender firewall with advanced security
  • Go to: Inbound Rules
  • Right clic on Inbound Rules Filter by Group -> Filter by Remote Service Management
  • Enable those 3 rules for domain (if you set your connection as Domain)

Remote Service Management (NP-In)
Remote Service Management (RPC)
Remote Service Management (RPC-EPMAP)

PsExec v2.34

C.

Cramaboule
  • 11
  • 1
0

The command indirectly open a user session under the specified username to run the process, thus it will be long, you can't do much for that problem.

Only tip to make it a bit faster:

  • You can try with -s to run the process as a LOCAL SYSTEM.

  • Try with -e, so it does not load the user profile.

yagmoth555
  • 17,495