So I have a bat script that I am currently running on my local machines Task Scheduler. In order for it to work on my local I had to use Configure for Windows Vista, Windows Server 2008 under security options. If I do not it triggers the bat but does not run properly. So now I am moving it over to Visual Cron and it is doing the same thing. It triggers the program but does not run properly. I assume I need to change a setting somewhere so my computer knows to run with the same Configure for WIndows Vista, Windows Server 2008. Where can I change that? I see this in the documentation but no explanation
<Please add the steps to check Launch and Activation Permissions, Access Permissions, Configuration Permissions based on the default of Windows Server 2008>[

So I have a bat script that I am currently running on my local machines Task Scheduler. In order for it to work on my local I had to use Configure for Windows Vista, Windows Server 2008 under security options. If I do not it triggers the bat but does not run properly. So now I am moving it over to Visual Cron and it is doing the same thing. It triggers the program but does not run properly. I assume I need to change a setting somewhere so my computer knows to run with the same Configure for WIndows Vista, Windows Server 2008. Where can I change that? I see this in the documentation but no explanation
<Please add the steps to check Launch and Activation Permissions, Access Permissions, Configuration Permissions based on the default of Windows Server 2008>[

Hi Chad,

Please send screenshots of how you set up the task to support@visualcron.com , and also include any error messages/output you get when trying to run it

---

So I was able to get around the issue. All the remote execution stuff I had working fine and it was triggering the program. The problem was I was triggering an old legacy program and VisualCron was not able to do it correctly. Windows Task Scheduler has a security option on how you want to trigger the programs. If you used the default it had the same issue VisualCron did but if you changed the option in task sheduler to Configure for (picture I attached) Windows Vista, Windows Server 2008 then it would work fine in Windows Task Scheduler. VisualCron does not seem to have those options. To get around the issue I installed the program I was trying to run on the server where VisualCron is located. I at first had same issue but when executing locally VisualCron had more options so I was able to get around issue by changing Execution Context settings to foreground execution. All working now. Thanks.

So I was able to get around the issue. All the remote execution stuff I had working fine and it was triggering the program. The problem was I was triggering an old legacy program and VisualCron was not able to do it correctly. Windows Task Scheduler has a security option on how you want to trigger the programs. If you used the default it had the same issue VisualCron did but if you changed the option in task sheduler to Configure for (picture I attached) Windows Vista, Windows Server 2008 then it would work fine in Windows Task Scheduler. VisualCron does not seem to have those options. To get around the issue I installed the program I was trying to run on the server where VisualCron is located. I at first had same issue but when executing locally VisualCron had more options so I was able to get around issue by changing Execution Context settings to foreground execution. All working now. Thanks.

Ah, I see! Thanks for the information. Great that you got it working now

---