Deployment Solution

 View Only

Installation Wrapper [vbscript] with Reboot Timeout for Software Delivery 

Jul 16, 2009 05:46 PM

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

imagebrowser image

5. Displays a message with REBOOT TIMEOUT of 60 seconds [which will force the system reboot after 60 sceconds]

imagebrowser image

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. 

Statistics
0 Favorited
1 Views
1 Files
0 Shares
0 Downloads
Attachment(s)
zip file
Install_Wrapper_With_Reboot_TimeOut.zip   1 KB   1 version
Uploaded - Feb 25, 2020

Tags and Keywords

Comments

Aug 13, 2013 06:35 AM

well done Eshwa,

Aug 13, 2013 06:22 AM

Though we implement this via SCCM, this is a nice script to have.

Mar 27, 2013 03:57 AM

cool script. thanks

Oct 26, 2009 02:30 PM

Good One

Jul 21, 2009 10:18 AM

Good job Eshwar. Keep it up.


Cheers,
Tillu

Jul 20, 2009 04:24 AM

Thank you for deleting all SPAM posts

Jul 17, 2009 05:17 AM

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

Jul 16, 2009 06:13 PM

You have filled a big gap, and frequently asked request in Software Delivery functionality.

Related Entries and Links

No Related Resource entered.