This was posted by one of my co-workers on another forum, but no reply was
given. So I'm turing to you:


Has anyone seen bizarre behavior with ARCServe in which trustee assignments
are created that weren't there originally. I have a few servers I replaced
that had the following TAs before:

vol1:users\Staff\User 1 -- TA (-RWCEMF-) for User 1
vol1:users\Staff\User 1 -- TA for User 2
....etc.

================

Following the restore, it looks like this

vol1:users\Staff\User 1 -- TA for User 1
vol1:users\Staff\User 1\Word Documents -- TA [-RWCEMF-] for User 2

vol1:users\Staff\User 2 -- TA for User 2
vol1:users\Staff\User 1\Word Documents -- TA for User 3

================

Basically, it took all "Word Documents" folders and gave the next user
(alphabetically in the OU) [-RWCEMF-] rights to it. I checked to make sure
it wasn't actually the next user's documents and it doesn't appear to be.

It did it with other directories as well, basically anywhere explicit TAs
are involved.

Environment
NetWare 6.5 SP3
ARCServe 9.01
Two of the servers have eDir 8.7.3.6 (since withdrawn and I haven't checked
the third), but didn't see this issue listed in the TID.


========================

Questions:
1. Anybody seen this, and if so, how did you deal with it?

2. Is there a quick way to remove all explicit TAs from a directory tree.
I'd like to remove everything from vol1:users\staff and then re-create them
via Homes. I tried using "rights" from the command-line, but it looks like
it just assigns rights and can't operate recursively down through the
directory structure.