2007 1:43 AM
To: bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] Win2k Automated Upgrade from 1.3x to 2.0
I've been looking for a way to automate the setup on xp workstations as
well. After some fifteen tries to install and uninstall bacula in
various ways i've decided
Thanks, Michel
that explains why the message is shown regardless of the /S switch.
It's sad, though, that this issue was overlooked, as it is a real bug
for those, who use bacula in large windows based environments.
Mantas.
Michel Meyers wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mantas M. wrote:
> I've been looking for a way to automate the setup on xp workstations as
> well. After some fifteen tries to install and uninstall bacula in
> various ways i've decided to go the with the merest:
>
> 1. stop the service
> 2. replace t
I've been looking for a way to automate the setup on xp workstations as
well. After some fifteen tries to install and uninstall bacula in
various ways i've decided to go the with the merest:
1. stop the service
2. replace the binary files
3. start the service again.
as far as i've tested this,
Vladimir Doisan wrote:
> I think there is a bit of work needed to get the update 1.38 to 2.0
> happen automatically.
> If I understand correctly, you stop service, copy files, start service.
> Which would work just perfectly for upgrades 1.38.x -> 1.38.y
> and with slight path modifications it will
/install and puts it
into the service command line.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Arno
Lehmann
Sent: Thursday, January 25, 2007 12:50 AM
To: 'bacula-users'
Subject: Re: [Bacula-users] Win2k Automated Upgrade from 1.3x to 2.0
He
m: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Arno
> Lehmann
> Sent: Thursday, January 25, 2007 12:14 AM
> To: 'bacula-users'
> Subject: Re: [Bacula-users] Win2k Automated Upgrade from 1.3x to 2.0
>
> Hello,
>
> On 1/25/2007 8:54 AM, Robert N
ge-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Arno
Lehmann
Sent: Thursday, January 25, 2007 12:14 AM
To: 'bacula-users'
Subject: Re: [Bacula-users] Win2k Automated Upgrade from 1.3x to 2.0
Hello,
On 1/25/2007 8:54 AM, Robert Nelson wrote:
> Don't use sc.exe,
use my installation was broken, though.
Arno
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Vladimir
> Doisan
> Sent: Wednesday, January 24, 2007 2:53 PM
> To: Arno Lehmann
> Cc: bacula-users
> Subject: Re: [Bacula-users] Win2k Auto
al Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Vladimir
Doisan
Sent: Wednesday, January 24, 2007 2:53 PM
To: Arno Lehmann
Cc: bacula-users
Subject: Re: [Bacula-users] Win2k Automated Upgrade from 1.3x to 2.0
Very cool!
I am crazy enough to start working on it today unle
Very cool!
I am crazy enough to start working on it today unless my wify shoots me
if I spend too much time working :)
Since you told me the most important command "sc", the script is ez. If
I will not have any emergencies at work, I will have testing done tomorrow.
Thanks a lot!
Arno Lehmann wro
Hello,
On 1/24/2007 10:38 PM, Vladimir Doisan wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I think there is a bit of work needed to get the update 1.38 to 2.0
> happen automatically.
> If I understand correctly, you stop service, copy files, start service.
> Which would work just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I think there is a bit of work needed to get the update 1.38 to 2.0
happen automatically.
If I understand correctly, you stop service, copy files, start service.
Which would work just perfectly for upgrades 1.38.x -> 1.38.y
and with slight path modific
Michel, that's the one I saw, I will try test deployment.
thanks!
Michel Meyers wrote:
> Vladimir Doisan wrote:
>>> Oh, so the install directory would still be c:\bacula (whatever the 1.3x
>>> was)?
>
> No, the new installer unfortunately uses the Program Files directory for
> it (but I think it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vladimir Doisan wrote:
> Oh, so the install directory would still be c:\bacula (whatever the 1.3x
> was)?
No, the new installer unfortunately uses the Program Files directory for
it (but I think it's the same for all machines, unless you have multiple
Oh, so the install directory would still be c:\bacula (whatever the 1.3x
was)?
Maybe I was looking at the different script, or mixed it up with
something else... Could you give me the link?
Thanks!
Michel Meyers wrote:
> Vladimir Doisan wrote:
>>> Does anyone have any scripts to push updates to cl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vladimir Doisan wrote:
> Does anyone have any scripts to push updates to clients on Windows 2000
> network?
> OR alternatively,
> does Bacula-2.0.1.exe has any command line switches to help to automate
> deployment?
>
> If, nothing exists, I will write
Does anyone have any scripts to push updates to clients on Windows 2000
network?
OR alternatively,
does Bacula-2.0.1.exe has any command line switches to help to automate
deployment?
If, nothing exists, I will write batch or bash script to do it.
BTW - I did see the script to update existing 1.3x
18 matches
Mail list logo
