-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Foo wrote:
> Hi,
> 
> I'm looking at a large rollout, and estimate around 16 hours of non-stop  
> clicking for the Windows side of things (I've got the Linux side covered).
> Is it possible to automate the Windows installer with arguments that fill  
> in the various fields such as hostnames, IP addresses, passwords etc.?

If does have a /S switch (must be capital) that should make it
auto-install the FD with the default settings. You'll have to fill in
the config files for yourself, or somehow replace them further down in
your script.

> If not, is it possible to take apart the installer and write new scripts  
> doing this and how much work would this be? It could be a generic  
> installer choosing from a plaintext file with a list of fixed hostnames,  
> IP addresses and passwords, or a unique installer per server, as long as  
> both can simply be copied and run silently.

The installer uses NSIS (http://nsis.sf.net) and its source files are
included with the Bacula source, so no need to take it apart. As to how
much work it'll be to implement the mechanisms you describe, I
unfortunately don't know.

Greetings,
       Michel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)

iEYEARECAAYFAkl99PYACgkQ2Vs+MkscAyVn+QCglmU6rntNP+kukJ+rESUH1fEP
RE0AmQGtM44k9jbJC3oHaUCaGECMbqae
=Hrb9
-----END PGP SIGNATURE-----


------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users