> The fact that sometimes the permissions
> of a directory get lost during restore and
> you "get back" the NT defaults (rights
> inherited from parent dir), seems to be a
> bug in ADSM.

Are you doing "Restore by directory tree" or
"Restore by file specification" from the GUI?
Or are you using "Restore subdirectory branch"
or the command line interface?

> We did some tests and got the result that:
> - ADSM is able to restore directory
>   permissions sometimes

"Restore by directory tree" and "Restore by file
specification" restore files only, not directories.
Instead, directories will be recreated with the NT
defaults, as you've observed. "Restore subdirectory
branch" and a command line restore will actually
restore the directories, causing the rights to be
put back.

> - The permissions of all files get restored
>   correct

> - ADSM fails when any user or group (that
>   had permission entries on the directory)
>   does not exist during restore time. This
>   can happen when users or groups get deleted
>   and the directory permissions don't get
>   updated (and there's really no need to do
>   so),

I tried this, but could not make it fail. The
files were restored every time. Of course,
rights for the deleted user or group were not
restored. But other permissions were restored
correctly.

>   or when you restore to another machine
>   that is a member of the same domain but has
>   different local groups (e.g.
>   server\administrators is different from
>   machine to machine).

I'm not too sure about this specific scenario. I
did try to restore to a different machine, with
not problems.

I did all my testing with client version 2.1.0.6.

Andy Raibeck
ADSM Level 2 Support