for clarification purposes, the vbrunas script, in short, executes this:
/runas domain\admin command.exe
when the shell prompts for the admin password, the script enters the password string and executes the command
the script was deployed successfully using a batch file installation under the current user account (as opposed to the Local System account), but this method is unfavorable as the batch file containing administrative credentials would be downloaded to the client machine. However, can someone explain why the script successfully runs commands from the current user account and not the local system account?
Edit or ReWrite your VB to run STARTASUSER before the RUNAS functions
Package your vbscript in a SWD, have it dropped your VBScript on the system and have the SWD run a STARTASUSER with your VBScript Name and parameters.
Either way you'll need to have it run at Next Login with a STARTASUSER. Why at Next Login? Because STARTASUSER does you no good if no one is logged in. My 2 cents worth...