![]() Some common questions related to this process and elevated privileges:ġ. If we receive anything else we won't know how to continue. Success is a return code of 0 and failure is a return code of 1. We don't know if any type of exit code has been written into the script itself. It simply puts it into the database and then writes it into the batch file. GSS doesn't know what you've put into the run this script section of the task. Something to remember when running a Run Script task. Upon completion of the running of the script you'll either receive a success or failure status up from the Dagent to the GSS. pszCmdExe=C:\Windows\system32\cmd.exe, pszCmdLine= /C ""C:\Windows\TEMP\rxscript.bat" ", user=epm\administrator, bWait=true CExecute ExecuteCmdLine() Calling ExecuteCmd. You'll see the following in the aclient.log. It will then move onto the running of the file. Once the file has been successfully delivered, the Dagent will send a status update to the GSS. The GSS will then open a connection and begin to send the rxscript.bat file down. You'll see the same information listed above. Once the Dagent receives this information you'll see it reflected in the aclient.log file. The above information is the details about the job that was created in the GSS console. a70-CCtrlServer::SendDataToClient - Exited. You'll then see this in the axengine.log file. It is how the GSS is telling the Dagent what to do. The socket specified here is for the initial handshake being made between the GSS and the Dagent. ![]() a70-Socket: Sent on socket (1620) - 344 chars sent. a70-CCtrlServer::SendDataToClient - Entered. ![]() a70-CFileTxSession::OpenFile(): Got file size 6, high 32 bits = 0 a70-CFileTxSession::SetTransferInfo(): After calculating m_skey a70-CFileTxSession::SetTransferInfo(): After calculating m_sTruncatedkey a70-CFileTxSession::SetTransferInfo(): keyTmp = 404d6 a70-CFileTxSession::SetTransferInfo(): strTemp = 404d6 a70-CFileTxSession::SetTransferInfo(): truncatedKeyTmp = 404d6 a70-CFileTxSession::SetTransferInfo(): After Initailizing KeyTmp a70-CFileTxSession::SetTransferInfo(): Initailizing KeyTmp a70-CFileTxSession::SetTransferInfo () - Entered. ![]() a70-CRxCtrlServer::CopyFileToComputer (CSession. a70-CRxCtrlServer::CopyFileToComputer (CSession) - Entered. a70-CRxDatabase::ReplaceTokens - Exited. a70-CRxDatabase::ReplaceTokens - Entered. The next step in the process is the server reaching out to the Dagent telling it that there is work to be done. The batch file will contain whatever information was placed in the 'Run this cript:' section of the Run Script task. ' a70-C:\Program Files (x86)\Altiris\eXpress\Deployment Server\Temp\5000011.bat created in first attempt' will be seen in the axengine.log. This batch file will be named with the computer id and then. The next step in the process is a batch file will be created in the Temp directory under the eXpress share. If there are multiple tasks within the job the NEXT_TASK_SEQ= value will start with zero and then will increment up one when the next task starts. Processing scheduled event: EVENT_ID= NEXT_TASK_SEQ=0 STATUS_CODE=0 COMPUTER_ID=5xxxxxxx With logging level for this service set to 7 you'll see the following in the axengine.log. This is dynamically chosen by the axengine at the time the job is scheduled.Īfter 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. 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. The purpose of this tech article is to explain the processed used by the Ghost Solution Suite server when performing Run Script tasks.
0 Comments
Leave a Reply. |