Pre-command doesn't run if remote server is offline
We are using Backup Exec 2012 and I have one backup job that fails frequently. I am using a Windows Remote Agent to back up a remote workstation that is used to create multimedia content and has a fairly significant amount of local storage. I have created a script that sends a WOL "magic packet" to the machine and waits until it is awake before exiting. This script is configured within the job to run on the local media server. This script works flawlessly when run manually, however setting it as a pre-command to the backup job, it does not even run if the remote machine is turned off (it does run if the machine is on). I have the pre-command execution timeout set to the default of 15 minutes but the job fails after only five minutes. The error is "Backup Exec could not log on to the server with the logon account specified for it". Backup jobs are however successful if the machine is on.
This all leads me to believe that something in the BE job engine is attempting to connect to the remote machine and causing the job to fail before the pre-command ever executes. I read another thread on this site that discussed whether or not a snapshot was attempted prior to the pre-command but the conclusion was that the pre-command runs before any snapshotting.
My question is: is there some other setting within the backup job that is instructing Backup Exec to attempt to connect to the remote machine prior to executing any pre-command?
Any assistance with this is greatly appreciated.