On Wed, 27 May 2009 23:55:47 +0200, Jayson Broughton
wrote:
> Surely there is an easier way to automate installs than to create
> an NSIS file from scratch.
What I eventually did:
- got Sysinternals' (now Microsoft) psexec utility from
http://download.sysinternals.com/Files/PsTools.zip
- co
, May 28, 2009 12:26 AM
To: Jayson Broughton; Bacula-users@lists.sourceforge.net
Subject: RE: [Bacula-users] automating windows client installs
>
> I have also tried bacula-3.0.1.exe /Silent For a silent install, and
it does
> work, but the config files are @computer_name@ instead
>
> I have also tried bacula-3.0.1.exe /Silent For a silent install, and
it does
> work, but the config files are @computer_name@ instead of the actual
computer
> name displayed during a manual install of the software. Besides
having to
> write a WMI script to grab the computer name, and a SED
So I have looked through the list archives on automating windows installs,
and the only one I found was written back in 2006 with NSIS. I have spent
the good portion of 2 days going through the bacula source with NSIS
compiler, and after close to 3000 lines of code in at least 3 files, Im
baffled.
