How does the Run Script process work within the Ghost Solution Suite?
Last Updated May 22, 2017
The purpose of this tech article is to explain the processed used by the Ghost Solution Suite server when performing Run Script tasks.
The first thing you need to know about the Run Script process is that the file transfer will happen on ports ranging from 1025 to 65536. This is dynamically chosen by the axengine at the time the job is scheduled.
After scheduling a Run Script task job through the GSS console, the Altiris eXpress Server service will create an entry in the database for the job. This entry will be given an Event_ID. With logging level for this service set to 7 you'll see the following in the axengine.log.
The above information is the details about the job that was created in the GSS console. Once the Dagent receives this information you'll see it reflected in the aclient.log file. You'll see the same information listed above. The GSS will then open a connection and begin to send the rxscript.bat file down.
Once the file has been successfully delivered, the Dagent will send a status update to the GSS. You'll see the following in the aclient.log.
Something to remember when running a Run Script task. GSS doesn't know what you've put into the run this script section of the task. It simply puts it into the database and then writes it into the batch file. We don't know if any type of exit code has been written into the script itself. Success is a return code of 0 and failure is a return code of 1. If we receive anything else we won't know how to continue.
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe