Installation Wrapper [vbscript] with Reboot Timeout for Software Delivery
Some time back I published a wrapper script [vbscript and wise script] that will install the application with EXIT CODE as part of Software Delivery.
I saw posts on Connect asking for installer wrapper that will install the application and shows a completion message box to the user with specified TIMEOUT [60 mins typically]. Recently there was a request for SYSTEM REBOOT TIMEOUT message.
Keeping in all the requirements in mind, i have created the following script which will
1. Check for the source executable file [SETUP.MSI] in the source folder
2. Executes the application with specified commandline switches [/QB,/QB!, /QN,/quiet,/passive,/noreboot]
3. At the end of the installation, check for the application install return code [Exit Code]
4. Upon successful install, wrtites the result to the EVENT LOG and displays a message box [install successful and requires a reboot] to the user with 60 minutes TIMEOUT
5. Displays a message with REBOOT TIMEOUT of 60 seconds [which will force the system reboot after 60 sceconds]
So the first message box after the install will have 60 mins of timeout and reboot message box will have 60 seconds timeout. You can change the timeout according to your convenient
Feel free to edit the script according to your requirement.
Thanks,
Eshwar.
Comments 6 Comments • Jump to latest comment
You have filled a big gap, and frequently asked request in Software Delivery functionality.
Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.
You are welcome Jim!
I think these issues will not occur if we follow a STANDARD, especially in Software Delicery. I mean ...
1. Let us decide what Altiris should do
2. Let us decode what script/wrapper should do
In my openion, we should use Altiris to Create collection and deploy software to the colletion.
For Prerequisite checks, displaying a TIMEOUT message box to the user before and after install, sending EXIT CODES, we should use wrappers/scripts.
One has to decide on System Reboot, depending upon the Company/Client requirement. In our case we handle the System Reboot with Altiris. This may not be mandatory in all the scenarios.
If we standardise the wrapper/script Template so that we can ease some load on Altiris and thus smothenning the Software Delivery.
Thanks,
Eshwar
Thanks, Eshwar
Thank you for deleting all SPAM posts
Thanks, Eshwar
Good job Eshwar. Keep it up.
Cheers,
Tillu
Cheers,
Tillu
Good One
Wiseuser
Altiris Certified Professional
cool script. thanks
Would you like to reply?
Login or Register to post your comment.