I am trying to execute a .BAT file that sits within a remote server \\A and a directory my network user has access to. I can execute the batch .BAT just fine when I log into that \\A server via RDP. The remote server is Windows Server 2008 R2. When I try to run PsExec.exe from a different \\B server with the PsExec.exe on a local folder in \\B, I am trying to execute the .BAT on \\A:
D:\PSTools>psexec \\IP -u Domain\user -p password /accepteu
la -i -d cmd /c "D:\Folder\MyRename.bat" >> test.log
PsExec v2.11 - Execute processes remotely
Copyright (C) 2001-2014 Mark Russinovich
Sysinternals - www.sysinternals.com
Starting cmd on <IP>... <IP>...
cmd started on <IP> with process ID 4580.
This looks like it was successful, but it is not running the .BAT file. The user/password is the same account I use to RDP into server \\A, which I can run manually just fine.
Can someone help me determine why the PsExec looks like it is running the .BAT file remotely, but is not?