OSD Script Section
Hi All
Just wondering if there is a way that you can supress the CMD windows that pop up when they run an application that has a script running in the <SCRIPTBODY> section of the OSD.
I have changed the script into VB format as I know you can supress the boxes in VB using the ,0 option, but that doesnt seem to happen if I import the VB text into the OSD. Anyone got any ideas?
Just wondering if there is a way that you can supress the CMD windows that pop up when they run an application that has a script running in the <SCRIPTBODY> section of the OSD.
I have changed the script into VB format as I know you can supress the boxes in VB using the ,0 option, but that doesnt seem to happen if I import the VB text into the OSD. Anyone got any ideas?
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
kkaminsk
14 years ago
Have you tried the <HREF> method? If the command line isn't silent then you'll have to make it hidden using VBS or CMDOW.EXE. Problem with CMDOW.EXE is some antivirus software doesn't like that application and considers it malware.
Posted by:
earthworm jim
14 years ago
Yeah, I have tried the HREF method and pointing it to a VB file on a shared drive, but the problem with that is if the user does not have access to the shared drive the app wont launch as it cant find the file. I need it to carry on launching if it cant find it.
Posted by:
kkaminsk
14 years ago
I know every example of HREF I have seen uses a file up on the network drive but I'm 99.999% confident that you could place the script inside the sequence and launch it from there. The key is that I haven't tested that but it should work just fine as long as the PROTECT flag is TRUE. If PROTECT is FALSE then there might be an issue.
If you still want to launch the script from a network drive but have it fail gracefully you could set WAIT to FALSE but then App-V doesn't wait for the script to complete. You could use SUCCESSRESULT="1" or something to that extent but then when the script runs successfully it could potentially fail. What I would test is to see if you set SUCCESSRESULT to a non 0 exit code will zero still be a success. Also if you are interested in using SUCCESSRESULT there is ABORTRESULT to set a failure exit code so you could set 0 to be a failure code. The documentation is a bit sketchy with these parameters but maybe they can help you.
If you still want to launch the script from a network drive but have it fail gracefully you could set WAIT to FALSE but then App-V doesn't wait for the script to complete. You could use SUCCESSRESULT="1" or something to that extent but then when the script runs successfully it could potentially fail. What I would test is to see if you set SUCCESSRESULT to a non 0 exit code will zero still be a success. Also if you are interested in using SUCCESSRESULT there is ABORTRESULT to set a failure exit code so you could set 0 to be a failure code. The documentation is a bit sketchy with these parameters but maybe they can help you.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.