I am trying to install a batch file through active directory and group policy. The batch file installs DM Hummingbird document management software.

Here is the file. It is an Installshield silent install:

"\\bcscnet.ca\dfs\DIST\apps\CLIENT\Hummingbird\DM Client 5.1.0.5\setup.exe" dp="\\bcscnet.ca\dfs\DIST\apps\CLIENT\Hummingbird\DM Client 5.1.0.5\Deployment\PilotStaff\PilotStaff.ini"

A bit of an ugly monster but it does install the necessary components for active integration using Microsoft Office and Lotus Notes.

This file takes about 2-3 minutes to complete. When it is done, it pops up a window saying that the user must click the FINISH button to restart the computer before the integration takes place.

I was going to place this simple batch file that I call "pilot.bat' into an msi wrapper program using the Windows Wrapper Installer Wizard - a handy little gem for batch file etc. deployments.

When I do this and tell the resulting msi to reboot - it does not. It seems to just get to the window with the FINISH button and stop.

I can get the batch file to run but not reboot - it seems to require intervention to click that FINISH button.

Can anyone suggest a way to deploy this batch file as an msi through active directory and group policy - "and reboot the computer".

Thanks again

John Falloon
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
How about calling an external executable (or calling an executable included in your setup)at the end of the installation? There are a lot of commandline utilities available te reboot the workstation. (e.g. shutdown.exe)
What do u use to deploy the software? It could be a good idea to let the software used to deploy the package reboot the system for you. SMS 2003 has an option to let SMS reboot the client at the end of a software installation.
Answered 12/14/2005 by: neo2000
Purple Belt

Please log in to comment
0
You are using an MSI to deploy a batch file that launches a setup.exe?

Skip the batchfile and just use a custom action in the MSI to launch the setup.exe. Your problem doesn't appear to be in the batchfile but in the setup.exe. You need to find out if it has a switch for NOREBOOT or else repackage it.
Answered 12/15/2005 by: xythex
Orange Senior Belt

Please log in to comment
0
Bit late :)
Edit the ini file and add the values
SkipFinishDLG=Y
AutoReboot=N
Answered 11/16/2011 by: ditch_nz
Purple Belt

Please log in to comment
0
are you making the computer reboot after the installation? if so, have you considered that the user could be working some documents and have to save them?

if you make a hard reboot, think about your popularity, which will be very low ;-)
Answered 11/17/2011 by: kardock
Second Degree Green Belt

Please log in to comment
0
@Ditch_nz - nothing like replying to a post that is SIX YEARS OLD! [8D]
Answered 11/17/2011 by: bearden3
Purple Belt

Please log in to comment
0
oh man, i missed that.

i think 6 years is a new record :)
Answered 11/17/2011 by: kardock
Second Degree Green Belt

Please log in to comment
Answer this question or Comment on this question for clarity