|
 auto bacula install?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Matt wrote:
I am trying to implement bacula in an office with up to 30 windows
clients connecting to a linux server. The idea is to have the user
install the file daemon themselves. However the win32 package on
bacula.org requires the user to edit the config files themselves. The
users in this office are not computer savvy so it would be nice to cut
that part out. Any thoughts
Well, you could drop the config files onto the user's PCs via the
network, then run the Bacula installer in silent mode (checkout the /S
switch). Alternatively, you can build your own installer using the .NSI
files and NSIS (http://nsis.sf.net).
The biggest problem is that the config files are really custom for every
installation and while a discovery and config deployment system within
the director (where clients would for example just get installed without
any data and then use mdns or whatever to find the director and their
settings) would be very cool, it is also quite far away from what Bacula
is actually supposed to do: Taking backups.
The installer could also be changed to parse a specific config file (put
both in the same directory, run the installer and it does everything
according to its 'script').... it's just a matter of finding somebody
able to do so and defining the 'best' way to do it. (Just throwing ideas
around here, I'm no coder and not savvy enough to actually build them.)
Greetings,
Michel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
iD8DBQFGeBUm2Vs+MkscAyURAtoCAJ0T23YTFgfkPYtq5m8WrdRexPzDXwCfZ/Zt
khurHTu6Wt7WW8f0LfRo4vg=
=ULCM
-----END PGP SIGNATURE-----
|
