Default behavior when creating a script Task is for the script to be created in "C:\Temp" and executed from there. Certain security configurations block anything from being executed from the root of "C:\" and "C:\Temp" as well as some other locations as they are commonly used by viruses and malware to install from. Are we able to change the behavior of the product to stop it trying to run things from there as it prevents us using that functionality within the product?
The product is working as designed; there is no such functionality built into the product.
Create a script or copy file task to copy the file to the desired directory, then execute a task with a batch file (or other mechanism) to 'kick off' the previously copy file.
Please see the below example:
Create a script or copy file task to copy the file to the desired directory, then execute a task with a batch file (or other mechanism) to 'kick off' the previously copied filed. In this instance create a‘Copy File’ task to stick a batch file on an endpoint; this exercise copies “Test.bat” to “C:\Program Files\Altiris\ScriptTest\” (*All this batch file does is create a text file with some text within in the “…\Altiris\” directory*):
Create a script task to execute the batch file. Upon success this will place the text file in the correct directory:
Now this is a simple example, but this process should be applicable to different scenarios.
Subscribing will provide email updates when this Article is updated. Login is required.