OSD Scripting Event = "STREAM"
Hi everyone,
Trying to get clarification on this as all the material I have on OSD scripting is leaving me a little fuzzy on this point. We have an OSD file that runs a .vbs script with this as the header:
<SCRIPT EVENT="STREAM" TIMING="PRE" PROTECT="FALSE" WAIT="FALSE" TIMEOUT="30">
We were hoping that this would only run when the software is 'streamed' not everytime it was launched but from what we have found during testing is that the .vbs runs everytime the application in launched. If that is true then it seems to me that my header above is no different that having EVENT='LAUNCH' TIMING="PRE"...
Did we do something wrong or was our understanding just wrong?
Thanks!
Trying to get clarification on this as all the material I have on OSD scripting is leaving me a little fuzzy on this point. We have an OSD file that runs a .vbs script with this as the header:
<SCRIPT EVENT="STREAM" TIMING="PRE" PROTECT="FALSE" WAIT="FALSE" TIMEOUT="30">
We were hoping that this would only run when the software is 'streamed' not everytime it was launched but from what we have found during testing is that the .vbs runs everytime the application in launched. If that is true then it seems to me that my header above is no different that having EVENT='LAUNCH' TIMING="PRE"...
Did we do something wrong or was our understanding just wrong?
Thanks!
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
bertman
13 years ago
The location of the script has to be between <DEPENDENCY> </DEPENDENCY>.
I don't know where the VBS is, but when this script is also in the sequence, you need te use TIMING="POST" (after streaming).
And maybe you can try PROTECT="TRUE" (so he will stay in the bubble).
Normally I use a CMD.EXE instead of the VBS, to test if I can start and access the script.
I don't know where the VBS is, but when this script is also in the sequence, you need te use TIMING="POST" (after streaming).
And maybe you can try PROTECT="TRUE" (so he will stay in the bubble).
Normally I use a CMD.EXE instead of the VBS, to test if I can start and access the script.
Posted by:
DannyC
13 years ago
The EVENT tag dictates when the script runs but doesn't have any logic to say that it only runs once or only at FIRST stream. The only practical difference between EVENT="LAUNCH" TIMING="PRE" and EVENT="STREAM" TIMING="PRE" is that you could use the latter to test for some condition on the client to determine whether you even want to bother streaming the app or not. Once it's streamed then there's not a lot of difference really.
I'd suggest that you include some sort of 'flag' condition in your script (create/check for a log file for example) which could be used to make sure it only does whatever it is it needs to do once.
I'd suggest that you include some sort of 'flag' condition in your script (create/check for a log file for example) which could be used to make sure it only does whatever it is it needs to do once.
Posted by:
kkaminsk
13 years ago
As a FYI you might want to check out this PDF and read pages 23-24.
http://www.google.ca/search?q=app-v+abortresult+and+successresult&sourceid=ie7&rls=com.microsoft:en-ca:IE-SearchBox&ie=&oe=&redir_esc=&ei=KbibTNvgD83wngfO_vD4Dg
Also more specifically read this document for some abortresult and successresult examples on page 42.
http://download.microsoft.com/download/F/7/8/F784A197-73BE-48FF-83DA-4102C05A6D44/App-46_Sequencing_Guide_Final.docx
http://www.google.ca/search?q=app-v+abortresult+and+successresult&sourceid=ie7&rls=com.microsoft:en-ca:IE-SearchBox&ie=&oe=&redir_esc=&ei=KbibTNvgD83wngfO_vD4Dg
Also more specifically read this document for some abortresult and successresult examples on page 42.
http://download.microsoft.com/download/F/7/8/F784A197-73BE-48FF-83DA-4102C05A6D44/App-46_Sequencing_Guide_Final.docx
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.