Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


Sander van Dragt
2016-03-25T15:08:53Z
I've got a Remote Execute task with the following details:

credentials: myserviceuser@domain (Local: true, Loadprofile:true)
Host name: myserver
Command: powershell
Arguments: -c "get-adgroup 'testgroup'"

The Active Directory management module for Powershell is installed on myserver. 'testgroup' exists.
I can successfully run powershell -c "get-adgroup 'testgroup'" as the myserviceuser when starting a remote desktop session to myserver.

However VisualCron returns "Incorrect function.Exception in Task: Non zero exit code" and I think this is because it does not recognise that the active directory management module is installed on the server.

Is the remote execute task actually doing a remote login then executing the task and why does it not recognise the logon environment?
I don't want to create a manual task scheduler job and trigger this from VisualCron but that would be a work around.
Sponsor
Forum information
Support
2016-03-25T16:13:14Z
Originally Posted by: Sander van Dragt 

I've got a Remote Execute task with the following details:

credentials: myserviceuser@domain (Local: true, Loadprofile:true)
Host name: myserver
Command: powershell
Arguments: -c "get-adgroup 'testgroup'"

The Active Directory management module for Powershell is installed on myserver. 'testgroup' exists.
I can successfully run powershell -c "get-adgroup 'testgroup'" as the myserviceuser when starting a remote desktop session to myserver.

However VisualCron returns "Incorrect function.Exception in Task: Non zero exit code" and I think this is because it does not recognise that the active directory management module is installed on the server.

Is the remote execute task actually doing a remote login then executing the task and why does it not recognise the logon environment?
I don't want to create a manual task scheduler job and trigger this from VisualCron but that would be a work around.



Have you tried the full local path to powershell.exe?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Scroll to Top