Amanda 2.5.1p1 Windows client released

[paddy]

Amanda 2.5.1p1 packaged windows client is available for download at [URL="http://www.zmanda.com/downloads.html"]Zmanda downloads [/URL]page.

Please take a look at the [URL="http://wiki.zmanda.com/index.php/Windows_client"]documentation for the Windows client[/URL] package at the Amanda wiki.

If you have questions regarding Windows client, please post them in [URL="http://forums.zmanda.com"]Amanda forums[/URL].

Thanks,
Paddy

[KikoAlbiol]

Seems that there is a mismatch between diferent national windows versions,

In spanish these changes are required

Administrators->Administradores
Backup Operators->Operadores de backup

I don't know if there is a mapping in the register or via system function to know the mapping for the other versions

[paddy]

Hi KikoAlbiol,

We have not tested community client on languages other than English (I should say, US english).

Any help with spanish would be useful. When you changed ownership of files and directories to "Administradores" and "Operadores de backup", did the Windows client work?

Thanks,
Paddy

[KikoAlbiol]

Ok, I tried to create the acounts for Administrator, an Backup Operators, the system lets me to do the changes but the installer does not work...

Could you send me a copy of the script that creates users and passwords to check groups ad users and I'll try to match to Spanish?

[KikoAlbiol]

Please see:

[url]http://www.microsoft.com/technet/scriptcenter/resources/qanda/jul05/hey0722.mspx[/url]

BV Scripting

There is a discussion about administrators account. As soon as I can get the information about Backup Operators I'll send you

[KikoAlbiol]

[url]http://support.microsoft.com/kb/243330[/url]

[paddy]

Good stuff. Take a look at two files

/var/lib/amanda/postinstall.sh
/var/lib/amanda/manifest

postinstall.sh uses the file manifest to check for ownership and groups. There are two ways to do this

1. We could create different manifest for different languages
2. use chgrp/chown to use security ids instead of user names/group names.

What do you think?

Paddy

[KikoAlbiol]

First I'dont know veri well how installers works so may be my opinion can not be used in this enviroment.

;/var/lib/amanda/postinstall.sh
;/var/lib/amanda/manifest

;postinstall.sh uses the file manifest to check for ownership and groups. There ;are two ways to do this
;1. We could create different manifest for different languages
Now there are a little coupling between postinstall.sh an manifest...

I think postinstall.sh sould include several variables such as:

ADMINISTRATOR="Administrator"
GADMINISTRATOR="Administrators"
,....

You should think that amanda is an enterprise program and in these enviroment these accounts can be changed for security porpouse.

So you can replace the file manifest using sed and 'magic quotes'

/usr/share dir 775 %ADMINISTRATOR% %GADMINISTRATOR%

This shoud solve the problem by having only a small 'variable context' you can select at the begining.

At this point look at the script postinstall.sh and you'll find references to standard groups (Backup Operators)

;2. use chgrp/chown to use security ids instead of user names/group names.
;

Security IDS are also not fixed, The only thing fixed is the pre and post, as you can read from microsoft, and I'don know how to access to this information without using VB (may be this will be the 'final' solution).

In a non VB solution favorite installation script should:

1.- Ask for language (initial gess).
2.- Get then an initial user/group (simple installation)
3.- Ask for changes (advanced instalation)
4.- Finish as you do now

;What do you think?
;
;Paddy

[KikoAlbiol]

First sorry if my opinos goes beyond the scope of an installer, as UNIX guy, I'dont know very well how windows installers works, so may be my opinion can not be used in this enviroment.

;/var/lib/amanda/postinstall.sh
;/var/lib/amanda/manifest

;postinstall.sh uses the file manifest to check for ownership and groups. There ;are two ways to do this
;1. We could create different manifest for different languages

Now for this let me tell you that there is a little coupling between postinstall.sh an manifest... (Backup Operator is refered in postinstall.sh script)

I think postinstall.sh sould include several variables such as:

ADMINISTRATOR="Administrator"
GADMINISTRATOR="Administrators"
,....

You should think that amanda is an enterprise program and in these enviroment these accounts can be changed for security porpouse.

So you can replace the file manifest using sed and 'magic quotes'

/usr/share dir 775 %ADMINISTRATOR% %GADMINISTRATOR%

This shoud solve the problem by having only a small 'variable context' you can select at the begining.

(remind the 'Backup Operator' in bash script)

;2. use chgrp/chown to use security ids instead of user names/group names.
;

Security IDS are also not fixed, The only thing fixed is the pre and post, as you can read from microsoft, and I'don know how to access to this information without using VB (may be this will be the 'final' solution).

In a non VB solution favorite installation script should:

1.- Ask for language (initial gess).
2.- Get then an initial user/group (simple installation)
3.- Ask for changes (advanced instalation)
4.- Finish as you do now

;What do you think?
;
;Paddy

[paddy]

Hi KikoAlbiol,

If I make the following changes

Administrator -> Administradores
Backup Operators->Operadores de backup

and build Windows client for testing, will you be able to try it with Windows spanish version?

Thanks,
Paddy