How pipe vbscript output into kbox logs
Hi
I am trying to figure out how I can execute a vbscript on a workstation and retreive an output from that script back into the kbox logs. I am using an online kscript with a dependency of the vbs file and and on success task which runs cscript and the vbs. The script I am using will amend the boot order on a HP system, the result of this script could be any one of 6 outputs, from 'success' to 'access denied' or 'failure'. Obviously I can set the errorlevel that the vbscript pipes out relative to the output but I cant see how to pipe this back to the kbox. All I can do is be advised that the script executed ok. My next step was going to be to create a file/reg entry from the vbscript for each output and then create another kscript task for each one, this just seems a bit long winded and inelegant.
What I would ideally like would be to see the result of the script after it has executed on 300+ machines and clearly identify which ones had a problem at a glance.
Any help much appreciated.
Many thanks
Simon
I am trying to figure out how I can execute a vbscript on a workstation and retreive an output from that script back into the kbox logs. I am using an online kscript with a dependency of the vbs file and and on success task which runs cscript and the vbs. The script I am using will amend the boot order on a HP system, the result of this script could be any one of 6 outputs, from 'success' to 'access denied' or 'failure'. Obviously I can set the errorlevel that the vbscript pipes out relative to the output but I cant see how to pipe this back to the kbox. All I can do is be advised that the script executed ok. My next step was going to be to create a file/reg entry from the vbscript for each output and then create another kscript task for each one, this just seems a bit long winded and inelegant.
What I would ideally like would be to see the result of the script after it has executed on 300+ machines and clearly identify which ones had a problem at a glance.
Any help much appreciated.
Many thanks
Simon
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
airwolf
13 years ago
Have the VBS output a value to an INI file, and then setup a custom inventory item to pull the value from the INI file.
Posted by:
jkatkace
13 years ago
I also believe that if you click the "wait for startup" checkbox in the Launch Program step in a task, one of the side effects is to pipe the stdout and stderr to the scripting logs.
Posted by:
shoddinott
13 years ago
Thanks for the input on this. In the end I used a registry key and a custom inventory item to get the desired outcome.
Cheers
Simon
Cheers
Simon
Posted by:
GillySpy
13 years ago
For those who come along and wonder how you might have done it, here's a similar example. This question is very similar to the "getting data into the registry" part
http://www.kace.com/support/kb/index.php?action=artikel&cat=5&id=968&artlang=en
Please include your code if you are able.
http://www.kace.com/support/kb/index.php?action=artikel&cat=5&id=968&artlang=en
Please include your code if you are able.
Posted by:
shoddinott
13 years ago
My code doesn't really differ from that article. It would have been great if I had seen that to begin with!
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.