Hi,
We just purchased full license of your product and we wanted to try to run remote tasks on several computers but what happen is VisualCron doesn't wait until remote tasks will be compelete, it is just triggers it. Output doesn't come back .. it shows in output "PID=1356". It is huge problem for us.
We run your product on Windows 2008 R2 system.
Please advise.
Thanks in advance,
Pavel

Hi Pavel,

currently, Windows return the PID after starting and give no other information when using Remote Execute API. It only tells if the process has started ok.

Currently, to get more control you need a local installation.

We have some thoughts about creating some workarounds however it will be some work and will give very few advantages because what our users really want is output from remote execute which requires some kind of agent installed at remote server and is not possible by default in Windows. So, we will probably focus on developing the agent.

---

Henrik it is super problematic implementation, you can easily doing remote execution by putting inside psexec for example. Please advise when agent structure can be implemented?

Yes, you can use PSEXEC any time and call it from VisualCron. What PSExec is doing is installing a remote service that executes.

While we have this in mind there are two things we need to consider first:

1. how we should implement this, as separate agent or via Server installation.
2. how do we handle licenses for this? One of the problem is that Remote Execute with agent conflicts with Server license installation

The question is how many remote servers you want to execute on?

---

30-60 servers I guess.

Right now the only recommended way is to call PSExec from VisualCron. I don't know any better tool.

We will, in some way add support for remote execution with output support but we can't give any dates right now. I am moving this topic to Feature requests.

---

I'm also using psexec for al my remote execute tasks using the normal execute task.
I'm using it mostly for executing an SSIS package on a different SQL server.
Works fine by me, but na all in one solution.. I'm in.

Regards
Erik

---