The situation: Two systems, and one has to be able to give a command to start software on the other.
We tend to use Psexec for it, so we tried it with this customer too. However, the process starts on that machine, but does not become interactive! It shows in Taskmanager, but there is no window, nor a minimized icon or anything. This should be a matter of using the -i switch, but that is already present (-s -i -d). Even Notepad.exe fails to start correctly when you try to start it using Psexec. Starting it directly on that computer works fine, but not remotely.
Tried making a new account with Admin rights: same problem. Calling a batchfile instead: the batchfile runs, starts the program, but again not interactively.
Googling tends to turn up people who forgot the -i switch, not people where that fails to work.
Simple file sharing is turned off (required for Psexec to work correctly)
Anyone has any idea what it might be, or knows of a similar tool which I could try using instead?
Edit: Searching a while turned up BeyondExec (download link), a FreeWare tool which is almost identical to Psexec (only had to change -d into -w), but which does work!
So unless it fails to work at the system I needed it for I no longer need information or help
Edit 2: And indeed, while it worked here on a test system it failed on the other system.
But... The cause and solution were found. A Windows update caused it, and it can be solved by specifying a process ID with Psexec. For some reason an automatically generated ID does not suffice anymore.
We tend to use Psexec for it, so we tried it with this customer too. However, the process starts on that machine, but does not become interactive! It shows in Taskmanager, but there is no window, nor a minimized icon or anything. This should be a matter of using the -i switch, but that is already present (-s -i -d). Even Notepad.exe fails to start correctly when you try to start it using Psexec. Starting it directly on that computer works fine, but not remotely.
Tried making a new account with Admin rights: same problem. Calling a batchfile instead: the batchfile runs, starts the program, but again not interactively.
Googling tends to turn up people who forgot the -i switch, not people where that fails to work.
Simple file sharing is turned off (required for Psexec to work correctly)
Anyone has any idea what it might be, or knows of a similar tool which I could try using instead?
Edit: Searching a while turned up BeyondExec (download link), a FreeWare tool which is almost identical to Psexec (only had to change -d into -w), but which does work!
So unless it fails to work at the system I needed it for I no longer need information or help
Edit 2: And indeed, while it worked here on a test system it failed on the other system.
But... The cause and solution were found. A Windows update caused it, and it can be solved by specifying a process ID with Psexec. For some reason an automatically generated ID does not suffice anymore.
Facebook
Twitter