 |
winbareos_without_config.PNG (81,480 bytes) |
|
|
Found out: Configs now at c:\ProgramData\Bareos. If there are existing configs while installer runs, new configs are stored as *.new (e.g. bareos-fd.conf.new). Hence software doesn't work, if again installed after an uninstall with wrong configuration. This makes user thing there is a bug despite having entered all config data correctly during installation. Solution should be: - rename old config to *old and install new config properly OR - ask user to confirm to overwrite existing config |
|
|
The new installer (-8.1) now creates shortcuts in the startmenu for each config file. Also, if config files exist, they are moved to *.old and the new ones are installed in the right path so that they are used. When doing this, the user is informed that the file was moved to *.old. |
|
|
Please give feedback |
|
|
with 8.1 even worse: there are no config files at all written to c:\ProgramData\Bareos - directory is empty. Links in task menu are present. |
|
|
Problem seems to be related to old bacula installation on that system. This does not seem to work. Make sure to first uninstall bacula before actually installing bareos. |
- Anonymous
